[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 607
  • Last Modified:

Restoring exchange 2007

I walked into a job with an exchange server running server 03 64 bit and exchange 2007.  It also has backup exec 12.5 installed running a weekly full and and incremental nightly.  I have cloned (using acronis) a domain controller and the exchange server to use for testing to do a  test restore of the exchange server.  Every time i run the restore i get an error stating:

A failure occurred querying the writer status

I think this has something to do with the log files.  Everytime i try the restore i select the option to purge logs and restore from backup (setting is within backup exec restore options).  I also tried the no loss option for restoring the log files which gives me a database that is in dirty shutdown state which will not mount.  Also i am trying to overwrite the current files on the drives instead of using RSG.  if any of you experts have an easier way to get this restored please let me know.  I am glad i am tesing this instead of attempting this out of necessity.  instead of cloning the server maybe i am better off installing a new server and attempting to restore i don't know.  The acronis image of the exchange server is from july and the backup set is the full backup from one week out of sept.  Thanks Experts!
0
IKtech
Asked:
IKtech
  • 8
  • 5
1 Solution
 
IKtechAuthor Commented:
Event Type: Error
Event Source: MSExchangeIS
Event Category: Exchange VSS Writer
Event ID: 9757
Description:
Exchange VSS Writer failed restoring a backup for 'Recovery Storage Group' because database recovery is supposed to occur after restore, but no log files are being restored and no existing log files were found in the logfile directory 'E:\first\E02*.log'.
   
I am also getting this error
0
 
RadweldCommented:
If your restoring back to the same location you have to set the tick box saying his database can be overwritten by a restore.

Can you recover anything to an alternate location? Databases that don't start because they are dirty can be cleaned up wih eseutil this is a command line tool that performs admin functions to exchange databases.

http://exchangeis.com/blogs/exchangeis/archive/2007/03/26/eseutil-a-quick-and-easy-tutorial.aspx

Eseutil /r requires logfiles to be played back into the database

Eseutil /p repairs the database without logfiles but you will lose data.
0
 
IKtechAuthor Commented:
V-79-57344-4615 - To support individual mailbox message and folder restores from Information Store backups, you must download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version 06.05.7888 or later on the Exchange 2007 server. This package can be found on the Microsoft web site.


i had the GRT option checked from symantec backup exec and i get this message when i do a backup.

Do you think the mapi client may be necessary to restore?
0
 
RadweldCommented:
If you want to restore individual emails I.e granular restore then you will need a mapi client, I actually thought the backup exec agent did this but that's not my speciality. If you want to restore an entire databases then this isn't needed as your just restoring a file at the end of the day. If your still getting vss errors then you need to test volume shadow copy with "vssadmin list writers" or vssadmin list providers

Any writers In a bad state will prevent backup or restore using vss technology.
0
 
IKtechAuthor Commented:
vssadmin list writers command reports no errors before the restore just after the failure.  Thanks for the response Radweld
0
 
RadweldCommented:
Which writer errors?
0
 
IKtechAuthor Commented:
Microsoft exchange writer
0
 
RadweldCommented:
Have a look at this and see if it applies,

http://www.symantec.com/business/support/index?page=content&id=TECH27875

Seams to be known with Symantec :-)
0
 
IKtechAuthor Commented:
http://www.symantec.com/business/support/index?page=content&id=TECH87383

i ended up using this document to restore to a flat file.  I was able to mount the database which is further than i've gotten before however i am still testing.  For my future backups i may not use GRT and do some testing with full and incremental backups.  Thanks for your help.  I appreciate it
0
 
IKtechAuthor Commented:
i also deleted the database and the logs before restoring the flat file to the same directory.
0
 
RadweldCommented:
Just a note, you should keep logfiles as these hold all transactions not in the database, in theory you can restore a db from the last backup and replay the logfiles into the db to get you within one transaction. The log chain has to be consistent with the db hough.
0
 
IKtechAuthor Commented:
i ended up restoring as a flat file via this document.
http://www.symantec.com/business/support/index?page=content&id=TECH87383

Then i change how i get backups moving away from Granular restore technology.  The restore works flawless when the backup is done with GRT.
0
 
IKtechAuthor Commented:
Thanks for the help gentlemen
0
  • 8
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now