Configuration Backup Copy Job?

[JTT]

Please add this feature - we really need a proper "copy job" option for Configuration backups, like one local and the second to S3, Cloudconnect etc.
File copy is not a solution, there is no versioning, how many copys to keep.

[mcz]

Yes, totally agree! We need an automated solution which manages retention and integrity. We need config backups on multiple repositories, somewhere on your site and somewhere on an immutable object storage for the worst case. It was also nice if veeam would copy the config backups from a SOBR to the capacity/archive tier automatically.

[ZockerMad]

+1 Feature Request: proper Copy Job (not File Copy, because of limitations) for Veeam Config Backup would be really easy to implement and nice to have. It is really hard to do a proper 3-2-1 Backup Rule with only NAS and Tape GFS Jobs (Tape Jobs to GFS Pools dont allow File Jobs).

Pls Veeam, i have been waiting many years for this simple solution!

[Gostev]

File copy is not a solution, there is no versioning, how many copys to keep.

Why not just use our file backup functionality? This has all these features you mention.

[RubinCompServ]

@Gostev,

Because backing up the backup config leads to complications when you need to rebuild your Veeam server but your Veeam server config isn't able to be directly restored because you have to restore the config from a backup before you can restore the config to the server.

[Gostev]

No, actually you don't need to do this. You can just import your file backups into a fresh VBR install. And if you create a dedicated logical repository for your configuration backups, you can guarantee that import operation takes a split second.

[matteu]

+1 for backup copy too.
Easier to manage than file backup and possible for all repositories types....

[mcz]

Why not just use our file backup functionality? This has all these features you mention.

You can't copy to an object storage... If that was possible, I'd use it...

[Gostev]

Object storage is totally supported for file backup jobs and it has always been - not only supported but also recommended actually (for scalability reasons).

[mcz]

Hmm... If I open the "new file copy job" wizard, I don't see my object storages (not part of SOBR) under the destination-section. I can only choose the server and the path to folder. Even if I choose the gateway-server of that object storage, I can only set a windows-path as destination.

what's wrong here? Thanks!

[Mildur]

Hi Michael

You are confusing the job types.
"File Copy job" is not a "File Backup Job". Anton talks about "File Backup Job".

File Copy Job: https://helpcenter.veeam.com/docs/backu ... ml?ver=120
File Backup Job: https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Best,
Fabian

[matteu]

So that mean I would have to create a share on my HLR ? No way for it
We just really need a way to be sure about the 3-2-1. On my side, I totally ignore why it s Stiller not possible after all these years
Veeam does an excellent improvment on other feature but not on this one .

[Gostev]

No need to create a share, File Backup jobs support all the same sources as File Copy jobs.

[FrancWest]

I wasn't aware of this functionality, but it seems to do the job for backing up configuration backups. However, the configuration behavior is different in regard to other backup job types.

It automatically creates a backup copy job (or more if you select multiple secondary targets). However, you can't rename this automatically created backup copy job. So we can't use our own naming convention.
Also, you can't create a copy job manually with the file copy job as a source.

The name of the backup job type 'File share' is a bit misleading, since you can select any file or folder without a share.

[matteu]

Will it consume an instance licence ?

[Mildur]

Hi Matteu

It uses our file backup engine. If you protect less than 500GB, no license will be consumed.
Case 1 "499 GB or less": https://helpcenter.veeam.com/docs/backu ... 0#examples

The name of the backup job type 'File share' is a bit misleading, since you can select any file or folder without a share.

I am currently working on it. Yesterday, we had a discussion about updating the UI in an upcoming version.

It automatically creates a backup copy job (or more if you select multiple secondary targets). However, you can't rename this automatically created backup copy job. So we can't use our own naming convention.

This is discussed here. I plan to discuss the request soon with the responsible Product Management Team.

Best,
Fabian

[Gostev]

@Mildur being a Veeam backup file, I believe it is excluded from licensing completely... irrespective of size.

[Mildur]

Yes, you are right. BCO file is in the excluded list.

Thank you,
Fabian

[matteu]

Thanks for both answer. It s a good workarround waiting for a solution included into the gui.
Just a new list array under the backup targette of the configuration but woth backup copy and maube a checkbox to enable it ^^

[BostjanUNIJA]

Adding two backup destinations in the gui for config backups would be great. Cmon Veeam team you can do it (please)

[cgsm]

While I agree it would be very nice to have two places in the GUI to save config file backups to, I think there is a reasonable way to do this with file backup jobs.

1) I have my config file backups set to save to the VBR server C:\ drive and retain 30 days.
2) I have a File Backup Job set to backup the folder containing all the config backup .bco files that runs once per day, saves to my local repo on my VBR server (V:\, separate disks), and "keep all versions for the last" set to 28 days.
3) I have a secondary location setup for this job, aka a copy job, that copies the backups to my immutable server/repo and retains them for the same 28 days.

This setup works well. I end up with almost a 2-month history since the oldest backup has 30 days of config file backups and the oldest backup itself is from 28 days ago.

I do not get hit with using an instance from my VUL license.

[mcz]

Hi everyone, just wannted to come back to tell you that I've implemented the file-backup solution and so far it works pretty well! Very little efforts for a very solid solution. Thank you!

[JaySt]

Adding two backup destinations in the gui for config backups would be great. Cmon Veeam team you can do it (please)

even though a file backup could work right now, i think this is the more elegant way to do it.
I would just prefer to have a "secondary target" dropdown activated when checkbox is enabled for it right there in the configuration backup menu.
Just have it run right after the primary one finishes succesfully or something, with the same retention setting as the primary one.

my reasoning:
it's cleaner: no job definition for this = cleaner.
I'ts more intuitive to configure and less likely to be forgotten
The configuration backup job as it is right now also does not have a job definition visible. It's not logical to only have the secondary to be visible in this way.

The only (big) advantage for doing this with file backup jobs is the fact nothing needs to be developed to achieve the requirement for a secondary copy.