Download SQL Server Plug-in User Guide

SQL Server Plug-in 7.3 User Guide

The master database – As the name suggests, this is the main system database. It contains
information about all other databases, as well as SQL Server instance configuration. Back up
this database frequently, especially when system changes are made.

The msdb database – This contains information about backup history, replication, and log
shipping. Protect this database often, using regular backups.

The model database – This a template database for SQL database creation. If customized
database configuration is done, this database needs to be protected by periodic backups
depending on how regularly customization changes.
2. User databases, which are created for or by users. SQL Server 2005 installations provide sample user
databases:

Northwind

AdventureWorks
Notes:
It is strongly recommended that the system (master, model and msdb) databases be backed up in one job, and
the other (user) databases be backed up in one or more other jobs.
During a recovery process, the master database must be restored first, by itself. Then the other system
databases can be restored.
4.10 Restoring System Databases
The master database contains important information about SQL Server installation. If it is damaged or
removed, the SQL Server instance will not start. The process of recovering the master database is described
below.
The msdb database can be restored in the same way as user databases.
The model database can be restored in the same way as user databases.
System databases in SQL Server include the master, model, and msdb databases that are shipped and
installed as part of SQL Server. This section describes how these databases are handled in a VSS snapshot
backup process.
The SQL writer supports restore of both model and msdb databases online, without shutting down the
instance. (This is an additional improvement over MSDE writer behavior).
4.10.1 Restoring the Master Database - VSS type backup
Steps for restoring an SQL Server master database:
1. Stop the SQL Server services.
Page 46