Offsite Backup Copy jobs in Ver 12

[Dima P.]

Glad to hear! Thank you for the feedback Andi Kola!

[michael.westphal]

Thank you for brining this function back.
What is with Veeam Agent Backups?
They are still not working for Backup copy as Copy jobs sources.

[stevehughes]

I've been running all our client sites on Ver 11 due to the removal of BCJ->BCJ functionality in Ver 12. I was very excited to see the new BCJ->BCJ functionality, until I upgraded a site to Ver 12.1.2.172 and found that the new BCJ->BCJ functionality doesn't support using CloudConnect as the destination. This is a scenario that we use heavily (per my original post). Just as well I tried this on one small set of BCJ jobs before converting all BCJ jobs to the new format. Is there a plan to ever address this?

[Dima P.]

Hello Steve,

This limitation is temporary and will be removed in one of the upcoming releases. Thank you for your post!

[Neturius]

Any update on the roadmap for this?

"Repository with rotated drives is not supported when Backup Copy job is used as a source"

Regards,
Peter

[gregom]

^^^ Yeah we're still needing this function back... We've scripted copying the files manually but if the backup copies get modified at the same time we're running the script it fails. This is causing us problems. It would be nice to know when the next update with this functionality will be coming.

[Dima P.]

Hello guys,

Thank you this limitation is on our radar too. Mind me asking what is going to be used as a target for such backup copy job?

[Neturius]

Targets are USB connected hard disks in our case.

Regards,
Peter

[Dima P.]

Understood. Thank you Peter!

[trofie]

It seems a bit rich to me that you force everyone to update to v12 as you end product support of v11, but at the same time, you haven't put all the required features people are using in the old version into the new version yet.
To add salt to the wound, this particular thread is over a year old, cmon team.

[Gostev]

you haven't put all the required features people are using in the old version into the new version yet

Which features are you referring to here?

[gregom]

Hello guys,

Thank you this limitation is on our radar too. Mind me asking what is going to be used as a target for such backup copy job?

We're backing up to a rotation of local hard disks that are physically installed in the backup server then removed after we've finished the backup copy.

[oskarb]

Yet another disappointment after upgrading to 12.1.2.172, thinking backup copies of copies were finally fixed. But alas no, because rotated drives. PLEASE add/restore this feature!!!

The use case is the same as has been described by others:

1. Primary backup repository online in the dedicated datacenter next to the production servers. NO STAFF ON SITE!
2. First backup copy job copies over the Internet to a secondary (online) repository server at the main office.
3. Second copy is to rotated drives that are also attached to the secondary repository because this is in the office where there is staff available to rotate the drives.

Currently, this second copy has to pull all the data across the Internet a second time which is absolutely ridiculous.

(To be clear, the second-level copy job needs to tolerate the target being rotated drives.)

It seems you imagine that everyone will have their primary data centre on-site at the office and then copy it off somewhere to a second site where there is no staff but for smaller companies it is likely the reverse. The *primary* systems are in a rented co-location facility with redundant power, AC, and Internet links, but no staff on site, while the secondary backup is in the main office (and it's probably the only server system in the office site).

[Dima P.]

It seems a bit rich to me that you force everyone to update to v12 as you end product support of v11, but at the same time, you haven't put all the required features people are using in the old version into the new version yet.
To add salt to the wound, this particular thread is over a year old, cmon team.

The functionality to use backup copy as a source from backup copy was brought back to the product as fast as possible but that caused several limitations to apply. Now we are working on those limitations one by one based on your feedback. Thank you for sharing you use case, we will raise the priority! Can you please your backup copy from backup copy rotated drive use case? Was it used as a source or as target?

We're backing up to a rotation of local hard disks that are physically installed in the backup server then removed after we've finished the backup copy.

Can you please clarify if the rotated drive was used as a source or as target for backup copy from backup copy job in the past? Thank you!

1. Primary backup repository online in the dedicated datacenter next to the production servers. NO STAFF ON SITE!
2. First backup copy job copies over the Internet to a secondary (online) repository server at the main office.
3. Second copy is to rotated drives that are also attached to the secondary repository because this is in the office where there is staff available to rotate the drives.

Thank you for the detailed use case! Added your vote to this request!

[gregom]

Dima, our rotated drives are used as the target in our scenario.

[nqrott]

Same issue here. Not sure what gone wrong with Ver.12. We are still regrading the upgrade from V11.
As there was no annoucment for a loss of essential features.

You need to fix the copy of copy to USB drives (rotated drives). thats the only way to make an airgap backup on an offsite location without sending the data twice over a wan connection.

And please do not only allow copy from copy jobs also lets us do backups / copies from an offsite repository, it is more intuitive.
I am still wondering how that was even possible to release V12 with so many missing features? Don't you read your own backup strategy recommendations?

[nqrott]

It seems you imagine that everyone will have their primary data centre on-site at the office and then copy it off somewhere to a second site where there is no staff but for smaller companies it is likely the reverse. The *primary* systems are in a rented co-location facility with redundant power, AC, and Internet links, but no staff on site, while the secondary backup is in the main office (and it's probably the only server system in the office site).

or the second location is next to a bank locker or boss's house with an secure safe.

[Gostev]

That's exactly what Veeam did in our very early days (boss' house).

[Gostev]

I am still wondering how that was even possible to release V12 with so many missing features?

@Dima P. just so everyone's clear, could you create a list of Backup Copy features related to rotated drives which existed in V11 but still do not exist in V12? Thanks

[Dima P.]

Hello folks!

Sure. With v11 it was possible to:

1. Set rotated drive as a source repository for backup copy job
2. Set rotated drive as a target repository for backup copy job
3. Add backup copy as a source job for the backup copy job

With v12.1:

1. It is possible to set rotated drive as a source repository for backup copy job
2. It is possible to set rotated drive as a target repository for backup copy job
3. It is not possible to set backup copy as a source job for the backup copy job

Thanks to the community feedback we've added the ability to set backup copy as a source to the backup copy job in the patch latest patch. However, since we wanted to bring this functionality back as soon as possible it's currently does not support configurations with rotated drives at source or target but we plan to remove such limitations in the upcoming versions. Thank you!

[gregom]

Well I'm glad to hear the issue is still being worked on, sounds like we still have to wait for the functionality we need. Honestly we are very disappointed like the others that these features were just dropped. Feels like a very M$FT thing to do. We're already being hit HARD by the Broadcom acquisition with increased costs, and costs with Veeam switching from socket based to instance based licenses... now features are pulled out from under us. I realize you didn't do it personally, but at this moment I must say that we are not happy customers.

[gregom]

Thanks to the community feedback we've added the ability to set backup copy as a source to the backup copy job in the patch latest patch. However, since we wanted to bring this functionality back as soon as possible it's currently does not support configurations with rotated drives at source or target but we plan to remove such limitations in the upcoming versions. Thank you!

Is the rotated drives support still coming? Is it in 12.2? I looked at the release notes but didn't see rotated drives mentioned.

[Dima P.]

Hello Michael,

Yes, it's planned. Thank you!

[Chris-DE]

I've been running all our client sites on Ver 11 due to the removal of BCJ->BCJ functionality in Ver 12. I was very excited to see the new BCJ->BCJ functionality, until I upgraded a site to Ver 12.1.2.172 and found that the new BCJ->BCJ functionality doesn't support using CloudConnect as the destination. This is a scenario that we use heavily (per my original post). Just as well I tried this on one small set of BCJ jobs before converting all BCJ jobs to the new format. Is there a plan to ever address this?

Waiting for it as well. Tenants with tree-conceptional Backups are making life hard for Service Providers. No roadmap till now, i guess?

[Dima P.]

Christian,

Stay tuned, cloud connect repository target for backup copy from backup copy backup is planned for the upcoming 12.3 update! Thank you!

[tgietz]

Hi,

good news. Rotated drives Support and Cloud Connect support as target from Backup Copy Jobs are now supported in v12.3

See Page 9 in v12.3 What's new document: https://www.veeam.com/veeam_backup_12_3 ... new_wn.pdf

Regards
Tobias

[michael.westphal]

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

[HannesK]

Hello,
correct, but to be fair: that never worked and this thread is mainly about a feature that worked before V12.

We count your request +1

Best regards
Hannes

[gregom]

Thanks for letting us know.... Trying it out now.

[gregom]

Seems to be working good in 12.3. I had to create new jobs but am able to copy backups from the local repository both which contains backups from local backups and backup copy jobs to rotated collection of hard drives.

So thanks for getting this back in and luckily we didn't have to pull from backups while it was broken and we were manually copying VBK files and such - because I tried and only had partial success with restores from those.