If you are having an error like the following when trying to restore your exchange databases:
05/31/2009 11:24:48 – Warning bpbrm (pid=14316) from client exchangeServer: WRN – Exchange database recovery may have failed. Please check the event log for further details.
05/31/2009 11:27:02 – end reading; read time: 0:03:36
05/31/2009 11:27:03 – Warning bpbrm (pid=14316) from client exchangeServer: WRN – Exchange database recovery may have failed. Please check the event log for further details.
05/31/2009 11:27:04 – Error bpbrm (pid=14316) client restore EXIT STATUS 185: tar did not find all the files to be restored
05/31/2009 11:27:04 – restored from image exchange2_1243565471; restore time: 0:04:24
05/31/2009 11:27:15 – end Restore; elapsed time 0:21:45
the requested operation was partially successful (1)
After backing up your files, and while dismounted, remove every file from the database and log directories and re-try your backup again.
For example: You have a database named First Storage Group. Database files reside in d:dbFirst Storage Group and Db log files reside in d:logsFirst Storage Group
After backing up them, go into these directories and delete everything in, then re-try your restore.
Not the most efficient way, but works. Any other solutions are always welcome :)
Posted in 
Tags: 
Loading ...
hi
1)can you please explain me your backup architecture .
2) where r u taking backup ? ( Disk Or Tape )
Regard.
Vinod
Hi,
Backup was taken into tape.
Architecture is simple actually:
tape < - SAN <- netbackup master/media server -> BACKUP_LAN -> exchange 2007
Nbu server and clients are connected through a private direct network and using these network for their hostnames.
Accroding to netbackup 6.5.3 documentation upgrade , exchange granular restoration does not support tape backup. for more details on exchange granular restoraton refer below link .
http://support.veritas.com/docs/305408
Take a disk backup for succesfully exchange granular restoration.