Discussion Locked

Exchange 5.5 disaster recovery server

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have built a server with the same organization and site as my main Exchange server. Both my main Exchange and the new backup servers are BDC's of my domain. My question is how can I restore a backup from Veritas Backup exec (Directory and Information store databases) to the new backup server and not affect my main Exchange server. Can I do it by disabling the Exchange services on the backup machine, restore from Backup Exec and then unplug from the network? Also, when I have restored it, how can I get the data out of one mailbox. I know how to do .psts but not sure how to connect to the backup server from outlook. Any help would be greatly appreciated.

6 replies

by tony.colgrove

You will want to pull this server off you network, and premote it. Use Backup Exec to restore the database. Make sure Outlook is installed on the DR server.
From Outlook open the mailbox and export it to a .pst.
Backup the pst and restore it on the product network. From the user create a new profile and import the .pst.

by infosecmn

Right now I only have one network. Do you mean disconnect from the network and promote to a PDC? If I promote before I disconnect, I will be the PDC of my domain. Also, how can I restore from backup exec if I am not on the network? Thanks

by cclawar1

We have been addressing this same issue for 2 months. We are using ArcServe for a backup solution but I beleive our issues are the same. Our conclusion:

The 2 servers CANNOT coexist. NT won't allow it. All service pack levels must be identical.

Before beginning, cut off access to your mail server so users can't alter your environement until your ready.

1) Since your new server is a BDC, you'll need to bring down your production server to start this process. We were able to install NT partially before installing networking to cut down on the down time for our production server. Alter the network properties of your production server to remove it from your domain. Bring it down.

2) Bring up your new server. Install NT from scratch, including service packs. Add it to your domain.

3) Install NT option pack for IIS configurations. (Production server is still down).
4) Install Exchange and SP for Exchange.
5) Install any backup agents onto your new server. ArcServe has an Exchange aware agent for live backups.
6) Once your new server is fully configured (with your production server down!), you can use your backup software to restore your Directory Store and your Information store to there original directory locations, but on the new server. In order for this restore to be clean you should rename the dsdata and mdbdata directories to dsdataold and mdbdataold and create new empty dsdata and mdbdata directories. Run your restore.

You should now have a new functioning server. If you do this work in stages you can keep your down time segmented to an hour or 2 each time. The largest window will be for your actual restore. We have not gotten a good handle on the time frame for this as yet. We are scheduled for a full test in the next 3 weeks.

by infosecmn

Thank you, the step by step instructions really helped. Also renaming the dsdata and mbddata was helpful.

This discussion is closed to new replies.