Laptop as DC for disaster recovery?

[Newell White]

We have a single-domain LAN with 2xW2k3 servers, 35 XP workstations and 5 XP
laptops accessing via VPN.
The PDC emulator also hosts SQLserver and an Access database which is
critical for all aspects of the business.
Total disaster risks we face are fire and tidal inundation.

In such event we would need to set up skeleton operation with small LAN to
handle:
(a) Diversion of manufacture and test (electronic PCB assemblies) to other
company sites
(b) Sales and customer support.
(c) Insurance claim for lost components and products.

I am considering recommending a disaster recovery strategy based on the
following:

1) Install W2k3 on a laptop, promote to 3rd DC , install SQLserver and and
database copy.
2) Fire up the laptop during business hours for replication and backing up,
take it off-site at night.
3) In event of disaster, sieze roles on laptop, buy proper server, replicate
and transfer roles to new server.

Obviously for a few days we will be dependent on a laptop with no RAID, and
MTBF of less than 2 years.

What other snags or pitfalls am I ignorant of?

Thanks,
--
Newell White

 

[Brian Spolarich]

On Jul 17, 11:04 am, Newell White
<NewellWh...@discussions.microsoft.com> wrote:
> We have a single-domain LAN with 2xW2k3 servers, 35 XP workstations and 5 XP
> laptops accessing via VPN.
> The PDC emulator also hosts SQLserver and an Access database which is
> critical for all aspects of the business.
> Total disaster risks we face are fire and tidal inundation.
>
> In such event we would need to set up skeleton operation with small LAN to
> handle:
> (a) Diversion of manufacture and test (electronic PCB assemblies) to other
> company sites
> (b) Sales and customer support.
> (c) Insurance claim for lost components and products.
>
> I am considering recommending a disaster recovery strategy based on the
> following:
>
> 1) Install W2k3 on a laptop, promote to 3rd DC , install SQLserver and and
> database copy.
> 2) Fire up the laptop during business hours for replication and backing up,
> take it off-site at night.
> 3) In event of disaster, sieze roles on laptop, buy proper server, replicate
> and transfer roles to new server.
>
> Obviously for a few days we will be dependent on a laptop with no RAID, and
> MTBF of less than 2 years.
>
> What other snags or pitfalls am I ignorant of?

I might do this in a virtualized environment versus running server
directly on a laptop. You get some flexibility that way, and can move
the virtualized server instance around at will. VMWare or the MSFT
virtual stuff both would work fine.

Given that AD relies heavily on DNS, you're going to want to make sure
that the virtualized server instance has a static IP that's registered
in DNS, that your virtualized server environment has bridged
networking, and that the virtual server does DNS, DHCP, etc.

With a little testing you should be able to add the virtual backup
system to your LAN and have it provide services as if it were a 'real'
server to test it, and then just keep it off and out of the production
config except to update its replicas. You could use File Replication
Services to keep a copy of the critical production filesystem data on
it, and use SQL replication to keep the SQL database up to date.

Given the beefiness of today's laptop hardware compared to even a few
years ago, there's nothing wrong with this approach. Moving to server-
grade hardware is simple, since you can just install a base OS on it,
install VMWare (or whatever), and copy the server virtual OS files
over to the new server to get going quickly and transparently.

 

[Greg O]

On Jul 17, 8:04 am, Newell White
<NewellWh...@discussions.microsoft.com> wrote:
> We have a single-domain LAN with 2xW2k3 servers, 35 XP workstations and 5 XP
> laptops accessing via VPN.
> The PDC emulator also hosts SQLserver and an Access database which is
> critical for all aspects of the business.
> Total disaster risks we face are fire and tidal inundation.
>
> In such event we would need to set up skeleton operation with small LAN to
> handle:
> (a) Diversion of manufacture and test (electronic PCB assemblies) to other
> company sites
> (b) Sales and customer support.
> (c) Insurance claim for lost components and products.
>
> I am considering recommending a disaster recovery strategy based on the
> following:
>
> 1) Install W2k3 on a laptop, promote to 3rd DC , install SQLserver and and
> database copy.
> 2) Fire up the laptop during business hours for replication and backing up,
> take it off-site at night.
> 3) In event of disaster, sieze roles on laptop, buy proper server, replicate
> and transfer roles to new server.
>
> Obviously for a few days we will be dependent on a laptop with no RAID, and
> MTBF of less than 2 years.
>
> What other snags or pitfalls am I ignorant of?
>
> Thanks,
> --
> Newell White

As long as you back up the system state on a DC you can recreate a new
DC quickly with that backup. I don't see why a laptop would make that
better, particularly as it would not be a suitable DC later.