JoyCara
asked on
Exchange Site Replication Service backup fails
We are currently using VERITAS Backup Exec 11.D for our nightly system backups of domain controllers, exchange, sql server, and a few other small items. Recently out of the blue, the backup job has started generating errors during the backup of exchange. Here is the log:
Backup- \\mailserver\Microsoft Site Replication Service\SRS Storage V-79-57344-33928 - Access is denied.
Access denied to database SRS MDB.
V-79-57344-33928 - Access is denied.
Access denied to database Log files.
I used the test credentials function in Backup Exec to make sure everything was being accessed properly, ran a test backup job, and it reported back successful on both accounts.
Next I called Symantec who had me go to the mail server and just backup the SRS database by using ntbackup. Just to make sure there was no problem with ntbackup, I tested it by backing up the First Storage Group which was successful. I had a look at the ntbackup log and this is what it said.
Backup Status
Operation: Backup
Active backup destination: File
Media name: "srsBackup.bkf created 8/3/2007 at 8:38 AM"
Volume shadow copy creation: Attempt 1.
Backup of "CCNMAIL\Microsoft Site Replication Service\SRS Storage"
Backup set #1 on media #1
Backup description: "Set created 8/3/2007 at 8:38 AM"
Media name: "srsBackup.bkf created 8/3/2007 at 8:38 AM"
Backup Type: Normal
Backup started on 8/3/2007 at 8:39 AM.
The 'Microsoft Site Replication Service' returned 'Error returned from an ESE function call (d).
' from a call to 'HrESEBackupSetup()' additional data '-'The 'Microsoft Site Replication Service' returned 'Functions called in an invalid sequence.
' from a call to 'HrESEBackupClose()' additional data '-'
The operation was ended.
Backup completed on 8/3/2007 at 8:39 AM.
Directories: 0
Files: 0
Bytes: 0
Time: 1 second
----------------------
The operation did not successfully complete.
----------------------
I'm not really able to find any information on goole, tech net, ect about this error message i'm getting. Anybody ever come across this before?
Backup- \\mailserver\Microsoft Site Replication Service\SRS Storage V-79-57344-33928 - Access is denied.
Access denied to database SRS MDB.
V-79-57344-33928 - Access is denied.
Access denied to database Log files.
I used the test credentials function in Backup Exec to make sure everything was being accessed properly, ran a test backup job, and it reported back successful on both accounts.
Next I called Symantec who had me go to the mail server and just backup the SRS database by using ntbackup. Just to make sure there was no problem with ntbackup, I tested it by backing up the First Storage Group which was successful. I had a look at the ntbackup log and this is what it said.
Backup Status
Operation: Backup
Active backup destination: File
Media name: "srsBackup.bkf created 8/3/2007 at 8:38 AM"
Volume shadow copy creation: Attempt 1.
Backup of "CCNMAIL\Microsoft Site Replication Service\SRS Storage"
Backup set #1 on media #1
Backup description: "Set created 8/3/2007 at 8:38 AM"
Media name: "srsBackup.bkf created 8/3/2007 at 8:38 AM"
Backup Type: Normal
Backup started on 8/3/2007 at 8:39 AM.
The 'Microsoft Site Replication Service' returned 'Error returned from an ESE function call (d).
' from a call to 'HrESEBackupSetup()' additional data '-'The 'Microsoft Site Replication Service' returned 'Functions called in an invalid sequence.
' from a call to 'HrESEBackupClose()' additional data '-'
The operation was ended.
Backup completed on 8/3/2007 at 8:39 AM.
Directories: 0
Files: 0
Bytes: 0
Time: 1 second
----------------------
The operation did not successfully complete.
----------------------
I'm not really able to find any information on goole, tech net, ect about this error message i'm getting. Anybody ever come across this before?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Then se if you have any Exchange diagnostics.
Something is not quite right.
I would also try to backup using NTbackup from a different server to see if the issue is Just on your BE server.
You need to identify the problem, be it Exchange or BE, and then remedy.
I hope this helps !