您要查找的是不是:
- Access to a recovery log is only performed when the exclusive lock is held. 对恢复日志的访问只有在持有排它锁定时进行。
- File locking is used to ensure exclusive access to the files that make up a recovery log. 使用文件锁定确保对组成恢复日志的文件的排它访问。
- Adding more than one server causes recovery log contention as both servers attempt to process recovery. 添加两个服务器将导致服务器争用恢复日志,因为两个服务器都试图处理恢复。
- To ensure that a failed server reclaims its recovery log when it restarts, and optionally enter a free-form description. 确保发生故障的服务器在重启后能收回其恢复日志,并随意输入自由格式的描述。
- In the case of the transaction service, the transaction HA policy provides the logic to determine which servers own a recovery log at any given time. 在事务服务场景中,事务HA策略提供逻辑以确定在规定时间内是哪台服务器拥有恢复日志。
- The policy essentially provides the logic for determining updated recovery log ownership in the event of a server failure. 在服务器发生故障后,该策略提供逻辑确定更新的恢复日志持有权。
- If transactional high availability is not in use, no requirement exists to specify the transactions recovery log directory. 如果没有使用事务的高可用性,无需指定事务恢复日志目录。
- Although these conditions are rare, left unchecked they have the potential to cause recovery log collision and consequent loss of data integrity. 虽然这些情形不常见,但是却有导致恢复日志冲突且随之损失数据的完整性的潜在危险。
- Log Manager, together with Checkpoint Manager, ensures that the recovery log on the quorum resource contains the most recent configuration data and change checkpoints. 日志管理器与检查点管理器一起确保仲裁资源上的恢复日志中包含最新的配置数据和更改检查点。
- To prevent such problems from occurring, WebSphere Application Server uses network file locking technology to ensure exclusive access to recovery log files. 要避免这样的危险发生,WebSphere Application Server使用网络文件锁定技术来确保对恢复日志文件的排它访问。
- This policy is a One-of-N type policy which provides automated peer recovery processing support such that only one server owns the recovery log at any time. 该策略是One-of-N类型策略,提供自动对等恢复处理支持确保任何时候都只有一台服务器持有恢复日志。
- Apart from enabling high availability and configuring the recovery log location for each cluster member, no additional WebSphere Application Server configuration steps are required to use this model. 除了对每个群成员启用高可用性和设定恢复日志所处位置外,使用该模式无需额外的WebSphere Application Server配置步骤。
- Adding two servers causes recovery log contention as both servers attempt to own the associated recovery logs. 添加两台服务器将导致争用相关联的恢复日志。
- Log truncation frees any virtual logs whose records all appear in front of the minimum recovery log sequence number (MinLSN). 日志截断将释放记录全部在最小恢复日志序列号(MinLSN)之前出现的所有虚拟日志。
- For application servers to perform peer recovery for each other, it is necessary for them to access the recovery logs. 要使服务器之间能执行对等恢复,服务器必须可对恢复日志进行修改。
- Consequently, a peer recovery process must not run and access the associated recovery logs if the original server is still running. 因此,如果初始服务器仍在运行时,则不能运行对等恢复处理以及访问相关的恢复日志。
- Adding a different server prevents the home server from owning its recovery logs and stops the home server from starting correctly. 添加不同的服务器将阻碍主服务器收回恢复日志,且主服务器不能正确启动。
- The list of static group servers can be thought of as the set of servers that attempts to own the recovery logs at the same time. 在静态组服务器清单上,列出的都是在同时间试图持有恢复日志的服务器。
- The quorum disk resource stores the most current version of the cluster configuration database in the form of recovery logs and registry checkpoint files. 仲裁磁盘资源以恢复日志和注册表检查点文件的形式存储群集配置数据库的最新版本。
- This requirement applies to peer recovery processing only; standard recovery processing of server recovery logs, driven when the server starts, still occurs automatically. 该要求只运用于对等恢复处理;服务器恢复日志的标准恢复处理在服务器开启后,仍将自动运行。