This post is more than 5 years old
2 Posts
0
766
August 27th, 2014 11:00
Protecting a standalone windows file server
Hello,
We need to start replicating our windows 2008 file server to our DR site.
Both production and DR have RP 4.0.1 clusters connected to VNX 5300
arrays. Our production file server uses an iscsi lun from the array to
hold user data. I have not been able to find good documentation on a
non-clustered windows file server so wanted to make sure of a few
questions that I can not find answers to.
1) can the lun in the dr site be in the storage group for the dr file
server and seen by the dr server, i heard but can not confirm that the lun
in the dr site should be in the recoverpoint storage group until needed
then removed from that storage group and placed in the dr file server
storage group
2) will share and acl info be replicated also or should i plan on fixing
this on the server after a failover
justpaul1
25 Posts
1
August 27th, 2014 11:00
From your questions, it is my assumption that you are using two different file servers and only the drive with the file share (not the operating system) is replicated. If that is not the case, please let me know.
1. To save steps at the time of DR, you can map the lun in the DR site to the SG. However, if you try to initialize/online the disk while the RecoverPoint target copy is not in image access mode, you will get a failure in Windows (and possibly an alert from RecoverPoint regarding the splitter blocking outside writes to the device). To access the replicated storage from the fileserver in the DR site, you would need to first enable image access mode in RecoverPoint for that CG, then online the disk in Windows. Once you are done testing/recovering, you should then offline the disk in Windows (to stop the operating system from attempting to write to it) and then disable image access in RecoverPoint.
2. RecoverPoint is a block-based replication product, which means it has no idea what is happening at the file level (NTFS acl, etc) and file and folder-level permissions would be replicated. However, your share creation and share permissions would need to be setup manually on your DR file server. Again, you could do that at the time of failover/testing recovery, or you could do it ahead of time by mounting the drive using the steps above, creating the share/setting the share permissions, and then dismounting the drive using the steps above. If you do create the share ahead of time, you would need to restart the server service after putting the disk online for the share to show up.
NCB_MIke
2 Posts
0
August 28th, 2014 03:00
Thank you for the information.