Recovering damaged files from a replication server

If you replicate data to a replication server, you can use the replication process to recover damaged files from that server. You can specify that the replication process is followed by an additional process that detects damaged files on the source server and replaces them with undamaged files from the target server.

Before you begin

Ensure that Tivoli® Storage Manager, Version 7.1.1 or later, is installed on the source and target replication servers, and that the node was previously replicated. Damaged files can be recovered only if you ran the node replication process at least once before the damage occurred.

Procedure

  1. Determine whether the system-wide setting for recovering damaged files from a target replication server is turned on. Issue the QUERY STATUS command:
    query status
    Review the output to find one of the following settings:
    • Replication Recovery of Damaged Files: On
    • Replication Recovery of Damaged Files: Off
    Tip: When you install the server, the default, system-wide setting for file recovery is ON. After you upgrade the server, the default setting is ON only if no damaged files were detected during the upgrade process. If damaged files were detected, the default setting is OFF.
  2. If the setting for recovering damaged files is OFF, turn it on by issuing the SET REPLRECOVERDAMAGED command and specifying ON:
    set replrecoverdamaged on

    If the REPLRECOVERDAMAGED system parameter is set to OFF, and you change the setting to ON, an automatic scan of the Tivoli Storage Manager system is started. You must wait for the process to be completed successfully before you can initiate the recovery of damaged files by using the REPLICATE NODE command.

  3. Recover damaged files by running the REPLICATE NODE command and specifying a value for the RECOVERDAMAGED parameter. Take one of the following actions:
    • To run the full node replication process and recover damaged files, specify the name of the node or node group, and the RECOVERDAMAGED parameter with a value of YES.
      For example, to run the full node replication process and recover damaged files for client nodes in the PAYROLL group, issue the following command:
      replicate node payroll recoverdamaged=yes
    • To run the node replication process only to recover damaged files, specify the name of the node or node group, and the RECOVERDAMAGED parameter with a value of ONLY.
      For example, to recover damaged files for client nodes in the PAYROLL group without running the full node replication process, issue the following command:
      replicate node payroll recoverdamaged=only
      Tip: The value that you specify for the RECOVERDAMAGED parameter of the REPLICATE NODE command overrides any value that you specify for the RECOVERDAMAGED parameter at the node level. For example, you register a node by using the REGISTER NODE command and specify NO for the RECOVERDAMAGED parameter. Then, you replicate the node by using the REPLICATE NODE command and specify YES for the RECOVERDAMAGED parameter. In this case, file recovery is enabled.