scheduled jobs failing since installation of SMSME (backup exec 10d)

[nico_wieland]

hi,

since the installation of symantec mail security for microsoft exchange (current version 5.0.3.360), the scheduled backup job for backupping the exchange mail storage groups fail everytime. curiously, these same jobs have no problem completing when they are run manually. when being run from the scheduler, they fail with the following error:

Error category : Other Errors
Error : fffffea9 - 0xa000fea9 (2684419753)
For additional information regarding this error refer to link V-79-65535-65193

(the above link links to http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml?EvtID=V-79-65535-65193 which sadly isn't online anymore).

further down, it states

File is corrupt : \\ZUREBE\Microsoft Information Store\First Storage Group\Log files
File is corrupt : \\ZUREBE\Microsoft Information Store\First Storage Group\Mailbox Store (ZUREBE)
File is corrupt : \\ZUREBE\Microsoft Information Store\First Storage Group\Public Folder Store (ZUREBE)

which is obvisouly not correct - not only does our exchange server report no errors, the same backup job reporting these errors doesn't report them when being run manually. before the installation of the SMSME, there was no problem at all.

we have updated backup exec 10d to version 10.1 rev 5629 and have applied service pack 1, and hotfixes 26, 27, 29, 31, 33.

SMSME version is 5.0.3.360.

OS version is win2k3, sp1, all security patches and a few others.

we tried everything we could think about, to no avail - any help or idea would be very much appreciated.

tia,

nico

[priya_khire]

Hello,

When is the scheduled job run? Are there also any errors in the event logs when the scheduled job fails? Refer to the following technote:

http://support.veritas.com/docs/269156

Also tried recreating the scheduled job and test the results. Make sure that the job timings don't clash with the Exchnage database maintenance timings.

[nico_wieland]

hi,

the job originally run around 2:30am. as this indeed looked like there was some maintenance going on at that time, we re-scheduled it to 11:30pm, to no avail.

even logs only show:

Backup Exec Alert: Job Failed
(Server: "ZUREBE") (Job: "Backup 00012") Backup 00012 -- The job failed.

For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

(the link's broken as the one in the backupexec log).
(edit: the link isn't actually broken, but leads to a generic help page:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml?EvtSrc=Backup%20Exec&EvtCat=None&EvtID=34113&EvtCatID=0&EvtType=Error&EvtTypeID=1&EvtRptTime=1158269459&EvtTZBias=-120&CoName=Symantec%20Corporation&ProdName=Symantec%20Backup%20Exec(TM)%20for%20Windows%20Servers&ProdVer=10.1.5629.0&FileName=beevents_EN.dll&FileVer=10.1.5629.0)

as for the support link you provided:

1. there is no shadow copy backup
2. disabling AV isn't really an option at this time, and besides it a) is symantec av so i'd expect it to work with the symantec backupexec, and b) the job works when run manually, so i don't think this is the problem
3. works both with ntbackup and when running the job manually.

regarding your last suggestion, we tried creating a new job, and when i let it run scheduled like 5min after ceration, it ran perfectly and i hoped the problem was indeed solved. i re-scheduled it to 11:30 again, and the job failed to run again, with the same error message. i'm really at a loss here.Message was edited by:
nico wieland

[nico_wieland]

fyi, our exchange version is 6.5 build 7638.2: sp2.

[shweta_rege]

Hello,


Kindly try the backup with the ntbackup and let us know the results...




Thank You,

Shweta