How can restore Exchange 5.5 from backup?

[shadowfax1066]

Hi, we are having troubke rebuilding Exchange 5.5 from tape, we have a server with c (os), d (logs) and e (databases) drives. We ahve built a new server with same drives then run optimizer and moved files to the correct same location as our live server. We then installed SP4 for exchange, stopped the services & deleted the files from the mtadata, mbdata & dsadata folders on all partitions then used veritas backup to restore the most latest files/database. Well no services startup after, we have only managed to do this once, but can't successfully do it now..................any ideas?

Thanks

AW

 

[Serbtastic]

Have you opened a support call with Veritas?

 

[shadowfax1066]

They says we are backing everything up and told us we need to speak to MS. Seems nobody knows....

 

[Guch]

Please see the MS article.
Follow it to the tee.
I have tried and tested the procedure, and it works.

http://support.microsoft.com/default.aspx?scid=kb;en-us;296229

Regards

 

[zbnet]

Also, for full 5.5 DR, see

http://www.microsoft.com/exchange/techinfo/administration/55/backuprestore.asp

 

[PBurcin]

After your restore, run ISINTEG /PATCH. This must be run after a restore is completed. Then see if services will start. IF not, check the application event log to see what is happening.

 

[PMCDad]

I had a similar problem here, we needed to restore from older backup. The one we started with was corrupted as well. Our crash was due to a virus issue.

What happened to yours? Hardware or software problem?

 

[jdeaner]

The best bet is to do offline backups of the edb. The logs are not needed with a consistant shut down (taking the edb offline). Restore from an offline DB is the best bet if you have one. We had veritas exec online backups only which caused all kinds of problems upon restore (missing contact data, corrupt messages, etc..) and the DB was only workabe after defragmentation. We restored our DB online from tapes, defrag'd, isinteg-patched and then Xmerged everyting out, configured local PST's then dumped the old DB and started fresh. This is what MS will most likely tell you to do.

 

[SimonDavis]

You also need to make sure your databases and logfiles match. There are instructions for it on MS website, I think if you search for say crossmatching exchange 5.5 you'll find the article.

The restore of course should have done it properly, but I have had problems in the past and resolved it by doing this.

Basically, the databases headers are examined, and they will list the logfiles they need. If you have the wrong ones, it all goes pear shaped.