2011-09-21 11:03 PM
We have a setup with 2 NetApp on different sites (Production and DR site) serving Windows shares. Data is replicated from Production to DR via SnapMirror
My question is how can we automate the failover to the DR site for the Windows shares in case the Production site goes down? We were thinking of changing the DNS entries for the Production system so that it will point to the DR site. However, this will likely take some times to propagate between the different DNS servers.
Another option is to have a second login script to map to the DR system and the users will need to re-login.
Is there any alternative to these?
2011-09-22 12:53 AM
For DR solution, with SnapMirror, you can, if you have multistore license, use the vFiler-DR...
But that depend if you are in Production or in tests actualy ..
The vFiler-DR, use a vFiler inProduction, and copy all data and indentity of vFiler on DR site.
If the primary site down, you have just on command to take production on DR site.
To check that see the : https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=18219
the TR - 3462
Or you can use a Windows DFS achitecture to made a DR site in AD.
2011-09-23 12:18 AM
For DFS, just a point to check, on NetApp solution, the DFS can not be a DFS Root, just a share, in a DFS root on AD server...
However it's work fine in DFS.
2011-09-23 01:57 AM
Perhaps you can semi automate this by using dfscmd.exe commands in a batch file to create new DFS links which point to the DR site when needed? When created you would then of course need to wait for AD replication.
2011-09-29 09:35 AM
DFS would do this, but you want a simple solution just create a DNS alias for the filer and in the event of a DR situation update the DNS record with the IP address of the backup filer
2011-09-30 01:42 AM
We prefer to go for the DFS-R Architecture.
By having multiple targets on both filers and some other storage devices with priorities based on used domain-controller the user can always find a copy and all data is automatically secured for continuity.
For compliancy measures only one of the targets needs to be backed-up.