SQL Server Backup and Restore - Simple Talk

Chapter 2: Planning, Storage and Documentation
Example restore requirements and backup schemes
Based on all the information gathered for the SLA, we can start planning the detailed
backup strategy and restore for each database. By way of demonstrating the process, let's
walk through a few common scenarios and the recommended backup strategy. Of course,
examples are only intended as a jumping-off point for your own SQL Server backup and
restore plans. Each server in your infrastructure is different and may require completely
different backup schedules and structures.
Scenario 1: Development server, VLDB, simple file
architecture
Here, we have a development machine containing one VLDB. This database is not structurally
complex, containing only one data file and one log file. The developers are happy
to accept data loss of up to a day. All activity on this database takes place during the day,
with a very few transactions happening after business hours.
In this case, it might be appropriate to operate the user database in SIMPLE recovery
model, and implement a backup scheme such as the one below.
1. Perform full nightly database backups for the system databases.
2. Perform a full weekly database backup for the VLDB, for example on Sunday night.
3. Perform a differential database backup for the VLDB on the nights where you do not
take the full database backups. In this example, we would perform these backups on
Monday through Saturday night.
71