Reestablishing Protection After Drive Failure or Disk Upgrade on a File Server

  • Article

Published : September 27, 2005

In some situations, you might need to restore data from tape because of a disk failure, disk upgrade, or changes to the protected file server volume globally unique identifier (GUID). When you replace a disk, each volume on the new disk is assigned a new GUID. Even if you give the new volume the same drive letter as the volume in the old disk, DPM will not recognize the new GUID. DPM will detect the change in membership and create an alert during the next synchronization job. The replica for each volume on the old disk will immediately be marked inconsistent.

To restore the data to the volumes on the new disk and to provide protection for the volumes being restored

  1. Back up the replica of the old volumes from the DPM server to tape, if a replica backup for each volume is not already available.

    Note

    For instructions on backing up replicas, see the “Archiving and Restoring Data” chapter in this guide (https://go.microsoft.com/fwlink/?LinkId=46368).

  2. Restore the data from each of the old volumes to a new volume by using any of the following procedures:

    • Use the Recovery task area in DPM Administrator Console to recover data from a shadow copy of the old volume to the new volume by changing the recovery destination.

    • If a file server backup of the old volume exists on tape, restore the data to the new volume on the file server from the tape backup. For instructions on using the backup software, see the documentation for the backup software.

    • Use the backup of the replica from step 1 and follow the steps in the section “Restoring Data to File Servers from Tape” in the “Archiving and Restoring Data” chapter in this guide (https://go.microsoft.com/fwlink/?LinkId=46368).

  3. Remove each volume of the old disk from its protection group. Alternatively, you can wait for the nightly Intent Refresh job to complete because DPM will discover all changes in protection and create an alert. The alert will display one New group member for each volume on the new disk and one Disappeared group member for each volume on the old disk. You should choose to stop protecting each volume on the old disk and start protecting each new volume. You can delete all old volume replicas and shadow copies if they are no longer needed for recovery operations, including end-user recovery.

  4. Use the Create New Protection Group wizard in DPM Administrator Console to add new volumes to the protection group. For each new volume that you add to the protection group, on the Choose Replica Creation Method page of the wizard, select I will transfer the files to Data Protection Manager myself.

  5. Create the initial replica for each volume by using your backup software and the replica backup that was created from the old volumes in step 1. You will need to use FsPathMerge on the DPM server because the backup and the restore hierarchies do not match. Alternatively, you can use a tape backup of the old volume that was backed up from the file server. Do not run synchronization with consistency check at this time.

    Note

    For more information on creating a replica by using a tape backup, see “Manual Replica Creation” in the “Troubleshooting” chapter in this guide (https://go.microsoft.com/fwlink/?LinkId=46369). For instructions on using FsPathmerge on the DPM server, see the “Archiving and Restoring Data” chapter in this guide (https://go.microsoft.com/fwlink/?LinkId=46368).

  6. Manually create a shadow copy for each new protected volume on the DPM server.

  7. Run synchronization with consistency check for each new volume.