Exchange2007 Windows backup failing to complete
-
1. prosince 2010 1:25
Devin
Všechny reakce
-
1. prosince 2010 14:22
Dear Devin,
Would you provide more details
Windows Server version? how you are initiating backup? what is the exact error? anything in the eventlog? have you been able to do a successful backup before? if yes what changed?
thank you.
MCSE | MCITP - Server 2008 | MCITP - Exchange 2007 | MCTS - Exchange 2010 -
2. prosince 2010 9:05Hi Devin,
Any update for your issue?
Could you please post more information like above referred?
And we could do more research regarding to your issue.
How about make a test again manually?
Regards!
Gavin
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
9. prosince 2010 9:39Hi Devin,
Any update for your issue?
Regards!
Gavin
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
12. února 2011 19:25Sorry for the delay. Here is what is happening. I had set my servers(2 win2k8ent and 1 2k3Ent) to backup with Symantec BackupExec 12.5 3 times a day. On the Windows 2008 servers I had set them to backup using the windows backup 3 times a day also so I would have interleaved backups. Everything has run lick a champ. After a batch of update(I do not know which ones) I noticed the occasional bump where one would fail. So I set up individual jobs to backup each database and then do the OS and system state. Within the Microsoft backup I receive the error that the backup ran but Exchange would not be available for restore. Within the BEX 12.5 all of the databases fail. I have upgraded all driver, clients etc. to the current versions. I ran esutil on each Db with absolutely no errors reported. I have run checkdisk, defraged(Forced Exchange to run it's defrag) dismounted and remounted each database. I had oopened up a case with Microsoft about 8 months ago and contacted the support rep and he replied he is in a different group and would try to get someone to reply to me(its been a week with no joy) so I could get the case notes to try and resolve it myself. Does anybody else have any ideas as to what I could try in the mean time?
Devin -
17. února 2011 20:05
Are you using full backups, incremental or differential with windows backup and are you trying brick level with symantec.
can you check the event id for exchange backup on exchange server and find which one is sucessfull and to what level.
are you usng circular logging, can you check the ackup status in ESM .
-
17. února 2011 21:54Where I am now with it is trying to backup individual databases with the Backup Exec product. The windows server backup just gives the genereis "Echange will not be available" blah blah blah. Within BE12.5 I am getting different errors which I have been tracking down. It seems to be pointing at the Exchange VSS writer from the error message. I have run the vssadmin list writers and I can see the exchange writer and it is in stable condiion. I have looked through the Symantec docs and tried to edit the registry to not disable the writer(s) and that did not work so I removed that entry. It states "Resources specified for snapshot do not have valid data on them"(error 34113). I have edited the job to specify only a database. I have tried each of the 5 databases to no avail. The job starts and about 10 seconds in it bombs out.
Devin -
15. května 2012 17:55 Somehow the cr files were put on the same hard drive. Once I moved them to a separate drive it worked!
Devin
- Označen jako odpověď DevinWhite 15. května 2012 17:56
.png)
