Backup Copy of Weekly Active Full to start GFS

[Byte-Selector]

Hello!

My customer in using hourly backups and and one weekly Active Full. He wants to use this weekly Active Full to start a GFS cycle. The GFS will be on the same deduplicating backup repository.

Solution 1: Copy the Active Full to a GFS que. How do to that without involving any Synthetic Fulls?

Solution 2: Move the Active Full of week 1 to GFS que, after Active Full of week 2 is created?

What is the best way to solve this within Veeam?

Regards
Byte-Selector

[foggy]

Not sure what you're trying to do. GFS retention in Veeam B&R can be achieved with the backup copy job.

[Byte-Selector]

Running a Backup job, with hourly schedule and weekly Active Full is fine for short term backup.

For long term backup the weekly Active Full backup shall be archived with a GFS Cycle. Therefor exactly the Active Full shall be put in the GFS Cycle after the Active Full in week 2 has been created.

Possible Solutions, not jet found in Veeam.

Solution 1: Copy the Active Full to a GFS que. How do to that without involving any Synthetic Fulls? IO is between Veeam host and repository, not the best for IO.

Solution 2: Move the Active Full of week 1 to GFS que, after Active Full of week 2 is created?
a) Local move an repository, nearly no IO, good.
b) Move is between Veeam host and repository, not the best for IO.

Solution 3: Keep the Active Full in original queue, but don't keep incrementals more than one week. No IO, good.

Regards
Byte-Selector

[foggy]

Have you reviewed the backup copy jobs referred to above? Automatic GFS retention in Veeam B&R is possible with backup copy jobs only, there's currently no GFS mechanism in regular backup jobs.

[Byte-Selector]

Within a Backupcopy Job running on top of a Backupjob I don't see the option to Copy only the existing weekly Active Fullback without use of any existing incremental and with no other transforming action.

Within the Backup Job I don't see the option to schedule only a Active Fullbackup within a week.

Regards
Byte-Selector

[foggy]

Within a Backupcopy Job running on top of a Backupjob I don't see the option to Copy only the existing weekly Active Fullback without use of any existing incremental and with no other transforming action.

Right, backup copy job is always incremental with 2 as the minimum number of restore points in the regular chain.

Within the Backup Job I don't see the option to schedule only a Active Fullbackup within a week.

You can set active full to be performed on every day the job is scheduled to run at. With these settings active full backup will be created every job run.

[Byte-Selector]

So there is no way to setup any kind of high frequent backup (incremental's per hour) and weekly active full, and to reuse the existing weekly Active Full Backup on the repository for long term backup?

[foggy]

You can do that with two jobs: regular backup job for hourly incremental backup with weekly active full and backup copy job with that backup job as a source for long term retention (though separate backup files will be created by the backup copy job).