About duplication exclusions
The following can eliminate an image from duplication:
Catalog backup images are not duplicated.
If Disk Only is specified on the Duplication tab, an image that has no disk copy is not duplicated.
If Vault determines that an image is already duplicated, Vault does not duplicate the image again. Vault uses the following criteria to determine if an image is already duplicated:
For One Copy Only. If the image exists in the Off-site Volume Pool, Vault does not duplicate it. Conversely, if a copy of the image is not in the Off-site Volume Pool, Vault duplicates it.
For Concurrent Copies. Vault uses the setting ( or ) to decide whether or not to duplicate an image. Each of the copies has its own setting. Vault interprets the user's intent as follows:
| If the setting for the copy is , that copy is not critically important to the user. The duplication job ends with a partially successful (1) status if at least one of the other copies succeeds. If the current copy is the only one that fails, Vault does not re-duplicate the image the next time the profile runs. If all copies are set to , at least one of those copies must exist or Vault duplicates the image. |
| If the setting for the copy is , that copy is critically important to the user, and none of the copies are successful. This failure forces Vault to retry the duplication the next time the profile runs if that image is selected for duplication (if the time window of the profile allows that image to be selected again). However, if an unscheduled (and unlikely) event creates copies of the image, more than one copy of the image may be assigned to the destination volume pools. If the duplication operation results in more than the Maximum Backup Copies, the duplication step fails. (Maximum Backup Copies are configured in .) |