Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12345»»»

Safety in Numbers Expand / Collapse
Author
Message
Posted Thursday, February 11, 2010 9:56 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 6:20 PM
Points: 33,078, Visits: 15,192
Comments posted to this topic are about the item Safety in Numbers






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #864450
Posted Friday, February 12, 2010 12:57 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, August 23, 2012 2:09 PM
Points: 100, Visits: 123
It is quite difficult to get your head around this one, Deciding what to keep and what not to.

I always keep the last Three Full Backups, the Transaction Log backups and Differential Backups between them.
Once the Full Backup is performed on Sunday night, these are restored on a Test DB on monday morning, if they fail, Back it up again.

I became complaisant with the backup routine and decided that One Full was enough after IT complained i was using too much disk space on the SAN for storing the DB backups and suggested I alter my backup routines... so I began to keep only the last full and the transaction logs after, but got seriously burned one day a few months ago when the backup on the disk were corrupted and the DB server went down on monday morning before i came in due to a hardware failure.

We live and learn, but that day in August will probably remain with me forever more...

Leon
Post #864476
Posted Friday, February 12, 2010 1:12 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, June 3, 2014 8:16 AM
Points: 295, Visits: 1,011
About full backups, we take one each night for each database. We store them at a different safety location. I believe requirements might vary a lot depending on the company. I'm btw a Consultant at a Company where you can purchase a pension insurance and you have funds to chose between and thus you get a yield on the pension.
Post #864480
Posted Friday, February 12, 2010 2:01 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Saturday, March 29, 2014 11:41 AM
Points: 753, Visits: 133
I used to retain the last 2 Full AND Transaction Log backups pending verification of a RESTORE into a shadow DB however, after listening to sob stories from the IT geeks that my disk usage had risen from 4 GB to >16 GB, I dropped down to retaining the last Full Backup only.

I had an erraneous backup on my main DB recently which only came to light when I attempted a RESTORE into my shadow DB. It was a nervous couple of hours before I could RESTORE another hastily triggered Full backup, an event that highlighted how precarious and inadequate my maintenance plan was.

I've since returned to retaining my last 2 Full AND Transaction Log backups.


Glen Parker
Post #864494
Posted Friday, February 12, 2010 2:13 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, July 25, 2014 5:21 AM
Points: 1,205, Visits: 923
I've typically kept two full backups (the most recent and the one before that) along with the log backups between them, just in case.

Hi Steve, nice article. It is always necessary to get other people's take on backups. I also keep two full backups but only logs up to the last full backup. Why would you want to keep log backups between? Like to hear your ideas.


Manie Verster
Developer
Johannesburg
South Africa

I can do all things through Christ who strengthens me. - Holy Bible
I am a man of fixed and unbending principles, the first of which is to be flexible at all times. - Everett Mckinley Dirkson (Well, I am trying. - Manie Verster)
Post #864500
Posted Friday, February 12, 2010 2:53 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Wednesday, July 2, 2014 1:09 AM
Points: 834, Visits: 329
2 backups on disk (3 for system tables), 7 days on on site disk/tape, copies offsite.
Restore of main database every month from Live to Dev environment to
a) eliminate any baseline differences in code (bad change control mentality by developers to blame aka "It works so what?")
b) test backup
Post #864510
Posted Friday, February 12, 2010 2:57 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, April 17, 2014 3:29 AM
Points: 238, Visits: 421
Right, just re-read your post, you're not interested in tapes.

Personally I don't see the difference, the only difference between keeping a backup on tape or on disk is that disk is quicker to restore.

Maybe I'm being thick here but a file is a file is a file.

Isn't it?

Anyway, a week, from disk.
Post #864511
Posted Friday, February 12, 2010 3:08 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, June 25, 2013 5:15 AM
Points: 4, Visits: 4
Where I work we keep every single backup, we keep an immediate copy here in the building of the previous day's data, then backup the previous backup to another server somewhere else in the country. There at the other location I think we operate the father father son theory in which you hold 3 copies of that data. Depending on which DB and how important the data is on that DB, we have more/less backups than what i've just said, but thats the typical setup we have here for standard importance DBs
Post #864515
Posted Friday, February 12, 2010 3:10 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, June 25, 2013 5:15 AM
Points: 4, Visits: 4
dcooper 32364 (2/12/2010)
Where I work we keep every single backup, we keep an immediate copy here in the building of the previous day's data, then backup the previous backup to another server somewhere else in the country. There at the other location I think we operate the father father son theory in which you hold 3 copies of that data. Depending on which DB and how important the data is on that DB, we have more/less backups than what i've just said, but thats the typical setup we have here for standard importance DBs

In addition to this, we have some data that is so Old that it's stored on tapes and restoring it is a 2 man job, one person has to scan the data while someone else is manually inserting and removing the next tape,
Post #864516
Posted Friday, February 12, 2010 3:21 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 17, 2012 3:33 AM
Points: 258, Visits: 66
I work in the Insurance industry. We do full backups every weekday to disk and then to tape. The tapes are then sent offsite. The tape rotation we use allows us to restore to any position within the last month and any month end position that we have a tape for. We keep all monthly tapes forever - but expect that the tapes will become unreadable way before then. Is anyone else subject to eDiscovery procedures?


Post #864520
« Prev Topic | Next Topic »

Add to briefcase 12345»»»

Permissions Expand / Collapse