Hello,
In documentation (https://documentation.commvault.com/2023e/expert/configuring_worm_storage_lock_01.html) I see note: “Associating DDB backups and index backups to WORM copies is not recommended.”
Could you please say why, and what are consequences if I will do so?
Br,
Andrejs
Solved
Associating DDB backups and index backups to WORM copies
+7Best answer by Albert Williams
Hello
DDB and index backups in concept are an admin job to make it easier to recover from a lost or compromised DDB or index. In the case that the DDB or index backup is not available we can still rebuild the DDB and index from what the CS knows and the data at rest.
What this means is the DDB and index backup should be ready and available for quick access with low retention as multiple copies of this backup are just not that useful. Generally WORM is going to have a longer retention and slower read speeds so it defeats the use case of the backup in the first place.
It will work, just slower and the point of the backup is to make recovery times of the DDB or index faster and this is why it is not recommended.
Kind regards
Albert Williams
- Vaulter
- 621 replies
- Answer
Hello
DDB and index backups in concept are an admin job to make it easier to recover from a lost or compromised DDB or index. In the case that the DDB or index backup is not available we can still rebuild the DDB and index from what the CS knows and the data at rest.
What this means is the DDB and index backup should be ready and available for quick access with low retention as multiple copies of this backup are just not that useful. Generally WORM is going to have a longer retention and slower read speeds so it defeats the use case of the backup in the first place.
It will work, just slower and the point of the backup is to make recovery times of the DDB or index faster and this is why it is not recommended.
Kind regards
Albert Williams
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.