高级的“混合介质”备份管理器。
万一要从备份中恢复队列管理器，对所有那些应用程序的影响在最好的情况下也是不可预测的。
If the queue manager is ever restored from the backup, the impact to all those applications is unpredictable at best.
下面的说明需要使用部署管理器的稳定状态备份。
The instructions below require a stable state backup of the deployment manager.
停止备份节点上的队列管理器。
许多企业都在队列管理器运行时进行文件系统备份。
Many shops take that filesystem backup while the queue manager is running.
创建一个修改后的部署管理器启动脚本，用于使用备份节点维护的配置。
Creates a modified deployment manager startup script for use with the configuration maintained with the backup node.
选择部署管理器配置的稳定备份。
Select a stable backup of the deployment manager configuration.
正如我们前面提到的，部署管理器的稳定状态备份是执行托管节点回滚所必需的。
As mentioned, a stable state backup of the deployment manager is required to perform a managed node rollback.
备份策略：我看到过的大多数最佳实践文档，包括关于该主题的IBM红皮书，都建议备份队列管理器下的文件。
Backup strategy: Most of the best practice documents I have seen, including the IBM Redbook on the subject, recommend backing up the files under the queue manager.
虽然由于备份集不可用而导致队列管理器恢复失败的情况不常发生，但是我还是看到过几次这样的情况。
It doesn't happen often, but I have seen several occasions where a restore of a queue manager failed because the backup set was unusable.
此系统的一个主要优点是，在使用备份系统时，对部署管理器的主存储库所做的任何更改都会被提交。
One major advantage of this system is that any changes made to the deployment manager's master repository while using the backup system are committed.
虽然停止部署管理器来防止在运行备份时发生修改是个好主意，但是这个操作是没有必要的。
While it is a good idea stop the deployment manager to prevent changes from being made while the backup is running, this action is not necessary.
要将此节点设置为备份，您需要自动复制部署管理器的计算单元范围的配置。
To set up this node as a backup, you need to automatically replicate the deployment manager's cell-wide configuration.
对部署管理器配置进行备份。
不过，不能将备份并行化，并且没有直接到存储管理器的接口。
However, you are not able to parallelize your backups and there is no direct interface to a storage manager.
当某个节点与部署管理器联合时，首先备份基本节点的配置，然后替换为包含节点代理的新配置。
When a node is federated with a deployment manager, the base node's configuration is first backed up, then replaced with a new configuration containing the node agent.
恢复备份的版本 5 的部署管理器配置。
从部署管理器删除节点时，将恢复在联合节点时备份的配置。
When a node is removed from the deployment manager, the configuration that was backed up when it was federated is restored.
要让部署管理器位于备份系统(10.0.0.6)上，我们需要设置所谓的多主dns项。
To enable the deployment manager to be located on the backup system (10.0.0.6) we need to set up what's called a multi-home DNS entry.
提到备份队列管理器，存在两种学派。
When it comes to backing up the queue manager, there are two schools of thought.
恢复您在步骤8中备份的部署管理器配置。
Restore the deployment manager configuration you backed up in Step 8.
本节主要关注从备份文件中恢复部署管理器的配置。
This section focuses on restoring the configuration of the deployment manager from the back up file.
在备份节点(ha2)上，以用户mqm身份创建队列管理器。
On the backup node (ha2), create the queue manager as user MQM.
在文件系统级备份WebSphereMQ时，备份包含当时队列管理器上存在的所有消息。
When WebSphere MQ is backed up at the filesystem level, the backup contains any messages that happened to be on the queue manager at that point in time.
在备份节点上，使用strmqm命令启动队列管理器 ha.queue.manager。
Start the queue manager, ha.queue.manager, using the strmqm command, on the backup node.
然而，如果要备份您的cell配置，您应当从部署管理器概要文件中运行它。
For the purpose of backing up your cell configuration, however, you should run it from the deployment manager profile. The execution of the script is shown below.
在备份服务器上启动部署管理器。
通过将整个配置树从实际的部署管理器节点复制到另一个应用服务器节点，部署管理器可以在备份节点上快速重启。
By replicating the entire configuration tree from the actual deployment manager node to another application server node, the deployment manager can be quickly restarted on the backup node.
部署管理器必须具有单元中所有节点的全部信息，因此备份目录必须来自于V5部署管理器节点。
The deployment manager must have complete information for all nodes in the cell, so the backup directory must come from the V5 deployment manager node.
当您进行备份后，将其副本放到一个高度可用的文件系统中；否则，部署管理器服务器出现磁盘故障会使这些备份变得不可用。
When you have the backup, place a copy of it in a highly available file system; otherwise, a disk outage on your deployment manager server could make the backups unavailable to you.
应用推荐