Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Database Backup Shipping Expand / Collapse
Posted Wednesday, December 26, 2007 12:13 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, February 8, 2012 1:38 PM
Points: 56, Visits: 107
We are looking for some off-site database backup storage strategies, and I was hoping that I could get some ideas and/or best practices from the group? Prior to my coming to this company, the previous developer/administrator/programmer/everything under the sun,had no database backups whatsoever taking place. I have changed this by creating regularly scheduled maintenance plans, full, differential, and transaction log backups etc.. However, recently, our clients have required that we keep our database backups off-site completely. Our servers are located in Kentucky, and our business physical locations are in northern Idaho and Washington, and I was just wondering on what you folks do.

Thanks in advance,
Post #436463
Posted Thursday, December 27, 2007 6:23 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Thursday, February 26, 2009 3:02 PM
Points: 515, Visits: 655
In an nutshell: We write all BAK and TRN backup files to a specific folder (DB_BACKUPS) on each database server. Several times a day (depending on the frequency of BAK or TRN writes) a centralized server "picks up" the contents of the "DB_BACKUPS" folder and writes the contents to a Virtual Tape Library (VTL). VTL contents are then written to Tape and are held off site. We have a 2 day retention of backups on local severs, roughly 7 days retention at the VTL and (in theory) limitless on Tape.

Happy T-SQLing

Post #436633
Posted Thursday, December 27, 2007 7:44 AM



Group: General Forum Members
Last Login: Yesterday @ 10:32 AM
Points: 5,645, Visits: 8,169
Two options quickly come to mind:

1) Assuming you are at a colocation facility you can pay them to process and handle backup archival and offsite storage. Or have a third party come in and do it for you (think Iron Mountain or the like).

2) Make some scripts that will zip up your backups (you can avoid this if you use a third party backup compression package) and FTP them across the wire to your facility. This can serve the additional purpose of fairly quick disaster recovery if your kentucky site goes offline. Simply restore the backups at your home site.


Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #436664
Posted Thursday, December 27, 2007 9:18 AM



Group: Administrators
Last Login: Yesterday @ 8:26 PM
Points: 34,363, Visits: 18,575
I've used any of the above techniques. Third parties make the most sense unless you can dedicate someone to go to the bank or somewhere else every day and move tapes.

We've always kept a day's (at least) worth of backups on disk. If possible, move those to another server other than the main server they're from. That way you can quickly recover from an "oops" moment or a disk crash.

I'd also recommend, if possible, that you make 2 tape copies a day. We used to do this, keep one in a safe onsite and one offsite. Tapes are fragile in some ways and they might not restore, which might be the day that you need to restore.

Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #436719
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse