When a site failure occurs on the primary site, a failover is invoked so that transactions are run against the database at the target site.
如果在主站点发生站点故障,那么就会调用一个故障转移以便事务可以在目标站点上针对此数据库运行。
Without HADR, a partial site failure requires restarting a server, one or more instances of DB2, and the databases under each instance's control.
如果不使用HADR,在发生部分站点故障时,需要重新启动服务器、一个或多个DB 2实例以及每个实例控制的数据库。
You can deploy a disaster recovery solution to allow customers to continue to run their businesses even in the unfortunate circumstance of a full site failure.
您可以部署一个灾难恢复解决方案以使客户在全站故障的不幸情况下仍能继续运行其业务。
If a complete site failure occurs at the primary site, data availability is maintained by having the remote standby database take over as the primary database.
如果主站点发生全站点事故,远程备用数据库会接替主数据库,从而保持数据可用性。
If the transaction load was heavy at the time the partial site failure occurred, it can take several minutes to restart the instances and the databases affected.
如果在发生部分站点故障时事务负载很重,要花几分钟才能重新启动受影响的实例和数据库。
Tip: You can leverage the DB2 automatic client-reroute feature to automatically reconnect the application across sites once a site failure or reintegration has occurred.
提示:您可以利用DB2的自动客户端重路由特性来在发生站点故障或重新集成时自动地跨站点重新连接应用程序。
By duplicating the workload of the database to a separate site, these features protect users from production downtime in the event of a local hardware failure or a catastrophic site failure.
通过将数据库的工作负载复制到单独的站点上,这些特性使服务在发生本地硬件故障或灾难性站点故障时不会中断。
By duplicating the workload of the database to a separate site, these features protect users from production downtime in the event of a local hardware failure or a catastrophic site failure.
通过将数据库的工作负载复制到单独的站点上,这些特性使服务在发生本地硬件故障或灾难性站点故障时不会中断。
应用推荐