just stop the replication session, umount the fs from server_2, mount it on vdm01 and restart the replication again

hint: in the GUI changing umount/mount means deleting the old mount and creating a new mount

and yes, it will restart using a diferential copy and its non-disruptive for the source fs

vdm and data file system replication are independent replications but of course on a vdm failover the CIFS servers in the vdm expect the data file systems to also be mounted on that vdm

Hi Ral:

Thanks for your reply.  But when you go to the target/destination side and when I create the mount point, it will not allow me to choose the replicated datamover (does not appear as an option).  It only allows you to choose server_2 or any other active data mover.  Would you have any other ideas?

My plan was to

1. stop replication

2. delete the replication from source and destination (I hope this leaves the replicated filesystem at the destination)

3. create new replication specifying parameters, now with VDM and to use an exisitng filesystem (hopefully can just choose the one that is there)

4. start replication

I'm hoping this does not require a full sync.

dont delete the data fs replication - that will cause a new full sync

I guess what you are seeing is because the dst vdm isnt mounted/loaded. I would try stopping the vdm replication

are you using the GUI or CLI ?

you shouldnt have to create the mountpoint (directory) - if its there on the src vdm its replicated to the dst vdm

Rainer

I think you are right, I'm not seeing the VDM in the destination because it is unloaded.  I stopped the VDM replication but it is still unloaded.

I'm using the GUI but could enter the CLI.  Thanks for your suggestions!

Any other ideas?  thanks

I would see what the manual says - maybe try the CLI route - sometimes the GUI doesnt allow you things that are possible

or maybe try deleting the vdm replication and setting it up again - vdms are so small they replicate pretty fast

Ok, here is the procedure.

1. Stop the VDM01 replication

2. Stop the fileystem replication

3. CLI to disaster recovery site and

     a. unmount the filesystem with                 server_umount server_2 -p /Public

     b. mount the filesystem to the VDM with   server_mount VDM01 -o ro Public /Public

4. Check in Celerra Manager that the Public filesystem is not associated with VDM01 and not server_2 under Filesystems

5. Restart replication for VDM01 and Public filesystem

ral67, you were right, this could be accomplished in command line but not gui.

Hey

Does stopping and starting the replication needs to be done on Source VNX?