I was never big fan of this daily/weekly/monthly approach
On schedule, you set level. Level is full is DB backup. Level incr is TLOG backup.
As for retention, you set it via policy. If you need to have multiple retentions, I would keep it simple and have just one. Then one of the backups (say daily full) I would promote to any other policy I need (eventually together with moving it to another pool/medium as in my case that would be different from operational backup storage).
ok I got most of that, I guess I need to work on the policy part. Each group I created has a different retention policy and schedule to override the client. here are some images I have of each group and one of the clients
I never played with override in group for schedule, but I guess it may come handy when using less client resources so that single resource is part of multiple groups. One thing I noticed is that you use different browse and retention policies; SQL restores require ssid to be browsable so if you plan to keep it for 7 years, quarter as browse policy might be deal breaker unless you keep index for period of 7 years and you can merge back index in case that you need to do restore after 6 years.
ble1
4 Operator
•
14.4K Posts
0
June 10th, 2015 14:00
I was never big fan of this daily/weekly/monthly approach
On schedule, you set level. Level is full is DB backup. Level incr is TLOG backup.
As for retention, you set it via policy. If you need to have multiple retentions, I would keep it simple and have just one. Then one of the backups (say daily full) I would promote to any other policy I need (eventually together with moving it to another pool/medium as in my case that would be different from operational backup storage).
ADNorton
12 Posts
0
June 11th, 2015 03:00
ok I got most of that, I guess I need to work on the policy part. Each group I created has a different retention policy and schedule to override the client. here are some images I have of each group and one of the clients
ble1
4 Operator
•
14.4K Posts
0
June 11th, 2015 06:00
I never played with override in group for schedule, but I guess it may come handy when using less client resources so that single resource is part of multiple groups. One thing I noticed is that you use different browse and retention policies; SQL restores require ssid to be browsable so if you plan to keep it for 7 years, quarter as browse policy might be deal breaker unless you keep index for period of 7 years and you can merge back index in case that you need to do restore after 6 years.
ADNorton
12 Posts
0
June 11th, 2015 10:00
Ok I changed the browse time to match the retention time.