机组具有自动停机系统，使用方便。
事务上下文中的写操作会被应用到所有副本，通过恢复时更新，当时宕机的副本也能够被更新。 “这个机制使得多个地理上分开的系统联合提供一个连续运行的不停机系统设计成为可能。”
Write operations apply to all replicas within the context of a transaction, with the ability to update replicas that are not available through updates upon recovery.
现在，目的地是浩瀚的网络世界，电脑行业还表示，快速启动系统就是迎合甚至一时的停机时间也使人焦躁的信息成瘾社会。
Now the destination is the vast world of the Web, and the computer industry says the fast-boot systems cater to an information-addicted society that is agitated by even a moment of downtime.
在非常繁忙的系统中，对这些数据进行广播的需求可能也就意味着永远无法报告这些信息，这些数据可能过期，或者在系统繁忙时将其报告为停机。
In very busy systems, the need to broadcast the data can also mean that the information is never reported, the data can be out of date, or the system could be reported as down when it is just busy.
关于安全补丁的一个重要方面，就是需要根据操作系统来安排停机时间。
An important aspect of security patches is that depending upon the operating system, downtime may need to be scheduled.
这在资源效率方面是有意义的：开发人员可以在正式编码之前，在系统停机时间收集和编写需求。
This makes sense in terms of resource efficiency: Developers can collect and write requirements during their down time, before serious coding begins.
迁移完成后，需要的唯一停机将是一次预定的系统重启。
After the migration is finished, the only downtime required will be a scheduled reboot of the system.
在由于人为或自然事故发生而触发强迫停机期间，这些冗余的、被动的安全系统不需要操作员或者电力的帮助即可工作。
These redundant and passive safety systems work without the help of an operator, or even electricity, during times of duress, be it man-made or natural.
因为这可以在计划内停机期间保持系统正常运行，从而提高可用性。
Because it allows one to increase their availability by keeping systems up during planned outages.
系统管理员甚至操作员(通过WPAR管理员)可以把这些虚拟操作系统分区转移到其他系统，而不需要停机。
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.
如果系统停机(即使很短的时间)，损失会很大，可能会影响业务的生存期。
If the system is down even for a moment, the loss might be substantial and it may affect the lifetime of the business.
与环境相关的硬件故障发生的几率最小，而软件故障和计划停机占整个系统停机时间的70%。
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.
这让系统能够在计划内停机期间正常运行，从而提高系统的可用性。
This increases the availability of systems by allowing the system to keep running during planned outages, without incurring downtime.
它可以将应用程序从需要计划停机以便进行维护的系统中移动到别处。
It moves applications away from systems that require scheduled downtime for maintenance.
需要注意的重要一点是，ISSW或ISSW2系统任何一个发生故障都会导致停机。
It is important to realize that the failure of either the ISSW or ISSW2 systems will cause an outage.
停机和错误会在网络上造成严重破坏，尤其是在许多系统采用相同配置的情况下。
Outages and errors can wreak havoc on a network, especially when many systems are running identical configurations.
在出现LPAR问题的情况下(或计划系统停机)，所有其中的WPAR也将受到影响。
In the event of an LPAR problem (or a scheduled system outage, for that matter), all underlying WPARs will also be affected.
在企业范围内，将这种唯一性的思想扩展到逻辑卷名，这样可以在发生计划内或者计划外停机时，在执行系统故障转移的过程中避免命名冲突。
Extending the unique mentality to logical volume names across the enterprise ensures naming conflicts will be avoided while performing system failovers during planned or unplanned outages.
RationalTestRealTime是为嵌入式和实时系统设计的，它通常都是设置成从不停机的。
Rational Test RealTime is designed for embedded and real-time systems, which are often designed to never stop.
对于低级的攻击，ping流可用于偷偷地查找信息，但是如果要截取向目标发送的包，则要求系统离线或停机。
At the low end, a ping flood can be used to uncover information covertly, but throttle up the packets being sent to a target or victim so that now, the system will go offline or suffer slowdowns.
我们有HACMP集群系统，所以在一个系统进行停机升级时在另一个595上处理生产工作负载。
We had HACMP clustered systems, so production workload was processed on another 595 while this one was down for the upgrade.
设置这些系统还需要一些停机时间或服务器的重新启动，所以您需要提前进行计划。
Setting up these systems also requires some downtime or restarting of the servers, so you will want to plant for it well in advance.
这肯定会增加系统停机时间。
所以转换过程中系统和数据库的总停机时间可能是6个小时。
So total system and database downtime during cutover could be as long as 6 hours.
这将增加系统停机时间。
如果某一个db2子系统停机，或者出于维护的目的暂时离线，那么数据共享组中的其他DB 2子系统就会接管目前离线的数据共享成员的工作负载。
If one DB2 subsystem goes down, or brought off-line for maintenance, other DB2 subsystems in the data sharing group take on the workload of the data sharing member that is now offline.
这种解决方案的总体效果是，不会因为单个或多个系统的故障而造成停机，具有更大的可伸缩性，而且成本更低。
The overall effect of the solution is there is no downtime due to the loss of individual or multiple systems, greater scalability, and lower costs.
这大大减少了系统和数据库停机时间。
这也会增加系统停机时间。
建议在公告的系统停机时间执行这一修改，除非正在运行副本服务器，可以应对在升级期间服务器不可用的问题。
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.
应用推荐