Re: Replicating Windows Server 2003 to create remote backup server
- From: "Anthony" <anthony.spam@xxxxxxxxxxxxxx>
- Date: Wed, 30 Aug 2006 08:24:15 +0100
Yes in your case I think it can, but make sure you have a normal backup of
the data as well.
Also, be aware that you can saturate the VPN link if you make too many
changes, as you can with any replication, but in your case that does not
sound like it should be a problem. There is some good documentation on how
DFS replication handles changes:
http://technet2.microsoft.com/WindowsServer/en/library/20ffb860-f802-455c-9ca2-5194f79a9eb41033.mspx?mfr=true
http://technet2.microsoft.com/WindowsServer/en/library/20ffb860-f802-455c-9ca2-5194f79a9eb41033.mspx?mfr=true
Anthony
"Lobo" <lobo_NO_SPAM_!!@xxxxxxxxxxxxx> wrote in message
news:OY8%23fS7yGHA.2640@xxxxxxxxxxxxxxxxxxxxxxx
Anthony, thank you very much again for answering, it certainly helped!
Just a last question about the replication of file system folders: Can't
File Replication Service be used to do the trick?
Best regards,
Lobo.
"Anthony" <anthony.spam@xxxxxxxxxxxxxx> escreveu na mensagem
news:ONWJFu5yGHA.1824@xxxxxxxxxxxxxxxxxxxxxxx
Hi Lobo,
You are well organised. I will try to pick up the remaining questions you
have asked.
- Replication of file system folders. Replication products like Legato
Replistor and Veritas Replication Exec will create a near real-time copy,
at the cost of licenses. NTBackup scheduled tasks with full and
differential replication can give you something close, as can many other
methods. You have to judge the risk against the cost.
- SQL log shipping will make a remote copy of the database with, for
example, a 15 minute delay. If that's not acceptable, replication
products will make it near real-time.
- You can leave the remote DC on, but use AD Sites and Services to
schedule infrequent replication. You don't really want the remote DC to
be Off. The idea of the delay in a DR plan is so that if your AD is
damaged you can avoid replicating the damage. Obviously you will also
lose changes in the gap, but that should not be too important in a
disaster.
- No problems with AD and DNS at a remote site for DR.
Hope that helps a little,
Anthony
"Lobo" <lobo_NO_SPAM_!!@xxxxxxxxxxxxx> wrote in message
news:eCBQ2i5yGHA.4796@xxxxxxxxxxxxxxxxxxxxxxx
Hi Anthony, thanks very much for answering.
Sorry, I'll try to clarify a little bit more. Yes, I'm concerned with
things
like hardware failure but I'm also concerned about simple things like
being
stoled. As I said, we are a very small company, and our office is a
simple
and normal house, with all the security lacks that a house like that is
supposed to have.
If something like being robbed happened to us, we could still buy some
new
machines, using the insurance payment or not, but we would need our most
valuable data available and it would be desirable to have our
"environment"
restored back either. So, if we had a replica server, for backup
purposes,
hosted in somewhere else (like my house), we could get that server and
put
it on our office so we can go on with life until we can fix the
situation.
Of course we could just backup everything that's needed to rebuild our
server, but, as I said before we don't have too much resources on that
area
(see, I am the network admin, but that's just because we don't have
anyone
better for the job, 'cause actually I'm a programmer/analyst), so,
imagine
having to rebuild the server under the pressures of such situation?
Now that I exposed the reasons, let me tell about the technical stuff:
- Today the old server already is a DC and is already replicating AD and
DNS; remember that this one was the original server, so, in the update
process we replicated all that information from one to another;
- DHCP isn't really a worry since our config is really simple;
- Exchange is also replicating information (or almost), since we also
needed doing that for the upgrade;
- The desired system folders are not being replicated, and I don't know
exactly how to do this one;
- SQL Server is also not being replicated, but this isn't so bad by now
and
I know that it has replication tools that will probably solve the
problem;
- Sharepoint and ISA are easier to reproduce, so they are not a problem
also.
What I really wanted to know is whether the idea is possible, 'cause I'm
not
too sure about simple things, like:
- It's OK to have a backup DC that's turned on only at night, for
example,
for replication purposes?
- Will we have problems with AD or DNS or something else with that kind
of
environment?
- Can I replicate system folders easily (and in a trustful way) using
Windows Server 2003 tools?
Thanks very much for the help, and sorry about the lengthy message!
Best regards,
Lobo.
"Anthony" <anthony.spam@xxxxxxxxxxxxxx> escreveu na mensagem
news:uh7SVgbyGHA.1936@xxxxxxxxxxxxxxxxxxxxxxx
| 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:
- Replicating Windows Server 2003 to create remote backup server
- From: Lobo
- Re: Replicating Windows Server 2003 to create remote backup server
- From: Anthony
- Re: Replicating Windows Server 2003 to create remote backup server
- From: Lobo
- Re: Replicating Windows Server 2003 to create remote backup server
- From: Anthony
- Re: Replicating Windows Server 2003 to create remote backup server
- From: Lobo
- Replicating Windows Server 2003 to create remote backup server
- Prev by Date: NIC teaming problem after migration 2000 to 2003
- Next by Date: Re: VPN with Linksys
- Previous by thread: Re: 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
|
