Reattaching healthy snapshot volumes

If you recovered using a roll-forward recovery to the point of failure, use the VSS Snapback wizard or vxsnap reattach command to reattach the snapshot transaction logs volume and the snapshot volumes of any databases that were not affected by the disk failure (and thus still have snapshot volumes associated with them).

To snapback a snapshot set

  1. Close the database application GUI and all Explorer windows, applications, consoles (except the VEA console), or third-party system management tools that may be accessing the snapshot set.
  2. From the VEA console URL bar, select the <host name> which is the system where the production volumes and snapshot mirrors are located, as the active host.

  3. Expand the system node, the Storage Agent node, and the Applications node.
  4. Right-click on the node of the application and click VSS Snapback.
  5. Review the Welcome page and click Next.
  6. Select the snapshot set you want to snapback and click Next.

    The XML metadata file contains all required information needed to snapback the snapshot set, including the names of the database and transaction logs volumes. Click the appropriate header to sort the list of available files by File Name or Creation Time. This file is deleted after the snapback operation has completed successfully.

  7. If a message appears that indicates some volumes have open handles, confirm that all open handles are closed and then click Yes to proceed.
  8. Verify that the snapback specifications are correct and click Finish.

To reattach the split-mirror snapshots to the original volumes from the command line

  1. Close the Exchange GUI and all Explorer windows, applications, consoles, or third-party system management tools that may be accessing the volumes.
  2. Type the command, replacing the example file name:
    vxsnap -x Image1.xml reattach writer="Microsoft Exchange Writer"

    The complete syntax for the vxsnap reattach command is:

    vxsnap -x <filename> [-f][-b] reattach writer=<writername>
    [secHosts=<secondary hosts>]