If you are using SAN replication, why not replicate the OS disks as well? have the server boot from the SAN disks. In DR, just boot the server from the SAN LUNs, it then becomes your normal server.
If you currently boot off the local disks it would take a bit of setting up and may not be worth the effort for the gain. That's the way we have it for a few of our clients. The DR server in normal mode boots off the local disks, with just the OS and EM agents for hardware monitoring. The HBAs are disabled in the BIOS until needed. The only other thing we have to do is change the IP settings. Full DR is invoked every Easter for testing. Tony On 7 Aug 2014 19:58, "Michael Leone" <oozerd...@gmail.com> wrote: > On Thu, Aug 7, 2014 at 2:45 PM, Kennedy, Jim > <kennedy...@elyriaschools.org> wrote: > > Two step it. > > > > 1) Your backup system handles the NTFS perms during the restore. > > There will be no restore, as there is no backup. As I said, the > replicated LUN will be mounted at the DR site on a replacement server. > (well, I mean, yes, we backup. But there's no way we am doing a 2TB+ > restored of 3M+ files. Not in any reasonable amount of time, anyway. > Hence the DR hotsite, and the replicated LUNs of the SAN) > > > > 2) Grab the sharenames and share perms from lanmanserver\shares. > > > > http://support.microsoft.com/kb/125996 > > > > After the registry import you can manually edit drive letters if they > changes. Done it this way several times. > > I will look into it. The drive letters won't change; we'll just change > the drive letter of the mounted volume, if we have to (and we > shouldn't need to) > > > ================================================ > Did you know you can also post and find answers on PowerShell in the > forums? > http://www.myitforum.com/forums/default.asp?catApp=1 > > ================================================ Did you know you can also post and find answers on PowerShell in the forums? http://www.myitforum.com/forums/default.asp?catApp=1
