When configuring backups using the "snapshot only" repository, or regular Please verify Nimble Volume Collections configuration before running the snapshot-only job, otherwise it may not operate properly- for example, replicate more data than expected. It is recommended by the vendor that volumes should be in individual Volume Collections.
Lower RPO, in case the primary storage array is still available, when a restore It is however a great complement to traditional backups to achieve
It is not recommended to rely on storage snapshots as backups, as it violates Instead Veeam will orchestrate the creation of a storage snapshot, and canĮntirely skip VMware snapshot creation, in case application-aware image processing Veeam will not copy any data from the source storage to a target repository. When a job is configured for using "Nimble snapshot" as the backup repository,
- Associate the desired volume for replication on the Volumes Tab.
- Minimum - or any desired configuration, as these configurations will not be Weeks or Repeat Every Week and Replicate to set to "2" as the Nimble configuration will not allow empty scheduling. Note that Veeam Backup & Replication uses its own engine to initiate the creation and replication of snapshots.
Set the scheduling for Nimble Storage snapshots. To the secondary Nimble array before the backup job starts. Veeam will orchestrate the creation of a volume snapshot, and initiate replication Add a new volume by clicking on New Volume CollectionĪdd the Volume Collection Name on the Introduction.īe careful with the naming to stay within the limits of 80 characters.Browse the NimbleOS web GUI: Manage - Protection - Volume Collections.Orchestration of snapshot creation and replication between Nimble Storage arrays. This section contains integration specific information for configuring Sizing Targets for WAN Accereration Relationship Protecting Veeam Backup & Replication Configuration Veeam Backup & Replication Best Practices