ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual Server 2005

Recent Virtual Server 2005 posts

* CIFS and iSCSI Performance very poor
* NAT"ing with VS EE & Loopback Adapter
* Installation Problems
* restart virtual server via script
* Now that VMWare Server is free, will MS free also VS2004
* Automated Deployment Sservices ADS cannot take control of device
* When the Host is Shutdown....
* PXE boot very slow
* Virtual Server 2005 R2 and Mandriva 2006
* How can I find out what version of VS2005 R2?
* Trying to startup and Guest OS or use VSMT both yield the same err
* disable auto start on connect
* remote R2 & clipboard
* Odd VMRC Mouse Behavior
* Automated Deployment Sservices ADS cannot take control of device
* EFS encryption of VHD files for virtual Domain Controllers
* vpcSP1 saved state break after upgrading VS to R2??
* Add Virtual Machine Using existing .vmc file
* VBScript remote connect to Virtual Servers
* best practice to copy/clone a virtual machine?

Add Solution

Disaster Recovery Plan

Source: microsoft.public.virtualserver
Sent: 02/15/2006
From: Ralphdjr
Message:

I am transitioning from SBS2003 to Standard Server and will have several
physical servers in our domain. I am looking at VS to be a part of a DR plan.
I see it working something like this: I have two spare physical servers one
onsite one offsite each of these servers has a virtual server instance that
matches the production servers onsite. If one of the production servers fails
I can fire up the spare server, start the VM instance of the failed server
restore the most recent data and put it into production. In a catasrophic
disaster the offsite server could be retrieved and all server instances could
be started and updated to provide failover services.

First, does this make sense.
2nd, What would the licensing requirements look like. I have read the
December 2005 licensing paper and I am not able to determine what I would
need.
3rd, should the spare servers be DCs? or is there a better way to preserve
the domain and active directory. The offsite server would have a DSL Wan
connection to the main office.
4th Is there a whitepaper with other DR plans using VS?

--
Thanks

Post Reply | This is Spam! | Mark as Spam

Related Messages

RE: Disaster Recovery Plan

Sent: 03/29/2006
From: Mario Colon
Message:

Have you gotten any feedback on this? I am looking to do the same thing in
our environment. Any feedback is appreciated.

Mario Colon
(email address - cut out)

"Ralphdjr" wrote:

Show quoted text

> I am transitioning from SBS2003 to Standard Server and will have several
> physical servers in our domain. I am looking at VS to be a part of a DR plan.
> I see it working something like this: I have two spare physical servers one
> onsite one offsite each of these servers has a virtual server instance that
> matches the production servers onsite. If one of the production servers fails
> I can fire up the spare server, start the VM instance of the failed server
> restore the most recent data and put it into production. In a catasrophic
> disaster the offsite server could be retrieved and all server instances could
> be started and updated to provide failover services.
>
> First, does this make sense.
> 2nd, What would the licensing requirements look like. I have read the
> December 2005 licensing paper and I am not able to determine what I would
> need.
> 3rd, should the spare servers be DCs? or is there a better way to preserve
> the domain and active directory. The offsite server would have a DSL Wan
> connection to the main office.
> 4th Is there a whitepaper with other DR plans using VS?
>
>
> --
> Thanks

Re: Disaster Recovery Plan

Sent: 03/29/2006
From: "Ben Armstrong [MSFT]" <(email address - cut out)>
Message:

This is definitely a reasonable and doable strategy. Unfortunately I am
not a licensing expert - so I do not know what the stance would be there
- nor do I know of any specific documentation for this scenario.
--
Cheers,
Benjamin Armstrong
===============================
Virtual machine Program Manager

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.

Mario Colon wrote:

Show quoted text

> Have you gotten any feedback on this? I am looking to do the same thing in
> our environment. Any feedback is appreciated.
>
> Mario Colon
> (email address - cut out)
>
> "Ralphdjr" wrote:
>
>> I am transitioning from SBS2003 to Standard Server and will have several
>> physical servers in our domain. I am looking at VS to be a part of a DR plan.
>> I see it working something like this: I have two spare physical servers one
>> onsite one offsite each of these servers has a virtual server instance that
>> matches the production servers onsite. If one of the production servers fails
>> I can fire up the spare server, start the VM instance of the failed server
>> restore the most recent data and put it into production. In a catasrophic
>> disaster the offsite server could be retrieved and all server instances could
>> be started and updated to provide failover services.
>>
>> First, does this make sense.
>> 2nd, What would the licensing requirements look like. I have read the
>> December 2005 licensing paper and I am not able to determine what I would
>> need.
>> 3rd, should the spare servers be DCs? or is there a better way to preserve
>> the domain and active directory. The offsite server would have a DSL Wan
>> connection to the main office.
>> 4th Is there a whitepaper with other DR plans using VS?
>>
>>
>> --
>> Thanks

Re: Disaster Recovery Plan

Sent: 03/30/2006
From: Ralphdjr
Message:

I have opened and closed a ticket with the presales department of Microsoft,
they directed me to the virtual server technical support team and although
they attmpted to be helpful - they did not have a script to follow! and I
gave up trying to make them understand my concept. I have not been able to
reach anyone on the Virtual Server development team - they simply have not
responded to my emails.

I have aquired two new servers and I am proceeding with my plan. Based on my
research my licensing will look like this: 2 copies of Server 2003 R2 for the
host servers, 2 copies of Virtual Server 2005 R2 one for each of the servers
- That is it. The virtual machine copies of my production servers and the
server software (exchange, SQL etc.) will only be loaded into memory in the
event of a hardware or other failure of one of the production servers, which
will mean that they are not running and those licenses should cover the VM
copy that takes thier place.

I have talked extensively with the sales and licensing people in presales at
Microsoft and they just direct me to the whitepapers on the subjects - they
are not allowed to interpet the meaning. Basically what they are saying is
have your attorney talk to our attorney. It is just a load of @#$% when you
are just trying to stay compliant.

I still don't know about the host servers being DCs to preserve the domain
but that is the way I am going to set it up. It will take me a month or two
to complete the setup and testing of this at which time I will attempt to
author a whitepaper on my DR system.
--
Thanks

"Ben Armstrong [MSFT]" wrote:

Show quoted text

> This is definitely a reasonable and doable strategy. Unfortunately I am
> not a licensing expert - so I do not know what the stance would be there
> - nor do I know of any specific documentation for this scenario.
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
>
> Mario Colon wrote:
> > Have you gotten any feedback on this? I am looking to do the same thing in
> > our environment. Any feedback is appreciated.
> >
> > Mario Colon
> > (email address - cut out)
> >
> > "Ralphdjr" wrote:
> >
> >> I am transitioning from SBS2003 to Standard Server and will have several
> >> physical servers in our domain. I am looking at VS to be a part of a DR plan.
> >> I see it working something like this: I have two spare physical servers one
> >> onsite one offsite each of these servers has a virtual server instance that
> >> matches the production servers onsite. If one of the production servers fails
> >> I can fire up the spare server, start the VM instance of the failed server
> >> restore the most recent data and put it into production. In a catasrophic
> >> disaster the offsite server could be retrieved and all server instances could
> >> be started and updated to provide failover services.
> >>
> >> First, does this make sense.
> >> 2nd, What would the licensing requirements look like. I have read the
> >> December 2005 licensing paper and I am not able to determine what I would
> >> need.
> >> 3rd, should the spare servers be DCs? or is there a better way to preserve
> >> the domain and active directory. The offsite server would have a DSL Wan
> >> connection to the main office.
> >> 4th Is there a whitepaper with other DR plans using VS?
> >>
> >>
> >> --
> >> Thanks
>

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: