I give up :-(

[Daskynic]

I get this error:

savegrp: suppressed 3 lines of verbose output
[7524] 06/20/07 23:02:12 Processing storage group "SRS Storage"
[7524] [E] 06/20/07 23:02:12 HrESEBackupSetup: unknown error -939585532 (0xc7ff1004) (0xc7ff1004)
[7524] [E] 06/20/07 23:02:12 hrErrorFromESECall last error: -1003 (0xfffffc15)
[7524] [E] 06/20/07 23:02:12 Unable to promote backup level to full.
[7524] [E] 06/20/07 23:02:12 HrESEBackupSetup: unknown error -939585532 (0xc7ff1004) (0xc7ff1004)
[7524] [E] 06/20/07 23:02:12 Instance ID: 0
[7524] [E] 06/20/07 23:02:12 hrErrorFromESECall last error: 997 (0x3e5)
[7524] 06/20/07 23:02:12 Completed backup of SRS Storage Status: 0xc7ff1004
unknown error -939585532 (0xc7ff1004)
[7524] [E] 06/20/07 23:02:13 Backup operation finished with errors. No savetime was sent.

 

[605]

Me too.

With this lack of information almost nobody will be able to help you if he does not recognize the application by the error codes.

It looks like a database error and you expect a NW problem. However, with those clear error messages which are issued by the database (NW does not know error numbers!), it should be possible to search the docs/web.

 

[bombcan]

What type of backup is this???What are your the version?

 

[wallace88]

Do you really need to backup the Exchange SRS???

Site Replication Service (SRS) implies that you are using Exchange 5.5 in an active directory environment with other Exchange 2000/2003 servers. Is this correct? SRS could be enabled, but not used/configured. Verify this with your exchange admin. If this is the case, you can exclude this from backups.

Generally speaking, when you backup exchange and get some message with something that starts with: HrESE, this is a message that is coming from Exchange. It is then sent back to NetWorker, and NetWorker reports it in the savegroup logs.

You can also try verifying/repairing the exchange database. Look at the following article for more details:

http://support.microsoft.com/default.aspx?scid=kb;en-us;318429

Try using ntbackup to backup exchange. This takes NetWorker out of the picture. If ntbackup fails, then it is an exchange issue and you need to call... Microsoft.