EMC Celerra DR testing

create new VDM

No it doesn't have to be the same CIFS server, ideally we'd want a completely new one. I've already tried this. On the DR side create a new CIFS server, join it to AD. Create a R/O or a R/W checkpoint (snapshot) but as soon as you go to mount it, it can't because vdm1 isn't loaded, or it can't see it becasue the replicated CIFS file system isn't associated with the new CIFS server.

does it have to be the same CIFS server, create a dummy one, create read/write snapshot and mount it to this CIFS server and verify data is there.

or create CIFS server on physical datamover, not virtual one

you are just creating a share:

server_export server_2 -Protocol cifs -name myshare /root_vdm_1/ckpt_readonly

you can see file system mount point using server_mount server_2

Even when I create a new vdm (bcpvdm) and associate a new CIFS server to this bcpvdm, you still can't create a share off the checkpoint because it thinks it has no associated file systems. The key is with the checkpoint because when you view it, it's data mover is vdm1(R/O) and the mount is data mover vdm1. See below screen shots.

ok - not sure how to do that. What does exporting do? Is this like mounting or associating the share?

Ok, i've created a new CIFS server on physical datamover server_2

Created a checkpoint of the replicated CIFS file system, using datamover server_2

from this point i'm not sure what to do because if you go to Replicas, Mounts the checkpoint /bcptest is associated with datamover vdm1. This is because when you create the checkpoint even though you specify server_2 at the top, it knows it's associated with vdm1 - see pic below (Data Movers:)

The other issue is, now i've got the checkpoint and it's mounted you can't create a share from this to the new CIFS server because it doesn't see that the datamover has any associated CIFS servers - see below

physical datamover can see that checkpoint, just need to export it ..use the command line.

Doesn't work.

[nasadmin@celerra ~]$ server_export server_2 -P cifs -name bcpshare /root_vdm_7/bcptest

server_2 :

Error 2224: server_2 : invalid operation

When creating my own vdm (bcpvdm) and doing the same, I'm getting the following

[nasadmin@celerra ~]$ server_export bcpvdm -P cifs -name bcpshare /root_vdm_7/bcptest

bcpvdm :

Error 22: bcpvdm : Invalid argument

Share error: Path does not exist

Server mount points are below

[nasadmin@celerra~]$ server_mount server_2

server_2 :

root_fs_2 on / uxfs,perm,rw

root_fs_vdm_vdm1_1 on /root_vdm_7/.etc uxfs,perm,ro

root_rep_ckpt_26_9627_1 on /root_rep_ckpt_26_9627_1 ckpt,perm,ro

root_rep_ckpt_26_9627_2 on /root_rep_ckpt_26_9627_2 ckpt,perm,ro

CIFS on /root_vdm_7/CIFS uxfs,perm,ro,triggerlevel=512,accesspolicy=NATIVE,nolock

root_rep_ckpt_25_9797_1 on /root_vdm_7/root_rep_ckpt_25_9797_1 ckpt,perm,ro,accesspolicy=NATIVE,nolock

root_rep_ckpt_25_9797_2 on /root_vdm_7/root_rep_ckpt_25_9797_2 ckpt,perm,ro,accesspolicy=NATIVE,nolock

root_fs_common on /.etc_common uxfs,perm,ro

root_fs_vdm_bcpvdm on /root_vdm_10/.etc uxfs,perm,rw

bcptest on /root_vdm_7/bcptest ckpt,perm,ro

ah..forgot one little detail, you have to do export it using the MMC, see Gustavo's post

Export a writable checkpoint of a replicated file system on the dest side?

@dynomox - getting closer, jumped on to give your solution a try. I can create the share now using MMC snapin to computer management for the temp CIFS server on the DR side, but when I go to map to it it says Access is Denied. Not sure why, I tried mapping as the domain admin which has full access on the prod side and even gave full share permissions with this account, still Access is Denied.

I'll play around with this more tomorrow, hopefully i've just missed a small detail.

The mount point for the share creation was C:\root_vdm_7\bcptest

Still can't get this working. CIFS server is created, checkpoint is created. When mapping to \\cifsserver\c$ I can browse teh root_vdm_7 folder, but I can't access the bcptest checkpoint folder. The permissions on root_vdm_7 only has UNIX GID=0x1 assigned to it.

I tried doing this again with a new VDM, but you need to associate a file system with this otherwise when you browse the \\cifsserver\c$ it fails to load any folders because it thinks the disks are missing.

Starting to think ACLs aren't being replicated correctly or there is a small detail which i've missed out when creating the new CIFS server.

I've checked the Local Administrator groups for the CIFS server through computer management and Domain Admins is listed so i'm not sure what else I can try. Obviously other people have this working after reading Gustavo's post in that link.

if you have access to bcptest on source you should have access to bptest on target, directory ACLs get replicated as they reside on the file system.