As far as Resource Manager and Library Server databases are concerned, once you have a baseline backup and all logs are intact, there is a guarantee that there will be no loss of data.
只要涉及到资源管理器和库服务器数据库，一旦有了一次原始备份，并且所有日志均完好无损，即可保证不损失任何数据。
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.
通过将整个配置树从实际的部署管理器节点复制到另一个应用服务器节点，部署管理器可以在备份节点上快速重启。
After reverting to a backup in this manner, remember to issue a REFRESH cluster command on the restored queue manager to ensure that it has up-to-date information about the cluster.
用这种方法返回一个备份后，记得在恢复后的队列管理器上发出一个REFRESHCLUSTER命令，以确保队列管理器拥有关于该集群的最新信息。
Start the deployment manager on the backup server.
在备份服务器上启动部署管理器。
To go back to a state before one of your many nodes was migrated, you would need a backup of your deployment manager from just before it was migrated.
要返回迁移第一个节点之前的状态，则需要在开始迁移部署管理器之前对部署管理器进行备份。
As a result, if you lose the data center where the deployment manager is running, you lose the ability to manage the cell until a backup deployment manager is brought up in the surviving data center.
因此，如果您失去运行部署管理器的数据中心，也就失去了管理计算单元的能力，直到仍然存在的数据中心启动备份部署管理器为止。
The instructions below require a stable state backup of the deployment manager.
下面的说明需要使用部署管理器的稳定状态备份。
Stop the queue manager on the backup node.
停止备份节点上的队列管理器。
Creates a modified deployment manager startup script for use with the configuration maintained with the backup node.
创建一个修改后的部署管理器启动脚本，用于使用备份节点维护的配置。
Start deployment manager on the backup server.
在备份服务器上启动部署管理器。
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.
正如我们前面提到的，部署管理器的稳定状态备份是执行托管节点回滚所必需的。
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.
虽然由于备份集不可用而导致队列管理器恢复失败的情况不常发生，但是我还是看到过几次这样的情况。
If the V6 deployment manager profile is on a new system, the backup directory will need to be copied to this new system.
如果V 6部署管理器配置文件在新的系统上，则需要将备份目录复制到该新的系统。
Use a file system backup methodology, specific to your operating system (and not explained here) to save the entire profile directory for the deployment manager.
其具体做法为：使用特定于操作系统的文件系统备份方法(此处不再赘述)保存部署管理器的整个概要目录。
In this exercise setup, since we only have one Resource Manager, replace icmnlsdb with RMDB to perform online backup for Resource Manager database.
在练习中，由于我们只有一个资源管理器，因而将icmnlsdb替换为rmdb，为资源管理器执行联机备份。
Probably the best commercial backup and storage management utility available now for Linux is the Tivoli storage Manager.
TivoliStorage Manager或许是现在可用于Linux的最好的商业化备份和存储管理实用工具。
Implementing hot backup for DB2 Content Manager affords business continuity and minimizes data loss or no loss of data if handled properly.
为DB 2ContentManager实现热备份将带来业务连续性，若处理得当，还将最小化数据损失，甚至完全不会有损失。
The distributed Content Manager system backup strategies and considerations can be complex and therefore out of the scope of this article.
分布式ContentManager系统备份策略和考虑事项非常复杂，超出了本文的讨论范围。
Since DB2 Content Manager consists of two databases in the minimum, you need to hot backup all databases in the manner mentioned above.
由于DB 2ContentManager至少包含两个数据库，因此需要以上述方式热备份所有数据库。
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.
要让部署管理器位于备份系统(10.0.0.6)上，我们需要设置所谓的多主dns项。
After backup, continue the installation procedure following the instructions given in the Tivoli System Automation Manager installation guide.
备份之后，按照Tivoli SystemAutomationManager安装指南中给出的说明继续安装过程。
After backup, continue the installation procedure following the instructions given in the Tivoli Service Automation Manager installation guide.
备份之后，按照Tivoli SystemAutomationManager安装指南中给出的说明继续安装过程。
After successfully performing the steps above, you can now move on to perform cold and hot backup for DB2 Content Manager.
成功执行上述步骤后，接下来就可为DB 2ContentManager执行冷备份和热备份了。
Filesystems level backup for DB2 Content Manager system is similar to that of offline full backup.
DB 2ContentManager系统的文件系统级备份与脱机完整备份类似。
To use incremental backup or automate the online backup, Oracle recommends Recovery Manager to be used.
要使用增量备份或自动化联机备份，Oracle建议使用RecoveryManager。
Or, you can mount the snapped file system and perform a backup of it to tape (via Tivoli Storage Manager for example).
或者可以挂载快照文件系统并将其备份到磁带（例如通过TivoliStorageManager）。
Copy the recent deployment manager config backup files to the new server.
将最近的部署管理器配置备份文件复制到新服务器。
Ha2 ACTS as a backup scheduling machine and central manager.
ha2作为备份的调度机器和中央管理器。
Compare, and if necessary restore, the database manager configuration parameters to those in the dbm.cfg.out backup file.
对比数据库管理者配置参数与dbm . cfg . out备份文件，在必要时进行恢复。
应用推荐