On Thu, Aug 7, 2014 at 4:57 PM, Charles F Sullivan <[email protected]> wrote: > Exporting the Registry file probably would work, especially for the small > number of file servers you need to recover. I used that as my method for a > large number of file server migrations that I have done in the past. (Now > it's mostly on NetApp NAS, so we don't have that luxury.) > > I'm sure the replicated SAN works fine for a file server DR solution, but > none of the Windows servers we restore in DR testing are file servers. If > it's a SQL server, domain controller, application server, etc. it will take > more than just the data itself on a disk to do a recovery. We restore > about 40 servers, including 12 Windows, in a site 250 miles away and we have > three days to do it. > > I'm curious about the SAN replication. How far apart are the sites? Is the > replication done over Ethernet?
The sites are actually only about 1.5 miles apart. (yes, I know. No, we didn't have a choice) The other site is one of our other buildings we built a small datacenter in. We have a 10G link to it. > > We do have some apps that need to be available immediately if our data > center is down. For those servers we use vSphere Replication, but that is > over Ethernet to a site about a mile away. We use SRM between our VMware sites, with an EMC RecoverPoint keeping the 2 SANs synced.
