Community only allows backup jobs and for so many workloads. Once you get to features like Backup Copy jobs you need a license unfortunately. No way around it.
Hmm...according to Veeam’s feature comparison amongst their product Editions, Copy Jobs are available in the Communty Edition, as noted on pg. 6.
Hmm...according to Veeam’s feature comparison amongst their product Editions, Copy Jobs are available in the Communty Edition, as noted on pg. 6.
That is odd I missed that part. Good catch Shane. So, in theory copy jobs should work then.
Chris - I actually thought BCJs not being allowed would be odd, and didn’t really remember seeing/reading that anywhere so looked it up. It’s essentially the same thing as a BU, but just taking the backups themselves and transferring them to some other repo and/or site location. Nothing really ‘enterprise-level’ about the process really.
Hey @Wallewek , can you share the explicit process of what you’re trying to do which provokes your error? Maybe a screenshot of the step if possible, as well?
This all depends on your backup target as for example you can add object storage for recovery in community/standard edition, but to back up to object storage you need the VUL or Enterprise. Let us know what storage you’re trying to back up to and what the source job type is (VM/Agent/NAS etc) and we can go from there. The link @coolsport00 shared gives a great license/feature breakdown to help narrow this down.
Do you use the WAN accelerator or SOBR function? If you do, those need an enterprise plus license.
Depends on the target storage, sobr and object storage are not supported in community editions. However, backup copy job is supported
I figured out my problem!
As I was going through the “Next” steps to set up my first backup copy job, on the Data Transfer page, before I had a chance to make a selection, I was presented with a highlighted warning that it needed Enterprise Plus edition. This is one of those “decoy” warnings that seems obvious to those who have done it before. Typical bad UI design and testing.
I now understand that I should ignore it. I shouldn’t have had to.
There was something else too, but I can’t see it now.
