What you are describing sounds like a complicated way to do DFS with replication. If you went that route up front and had the primary server as first choice in the namespace a fail over would be almost instantaneous except for open documents and no intervention required.
Or am I missing something. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Leone Sent: Thursday, August 7, 2014 3:24 PM To: [email protected] Subject: Re: [NTSysADM] Fwd: Saving share permissions, and re-applying them On Thu, Aug 7, 2014 at 3:13 PM, Charles F Sullivan <[email protected]> wrote: > I have always just exported this Reg key: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Shar > es Of course you could easily script the export using reg.exe in a > batch file. > > As long as the file server at both ends is Windows, as opposed to say > a NAS or SAMBA Server, I don't think it should matter what version of > Windows the source and target are. No, they will be Windows servers. A 1 node cluster, actually, as the DR for the 2 node production cluster. > This is awfully simple, but it has always worked for me. Just > remember to restart the Server service after you import the Reg file. > > In my DR testing I don't have to do anything like this, to be honest, > since the backup software includes the System State. True, but we won't be running restores. We have 2 sites, and SAN replication set up between them So the data on disk exists at the other site already. We would need to fire up the Windows boxes there; rename them to have the production server name; mount the SAN volume as disk drive. Import the share settings. And no users should be the wiser. They still see a server with the same name; the share permissions are the same as before; the NTFS folder permissions are already there on the disk. If you can afford it, this is the way to do DR. :-) No long wait for restores. I have 1 file server that has something like 4TB of data and 3M+ files (user folders and departmental shares). That would take forever to restore - open, write, close, verify all those small files ...
