full backup schedule

[ScottGao]

Hello

Would you please let me know how can I make full backup monthly \ weekly \daily in 1 job but can define copies of each other separately.
for example, 12 monthly full, 8 weekly , 21 daily.
I can define different job to complete this, But I feel it will wast space cause of unnecessary full duplicate in some days..

Would you please help me clear?
Thank you.

[HannesK]

Hello,
it does not sound like an object storage question. So I moved your question to the general forum section.

If you are talking about (primary) backup jobs: there is no option today for GFS (weekly / monthly / yearly) on backup jobs. V10 will allow that

For today, you can use the backup copy job. We did not allow GFS on backup jobs because, we wanted people to follow the 3-2-1 rule.

Best regards,
Hannes

[ScottGao]

Hello

I remember I post this topic at before, but lost it. So I try to post again.

can I define 12 monthly and 21 daily in one backup job?
retention policy only choose keep 33 copy, but how many monthly and how many daily?
Thank you.

[HannesK]

Hello,
you can click on "your posts" and you should get emails when someone answers



I answered that question to you some weeks ago...

Best regards,
Hannes

[ScottGao]

Dear Hannesk

Thanks for your reply.
Backup have two function. 1. disaster recover. 2. retrive history version.
3-2-1 may focus at guarantee of data safe when disaster recover.

my point is use less space have as much as possible of history version.
This is different target.
For example, synology NAS self backup can have hunders and years restore point with less space. especially for file server or some audit policy.

I will wait V10 to see what will release.
Thank you.

[foggy]

v10 will have the GFS mechanism in regular backup jobs as well, so worth waiting if that is what you're after.

[ChillyHellion]

Hello, and thank you for your help. I'm new to Veeam and have a question about scheduling.

I would like to set up a schedule that keeps the following recovery points:

* nightly recovery points for a week
* weekly recovery points for a month
* monthly recovery points for a year

My goal is to have recovery points that extend back a year's time, but provide increasing recovery point "resolution" for more recent recovery points, with longer gaps between older recovery points.

Below is my schedule as implemented, but I'm looking for any best practice advice on how to set up this kind of schedule. I found that I had to set up three different backup jobs, which I'm not sure is the best way to achieve this result:

* Nightly Incremental - Executes 7pm - Monday through Thursday - Retain 5 recovery points
* Weekly Synthetic Full - Executes 7pm - Friday - Retain 5 recovery points
* Monthly Full Backup - Executes 7pm - Last Saturday of every month - Retain 13 recovery points

Thank you.

[HannesK]

Hello,
and welcome to the forum.

For today, you are correct about backup jobs. Please see above the reasons for that (3-2-1 rule protecting our customers against unwanted data loss) and that we will change that with V10 because of copies to object storage based on repositories.

I suggest not relying on only one system to store backups and follow the 3-2-1 rule.

Best regards,
Hannes

[ScottGao]

Dear Chilly

Your way is not a best practice. Please read about GFS.
you just need to create 1 job, and define synthetic full at Saturday, and you define 3yearly, 12 monthyly, 2 weekly in same job.

in year beginning, week 1, a full A created, it tagged as (W,M,Y)
Week 2, Full B Tagged as (W)

in Feb week 1, tag (W) removed from full A, new full F will tagged (W, M)
in Feb week 2, tag (W) removed from full B, new full G will tagged (W)

please noted GFS FULL not count in retention policy. like 2 month ago FULL, will not count in retention policy restore point.
but it will use to restore incremental backup instead of create separate full for daily.
Thank you.

Scott

[HannesK]

@ScottGao: at the date when this topic was discussed, the options you mentioned were not available.

GFS on primary backup jobs were introduced in V10. V10 was released in February 2020.

[ScottGao]

Dear Hennesk

yes, key point is V10.