Arcserve Restore Full Exchange 5.5

[Budgie69]

I have taken a backup of Exchange using Arcserve Agent
I have restored Exchange onto our new Exchange Server, using the arcserve agent. I have used same domain name and IP etc as backed up Exchange

Database restores, but Directory Service for Exchange fails to restart, am i doing something wrong ? if so wot?


Please help

 

[ArcservePro]

The server name you restore Exchange to must be the same as the original.

Also, run an IS/DS consistency check after the restore, but before you restart Exchange. Chris Horvath - True Data Storage Networks Inc. - New York City
Premier CA VAR, Arcserve Training Center, StorageTek Dealer
arcserve_pro@yahoo.com

 

[mtnathan]

(1) Check the NT event log and see what error msgs you
are getting regarding Dir services.
(2) Check the consistency of the restored dbs using
eseutil and run isinteg -patch, before you start the services.
(3) CHeck whether you have the Restore in Progress key
in Hkey Local Machine\System\Current Control Set\MS Exchange IS, if it is there, delete and reboot.
(4) Start the MS Exchange services in this order
System Attendant, DS, IS.
(5) Open the Exchange Administrator and select the restored
Exchange server under servers, file - properties - advanced
- and run the consistency adjuster.

 

[Caustic]

If anyone has additional information on this I would be interested. I am having the exact same problem.

After restoring the IS and DS from tape onto a new server with a fresh install of exchange (same settings) the Directory service will not start.

eseutil reports that the database is inconsistent and there may be uncommitted log files, but attempting to recover or repair the ds fails every time.

isinteg -patch will not function because, of course, the directory service fails to start.

 

[mtnathan]

You do not need to really restore the directory store.
Reinstall Exchange.
Restore just the Information Store.
run eseutil /p <full path of the priv.edb>
run eseutil /p <full path of the pub.edb>
change into the exchsrvr\bin folder and run isinteg -patch
back to exchsrvr folder and
run eseutil /mh <full path of priv.edb> | more
run eseutil /mh <full path of pub.edb> | more
the result of the last two commands should be consistent.
Then start the services SA -> DS (this is the installed copy and not the restored copy of database) -> IS
Then start the Exchange Administrator.
Select the server under configuration - Servers
File Properties - Advanced - and run the consistency adjuster to adjust all inconsistencies and not to delete
any entries.
When you try to start the services, you might get some errors (service specific errors) at that point check the
NT event viewers and search Microsoft for that error code
and follow their advice. As long as the eseutil /mh
results show the dbs as consistent, the restore is fine and
complete.

 

[Caustic]

alright...

I've restored just the IS. SA starts, DS starts. I run the repair on both the IS and DS. The IS will still not start. I get an error when trying to run isinteg -patch: The priv store could not be updated. JET_errorFileAccessDenied

I assume this has something to do with the fact that exchange no longer has access to the original SAM database since the restore is taking place on an offline server.

Someone had suggested restoring to an online server with the same organization name as the original; that way I have access to the original SAM. But don't I have to have the same computer name also? This would, of course, cause a problem having two servers with the same netbios name on the network.