Chapter 3: Backing Up Microsoft SQL Server Databases 29
Chapter 3: Backing Up Microsoft SQL
Server Databases
This section contains information about backing up databases and Transaction
logs using CA ARCserve Backup, the Agent for Microsoft SQL Server, and
Microsoft SQL Server 7.0, Microsoft SQL Server 2000, Microsoft SQL Server 2005
and Microsoft SQL Server 2008.
This section contains the following topics:
Backup Overview
(see page 29)
Dynamic and Explicit Job Packaging
(see page 38)
Back Up a Database
(see page 42)
Backup Overview
To
back up
is to create a copy or image of a database, Transaction Log, Database
Differential, a list of changes that have been made since a previous backup, or a
collection of files or FileGroups on another device (typically a media drive). Use
CA ARCserve Backup and the Agent for Microsoft SQL Server to perform backups
using the SQL Server Backup statement.
Backing up a database creates a copy of its tables, data, system objects, and
user-defined objects. In the event of media failure, if you have been making
regular backups of your databases and their Transaction Logs, you can recover
your databases.
Important!
Transaction Logs are not backed up or truncated during full or
differential database backups. To back up and truncate Transaction Logs,
perform a separate Transaction Log backup. When you perform the Transaction
Log backup, select the Remove inactive entries from Transaction Log option to
truncate the log files. For more information about Transaction Log backups see
Transaction Log Backups in this chapter.
When a Microsoft SQL Server database backup is started in CA ARCserve
Backup, the Agent for Microsoft SQL Server initiates an online backup of the
database. This backup takes place while the database is active. The backup
captures the state of the data at the moment the statement is executed. No
partial transactions are captured. Any data changes made after the backup
begins are not captured in the backed up copy of the database.
