结尾日志备份（End log backups）.doc

结尾日志备份（End log backups） End log backups This topic is only relevant to databases that use a full recovery model or a bulk logged recovery model. For the most part, SQL Server 2005 and later require you to back up the journal end to capture logging that has not been backed up in either full recovery mode or bulk log recovery mode. The log backup that is executed for the tail of the log before the restore operation is called the end log backup. SQL Server 2005 and later usually require you to execute the end log backups before you begin to restore the database. The end log backups prevent loss of work and ensure integrity of the log chain. When the database is restored to the point of failure, the end of the log backup is the last relevant backup in the recovery plan. If you cannot backup the tail of the log, you can only restore the database to the last backup created before the failure. Not all restore scenarios require the execution of the end log backups. If the recovery point contains previously log backups, or you are ready to move or replace (cover) database, and in the latest backup after the database does not need to be recovered to a point in time, there is no need to use at the end of the log backup. Also, if the log file is damaged and cannot create an end log backup, you must restore the database without using the end log backups. Any transaction submitted will be lost after the latest log backup. For more information, see the following topic in this topic: do not use the end log backup to perform the restore operation. Backup log tail The ending log backup is similar to any other log backups, using the BACKUP LOG statement. It is recommended that you execute an end log backup in the following circumstances: If the database is online, whenever you are ready to restore the next operation to the database, use the WITH NORECOVERY backup log tail before you start the restore sequence: BACKUP LOG database name TO backup device WITH NORECOVERY Be careful： To