当某个ap处于这一状态时，AP就不能成为任意活动或备用应用程序(如rcs)的宿主。
While an ap is in this state, the ap cannot be a host to any Active or Standby applications, such as RCS.
下面的例子说明了如何在远处备用次要服务器上延迟应用日志文件。
The following examples show how you would delay applying the log files on the remote standby secondary server.
应选择防止复制向备用表应用存储冲突的数据的选项，防止新数据(假设新数据更好)被旧数据覆盖。
Choosing the option that prevents replication from applying the conflicted data to the standby table, prevents newer data (assumed to be better) from being overwritten by older data.
如果愿意，您可以按IP地址或主机名列出多个LDAP服务器副本，并且应用服务器将在主服务器失败时自动切换到备用服务器。
If you wish, you can list multiple LDAP server replicas by IP address or hostname, and the application servers will automatically failover to one of the backup servers if the primary fails.
在备用数据库上生成的日志文件不能应用于源数据库。
The log files generated on the standby database cannot be applied on the source database.
而用户应用程序必须重新建立到这个被激活的备用数据库的连接。
The user applications will have to make new connections to this activated standby database.
在复制了滞留的数据之后，即可在主系统上启动应用程序，将备用数据发送到主系统。
When the stranded data is replicated, the standby data can be sent to the primary by starting the apply program on the primary system.
如果一个备用源没有在本地公开相同的接口，那么您可以对这个源应用转换模式，然而对这个模式的讨论超出了本文的范围。
If an alternate source doesn't natively expose the same interface, you can apply a transform pattern to the source; however, this pattern is out of this article's scope.
在11.1中，备用服务器只允许应用程序读取数据。
In 11.1, the secondary servers only allowed applications to read data.
现在可以创建备用磁盘，然后将TL更新应用到这个磁盘上。
Now create the alternate disk and apply the TL update to it.
为了使备用数据库尽可能最新，应该不断地将源数据库上可用的非活动日志文件应用到备用数据库上。
In order to keep the standby database as current as possible, new inactive log files from the source database should be continually applied on the standby database as they become available.
移动设备用户界面/移动设备上的web应用和widget应用
两个站点均运行日志捕捉和应用程序，但在这个经过简化的场景中，数据仅进行单向复制，即从主站点复制到备用站点。
Running at both sites are log-capture and apply programs, but in this simplified scenario, data is only replicating one way — from primary to standby.
复制将在更新后的应用程序到达备用系统时立即开始排队更改后的数据，以备恢复主站点。
Replication will begin queuing changed data for return of the primary site as soon as the updated apps hit the standby system.
要避免这种中断，可以在该集群内的另一个队列管理器上定义该队列，这样，当您迁移一个队列管理器时，应用程序就可以使用备用队列。
You can avoid these outages by defining the queue on other queue managers in the cluster, so that whilst migrating one queue manager, applications can use the alternate queues.
在应用程序重新尝试连接之后，它应获得一个到备用数据库的新连接。
Once the application retries, it should obtain a new connection to the standby database.
XM使用与这相同的规则，应用它自己的缺省样式表，而不考虑备用样式表。
XM uses the same rules and applies its own default style sheet instead of considering alternate style sheets.
典型示例是灾难恢复测试，其中涉及故障转移到热备用系统、测试应用程序，然后退回到主系统。
The classic example is a disaster recovery test, which involves failing over to a warm standby system, testing the applications, and then failing back to the primary systems.
随后，应用程序就知道要转换到备用服务器。
The application then knows to switch to the secondary server.
设置了一个故障转移连接，用于将更新的应用程序自动从主站点切换到备用站点。
A fail-over connection is set up for automatic switchover of updating apps from primary to standby.
在主站点发生中断时，应用程序将自动切换到备用站点，但如果您愿意，也可采用手动流程。
When an outage occurs at the primary site, the apps switch automatically to the standby site although a manual process is available if preferred.
选择客户端主机(将要更新的服务器)，输入将要应用tl的磁盘—因为它将会成为一个备用磁盘，要保证这个磁盘没有被任何其他卷组(VG)使用。
Select the client machine (server to be updated), type the disk which the TL will be applied-since this is going to be a alternate disk, make sure the disk is not used by any other volume group (VG).
单元素模式可以确保应用程序通常只使用类的单个实例，但是仍然允许根据需要创建备用实例。
The singleton pattern ensures that only a single instance of a class is normally used by an application, but still allows alternate instances to be created as required.
应用程序可移回主系统，但最好等到应用程序首先完成备用系统的积压工作再移动。
Apps can be moved back to the primary, but it is best to wait until the apply program gets through the standby's backlog first.
当某个活动队列管理器失败或变得不可用时，JMS应用程序会自动重新连接到备用网关队列管理器。
Automatic reconnect for JMS applications to a standby gateway queue manager when an active queue manager fails or becomes unavailable.
在主数据库遭遇中断的应用程序不会将该问题暴露给终端用户，而是切换至备用服务器并重新发出连接。
Applications that encounter an outage at the primary database don't expose this problem to the end-user; rather, the application will switch to a cataloged secondary server and issue a reconnect.
在执行故障转移(failover)操作之后，AutomaticClientReroute这个DB 2特性立即把客户机应用程序从主数据库重定向到备用数据库。
Automatic client Reroute is a DB2 feature that redirects client applications from the primary database to the standby database immediately after a failover operation is performed.
对于1 -safe设置，事务在主服务器上提交后，控制权立即回到应用程序。复制到备用服务器的操作是异步进行的。
With the 1-safe setting, control returns to the application immediately after a transaction is committed on the primary server; replication to secondary server is done asynchronously.
我前面承诺过在这个应用程序里会用到少许的Linq代码，因此我准备用Linq来生成一个报告。
I promised there would be a little Linq code in this application, so I'm going to use Linq to generate a report for me.
对于2 -safe设置，只有当事务在主服务器和备用服务器上都提交之后，控制权才回到应用程序。
With the 2-safe setting, control returns to the application only after the transaction is committed on both the primary and secondary servers.
应用推荐