Yes, that would work - but again, it's an additional level of complexity. You could do it. I could do it. Most of the admins for my clients could not do it properly, except by pure luck.
Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Ken Schaefer [mailto:[email protected]] Sent: Thursday, February 02, 2012 9:55 PM To: NT System Admin Issues Subject: RE: Microsoft VM - 5 ways of backing up? How would this impact SQL Servers - they tend to be independent of each other. For those that are connected (replication/mirroring/log ship) you could restore the master, then manually set up the replication in the event of a real disaster (everything's gone) Cheers Ken -----Original Message----- From: Michael B. Smith [mailto:[email protected]] Sent: Friday, 3 February 2012 8:39 AM To: NT System Admin Issues Subject: RE: Microsoft VM - 5 ways of backing up? In my experience - if you HAVE an inappropriate backup, in an emergency, you will be tempted to use it. If you have more than a single DC/GC - then you are potentially a victim of this. If you have more than a single Exchange server - then you are potentially a victim of this. If you have more than a single SQL server - then you are potentially a victim of this. In Win8 - there are even more scenarios (think DHCP availability groups) that can lead to problems with this scenario. Just don't do it, is my advice. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Thursday, February 02, 2012 6:27 PM To: NT System Admin Issues Subject: Re: Microsoft VM - 5 ways of backing up? On Thu, Feb 2, 2012 at 5:05 PM, Michael B. Smith <[email protected]> wrote: > Backing up vhd's is easily doable, but DR using backed up vhd's is > scary with AD, SQL, and Exchange*. > * Can you say "USN rollback", or "SN rollback", or anything similar? > ... I knew you could. :-) That's certainly a nasty possibility... but isn't that mostly a problem with, shall we say, "inappropriate restores"? If it's an actual disaster and all the VMs have gone up in smoke, would restoring them to point-in-time be safe? I guess that wouldn't be so straight-forward in a larger org, but we're currently just one site. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
