Unique backup object names for logical logs
逻辑日志的惟一备份对象名称
These types of restores rely on the information in the logical logs.
这些类型的还原依赖于逻辑日志中的信息。
The second half provides the status information of the logical logs.
下半部分提供逻辑日志的状态信息。
The Number column indicates the number of logical logs sequentially.
Number列显示逻辑日志的编号。
Figure 52 shows a report generated to get more information about logical logs.
图52显示一个关于逻辑日志的报告。
Repeat steps 3 and 4 for all logical logs that are available to back up and restore.
对于可用的所有逻辑日志,重复步骤3和4,进行备份和恢复。
The primary server will not know that logical logs are staged at RS secondary server.
主要服务器将不会知道逻辑日志暂存在RS次要服务器上。
The backup of the logical logs is configured with the Informix ALARMPROGRAM mechanism.
logical logs备份是使用InformixALARMPROGRAM机制配置的。
During external backup, logical logs coming from primary are staged at RS secondary server.
在执行外部备份期间,来自主要服务器的逻辑日志暂存于RS次要服务器上。
The RS secondary server continues to receive logical logs from the primary but does not apply them.
RS次要服务器继续从主要服务器接收逻辑日志,但不会应用它们。
Without logical logs, the system is restored to a consistent point, which is the archive checkpoint.
如果没有逻辑日志,则系统被还原到某个一致的点上,即归档检查点。
This process might take a few minutes because the physical log and the logical logs will be cleared.
这个过程可能要花费几分钟的时间,因为要清除物理日志和逻辑日志。
IDS will be in online mode after the physical log and the logical logs have been completely cleared.
物理日志和逻辑日志完全清除之后,IDS将处于在线模式。
The logical logs TAB provides you with information on states and statistics of all the logical logs.
Logical Logs选项卡提供有关所有逻辑日志的状态和统计数据的信息。
After the physical restore completes, the database instance waits in fast recovery mode to restore logical logs.
在物理恢复完成之后,数据库实例处于快速恢复模式,等待恢复逻辑日志。
IDS stores information about each backup operation (dbspaces and logical logs) in a database called sysutils.
IDS在称为sysutils的数据库中存储关于每种备份操作(dbspaces和logical logs备份)的信息。
The logical logs could be still backed up by the ALARMPROGRAM while the special quarterly Level-0-Backup is running.
在运行每季度的0级备份时,逻辑日志仍然可以由ALARMPROGRAM备份。
Currently, the IDS CDC API supports capturing transactional data from current logs but not from archived logical logs.
当前,IDSCDCAPI支持从当前日志捕捉事务数据,但是不支持从存档的逻辑日志捕捉数据。
Consider increasing logical logs to account for the additional fragment-level statistics rows in the sysfragdist catalog.
考虑增加逻辑日志来存放sysfragdist目录中额外的片段级统计行。
After the RS secondary server is blocked, the logical logs coming from the primary server are staged at the RS secondary server.
当RS次要服务器阻塞之后,来自主要服务器的逻辑日志暂存于RS次要服务器上。
When you look for the customer table within 5 minutes, you see that the logical logs will not be applied on the RS secondary node.
当您在5分钟内查找customer表时,会发现RS次要节点上并未应用逻辑日志。
SDS or HDR secondary node can take over primary, and RS secondary server continues to receive logical logs from new primary server.
SDS或HDR次要节点可以接管主要服务器,而RS 次要服务器继续从新的主要服务器接收逻辑日志。
Whole-system backups are performed sequentially (dbspace after dbspace) and they can be restored without applying any logical logs.
全系统备份是连续执行的(一个dbspace备份完成后接着另一个dbspace备份),并且可以不使用任何逻辑日志来还原它们。
A backup in IDS is a copy of one or more dbspaces, blobspaces, spspaces, and logical logs and physical logs of an Informix instance.
IDS中的备份复制了一个或多个dbspace、blobspace、spspace和Informix实例的逻辑日志和物理日志。
Use the onmode utility as follows to set DELAY_APPLY to 5 minutes, delaying the applying of logical logs at RS secondary server by 5 minutes.
使用onmode实用工具将delay_apply设为5分钟,从而将RS次要服务器上的逻辑日志应用延迟5分钟,如下所示。
A cold restore has to be done if any of the critical dbspaces (such as root dbspace, dbspaces containing the logical logs, or the physical log) is down.
如果任何关键dbspaces(比如根dbspace,这些dbspace包含逻辑日志或物理日志)出错,则必须执行冷还原。
The problem that will appear in that case is that you will have some logical logs stored under the normal nodename and others under the dedicated nodename.
这种情况下将出现的问题是,有些逻辑日志存储在一般节点名下,另一些逻辑日志又存储在专用节点名下。
ER works by reading the logical logs, testing if a log record needs to be replicated, and finally sending that information to the appropriate participants.
ER首先读取逻辑日志,检验日志记录是否需要复制,最后将这些信息发送给相应的参与节点。
The consequence of this naming convention is that logical logs will never expire because they have always a unique name and thus will never become inactive.
采用这种命名惯例的结果是,逻辑日志永远不会到期,因为它们总有一个惟一的名称,因而绝不会进入不活动状态。
It is essential that you ensure your logical logs will be backed up regularly if you plan to do parallel backups or want be able to perform point-in-time restores.
如果计划执行并行备份或者希望能够执行指定到某一时间点的还原,则确保定期备份逻辑日志就非常重要。
应用推荐