Rolling back Disk Library with DDB

Hi ​@evgenich,

Please find the answers inline for the queries.

If a snapshot of the disk library cannot be restored / reset. Is it possible to simply change the path, or does CommVault need the exact path?

Commvault relies on the exact path of the disk library for backup and restore operations, so changing the path can be problematic unless done carefully.

Commvault typically uses absolute paths to reference its backup data locations, including disk libraries. Changing the location of the disk library or modifying the path (for example, moving the data to a different disk or folder) can cause issues and it can make the disk library offline, as Commvault will still be looking for the data at the original path.

Recommendation: Avoid changing paths if possible. If you must, you'll need to ensure that Commvault knows about the new location of the disk library and update the configuration accordingly.

How exactly does the restore work if we go back to an older snapshot?

When you restore from an older snapshot of the disk library, the restore process can be affected depending on the time between the snapshot and the current state of the backup.

A snapshot captures the state of the disk library at a specific point in time. When you restore from a snapshot that’s a few days old, Commvault will attempt to restore the backup data as it existed at the time of the snapshot. This means that any new backups taken after the snapshot won’t be available unless you sync or reconcile the newer data.

What happens to the dedup databases if the disk library is set back by 3 days, for example? Keyword consistency of the dedup databases. I think there is a cleanup process.

For ddb databases there will be ddb resync running to ensure consistency.

Regards

Karthik