cloudbase
asked on
Unable to backup Exchange 2007 Database
Hi,
I'm trying to backup Exchange 2007 CCR database using SCDPM 2010.
When I'm trying to create recovery point for one of the storage groups, I'm getting error that VSS encountered an error and referred to the event log of the MBX server.
On the event log I find the following errors:
The Microsoft Exchange Replication service VSS Writer instance 273f20c5-1a62-4082-bd59-c5 9c3dc1eb38 could not find file H:\SG01-Logs\E0100065588.l og. Backup is aborted.
Log file action LogCopy failed for storage group HEXCMS01\SG01. Reason: The directory name \\hexmbx02\273f20c5-1a62-4 082-bd59-c 59c3dc1eb3 8$ is invalid
I am a bit afraid of re-seeding the DB, last time I've done it users lost some mails, so I really appreciate if anyone who is familiar with errors like this can help me.
Thanks.
I'm trying to backup Exchange 2007 CCR database using SCDPM 2010.
When I'm trying to create recovery point for one of the storage groups, I'm getting error that VSS encountered an error and referred to the event log of the MBX server.
On the event log I find the following errors:
The Microsoft Exchange Replication service VSS Writer instance 273f20c5-1a62-4082-bd59-c5
Log file action LogCopy failed for storage group HEXCMS01\SG01. Reason: The directory name \\hexmbx02\273f20c5-1a62-4
I am a bit afraid of re-seeding the DB, last time I've done it users lost some mails, so I really appreciate if anyone who is familiar with errors like this can help me.
Thanks.
ASKER
Thanks,
how do I check that?
how do I check that?
Open command prompt and run the command
vssadmin list writers
- Rancy
vssadmin list writers
- Rancy
ASKER
On both servers every this is stable and no errors were found in the beginning.
Now after I've tried to re-run the backup and the same errors appeared in the logs, the state of Exchange VSS Writer has changed:
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8 e1acb462fb 7}
Writer Instance Id: {68358314-fe0c-43e6-8ad0-d ca18b5635c a}
State: [7] Failed
Last error: Retryable error
Now after I've tried to re-run the backup and the same errors appeared in the logs, the state of Exchange VSS Writer has changed:
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8
Writer Instance Id: {68358314-fe0c-43e6-8ad0-d
State: [7] Failed
Last error: Retryable error
Do you have any SCR as well ?
Is the CCR in healthy copy status ?
Can you check for this log file on the location E0100065588.log ?
Do you take backup from Active or Passive ?
- Rancy
Is the CCR in healthy copy status ?
Can you check for this log file on the location E0100065588.log ?
Do you take backup from Active or Passive ?
- Rancy
ASKER
No SCR installed here (is it even optional to have both CCR and SCR in the same infrastructure?)
Yes, the CCR is in healthy copy status
The specified log file is missing from both servers
The backup policy is Passive first
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8 e1acb462fb 7}
Writer Instance Id: {68358314-fe0c-43e6-8ad0-d ca18b5635c a}
State: [7] Failed
Last error: Retryable error
You'll need to restart the Information Store service - without that the VSS writers wouldn't be in stable state.
Regards,
Exchange_Geek
Writer Id: {76fe1ac4-15f7-4bcd-987e-8
Writer Instance Id: {68358314-fe0c-43e6-8ad0-d
State: [7] Failed
Last error: Retryable error
You'll need to restart the Information Store service - without that the VSS writers wouldn't be in stable state.
Regards,
Exchange_Geek
- Rancy