The best bet here is using GFS where you can schedule the Yearly backup to run at a certain period.  Or you can use a Backup Copy job with a similar setting as well.

Yep..agree with Chris here. Assuming you’re running a daily job, just configure your “main” Retention to run 30 days, scheduled once a day at whatever time; then configure/add GFS into your Job at the Storage section of the Job wizard by selecting “Keep certain full backups longer for archval purposes” option and click the Configure button to set your GFS points.

https://helpcenter.veeam.com/docs/backup/vsphere/backup_job_storage_vm.html?ver=120

One item of note though..I’d add at least a few monthly’s to your GFS if you can to make your Yearly be created more efficiently.

https://helpcenter.veeam.com/docs/backup/vsphere/gfs_retention_policy.html?ver=120

Thanks for the  answers. This is not related to this question , but if you can answer me , it will be helpful.

I know I can manually run an active full, is there a way to schedule the back copy job to do an active full rather then a synthetic full? I don't see any options in the Backup Copy job properties.

No the Backup Copy uses Synthetic Full to do the transfer so there is no way.  The only way you could do an active full would be a separate new job to run once to create the Active Full backup.

Let’s break this into two parts:

1. 30 days on prem, 1 year in cloud
2. One-time backup

For the first part, you could set up a Scale-Out Backup Repository, where the performance extent is a local repository, and the capacity tier is the Wasabi bucket. In the capacity tier settings, check the box to “Move backups to object storage as they age out of the operational restore window”. Set this to 30 days. This will satisfy your requirement to keep the backup On-Prem for the first 30 days. (Keep in mind that this setting applies to whatever backups you point to this Scale-Out)

For the second part, you can take a One-Time backup by using VeeamZip. With this, you can take a single point in time backup, and configure it to “Delete this backup automatically in X years”.

Thanks Chris. 

I do see this option? To read the entire restore point from the source backup instead of synthesizing it?

​@Nikks - that option will perform an Active Full for your GFS for your Backup Job..yes. What Chris shared about though was for Backup Copy Jobs.

I don’t want to run a daily. I want to run a one-time backup and keep the backup on the on prem storage for 30 days and in the cloud storage for a year or 2. I am trying to build a process for decommissioning VMs. Is it possible ?

Check my response, it fits your use-case perfectly.

Ohhh..ok. So a single run/backup to local/on-prem Repo, then move it from the local side after 30 days to your Wasabi and keep for a yr? Hmm...don’t think this is possible. The closest I can think of is configure your Backup Job schedule to run once monthly at a given time and day of week. Use a SOBR for your storage, as Tommy suggested above → Perf Tier would be your on-prem storage; Capacity Tier would be your Wasabi. Configure your SOBR to “move” your file rom Perf Tier to Wasabi at 30 days. 

https://helpcenter.veeam.com/docs/backup/vsphere/new_capacity_tier.html?ver=120

I can’t think of how you set retention for the Capacity (Wasabi) side for a yr though.

The VeeamZIP he’ll use to take the final backup before decommissioning will have 1 year retention, that’s how it will be removed from wasabi after 1 year.

Thanks Tommy. We have our backups write to wasabi as soon as they are created:

I don’t want to run a daily. I want to run a one-time backup and keep the backup on the on prem storage for 30 days and in the cloud storage for a year or 2. I am trying to build a process for decommissioning VMs. Is it possible ?

 

Check my response, it fits your use-case perfectly.

Thanks Tommy. We have our backups write to wasabi as soon as they are created:

 

Your current configuration gives you redundancy for the duration of the jobs retention period. If you add the “Move” checkbox, it will remove the backup files from your local repository after the set period. This is to be used as a way to reduce storage consumption in the performance tier. (Note that the setting is repository wide, and affects all backup files in the scale-out)

“The VeeamZIP he’ll use to take the final backup before decommissioning will have 1 year retention, that’s how it will be removed from wasabi after 1 year.” ← Gotcha...thanks! 

Thanks for the  answers. This is not related to this question , but if you can answer me , it will be helpful.

I know I can manually run an active full, is there a way to schedule the back copy job to do an active full rather then a synthetic full? I don't see any options in the Backup Copy job properties.

No the Backup Copy uses Synthetic Full to do the transfer so there is no way.  The only way you could do an active full would be a separate new job to run once to create the Active Full backup.

Thanks Chris. 

I do see this option? To read the entire restore point from the source backup instead of synthesizing it?

 

 

Yes that would do the active full you want versus the Synthetic.  As mentioned my comment was Backup Copy job options.

I don’t want to run a daily. I want to run a one-time backup and keep the backup on the on prem storage for 30 days and in the cloud storage for a year or 2. I am trying to build a process for decommissioning VMs. Is it possible ?

 

Check my response, it fits your use-case perfectly.

Thanks Tommy. We have our backups write to wasabi as soon as they are created:

 

Your current configuration gives you redundancy for the duration of the jobs retention period. If you add the “Move” checkbox, it will remove the backup files from your local repository after the set period. This is to be used as a way to reduce storage consumption in the performance tier. (Note that the setting is repository wide, and affects all backup files in the scale-out)

Our goal is to have backups stored to on-prem device for 30 days and copy to the cloud as soon as backup job are completed.

We want local retention to be 30 days, and my understanding is if the chose to  “Move Backups” the cloud will not have a copy until that date, which does not protect us for off prem.  screenshot below.

For the one-time backup, do we use days or restore points for retention policy to achieve a one-time backup?

I don’t want to run a daily. I want to run a one-time backup and keep the backup on the on prem storage for 30 days and in the cloud storage for a year or 2. I am trying to build a process for decommissioning VMs. Is it possible ?

 

Check my response, it fits your use-case perfectly.

Thanks Tommy. We have our backups write to wasabi as soon as they are created:

 

Your current configuration gives you redundancy for the duration of the jobs retention period. If you add the “Move” checkbox, it will remove the backup files from your local repository after the set period. This is to be used as a way to reduce storage consumption in the performance tier. (Note that the setting is repository wide, and affects all backup files in the scale-out)

Our goal is to have backups stored to on-prem device for 30 days and copy to the cloud as soon as backup job are completed.

 

We want local retention to be 30 days, and my understanding is if the chose to  “Move Backups” the cloud will not have a copy until that date, which does not protect us for off prem.  screenshot below.

 

For the one-time backup, do we use days or restore points for retention policy to achieve a one-time backup?

Days would be ideal and is the new way forward with Veeam.

Yep...Days is the way to go. And, as Chris mentioned, the Restore Points option will be deprecated beginning with VDP13:

https://forums.veeam.com/veeam-backup-replication-f2/deprecated-and-discontinued-features-for-our-2025-release-t97087.html#p536991

 That is an incorrect assumption. If you choose both, they will still be copied to the capacity tier immediately.

For the one-time backup, don’t use a job. Use a Veeam-Zip.