-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jan 14, 2016 9:45 am
- Full Name: Felina De Moor
- Contact:
Weekly job, always full
I have 2 questions, one about the primary backup job and one about the backup copy job. But first, what is it that we need:
- primary: 1x/week a full backup with 5 restore points to keep (so yes, always full, no incrementals)
- copy: exact copy of the primary job so 1x/week a full backup with 5 restore points
Q1 (primary): If both "Create synthetic full backups periodically" and "Create active full backup periodically" are checked and set on the same day will it then do a synthetic full or an active full? FYI: the job schedule is set on that same day.
Q2 (copy): How can we make sure that the copy job is always an exact copy of the primary job, in other words how do we make sure that the copy job is always a full? There is the option under GFS "Read the entire restore point from source backup instead of synthesizing it from increments" that should help but we want max. 5 restore points so how do we use this if we can't set the weekly, monthly, quarterly and yearly backup to zero? Or am I seeing this wrong?
- primary: 1x/week a full backup with 5 restore points to keep (so yes, always full, no incrementals)
- copy: exact copy of the primary job so 1x/week a full backup with 5 restore points
Q1 (primary): If both "Create synthetic full backups periodically" and "Create active full backup periodically" are checked and set on the same day will it then do a synthetic full or an active full? FYI: the job schedule is set on that same day.
Q2 (copy): How can we make sure that the copy job is always an exact copy of the primary job, in other words how do we make sure that the copy job is always a full? There is the option under GFS "Read the entire restore point from source backup instead of synthesizing it from increments" that should help but we want max. 5 restore points so how do we use this if we can't set the weekly, monthly, quarterly and yearly backup to zero? Or am I seeing this wrong?
-
- Product Manager
- Posts: 20389
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Weekly job, always full
It's not clear whether the jobs should be executed daily or weekly. Could you elaborate? Thanks.
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jan 14, 2016 9:45 am
- Full Name: Felina De Moor
- Contact:
Re: Weekly job, always full
The jobs should run weekly.
-
- Product Manager
- Posts: 20389
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Weekly job, always full
In this case you should do the following:
- primary job: set 5 as retention policy, let job run weekly on a predefined day, select the very day for active full backup
- secondary job: set 7 days as a sync interval, set 5 as restore points to keep, enable GFS, set 5 as number of weekly restore points, enable read the entire restore point option and select the day primary job creates active full backup as a weekly GFS day. Additionally, you prohibit job execution on all days, but the needed one, using backup window
Thanks.
- primary job: set 5 as retention policy, let job run weekly on a predefined day, select the very day for active full backup
- secondary job: set 7 days as a sync interval, set 5 as restore points to keep, enable GFS, set 5 as number of weekly restore points, enable read the entire restore point option and select the day primary job creates active full backup as a weekly GFS day. Additionally, you prohibit job execution on all days, but the needed one, using backup window
Thanks.
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Weekly job, always full
And to answer your Q1, in this case active full will be created.
Who is online
Users browsing this forum: Bing [Bot], Kirassant, kwangilsung, NightBird and 157 guests