This would add to the system downtime.
这将增加系统停机时间。
This will also add to system downtime.
这也会增加系统停机时间。
This will certainly add to system downtime.
这肯定会增加系统停机时间。
Again, if your customer satisfaction is mainly based on system downtime.
再次强调，这里假设您的客户满意度主要是基于系统停机时间。
This will eventually improve customer satisfaction if it is based on system downtime.
如果是基于系统死机时间，这将最终提高客户满意度。
This is why some customer sites which have a very low tolerance for unscheduled system downtime will often choose this option.
这也是一些对于事先未安排的系统宕机有很差容度的服务站点会选择这种操作的原因。
It allows an administrator to perform hardware maintenance, such as disruptive firmware updates, without requiring system downtime.
这使管理员能够在不停止系统的情况下执行硬件维护，比如更换损坏的固件。
The environmentally-related and hardware failures are the least likely to happen, whereas software failures and planned downtime contribute up to 70% of system downtime.
与环境相关的硬件故障发生的几率最小，而软件故障和计划停机占整个系统停机时间的70%。
It is advisable to execute this change during announced system downtime, unless you have the replica server running to take care of the unavailability of the server being upgraded.
建议在公告的系统停机时间执行这一修改，除非正在运行副本服务器，可以应对在升级期间服务器不可用的问题。
And operational downtime caused by reliability or performance problems can incur opportunity costs if customers are unable to access your system or the business is unable to do its work.
并且如果顾客不能访问你的系统或业务不能进行工作，那么由可靠性或性能问题引起的运作停工就会招致机会成本。
So total system and database downtime during cutover could be as long as 6 hours.
所以转换过程中系统和数据库的总停机时间可能是6个小时。
This increases the availability of systems by allowing the system to keep running during planned outages, without incurring downtime.
这让系统能够在计划内停机期间正常运行，从而提高系统的可用性。
This greatly reduces the system and database downtime.
这大大减少了系统和数据库停机时间。
High availability systems combine software with industry-standard hardware to minimize downtime by quickly restoring services when a system, component, or application fails.
高可用性系统将软件和工业标准硬件相结合，在系统、组件或应用程序发生故障时快速恢复来使停机时间最小化。
Long system and database downtime.
系统和数据库停机时间长。
A system is highly available when it achieves no unwanted downtime.
当系统没有不需要的停机时间时它具有高可用性。
After the migration is finished, the only downtime required will be a scheduled reboot of the system.
迁移完成后，需要的唯一停机将是一次预定的系统重启。
This reduces system and database downtime.
这减少了系统和数据库停机时间。
While it has several purposes, it is best used when performing scheduling outages, which allows for system maintenance to occur with no downtime.
虽然它有多种用途，但在执行计划停机时使用它是最合适的，它允许在不中断服务的情况下进行系统的维护。
System-wide startup files are also used to name printers, display bulletins about planned downtime, and provide new users with reasonable shell defaults.
系统范围的启动文件也可用于命名打印机，显示关于计划停机的公告，并为新用户提供合理的Shell缺省值。
This new cutover process is suspected to significantly cut down on total system and database downtime, but there are two concerns.
这个新的转换过程被认为可以显著减少系统和数据库总的停机时间，但是有两点需要考虑。
Those new features on ontape are very helpful; we can use this new feature in our cutover process to reduce chances of Informix errors and to reduce system or Informix downtime.
ontape 中的那些新功能非常有帮助；我们可以在转换过程中使用此新功能以减少出现Informix错误的机会和减少系统或 Informix停机时间。
Live Partition Mobility has enormous potential for dramatically reducing scheduled downtime for system maintenance activities.
LivePartitionMobility可以显著降低计划内系统维护活动的停机时间。
It does this by allowing either the systems administrator or even operators (through WPAR manager) to move these virtual operating system partitions to other systems, without incurring any downtime.
系统管理员甚至操作员(通过WPAR管理员)可以把这些虚拟操作系统分区转移到其他系统，而不需要停机。
An important aspect of security patches is that depending upon the operating system, downtime may need to be scheduled.
关于安全补丁的一个重要方面，就是需要根据操作系统来安排停机时间。
In addition to new features for managing database time, DB2 9.7 also helps administrators minimize downtime by making it possible to move database schemas without taking the system down.
除了管理数据库时间的新特性之外，DB2 9.7还支持在不停止运行系统的情况下转移数据库模式，这可以帮助管理员减少停机时间。
This downtime could be anywhere from 30-45 minutes to several hours, depending on the system.
根据系统的不同，停用时间从30 -45分钟到几小时不等。
A highly available system reliably provides an acceptable level of service with minimal downtime.
一个高可用性系统以最短的停机时间，可靠地提供了可接受级别的服务。
This mode of data center there are certain business continuity risk - that is, if a memory failure downtime, and all the storage system will connect the business system halt, even loss of data.
这种模式的数据中心存在着一定的业务连续性风险——即如果一台存储出现故障宕机，所有与这台存储系统有连接的业务系统就会停顿，甚至会丢失数据。
Meanwhile, downtime remains costly for businesses of any size, and you don't have to manage a huge enterprise to see the benefits of System Center.
同时，停机时间保持任何的大小的企业的成本，并且必须不管理一个巨大的企业若要查看系统中心的好处。
应用推荐