现在，美国人也开始发现一些能够用纸和胶水之类的简单材料解决机器故障的窍门了。
Today, Americans are finding their own tips and tricks for fixing malfunctioning devices with supplies as simple as paper and glue.
解决办法是给旅行者1号发信息，指示它使用备件更换故障部件。
The solution was to get a message to Voyager I to instruct it to use spares to change the failing parts.
本文的目的不是用来解决如何从由于媒介失败而引起的每个单一故障中恢复。
This article is not meant to address how to recover from every single failure due to media failure.
您可以通过分析性能指标来解决诸如故障条件或不可接受的延迟等问题。
You can solve problems like failure conditions or unacceptable latency by analyzing performance metrics.
这名工程师说，这是一个没有得到很好解决的随机故障。
'It was a random failure that was not managed very well,' the engineer said.
这种解决方案的总体效果是，不会因为单个或多个系统的故障而造成停机，具有更大的可伸缩性，而且成本更低。
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.
该解决方案将一个额外的DB 2服务器用作备用服务器，它在主服务器出现故障时接管其工作。
This solution involves using an additional DB2 server as a stand-by that can take over operations when the primary has to go down.
在这种情况下，只需在出故障的分区上重新发出重新启动数据库的命令就可以解决问题。
In this case, just re-issuing the restart database command on the failed partitions will resolve the problem.
通常，关于故障的数据决定解决问题的速度。
This data about a failure often determines how quickly an issue can be resolved.
该故障解决时，留给发现号升空的多余时间仅有数秒。
The problem was resolved with seconds to spare, clearing Discovery for launch.
在演讲中，他详细解释了导致探路者号重启的软件原因，故障如何定位，以及如何解决的。
In his talk, he explained in detail the actual software problems that caused the total system resets of the Pathfinder spacecraft, how they were diagnosed, and how they were solved.
识别、指定和解决常见交换网络的介质问题、配置问题、自动协商和交换硬件故障。
Identify, prescribe, and resolve common switched network media issues, configuration issues, auto negotiation, and switch hardware failures.
故障诊断文档包含有关与每个组件相关的常见问题的信息，以及可采取来尝试快速解决这些常见问题的步骤。
The Troubleshooting document contains information about common problems related to each component and steps you can take to attempt a quick resolution to these common problems.
数据所有权、性能问题及单点故障还有更多普遍的问题都存在于这个解决方案中。
Data ownership, performance problems, and being a single point of failure rank among the more common problems with this solution.
但是，由于传统复制解决方案固有的异步本性，我选择了在故障转移小节描述这个场景。
However, due to the inherent asynchronous nature of traditional replication solutions, I have chosen to describe this scenario in the failover section.
一个构建发生故障时，我希望能够立即知道这一情况，以便就能够采取适当的行动来解决这一问题——不论那是编译错误、测试故障甚或是整体复杂性的增加。
When a build is broken, I want to know immediately so I can take the proper action to fix it — whether that be a compilation error, test failure, or even an increase in overall complexity.
因此当客户报告软件故障时，对于较小的公司来说，回过头来对该问题的解决可能更重要。
So when a customer reports a software bug, the turnaround on resolution of that issue might be comparatively more important for a smaller firm.
在故障检修时，这可能是一个令人迷惑的问题，往往能够通过按字母顺序排列公共属性解决。
This can be a confusing problem to troubleshoot, and it can often be resolved by arranging the public properties into alphabetical order.
本节将解决在用户组和讨论会中频繁出现的两个故障检修主题。
In this section, we address two troubleshooting topics that occur frequently in user groups and conferences.
万一软件或硬件发生故障，一个高可用性解决方案保证系统自动恢复。
A high availability solution guarantees that a system will automatically recover in the event of a software or hardware failure.
由于难于获得和了解故障检修工具和技术，用户(及任何解决这些问题的人)经常陷入困境之中。
What has often made the situation difficult for the customer (and for anyone troubleshooting these problems) is limited access to and understanding of troubleshooting tools and techniques.
更重要的是，也要考虑解决方案的故障恢复需求，并分配额外CPU资源来实现高可用性需求。
More importantly, also consider the failover requirements of the solution and allocate extra CPU power to fulfill your high availability requirements.
您可以部署一个灾难恢复解决方案以使客户在全站故障的不幸情况下仍能继续运行其业务。
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.
高可用性解决方案可以确保解决方案的任何组件的故障都不会导致用户无法使用应用程序及其数据。
A high availability solution can ensure that the failure of any component of the solution does not cause the application and its data to be unavailable to the user community.
的确出现故障时，在故障出现前未写出的数据可能会丢失，并不会因为服务器使用数据库还是DRS持久性解决方案而有所差别。
When a failure does occur, data that has not been written out before the failure occurred might be lost, regardless of whether the server is using database or DRS persistence.
此外，客户可以联系到二十四小时的客户维护代表，他们可以帮助解决用户在使用服务时遇到的小故障或具体问题。
Further, customers have access to around-the-clock customer care representatives who can help with glitches or specific problems users may have while using the service.
故障诊断：此页面是旨在帮助您诊断和解决与每个产品关联的问题的文档集合的前端。
Troubleshoot: This page is the front end for a collection of documents intended to help you diagnose and resolve problems associated with each product.
它指导您完成故障排除流程的所有阶段——从最初的问题症状到最终的解决方案。
It guides you through all phases of the troubleshooting process, starting with the problem symptoms and ending with an implemented solution.
当我向那些还没有使用过这项实践的技术专家们描述CI时，我常常会侧重于它的主要优点之一，即它可以缩短故障出现到故障解决之间的时间。
When I describe CI to technologists that haven't used the practice yet, I tend to focus on one of its major benefits: a decrease in the time between when a defect is introduced and when it is fixed.
虽然这个问题可以解决，但它仍然是出现故障时需要处理的又一个问题。
While it is possible to deal with this, it's still one more thing to deal with during a failure.
应用推荐