Considerations When Modifying a Block Backup Job

If you attempt to save a modified job to the original name, you are warned that the job definition will be replaced. To complete the save operation, click Yes.

If you modify a SnapVault backup job by deselecting source volumes or nodes or by changing the backup destination and then you save to the original name, relationships are immediately tagged for removal. Once you click Yes, the tagging of relationships for removal cannot be undone.

Run the Catalog condense before running the modified SnapVault job. The Catalog condense permanently removes the tagged relationships and reclaims space on the secondary. Running the SnapVault Job before the Catalog condense will result in job failure.

Note the following considerations related to modifying SnapVault backup jobs:

• Relationships are not deleted immediately after you save the job. You must run a Catalog condense to remove relationships.

• Once the modified job is saved, relationships are tagged for removal and the tagging cannot be undone. If you later add back deselected volumes, such as before the condense job is executed, relationships are recreated and result in new base backups.

• Deletion of relationships is currently not application aware. If an application is deselected, relationships of volumes associated with the application are not automatically deleted. If an application-associated volume is deselected, the relationship is deleted, but the next backup of the application adds back the volume and results in a new base backup.

The following table summarizes the result of several scenarios where the source is deselected or the destination changed and the job is saved without renaming:

Change to Source or Destination	Actions	Result
Source	Deselect a source volume or node, confirm OK, add back the source item, save, do not run Catalog condense, then run the backup job.	The volume is backed up, incrementals continue, but after the next Catalog condense the job runs as a base backup.
Source	Deselect a source volume or node, confirm OK, add back the source item, save, run Catalog condense, then run the backup job.	The volume is backed up but the job runs as a base backup.
Destination	Change the backup destination, save, run Catalog condense, then run the backup job.	Job succeeds to the new destination but runs as a base backup
Destination	Change the backup destination, save, do not run Catalog condense, then run the backup job.	Job fails. After the next Catalog condense the job succeeds to new destination but runs as a base backup.

For a review of scenarios and other expected product behavior related to modifying a backup definition, read knowledge base article 45784.