kj
Thu May 08 12:59:16 PDT 2008
Good luck, and hopefully it's a quick fixup with little or no loss of data.
You also want to investigate the root cause for the corruption. Exchange is
very good at maintaing db integrity. Proper antivirus exclusions are
important as is confidence in the disk (RAID?), UPS / battery backup, etc.
Nothing worse than having it happen again.
"SitsWithMouse" <SitsWithMouse@discussions.microsoft.com> wrote in message
news:2E917CF7-03FB-4A70-A8A6-EEDC1E22CE31@microsoft.com...
> Thanks for your inputs folks.
>
> Looks like we'll have to make the call to MS.
>
> "kj [SBS MVP]" wrote:
>
>> "Ditto" to the OP. DB corruption only gets worse, harder to fix,
>> potentially
>> more loss of data, and continued lack of backup ability.
>>
>> This one is worth the MS $upport call, unless you have a seasoned
>> Exchange
>> engineer close at hand.
>>
>> oh, and lock up all backups prior to the probem showing up. You might
>> just
>> need them.
>>
>>
>> Jim Behning SBS MVP wrote:
>> > Just because the users do not report issues does not mean there are
>> > not issues. Microsoft has some Exchange utilities to check database
>> > integrity. I had an account that showed Exchange backup issues but the
>> > users never complained. The utilities reported a damaged database that
>> > I had to toss out and start from scratch because it would no repair
>> > itself. That was after doing exports from the damaged database. Better
>> > to fix when small than to let it keep growing while damaged.
>> >
>> > On Wed, 7 May 2008 20:34:00 -0700, SitsWithMouse
>> > <SitsWithMouse@discussions.microsoft.com> wrote:
>> >
>> >> Hi Cliff
>> >>
>> >> No exchange issues at all. Users have not reported any problems
>> >> either.
>> >>
>> >> The only issues we have had are WSUS 3.0 SP1 related - where WSUS
>> >> periodically causes the reporting to fail for soem reason.
>> >>
>> >> In fact this server is quite new - it only went in at the start of
>> >> March.
>> >>
>> >> "Cliff Galiher" wrote:
>> >>
>> >>> I'd trust that what the backup says is true. This isn't a "backup"
>> >>> error. SBS (or NTBackup specifically) just makes calls to properly
>> >>> backup exchange, so it is exchange throwing this error. You
>> >>> haven't had other exchange issues yet?
>> >>>
>> >>> -Cliff
>> >>>
>> >>>
>> >>> "SitsWithMouse" <SitsWithMouse@discussions.microsoft.com> wrote in
>> >>> message news:1318A4C1-9042-4646-89B5-D646F8513712@microsoft.com...
>> >>>> Good day forum
>> >>>>
>> >>>> SBS Backups have recently started failing on an SBS 2003 R2 Premium
>> >>>> server.
>> >>>> The backups were running 100% error free until 10 days ago. We are
>> >>>> backing
>> >>>> up to USB drives and we are doing full backups.
>> >>>>
>> >>>> Exchange appears to be operating normally (from a user
>> >>>> perspective), but from the backup perspective it appears a little
>> >>>> off color.
>> >>>>
>> >>>> Logs pasted below.
>> >>>>
>> >>>> Any asisstance would be greatly appreciated.
>> >>>>
>> >>>> Thanks
>> >>>>
>> >>>> The SBS error log says:
>> >>>>
>> >>>> --------------------- start snip ------------------------
>> >>>>
>> >>>> Backup started on 2008/05/06 at 06:09 PM.
>> >>>> WARNING: Portions of "\Program Files\Exchsrvr\MDBDATA\priv1.edb"
>> >>>> cannot be read. The backed up data is corrupt or incomplete.
>> >>>> This file will not restore correctly.
>> >>>> Backup completed on 2008/05/07 at 03:04 AM.
>> >>>> Directories: 29787
>> >>>> Files: 321488
>> >>>> Corrupt: 1
>> >>>> Bytes: 223,739,984,398
>> >>>> Time: 8 hours, 54 minutes, and 33 seconds
>> >>>>
>> >>>> --------------------- end snip ------------------------
>> >>>>
>> >>>> 1st Windows Event log error after 6:09 is:
>> >>>>
>> >>>> --------------------- start snip ------------------------
>> >>>> Event Type: Error
>> >>>> Event Source: NTBackup
>> >>>> Event Category: None
>> >>>> Event ID: 8001
>> >>>> Date: 2008/05/07
>> >>>> Time: 03:04:27 AM
>> >>>> User: N/A
>> >>>> Computer: VMI-SBS2003P
>> >>>> Description:
>> >>>> End Backup of 'C:' 'Warnings or errors were encountered.'
>> >>>>
>> >>>> Verify: On
>> >>>> Mode: Replace
>> >>>> Type: Normal
>> >>>>
>> >>>> Consult the backup report for more details.
>> >>>>
>> >>>> For more information, see Help and Support Center at
>> >>>>
http://go.microsoft.com/fwlink/events.asp.
>> >>>>
>> >>>> --------------------- end snip ------------------------
>> >>>>
>> >>>>
>> >>>> and the next event viewer error (and last error) is:
>> >>>>
>> >>>> --------------------- start snip ------------------------
>> >>>>
>> >>>> Event Type: Error
>> >>>> Event Source: SmallBusinessServer
>> >>>> Event Category: SBS Backup
>> >>>> Event ID: 5634
>> >>>> Date: 2008/05/07
>> >>>> Time: 10:53:50 AM
>> >>>> User: N/A
>> >>>> Computer: VMI-SBS2003P
>> >>>> Description:
>> >>>> One or more components of Small Business Server Backup failed. For
>> >>>> more information, click Backup in Server Management, and view the
>> >>>> log files.
>> >>>>
>> >>>> For more information, see Help and Support Center at
>> >>>>
http://go.microsoft.com/fwlink/events.asp.
>> >>>>
>> >>>> --------------------- end snip ------------------------
>> >>>
>> >>>
>> > See what SBS support is working on
>> >
http://blogs.technet.com/sbs/default.aspx
>> > Check your SBS with the SBS Best Practices Analyzer
>> >
http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx
>>
>> --
>> /kj
>>
>>
>>