Re: Replicating Windows Server 2003 to create remote backup server
- From: "Anthony" <anthony.spam@xxxxxxxxxxxxxx>
- Date: Sun, 27 Aug 2006 10:05:23 +0100
Well it depends what you mean by "if something occurs". Failed hard disk?
Flood or fire? Each of those services needs a recovery plan, whether you are
large or small, running on one server or separate servers. Each one
replicates or backs up and recovers in a different way. Obviously your first
step if you have hardware failure is to repair the hardware and restore from
backup, so you are obviously thinking beyond that to some sort of
redundancy, resilience, availablity, DR. I have tried to think how to answer
your question, but it comes down to paraphrasing a google search on Backup
or Disaster Recovery. You need to narrow it down a bit.
Here are a few snippets.
- AD replication to offsite DC with delayed replication schedule. Normal AD
backup and recovery.
- DHCP inactive scope
- SQL log shipping, maintenance plan
- Sharepoint
http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsf20.mspx?mfr=true
- Exchange replication and recovery
- ISA backup restore configuration
If I just had a spare server and I wanted to beef up my protection a bit I
would look at this:
1) Make it a DC, offsite with delayed replication
2) Maybe set up an inactive DHCP scope but it is so quick to do it is hardly
worth the bother
3) Set up SQL maintenance plan and do log shipping to save some time
recovering from tape
4) Do a backup to disk of critical data
5) Set up parallel Exchange, Sharepoint and ISA configurations and
documement what has to happen to kick them in.
If you really do have a disaster and people can't get to the site, think
about a VPN for access to critical services to keep the business running.
Anthony
"Lobo" <lobo_NO_SPAM_!!@xxxxxxxxxxxxx> wrote in message
news:O4ACTRWyGHA.4732@xxxxxxxxxxxxxxxxxxxxxxx
Hello there.
We are a small company and we've just updated our only server (Windows
Server 2003 SP1) to a newer and better machine. Since we do not have too
much resources to guarantee a good disaster recovery plan, we started to
think about using the old machine as a replica of the new server.
It would be at a remote place and could be used as a backup if something
occurs with the official server (I mean, it could be brought physically to
our office and used instead the other). Is that possible? How could it be
done?
Our server has the following components:
- AD / DNS
- DHCP
- Exchange Server 2003
- SQL Server 2005
- Sharepoint Services
- ISA Server 2004
We do not have big volumes of information and what we are most concerned
about is having a functional copy of AD, backup of Exchange data and some
(file system) folders (that holds our most valuables bits of information).
Other concern is about having to setup a new fresh machine, that's why a
functional replica would come very handy for us.
Thanks in advance,
Lobo.
.
- Follow-Ups:
- References:
- Prev by Date: Re: Memory configuration - Windows Server 2003 32-bit and Opteron
- Next by Date: Re: Unable to start Windows 2003 SBS after SP1 install
- Previous by thread: Replicating Windows Server 2003 to create remote backup server
- Next by thread: Re: Replicating Windows Server 2003 to create remote backup server
- Index(es):
Relevant Pages
|
Loading
