Results 1 to 3 of 3
Thread: SQL Yearly Backup
12-17-2012, 10:06 PM #1
SQL Yearly Backup
I've been asked to setup an SQL db backup that will occur every year at the end of the fiscal year, and it will only require retaining for 1 year from its backup date. So the simple thought was to bind it to a management class with a one year retainonly value and be done.
BUT, then it occurred to me................since I am only running this backup once a year, the first backup does not go inactive until the next backup a full year later, so at that point the first backup has already been retained for a full year, meeting my requirements, and will now be on the expiration clock for an additional year and actually exist in backup storage for TWO years, unless I instead bind it to a short retainonly (7-10 days max), so that when the Year 2 backup occurs, the Year 1 backup inactivates and is gone a few days later, instead of remaining for an additional entire year.
Is this a normal method of handling it? The only risk I see is that if a backup is run before the next schedule then we lose the previous end of year backup before the next end of year backup happens.
Also been asked to setup a quarterly backup and only retain it for 90 days. Same situation as the yearly, more often.
Last edited by GregE; 12-17-2012 at 10:47 PM.
12-18-2012, 01:44 AM #2
- Join Date
- Apr 2007
- Oslo, Norway
- Thanked 17 Times in 17 Posts
I make a seperate node for yearly backups (and monthly).-= Trident =-
12-18-2012, 11:05 AM #3
Yep that's what I'm doing.
By oskie in forum Backup / Archive DiscussionReplies: 3Last Post: 07-28-2008, 10:55 AM
By Jcage in forum Backup / Archive DiscussionReplies: 2Last Post: 07-03-2008, 04:04 PM
By vvragav in forum Backup / Archive DiscussionReplies: 4Last Post: 03-03-2008, 12:47 AM
By Quake in forum Backup / Archive DiscussionReplies: 14Last Post: 12-20-2007, 12:16 PM
By LouisZ in forum OthersReplies: 2Last Post: 04-07-2003, 08:12 AM