That it's possible to simply create a *regular* backup job that writes directly to the cloud instead of first writing to local and then copying over. However with the newer v9 with cloud service providers, it sounds like this isn't necessary.
** I should note that in the previous version of Veeam v8, the cloud-connect *required* you to create a local backup and then all cloud-connect did was then copy these backup files to the cloud.
But, it's unclear whether this is best practices.
Hi, I've searched everywhere and can't seem to find any strategies for the newest version of Veeam (v9) with the new service provider interface for offsite storage - What are best practices for doing an offsite backup using a service provider? Can anyone confirm or expand upon the following?ġ) Don't use Reverse Incremental backups for the cloud backup as this would take a ton of unnecessary bandwitdh?Ģ) Should I create a cloud backup job that writes directly to the service provider cloud-repository? Or, alternatively should I setup a **local** backup meant for the cloud, then use a Veeam "Copy Backup" or similar to copy these backup files to the cloud? I'd prefer doing the former as this would simplify things and not require me to have multiple backups stored locally-I'd have my normal backup on local disks, and then my cloud backup purely on the remote repository.
0 kommentar(er)
