YOURSQLDBA Backup failure Case Brocade set

When you use YOURSQLDBA for backup, maintenance, and administration, you occasionally receive messages that have failed backups. Causes YOURSQLDBA Backup to fail the situation compares much, intends in this article to the YOURSQLDBA backup failure case to do some summary, the collation.

1:YOURSQLDBA because the transaction log is full. The details are as follows:

Check the YOURSQLDBA backup failure log information and you will see the following type of error message.

The transaction log for database ' XXXX ' was full. To find out why space in the log cannot is reused, see the Log_reuse_wait_desc column in sys.databases. Error 3013, Severity, Level 1:backup DATABASE is terminating abnormally.

If the above error message appears, first check the properties of the log file for the database to see if it disables the autogrow or maximum file size setting too small. I've come across one of these cases, and found that the log files for the database are autogrow and are not limited in size. Check that the server discovers that the database log is on the same disk as more than 20 g, wondering how the error was generated? Later, after I configured a job to monitor disk alarms, I found that there was not enough disk space to cause this error. Because YOURSQLDBA maintains a database, it rebuilds and reorganizes a subset of the indexes. Causes the log file to explode during that time period. The YOURSQLDBA will truncate and shrink later, so when I go to check it, I don't see enough disk space.

2: Antivirus software causes YOURSQLDBA backup to fail

This case in this blog anti-virus software led to YOURSQLDBA backup failed inside introduced, do not do too much description.

3:backup Log is terminating abnormally backup log interrupted causing the entire job to fail

For specific reference this blog write on ... failed:112 (failed to retrieve text for this error. reason:15105), this case is due to a lack of disk space in the final analysis.

4: UPDATE STATISTICS cause YOURSQLDBA Backup to fail.

Specifically, this case is not a backup failure case, and it is a successful database backup. However, it encountered an error updating statistics, so the entire job report YOURSQLDBA job failed. For specific reference blog message 8134, Level 16, State 1, line 1th encounters a divisor error with zero

In addition, there are one or two cases, the resolution of the time is not recorded, and so on after the encounter, will be added in this article, add.

YOURSQLDBA Backup failure Case Brocade set