Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Could you briefly say about recommended backup plans depending on database size and backup/restore time.

Currently I have database that is about 1GB in uncompressed state but I expect it will grow very fast so I think it is important to be prepared.

Used system: Windows 2008 Server SQL: SQL Server 2008 Enterprise Edition.

share|improve this question
up vote 4 down vote accepted

Your recovery plans would be dictated by the needs of the business and the resources available - i.e. how critical is the data, what can you afford to lose and how much resilience can you justify for the cost etc.

If you give us more detail about your scenario you'll get some good suggestions coming through but at a basic level you should be looking at a full backup at least weekly (daily if the size doesn't grow too quickly and you can manage it) with more frequent diff backups taken. Log backups typically should be taken every 15 to 30 minutes depending on throughput.

Oh - and make sure your backups are going to a different drive/array or are getting copied to another off server location so that they're available to recover from if you lose the whole box (an easy mistake I've seen made!)

Finally - test, test, test! A backup strategy is no good if you don't know how to restore and/or your backups are corrupt. I'd test weekly.

If you want more resilience then you should look at things like log shipping, mirroring etc...

share|improve this answer

look at the recommendations/ discussion in this serverfault question

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.