MSSQL 2005 Backup or its related Error Messages
Severity level 10 messages are informational and indicate problems caused by mistakes in the information you have entered. Severity levels from 11 through 16 are generated by the user, and can be corrected by the user.
Severity levels from 17 through 25 indicate software or hardware errors (Please find the below update error messages).
We have to inform the system administrator whenever problems that generate errors with severity levels 17 and higher than it. The system administrator must resolve these errors and track their frequency. When a level 17, 18, or 19 errors occur, we can continue working, although we might not be able to execute a particular statement.
Error Messages
select message_id, severity, [text] from sys.messages where language_id = 1033 and severity <> 10 and [text] like ‘%backup%’
Msg IdSeverityError Message
2062211Replication database option -sync with backup- cannot be set on the publishing database because the database is in Simple Recovery mode_
141116The remote copy of database -_*ls has not had enough log backups applied to roll forward all of its files to a common point in time_
147516Database mirroring cannot be enabled because the -_*ls database may have bulk logged changes that have not been backed up_ The last log backup on the principal must be restored on the mirror_
147816The mirror database, -_*ls, has insufficient transaction log data to preserve the log backup chain of the principal database_ This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database_
183316File _ls- cannot be reused until after the next BACKUP LOG operation_
193116The SQL statement cannot be executed because filegroup __*ls- is offline_ Use the sys_database_files or sys_master_files catalog view to determine the state of the files in this filegroup and then restore the offline file(s) from backup_
250516The device __*ls- does not exist_ Use sys_backup_devices to show available devices_
251516Page -S_PGID, object ID -d, index ID -d, partition ID -I64d, alloc unit ID -I64d type -_*ls) has been modified but is not marked modified in the differential backup bitmap_
251616Repair has invalidated the differential bitmap for database -_*ls_ The differential backup chain is broken_ You must perform a full database backup before you can perform a differential backup_
251716Bulk-logging has been turned on for database -_*ls_ To ensure that all data has been secured, run backup log operations again_
300216Cannot BACKUP or RESTORE a database snapshot_
300416The primary filegroup cannot be backed up as a file backup because the database is using the SIMPLE recovery model_ Consider taking a partial backup by specifying READ_WRITE_FILEGROUPS_
300616The differential backup is not allowed because it would be based on more than one base backup_ Multi-based differential backups are not allowed in the simple recovery model, and are never allowed for partial differential backups_
300716The backup of the file or filegroup -ls is not permitted because it is not online_ BACKUP can be performed by using the FILEGROUP or FILE clauses to restrict the selection to include only online data_
300816The specified device type is not supported for backup mirroring_
300916Could not insert a backup or restore history/detail record in the msdb database_ This may indicate a problem with the msdb database_ The backup/restore operation was still successful_
301016Invalid backup mirror specification_ All mirrors must have the same number of members_
301116All backup devices must be of the same general class (for example, DISK and TAPE)_
301616Backup of file _ls- is not permitted because it contains pages subject to an online restore sequence_ Complete the restore sequence before taking the backup, or restrict the backup to exclude this file_
302116Cannot perform a backup or restore operation within a transaction_
302316Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on a database must be serialized_ Reissue the statement after the current backup or file manipulation operation is completed_
302416You can only perform a full backup of the master database_ Use BACKUP DATABASE to back up the entire master database_
303316BACKUP DATABASE cannot be used on a database opened in emergency mode_
303516Cannot perform a differential backup for database -ls, because a current database backup does not exist_ Perform a full database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option_
303816The file name -ls is invalid as a backup device name_ Reissue the BACKUP statement with a valid file name_
303916Cannot perform a differential backup for file _ls- because a current file backup does not exist_ Reissue BACKUP DATABASE omitting the WITH DIFFERENTIAL option_
304116BACKUP failed to complete the command -_*ls_ Check the backup application log for detailed messages_
304316BACKUP _ls- detected an error on page (-d:-d) in file _ls-_
304416Invalid zero-length device name_ Reissue the BACKUP statement with a valid device name_
304516Differential BACKUP or RESTORE is not supported on the FAT file system_ The path -_*ls is not usable_
304616Inconsistent metadata has been encountered_ The only possible backup operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR or NO_TRUNCATE option_
304716The BackupDirectory registry key is not configured correctly_ This key should specify the root path where disk backup files are stored when full path names are not provided_ This path is also used to locate restart checkpoint files for RESTORE_
304816BACKUP LOG WITH TRUNCATE_ONLY cannot operate on database _ls- because it is configured for database mirroring_
304916BACKUP detected corruption in the database log_ Check the errorlog for more information_
305016SQL Server could not send the differential information for database file _ls
No comments:
Post a Comment