FAQ - Backing up buckets

What is the maximum amount of data that you can store in a single BackupVault?

There is no limit on the amount of data or the number of recovery ranges that can be stored in a single backup vault.

How many backup vaults can I provision?

Each Object Storage instance can contain up to 1000 buckets and backup vaults combined.

Is there a limit on the number of concurrent restore operations that can occur?

Yes. Each backup vault can service a maximum of 3 active restore operations.

Can I restore partial paths, for example a prefix, or individual objects?

No. Restore operations always sync all the objects that were current at the requested restore point-in-time.

What operations are supported on a bucket after a Backup Policy has been set?

All operations on a bucket are supported, except for the disabling versioning and deletion of object-versions.

Deletion of an object before it is synced to the BackupVault triggers an unrecoverable failure that causes the Backup Policy to fail permanently. For more information, go to Configure backups.

What are the user's responsibilities with Backup?

It is the user's responsibility to monitor for and remediate BackupPolicy sync failures. Users are recommended to periodically check BackupPolicy state no less than once per week.

How do I make my restored bucket identical to the source?

Not all actions performed on the source-bucket are synced to the BackupVault. If Restore operations need to result in an identical copy of the source bucket, then it is the user's responsibility to not perform actions that are not synced. For more information on what is synced, go to Configure backups.

It is our recommendation that the Restore target bucket be empty in order to avoid conflicts with restored objects. The Restore target bucket should also not have a BackupPolicy enabled on it. Restore to the source bucket is possible, but it is recommended that the BackupPolicy be deleted before beginning a Restore and then reenabled once Restore is complete.