|
|
Posted by Mike Epprecht \(SQL MVP\) on 08/11/05 00:54
Hi
1. B
2. If it is a write failure, yes it will be in the SQL Log. If it is data
corruption, it is in the SQL Log.
For a backup to fail, due to internal SQL Server problems is very very rare,
and I have not seen it on a clean database before.
Most failures are caused by running out of disk space or anti virus messing
around on the file when SQL is trying to write to it.
Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Stephanie" <stuttle@centene.com> wrote in message
news:1123710578.824686.208370@g47g2000cwa.googlegroups.com...
>I have not been able to find any details about backup failures for
> MSSQL 2000. I am researching the following:
> 1. when a backup fails at a certain point during the process does the
> backup:
> A. stop there having recorded some details?
> B. quit without backing up any of the data it already processed?
> C. skip the data it cannot read and move on?
> 2. Does the error log record any of the details above? For instance, if
> there is a table that the backup could not write to .bak, does the
> error log report exactly where the error was?
>
> I need a way to obtain a Backup Exception 'Report' that when a backup
> fails it can tell me what did not get into the .bak file. I would
> prefer automatic notification. Our Oracle DBs have something setup
> that can be run when a piece of the DB does not get backed up letting
> the Oracle DBA know where there are issues.
>
> Thank you,
> Stephanie
>
Navigation:
[Reply to this message]
|