Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Greg Scott <GregScott@InfraSupportEtc.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Exchange server 5.5 Disaster Recovery
Date: Fri, 17 May 2002 13:33:59 +0000	[thread overview]
Message-ID: <marc-lartc-102164152018909@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102163298711061@msgid-missing>

If you can afford the down time, you could stop all your Exchange services
on the primary system, copy all files in the exchsrvr directory, then
startup the services again.  Another option would be to buy Backup Exec and
buy the Exchange backup agent and use this agent to backup the files.  I
think BUEXEC has the ability to go disk to disk.

I don't remember the particulars about Exchange itself, but I vaguely
remember some capability for Exchange to keep redundant copies of the data
stores across the same site.  I'd have to look this up to be sure.

- Greg



-----Original Message-----
From: Azad Mahmoud [mailto:azad.mahmoud@dionach.com]
Sent: Friday, May 17, 2002 5:56 AM
To: lartc@mailman.ds9a.nl
Subject: [LARTC] Exchange server 5.5 Disaster Recovery



Hi,

As a plan for a disaster recovery network (in a second location), is
there any way of synchronising the current Exchange server remotly with
the DR one in our location, or is there any way of doing this process
through a backup and restore procedure?


Thanks





****************************************************************************
*
Disclaimer: This e-mail and any attachments are confidential. 

It may contain privileged information and is intended for the named 
addressee(s) only. It must not be distributed without Dionach Ltd consent.
If you are not the intended recipient, please notify the sender immediately
and destroy this e-mail. 

Any unauthorised copying, disclosure or distribution of the material 
in this e-mail is strictly forbidden. Unless expressly stated, opinions 
in this e-mail are those of the individual sender, and not of Dionach Ltd.
****************************************************************************
*

______________________________________________________________________
This message has been checked by Dionach for all known viruses using
MessageLabs Virus Scanning Service. For further information visit
http://www.dionach.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2002-05-17 13:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17 10:55 [LARTC] Exchange server 5.5 Disaster Recovery Azad Mahmoud
2002-05-17 13:33 ` Greg Scott [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-102164152018909@msgid-missing \
    --to=gregscott@infrasupportetc.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox