它满足性能和故障转移时间要求吗？
因此，您将使用并发访问以获得更快的故障转移时间。
Therefore, you should use concurrent access for faster failover time.
为了使故障转移时间更快，要调优这些DB 2UDB配置设置。
For faster failover times, these are the DB2 UDB configuration Settings to tune.
我们还可以对原始磁盘进行 并发访问，甚至可以进一步减少故障转移时间。
We can also have the concurrent access on for the raw disks, and that even further reduces failover time.
我们成功达到了此POC的目标，因为大多数情况下所测的故障转移时间约为60秒。
We succeeded in achieving the goal of this POC because the measured failover time was approximately 60 seconds in most cases.
为了获得更快的故障转移时间，最佳配置是使用dms表空间和原始设备，甚至最好允许对磁盘的并发访问。
For faster failover time the best configuration is to use DMS tablespaces and raw devices, and even better allow concurrent access to the disks.
我们需要测试性能、可靠性、稳定性，并需要取得最快的故障转移时间，其目标故障转移时间要少于60秒。
We wanted to test for performance, reliability, stability and the requirement to achieve the fastest failover time with a target failover time below 60 seconds.
通过数据库管理的空间(DMS)和原始设备，我们可以减少磁盘资源的故障转移时间，因为在故障转移时将不会进行磁盘检查。
With database managed space (DMS) and raw device, we can decrease the time to fail over the disk resources, because there will be no checking of disks during failover.
如果数据库很大，那原始设备的使用也能减少故障转移时间，因为进行故障转移时，操作系统不必对文件系统进行文件检查(fsck)。
Raw device usage also improves failover time in case the database is large, because during failover the operating system does not have to do a file check to the file system (FSCK).
如果数据库很大，那原始设备的使用也能减少故障转移时间，因为进行故障转移时，操作系统不必对文件系统进行文件检查(fsck)。
Raw device usage also improves failover time in case the database is large, because during failover the operating system does not have to do a file check to the file system (FSCK).
应用推荐