Why not Cloud Connect support ?

[JLundgren]

Hello,

I have read a few articles about limitations but I cannot find any explanation why directing backup jobs to Cloud Connect is not possible.

1) Why is VCC not supported ?

2) Will VCC support be a feature coming soon/at all ?

3) Is VCC supported using Backup Copy jobs ?

4) If VCC is not supported, is protecting AHV-vm with Veeam Agents, the way to go ? (supposing using VCC is a requirement)

5) If using Veeam Agents is the way forward, are there any drawbacks, considering the fact that all vm are AHV-based/AHV-client tools ?

Thanks.

[Vitaliy S.]

Hi Johnny,

As you've stated direct backup to VCC is not supported, but you can use backup copy jobs when sending AHV backups to a cloud repository. Direct backup to VCC is something we'd like to address down the road, but there is no ETA at the moment.

You can use Agents with the conjunction of the VSPC but it seems like backup copy jobs should do the trick.

Thanks!

[ronnmartin61]

Vitaly is correct that you can land AHV backups to VCC with backup copy however your restore options are limited.

[JLundgren]

Hello,

Thanks for your answers but could you elaborate more on my questions in the 1 to 5 format.

[Vitaliy S.]

Hey Johnny,

This is all I can give you for now:
1. Technical reasons
2. No ETA at the moment
3. Already answered in my original post
4-5. Veeam Agents is not the way to go, it's better to use the native engine for backing up VMs.

Thanks!

[Mildur]

I don‘t see Cloud Connect as a primary Backup target for any veeam backup Job.
- There isn‘t the instant vm recovery feature (for vmware or hyperv)
- The RTO will most of the time not be as fast as needed by the customer.
- The Connection to the cloud connect Provider needs to be stable, or the backup job gets canceled.
- No SureBackup Job available for VmWare/HyperV.
- Backup Copy Jobs for 3-2-1 Rule are not available for Cloud Connect Repos as a Source.

Veeam Agents is not the way to go, it's better to use the native engine for backing up VMs

As soon there are this features available:
- VM Guest Files Indexing from Veeam
- Application Aware Processing from Veeam (Log Truncation)
Without this features, i will always backup my database server and with the agent I can dispense the indexing stuff, but if we want to use Enterprise Managers search features for file server, we need the indexing data too

[JLundgren]

Thanks for your efforts of answering me !
I understand the general limitations of using VCC as the primary destination for backupjobs.

Do using Veeam Agents on AHV-based vm, differ from Vsphere/Hyper-V based vm, in terms of features/other limitations ?
Or does hypervisor-choice not matter in this regard ?

[Mildur]

Veeam Agents are the same in terms of function. The hypervisor does not matter

[JLundgren]

Ok, I was thinking in terms of differencies like: virtual hardware, hypervisor client tools, BMR or other.
But then Veeam Agent features are identical regardless of hv-choice. Yes ?

[Mildur]

You can restore a Veeam Agent to each of Veeam supported Hypervisor.
For restore directly to a Nutanix Cluster as a VM for BMR purposes, you will need the backup Files on a local backup target. Cloud Connect is here not possible/supported.
Therefore, you will need todo the typical Agent Restore process:

Todo a restore:
1) create a recovery ISO for each VM with included drivers from the Agent GUI (or single one should be enough)

2) If you need a Restore or the hole AHV VM, do the following:
a) create a empty vm with the required cpu, ram and disk from the original vm
b) boot the vm up from the recovery ISO
c) to the restore from the recovery environment, you can choose the cloud connect Repo as a Source for the restore

https://helpcenter.veeam.com/docs/agent ... tml?ver=50

Test the procedure, before you go live with it for your productive vms