CPU负荷增长尽管(写)事务量没有变写日志个数没有变日志文件同步的往返信号传输时间就会延长。
When the CPU load goes up, the time taken for a log file sync round trip can increase even when the number of log file syncs and the volume of redo log generated doesn't change.
结果就是队列文件的备份与日志文件的备份存在些许的不同步现象，可能会有一个或多个文件被破坏。
This results in the backup of the queue files being slightly out of sync from the backup of the log files, and the possibility that one or more of the files will be corrupted.
为了在备用服务器上保持数据库的一个同步副本，系统会一致地将DB 2HADR日志文件从主要服务器发送到备用服务器来保持二者的同步。
To keep a synchronized copy of the database on the standby server, DB2 HADR log files are consistently sent from the primary to the standby to keep the two in sync.
这些任务包括轮转日志文件以避免装满文件系统、备份数据和连接时间服务器来执行系统时间同步。
These include rotating log files so filesystems do not become full, backing up data, and connecting to a time server to keep your system time synchronized.
用于备份操作(例如，数据库、日志或文件备份)中的内部数据结构同步。
Used for internal data structure synchronization within a backup operation, such as database, log, or file backup.
问题：“为什么我们开始长时间等待log file sync(同步写日志文件)？ ”？
Question: "Why have we started to see such a big increase in log file sync wait time?"
检查点(CKPt)——将数据文件头和控制文件头与当前重做日志和检查点数同步。
Checkpoint (CKPt) - Synchronizes the headers of data files and control files with the current redo log and checkpoint Numbers.
恢复后，如果将事务日志文件播放到恢复的数据库，搜索索引可能变得与数据库不同步。
The search index can become unsynchronized with the database after a recovery if transaction log files are played into the recovered database.
可以弄一个和源数据库一样的备份数据库，通过源数据库生成的归档日志文件，把源数据库里的数据同步到备份数据库中。
You can keep a standby database current with its original database by continuously applying the original archived redo logs to the standby database.
此外，为了解决文件系统的一致性问题，在比较了同步写和原子更新等恢复技术的基础上，结合嵌入式存储的自身特点，提出了日志记录的恢复机制。
In addition, in comparison with synchronous writes and atomic updates, considering embedded storage characteristics, it presents log record recovery mechanism for consistency of the file system.
只读快照则必须保证文件系统在开始快照之前就得和设备同步，因此需要日志重现。
With read-only snapshot you need to make sure filesystem synchronizes device before snapshot is taken so no journal replay is needed.
只读快照则必须保证文件系统在开始快照之前就得和设备同步，因此需要日志重现。
With read-only snapshot you need to make sure filesystem synchronizes device before snapshot is taken so no journal replay is needed.
应用推荐