Summary
This article describes how to delete a SnapVault relationship on a NetApp controller.
Symptoms
Some circumstances that can lead to orphaned qtrees or a need to remove qtrees as part of a troubleshooting procedure.
Resolution
A Catalogic Software block backup job to a NetApp secondary creates a SnapVault relationship the first time it is run. Subsequent backup jobs update the contents of the qtrees created on the secondary by the initial SnapVault job. At the conclusion of every SnapVault backup job, a snapshot is taken of the volumes that house the qtrees that make up the SnapVault relationship. Each of these snapshots has a retention period associated with it, which are cataloged as part of the metadata information and stored in the Catalog. When a SnapVault backup job exceeds its retention period, the master server contacts the NetApp secondary and deletes the appropriate snapshots from the appropriate volumes. Qtrees exist at the root of the volume and generally do not require any special treatment for as long as the backup job is active. The management console and condense process coordinate to remove qtrees as needed.
However some circumstances can cause orphaned qtrees that need to be removed. For example, qtrees may need to be removed as part of a troubleshooting procedure.
To delete a SnapVault relationship on the secondary server:
- Telnet (or SSH) into the NetApp secondary storage system as root. Get a list of all the SnapVault relationships by issuing the snapvault status command from the command line. The following is sample output:
- Identify all the relationships in the Destination column of interest, and issue the following command for each of the relationships:
snapvault stop -f <destination>
- To delete the first relationship listed above, issue the following command:
snapvault stop -f fas270:/vol/Backup/[JobA]WIN2KSERVER@2DA2C1CE401A11D78F9A806D6172696F - Confirm that the relationships are all deleted by issuing a subsequent snapvault status command.