Offsite Backup Copy jobs in Ver 12

[gregom]

Hello Dima,

still no copy from copy job for Windows Agent Backup possible?
I really hoped this would be available in the latest update.

Regard
Michael

We have a few agent backups and were able to include them in our backup copy to rotated media...

[HannesK]

@gregom: backup copy to rotated media is different than "backup copy from backup copy". I just tested it with Veeam agent for Windows & Linux with "managed by server" backup jobs and "immediate" backup copy jobs and "backup copy from backup copy" does not work (as expected)

[masonit]

unsupported for now
- VCC as source
- VCC as target

Best regards,
Hannes

Hi!

Is this still true?

\M

[Mildur]

Cloud Connect as target is supported since v12.3.
Cloud Connect as source was never supported in any type of backup copy job.

Best,
Fabian

[oskarb]

So, as mentioned earlier in this thread, in one of the 12.x updates it finally became possible to have a second copy job targeting rotated drives that used the first copy job as source, which is useful to avoid pulling the data across WAN a second time. This was with vmware.

Since then the vmware situation has become untenable and migration to Proxmox is underway and unfortunately that means we are back to Veeam disappointment. Veeam currently supports backup of Proxmox clusters, and copy jobs for said backup. Just as for vmware in around 12.0, 12.1, it still on 12.3 does NOT support a second copy job targeting rotated drives and using the first copy job as source to avoid double pull over WAN when the original source is a Proxmox cluster.

To recap, the setup is:

1) Proxmox cluster in datacenter with no staff on site.
2) Backup job targets local repo on fast LAN in datacenter.
3) First copy job pulls across WAN to a second (non-rotated) repo ("copy1-repo") located on a storage node that sits in an office environment where there is staff available.
4) Second copy targets a report using rotated drives. The drives get attached to the same storage node as in step 3. This job should use the first copy job (or repo "copy1-repo") as source to avoid pulling across WAN again.

Step 1-3 works in 12.3.something that we currently have. Step 4 works if the original source is VMware, but not when it's Proxmox.

I brought this up with support in case #08144135 and was asked to comment here.

With our Proxmox migration picking up speed, this is starting to become a blocker and possibly we will have to find a different solution for our backups.

There are other surprising limitations in Veeam when the runtime environment is Proxmox too; for example item level restore for SQL Server. This feels surprising, because it's the same Windows and the same SQL Server as when the VM was running on VMware, yet now when it's running on Proxmox it seems Veeam doesn't want to run the windows guest interaction features. I guess that means also no item-level restore for AD... we have not migrated any domain controllers yet so I haven't tested it. We could perhaps live without some of these features, at least the databases can be handled through file-level restore which does seem to work. The question for us is, if Veeam doesn't actually have these features when the runtime is Proxmox, is there any point in us paying a premium for Veeam compared to a cheaper solution. At some point we have to make a decision about that.

[Mildur]

Hi Oskar,

Proxmox capabilities may currently be limited compared to our VMware support. With VMware we’ve had more than a decade to build features and enhance capabilities in Veeam.
But Proxmox is still fairly new in our product portfolio, and we’re adding new functionality with every release.

Please keep an eye on v13.1 which will release in the next few weeks — it will, for example, bring replication support.
Regarding Backup Copy from Copy, I don’t have any news right now, but I’ll check with our Proxmox Product Management team.

yet now when it's running on Proxmox it seems Veeam doesn't want to run the windows guest interaction features.

This sounds like a technical issue, because Guest Processing is supported since v13.0.1. So it should be possible todo Application Item Restore of supported applications.
Please investigate this together with our Customer Support.

Best,
Fabian