log backup 中文意思是什麼
log backup
解釋
日誌備份-
Log sequence number of the most recent log backup
最新的日誌備份的日誌序列號。 -
Is reusable only after the next log backup
必須在進行日誌備份后,才可以使名稱( -
Of the next log backup restored must match this value
還原的下一個日誌備份的 -
If the database is offline and does not start. try to take a tail - log backup. because no transactions can occur at this time, using with norecovery is optional
如果數據庫包含要備份的、在記錄間隔期間執行的大容量日誌更改,則僅在所有數據文件都存在且未損壞的情況下,尾日誌備份才會成功。 -
A tail - log backup is taken after a failure in order to prevent work loss and can contain either pure log or bulk log data
在發生故障后提取尾日誌備份,以防止工作丟失,該備份中可以包含純日誌數據也可以包含批量日誌數據。 -
Typically, a copy - only log backup is used once and then deleted. when used with backup database, the copy only option creates a full backup that cannot serve as a differential base
如果未指定物理塊大小,則還原時需使用已緩存的i / o ,這將導致效率降低(尤其對于大型備份) 。 -
Added discussion of how a log backup is constructed
添加了有關日誌備份構造方式的討論。 -
The following illustration shows how a log backup is constructed
下圖闡釋了日誌備份的構造方式。 -
Norecovery takes the database into the restoring state. this guarantees that the database does not change after the tail - log backup. the log is truncated unless the no truncate option or copy only option is also specified,
當需要對某個文件執行離線還原以便與數據庫匹配時,或按照計劃故障轉移到日誌傳送備用服務器並希望切換回來時,會用到此操作。 -
If a transaction log backup in this log chain is lost or damaged, you can restore only transaction logs before the missing transaction log
如果此事務日誌鏈中的事務日誌備份丟失或損壞,則您只能還原丟失的事務日誌之前的事務日誌。 -
The copy - only log backup has no effect on the log chain, and other log backups behave as if the copy - only backup does not exist. for more information, see
在進行完整數據庫備份或差異備份時, sql server會備份足夠的事務日誌,確保還原數據庫時生成一個一致的數據庫。 -
Full - text index modified after transaction log backup
>對事務日誌進行備份后全文索引被修改 -
If the next backup is a log backup, use the
如果下一個備份是日誌備份,請使用 -
Then take a log backup from the production database
然後從生產數據庫進行日誌備份。 -
Norecovery is useful when failing over to a secondary database or when saving the tail of the log before a restore operation. to perform a best - effort log backup that skips log truncation and then take the database into the restoring state atomically, use the no truncate and norecovery options together
在完整恢復模式或大容量日誌恢復模式下,使用文件和文件組備份恢復數據庫時,還需要從一個或多個日誌備份(使用backup log創建)中還原事務日誌。 -
If the tail - log backup succeeds, you can avoid any work loss by restoring the database up to the point of failure
如果尾日誌備份成功,則可以通過將數據庫還原到故障點來避免任何工作丟失。 -
Sql server 2005 usually requires that you take a tail - log backup before you start to restore a database. the tail - log backup prevents work loss and keeps the log chain intact
除非restore語句包含with replace或with stopat子句,否則,還原數據庫而不先備份日誌尾部將導致錯誤。 -
Before you can create the first log backup, you must create a full backup, such as a database backup or the first in a set of file backups
在失敗后創建尾日誌備份可以防止工作損失,並且,尾日誌備份可以包含純日誌或大容量日誌數據。 -
However, sometimes a transaction log backup is larger than a full backup
不過,有時事務日誌備份要比完全備份還大。 -
Is a special - purpose full backup or log backup that is independent of the normal sequence of conventional backups
Sql server 2005引入了對于創建僅復制備份的支持,此備份不影響正常的備份序列。
分享友人