Object Storage Repository

• General
  • API call cost estimation
  • Immutability
• Using Object Storage with Veeam Products: KB4241
  • Supported Object Storages and repository structure: User Guide
• User Guide
  • Add Object Storage Repository

  Important: When creating an S3 bucket or Azure Blob, only enable versioning in combination with Object Lock (immutability). Never enable versioning when immutability will not be used.

Retention policy

VB365 has two retention policies: snapshot-based (=default) and item-level. Depending on your client’s requirements, one or the other will be chosen.

• Use snapshot-based retention to keep all items and versions for the configured retention period. Similar to how image-level backups work.
  Example: Backup all items (full backup) and then backup only the new/changes (incrementals) and keep for 3 years. All items will be kept for at least 3 years.

  This retention type is the default and is most used to make sure that all the items and versions are backed up and kept for the required period agreed with the client.

• Use item-level retention to keep items based on its creation time or last modification time and that that fall within the configured time period.
  Example: Backup all items with a last modification date from within the last 3 years. Items not modified within the last 3 years are not even be backed up.
  Items will also be deleted from backup once their creation or last modification date exeeds the configured retention period.

  This retention type is used in certain compliancy scenarios.
  Example: In the HR department, it might not be allowed to store items older than 3 years for legal and compliance reasons.
  Therefore items created or modified longer than 3 years ago, must be removed from backup.

More details and examples: User Guide

Sizing

Important: The current maximum of supported repositories per controller is 200.

When it comes to backup storage sizing, use the official VB365 Capacity Calculator to estimate storage consumption.

---