How Does Veeam Cloud Connect Work?
The Veeam Cloud Connect Infrastructure is fully managed by our internal support team. This service requires no extra hardware. This service is not designed as a complete replacement for local backup repositories.
Built into the existing Veeam Backup & Replication V8 management console, our “Service Provider” can be added using the provided URL, port, username and password. No other configuration is required.
Once the service provider has been added the Cloud Backup repository is made available and can be used in almost the exact same way as any other repository available in the inventory
Users can configure the following jobs and perform the following tasks against the cloud repository:
- vCD backup (for VMware vSphere platform)
- Backup copy (to cloud repository only. Backup copy from the cloud is not supported.)
- File copy (manual operations)
- Restore Tasks
- Full VM restore
- VM files restore (for VMware vSphere platform)
- VM disks restore
- VM guest OS files restore (Microsoft Windows FS only. Multi-OS restore is not supported.)
- Application items restore
Backup Copy Jobs
To follow the 3-2-1 backup best practice, you can configure a backup copy job and target it at our Veeam Cloud Connect repository. Backup copy jobs allow you to create several instances of the same backup file in different locations, onsite or offsite. For example, you can configure a backup job to create a VM backup on the local backup repository, and use the backup copy job to copy the created VM backup from the local backup repository to the cloud repository. Copied backup files have the same format as those created by backup jobs, and you can use any data recovery option for them.
During the backup copying process, Veeam Backup & Replication does not simply copy a backup file from one backup repository to another. Instead, Veeam Backup & Replication retrieves data blocks necessary to create a restore point as of the latest point in time and copies this data to the cloud repository. The backup chain produced on the target backup repository is forever-incremental: the first file in the chain is a full backup while all subsequent restore points are incremental.
The backup copy process is job-driven. When you create a backup copy job, you define what backup file you want to copy, the target repository for storing the copy, retention policy and other settings for the copying process. The backup copy job supports the GFS retention scheme, allowing you to design a long-term archiving plan.
The backup copy job runs continuously, in cycles. By default, a new backup copy cycle begins every day; however, you can specify any time interval needed. At the beginning of every backup copy interval, Veeam Backup & Replication checks the source backup repository: if a new restore point has been added to the primary backup chain, Veeam Backup & Replication automatically copies it to the target backup repository. After that, the backup copy job is put on hold until a new backup copy interval begins and a new point appears on the source backup repository
If you have Veeam enterprise plus licensing you can make use of Veeam’s built in WAN acceleration tool. Veeam 8 Enterprise plus includes a purpose build WAN acceleration tool, specifically for moving existing Backup Jobs to an offsite location. The WAN acceleration engine can help speed up and reduce WAN traffic by as much as 50X. There are no additional charges for the WAN acceleration Service. Cached data will consume part of the assigned storage quota.
If Veeam enterprise plus licensing is not available then, the solution will still work but no WAN acceleration will be used to send the data offsite.
Depending on the volume of data being protected and your internet connectivity it may be necessary for us to ship the initial seed of data. When using seeding we recommend all backup jobs are configured for encryption. This will protect the data while it is being physically shipped to the Data Centre.
There are no setup charges or any other charges for data seeds during the initial setup.