NetVault Backup APM For SQL Server Users Guide

NetVault: Backup
Application Plugin Module (APM)
for SQL Server

version 5.6
Users Guide
MSG-101-5.6-EN-01 03/23/10
Copyrights
NetVault: Backup APM for SQL Server Users Guide
Software Copyright 2010 BakBone Software
Documentation Copyright 2010 BakBone Software
This software product is copyrighted and all rights are reserved. The distribution and sale of this
product are intended for the use of the original purchaser only per the terms of the License
Agreement. All other product trademarks are the property of their respective owners.
The NetVault: Backup APM for SQL Server Users Guide is copyrighted and all rights are
reserved.
This document may not, in whole or part, be copied, photocopied, reproduced, translated,
reduced or transferred to any electronic medium or machine-readable form without prior consent
in writing from BakBone Software.
THIS PUBLICATION IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT.
THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL
ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE
CHANGES WILL BE INCORPORATED INTO NEW EDITIONS OF THE PUBLICATION.
BAKBONE SOFTWARE MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE
PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY
TIME.
19992010 BakBone, BakBone Software, NetVault, Application Plugin Module, BakBone
logo, Integrated Data Protection, SmartDisk, Asempra, FASTRecover, ColdSpark and
Spark Engine are all trademarks or registered trademarks of BakBone Software, Inc., in the
United States and/or in other countries. All other brands, products or service names are or may
be trademarks, registered trademarks or service marks of, and used to identify, products or
services of their respective owners.
BakBone Software
9540 Towne Centre Drive, Suite 100 San Diego, California 92121 866.484.2663
Table of Contents
Chapter 1: Introducing
NetVault: Backup APM for SQL Server
NetVault: Backup APM for SQL Server At a Glance ................................................... 7

Key Benefits ...................................................................................................................... 8
Feature Summary ............................................................................................................. 9
Target Audience .............................................................................................................. 10
Recommended Additional Reading .............................................................................. 10
Technical Support .......................................................................................................... 10
Documentation Updates ................................................................................................ 10
Chapter 2: Installing and Removing SQL Server APM
11
Installation Prerequisites ............................................................................................... 11

Deploying SQL Server APM ........................................................................................... 12
- Important Considerations ............................................................................................................... 12
Installing SQL Server APM ............................................................................................ 13

Removing SQL Server APM ........................................................................................... 14
Chapter 3: Configuring SQL Server APM
17
Configuring Authentication Details .............................................................................. 17

- Removing a SQL Server Instance ................................................................................................. 20
Specifying a Default Configuration (Optional) ............................................................. 20
Chapter 4: Backing Up Data
23
Defining a SQL Server Backup-and-Restore Strategy ................................................ 23

-
Reviewing the Available Backup Methods ..................................................................................... 24

Reviewing SQL Server Recovery Models ...................................................................................... 25
Defining an Online VDI (or Named Pipe) Backup Strategy and Reviewing Types ........................ 26
Examples of VDI Online (or Named Pipe) Backup Sequences ..................................................... 31
Defining a VSS Backup Strategy and Reviewing Types ................................................................ 34
Examples of VSS Backup Sequences ........................................................................................... 35
4
- Backing Up System Databases ..................................................................................................... 36
- Backing Up Replicated Databases ................................................................................................ 37
Performing Backups in SQL Server 2000 .....................................................................38

- Phase 1: Selecting Data for a Backup ........................................................................................... 38
- Phase 2: Setting Backup Options .................................................................................................. 40
- Phase 3: Finalizing and Submitting the Job ................................................................................... 44
Performing Online VDI Backups in SQL Server 2005/2008 .........................................44

Performing VSS Backups in SQL Server 2005/2008 ....................................................51

Chapter 5: Restoring Data
57
Restoring Data An Overview .......................................................................................57

Understanding the Online VDI Restore Process ..........................................................58
-
Reviewing the Phases of the Restore Sequence ........................................................................... 58

Understanding the Available Types of Online VDI Restores ......................................................... 59
Restoring System Databases ........................................................................................................ 61
Restoring Databases Involved in Replication ................................................................................ 62
Restoring Backups in SQL Server 2000 ........................................................................63

- Phase 1: Selecting Data Items for a Restore ................................................................................. 63
- Phase 2: Setting Restore Options .................................................................................................. 67
Restoring Online VDI Backups in SQL Server 2005/2008 ............................................69

- Phase 1: Selecting Data Items for a Restore ................................................................................. 70
- Phase 2: Setting Restore Options .................................................................................................. 74
Restoring VSS Backups in SQL Server 2005/2008 .......................................................77

- Phase 1: Selecting Data for a Restore ........................................................................................... 77
- Phase 2: Setting the Restore Options ............................................................................................ 79
Using Other Restore Procedures ...................................................................................80

- Renaming or Relocating a Database ............................................................................................. 80
- Restoring a Database to an Alternate Instance ............................................................................. 83
NetVault: Backup
APM for SQL Server Users Guide
- Restoring to an Alternate SQL Server ........................................................................................... 84
Appendix A: Using SQL Server APM in a Failover Cluster

Environment
87
SQL Server Failover Clustering An Overview ........................................................... 87

About this Appendix ....................................................................................................... 88
- Important Considerations ............................................................................................................... 88
Installing SQL Server APM ............................................................................................ 89

- Installation Prerequisites ................................................................................................................ 89
- Installing the Software .................................................................................................................... 89
Licensing SQL Server APM ........................................................................................... 90

Configuring SQL Server APM ........................................................................................ 90
Backing Up Data ............................................................................................................. 91
Restoring Data ................................................................................................................ 92
Using Multiple SQL Server Virtual Servers in the Same Failover Cluster ................. 93
-
Installation Requirements .............................................................................................................. 93

Configuration Requirements .......................................................................................................... 94
Backup Requirements .................................................................................................................... 95
Restore Requirements ................................................................................................................... 95
Appendix B: Troubleshooting
97
Troubleshooting ............................................................................................................. 97
NetVault: Backup
Chapter 1:
INTRODUCING
NETVAULT: BACKUP
APM FOR SQL SERVER
1.1.0
NetVault: Backup APM for SQL Server At a Glance
Key Benefits
Feature Summary
Target Audience
Recommended Additional Reading
Technical Support
Documentation Updates
NetVault: Backup APM for SQL Server At a

Glance
NetVault: Backup (NVBU) APM for SQL Server (SQL Server APM) increases
confidence in recoverability of SQL Server databases and eliminates the need for
complex scripting.
Through an intuitive graphical user interface (GUI) and automated workflow, the
APM offers users a centralized console to set up, configure, and define backup
and restore policies. Support for Online Virtual Device Integration (VDI) and
Volume Shadow Copy Service (VSS) backups provides users with the flexibility
to implement their preferred backup method, without requiring them to learn SQL
Server internals. SQL Server APM offers granular control, which allows users to
restore complete databases, partial databases, or individual data files quickly and
reliably, thereby minimizing downtime.
Through automatic integration with a wide range of backup devices, you can be
confident that your SQL Server is being protected, and that it is stored offsite for
disaster recovery purposes that provide proven business continuity.
Chapter 1
Introducing NetVault: Backup APM for SQL Server
1.2.0
Key Benefits
Increases Confidence and Reduces Risk While Deploying SQL Server

With SQL Server APM, database administrators (DBAs) no longer have to
worry about learning SQL Server internals before being able to implement a
backup policy that is flexible enough to account for a large number of
recovery scenarios. DBAs have the flexibility to choose the best method for
the job whether it is VDI, which provides maximum reliability and performance
while supporting the full range of SQL Server backup and restore
functionality, or Microsofts VSS framework, which allows volume backups to
be performed while applications on a system continue to write to the volumes,
all without writing complex scripts.
SQL Server APMs flexible backup features also include:
Online VDI- or VSS-based backups
Full, Differential Database backups while data is online and accessible
Incremental Transaction Log and Tail-Log backups
Copy-Only backups
Advanced Full and Differential File backups along with Partial Database
and Differential Partial Database backups
Protection for Filestreams
Protection down to the datafile level
Backup-compression support
Creation of backup checksums that are used during restores to detect

corruption
By relying on SQL Server APM to implement backup policies, DBAs can be

freed to focus on more critical tasks without risking the ability to recover
exactly what is needed in the unfortunate event of a failure. In addition, the IT
managers confidence is increased by knowing that SQL Server data is
protected, no matter what.
Speeds Up Restores to Reduce Downtime With SQL Server APM, DBAs

are no longer required to create a script or manually issue each command
required in the recovery process. Select what needs to be restored, the
backup set to restore from, and, if appropriate, the time or marked transaction
restore point, and SQL Server APM automatically performs the recovery
without further interaction. Not only are restores faster due to the reduced
reliance on human interaction, the chance for a syntax error in a manual
execution that would require a restart is eliminated, too.
Additional SQL Server APM restore and recovery features include:
Full, differential, incremental, and time and marked transaction point-intime restores
NetVault: Backup
Restores of complete databases, partial databases, or individual datafiles
Rename of datafiles
Restore VDI-based backups to an alternate server
Disaster recovery
Ensure Business Continuity with Automatic Integration of Backup

Devices With offsite backups being an important part of the data protection
plan for any mission-critical application, SQL Server APM takes advantage of
NVBUs fundamental integration with a wide range of backup devices, which
includes tape libraries, stand-alone tape devices, virtual tape (disk) libraries,
and shared virtual tape libraries. NVBU lets you select which backup device
to store the backup on. You can store the backup online in a virtual tape
library and duplicate the job to physical tape libraries shared by multiple SQL
Server databases, other proprietary databases, or used for backup.
SQL Server APM gives you the confidence that your SQL Server
environment is being protected, and that it is stored offsite for disaster
recovery purposes. At the same time, it frees administrators from being
present 24x7 as less-experienced SQL Server personnel can initiate restores
with the confidence that they will be performed correctly and as quickly as
possible, thereby reducing downtime and improving business continuity.
1.3.0
Feature Summary
Online VDI- or VSS-based backups
Full, Differential Database backups while data is online and accessible
Incremental Transaction Log and Tail Log backups
Copy-Only backups
Advanced Full and Differential File backups along with Partial Database and
Differential Partial Database backups
Protection for Filestreams
Protection down to the datafile level
Backup-compression support
Creation of backup checksums that are used during restores to detect

corruption
Full, differential, incremental, and time and marked transaction point-in-time
Verify-only restore option
Restores of complete databases, partial databases, or individual datafiles
Rename of datafiles
Restore VDI-based backups to alternate server
Disaster recovery
10
Chapter 1
Introducing NetVault: Backup APM for SQL Server
1.4.0
Target Audience
This guide is intended for users who are responsible for the backup and recovery
of SQL Server. Familiarity with SQL Server administration and the operating
system (OS) under which the database is running is assumed. Advanced
knowledge of SQL Server would be useful for defining an efficient backup and
recovery strategy for the database.
1.5.0
Recommended Additional Reading

BakBone recommends that you have the following documentation available for
reference while setting up and using this APM.
SQL Server 2008 Books Online

http://technet.microsoft.com/en-us/library/ms130214.aspx

http://technet.microsoft.com/en-us/library/ms130214(SQL.90).aspx

http://technet.microsoft.com/en-us/library/dd631854(SQL.10).aspx
Volume Shadow Copy Service

http://msdn2.microsoft.com/en-us/library/aa384961.aspx
1.6.0
Technical Support
BakBone Software is dedicated to providing friendly, expert advice to its
customers. BakBones highly trained professionals are available to answer
questions, offer solutions to problems, and generally help make the most of any
BakBone software purchase. Log on to the web site for more information.
http://www.bakbone.com/supportportal
1.7.0
Documentation Updates
For late-breaking documentation updates, refer to the BakBone Software
Knowledge Base. BakBones Knowledge Base article for NVBU APM for SQL
Server can be found at:
http://kb.bakbone.com/5420
NetVault: Backup
11
Chapter 2:
INSTALLING AND REMOVING

SQL SERVER APM
Installation Prerequisites
Deploying SQL Server APM
2.1.0
Important Considerations
Installing SQL Server APM
Removing SQL Server APM
Before installing the SQL Server APM, make sure the following software is
installed and properly configured on the machine that is to serve as the SQL
Server:
NVBU Server/Client Software At a minimum, the Client version of NVBU

software must be installed on the machine configured as the SQL Server.
SQL Server Software The machine must be running a supported version

of SQL Server. For a list of supported versions, refer to the NetVault: Backup
Supported APM and Plugin Platforms compatibility matrix. This matrix is
available at:
www.bakbone.com/documentation
Important: Service Pack 2 is a requirement for SQL Server 2005 to run on

Windows 2008 (both 32-bit and 64-bit). See:
www.microsoft.com/sqlserver/2005/en/us/system-requirements.aspx#ws
SQL Server VSS Writer Services If you want to implement a VSS backup
strategy for SQL Server 2005/2008 databases, the SQL Server VSS Writer
service must be running. The SQL Server VSS Writer is automatically
installed with SQL Server 2005/2008. However, the service is not set to start
automatically. To enable VSS backups, start this service from the Windows
Services panel (Start > Control Panel > Administrative Tools > Services).
BakBone recommends that you set the startup type for this service to
Automatic.
Note: For Users Upgrading from a Previous Version of SQL Server APM
With the introduction of SQL Server APM v5.0, SQL Server APMs internal name
has changed from MS SQL to SQL Server. When upgrading to v5.x from an
12
Chapter 2
Installing and Removing SQL Server APM
earlier version, do not remove the earlier version of the software before installing
v5.0. Installing v5.0 over an earlier version ensures that the backups created using
the previous versions can be restored using SQL Server APM v5.0. If you have
accidentally removed the previous version prior to installing v5.0, reinstall the
previous version first, and then install SQL Server APM v5.0; otherwise, the
previous backups will not be visible on the Selections tab in the Restore window.
NVBUs Application Cluster Support functionality offers support for the backup and
restore of clustered instances of SQL Server (Active/Passive). For complete
details on the installation, configuration, and backup procedures required to set up
this functionality with the SQL Server APM, see Using SQL Server APM in a
Failover Cluster Environment on page 87.
2.2.0
Deploying SQL Server APM

While it is possible to set up a single machine as both the NVBU Server and the
SQL Server (that is, all software installation and configuration requirements are
performed on a single machine), BakBone recommends that these two entities
exist on separate machines.
Figure 2-1:
Deployment
NetVault: Backup Server

SQL Server APM
NetVault: Backup Client Software
NetVault: Backup Server
2.2.1
SQL Server Machine
Regardless of configuration environment in place (that is, separate NVBU

Sever and SQL Server, vs. a single machine configured as both), the
SQL Server APM must be installed on the host where SQL Server resides.
Sample images and procedures throughout this guide assume that this twomachine environment is in place and all configuration requirements have
been met.
NetVault: Backup
13
If you have implemented SQL Server Replicated Databases, based on the

replication type and the database backup and recovery requirements, you
must obtain the required number licenses for SQL Server APM, and install
the APM on each host to be included in the SQL Server Replication
environment, including the following:
Publisher SQL Server APM must be installed on this node regardless

of the replication type implemented.
Distributor In case of Local Distributor, the Distributor will be running on

the same node as the Publisher. However, in case of a Remote
Distributor, the SQL Server APM must be installed on the Distributor host.
Subscriber If you want to back up the changed data in Subscriber

database, SQL Server APM must be installed on the Subscriber hosts.
This will allow you to synchronize the Publication database with the
Subscription database after recovery. If SQL Server APM is not installed
on the Subscriber nodes, you must re-initialize all subscription to the
publications in the Publication database after recovery.
The SQL Server APM will consider each of these nodes as individual Clients.
2.3.0

To install SQL Server APM, perform the following steps:
1. From the NVBU Console running on the NVBU Server, access the Client
Management window by clicking either of the Client Management buttons
on the command toolbar (or by selecting Client Management from the
Administration menu).
2. In the Clients pane, locate the machine configured as the SQL Server, rightclick it, and select Install Software from the pop-up menu.
Figure 2-2:
SQL Server
already added
to the NVBU
Server as a
Client
14
Chapter 2
3. In the additional window that appears, navigate to the location of the .npk
installation file for the SQL Server APM (for example, the NetVault: Backup
APM Installation CD or the directory to which the file was downloaded from
the BakBone web site).
Based on the OS in use, the directory path for this software may vary on the
installation CD.
4. Select the file entitled sql-xxxx.npk (where xxxx represents various
software platforms and version numbers), and click Open.
The installation process will occur automatically.
5. When the Install Software dialog appears that indicates the software was
successfully installed, click OK to dismiss it.
Figure 2-3:
Install
Software
dialog
2.4.0
Removing SQL Server APM

To remove SQL Server APM, perform the following steps:
1. In the Clients pane of the Client Management window, locate the machine
that houses the SQL Server APM (that is, the one configured as the SQL
Server), right-click it, and select Remove Software from the pop-up menu.
2. In the list of installed plugins that is displayed in the Remove Software
dialog, locate the SQL Server Application Plugin Module item and select it.
Figure 2-4:
Remove
Software
dialog with
SQL Server
APM selected
for removal
3. To begin the removal process, click Remove.
NetVault: Backup
15
4. When the Remove Software dialog appears, click OK to proceed (or Cancel
to abort).
Figure 2-5:
Remove
Software
dialog
5. When the confirmation message appears that indicates the software was
removed, click OK to close the dialog and return to the Client Management
window.
Figure 2-6:
Software
removed
successfully
16
Chapter 2
NetVault: Backup
17
Chapter 3:
CONFIGURING
SQL SERVER APM
Configuring Authentication Details
3.1.0
Removing a SQL Server Instance
Specifying a Default Configuration (Optional)
Configuring Authentication Details

Before initiating a backup, you must configure the APMs authentication details,
which includes authentication mode, user name, and password.
SQL Server provides two authentication modes: Windows Authentication and SQL
Server Authentication.
Windows Authentication With Windows Authentication, the user connects

through a Microsoft Windows user account. SQL Server validates the
account name and password using information in the Windows OS. This is
the default authentication mode, and is much more secure than Mixed Mode,
which allows a combination of Windows authentication and SQL Server
Authentication.
Windows Authentication uses Kerberos security protocol, provides password
policy enforcement in terms of complexity validation for strong passwords,
provides support for account lockout, and supports password expiration.
Microsoft strongly recommends implementing a Windows Authentication
mode for SQL Server.
SQL Server Authentication With SQL Server Authentication, you must

provide the user name and password for a SQL Server user with the
sysadmin server role.
To configure authentication:
1. From the NVBU Console running on the NVBU Server, open the Backup
window (via either of the toolbar buttons or by clicking Operations >
Backup).
A list of NVBU Clients is displayed on the Selections tab.
2. Locate the Client configured as the SQL Server, and open it to display a list of
APMs/plugins installed on the machine.
18
Chapter 3
Configuring SQL Server APM
To open any node on the Selections tab, do either of the following:
Double-click the node.
Right-click the node, and select Open from the pop-up menu.
3. Locate SQL Server APM in the list, and open it.

4. Right-click the All Instances node, and select Configure from the pop-up
menu.
Figure 3-1:
Configure
command
selected
The Configure dialog appears

Figure 3-2:
Configure
dialog
5. Complete the applicable fields:
Logon security mode Based on the Authentication Mode set for the
SQL Server, you can specify either a Windows Administrator or a SQL
Server Administrator account. To specify a Windows Administrator
account, select the Windows option. For a SQL Server Administrator
account, select SQL Server.
Important: You can only select SQL Server if the SQL Server Authentication
Mode is set to Mixed Mode/SQL Authentication.
NetVault: Backup
Login Details Depending on the option selected in the Logon security

mode frame, provide the appropriate account information in this frame:
19
For Windows authentication, provide the following information:
Administrator User Name Specify either a Local or Domain

Windows Administrator user name.
Password Enter the password associated with the

Administrator User Name.
Windows Domain If a Domain Administrator is specified in the

Administrator User Name field, enter the name of the domain.
You can leave this field blank if a Local Administrator user name is
specified.
For SQL Server authentication, provide the following information:
Administrator User Name Specify a SQL Server user with the

sysadmin server role.
Password Enter the password associated with the

Administrator User Name.
Instance Name Specify the exact name of the SQL Server instance
running (for example, SQLSERVER if the default instance, or
<HostName>\<InstanceName> and so on). As the instance is
successfully located, it is displayed on the Selections tab in the Backup
window for browsing and inclusion in a backup job.
Important: If a particular instance of SQL Server in a multiple-instance

environment cannot be accessed by NVBU (that is, it is not accessible in the
various windows of the NVBU Console), the exact instance or SQL Server name
of this machine must be manually entered in this field.
If both SQL Server 2000 and SQL Server 2005/2008 instances co-exist on a SQL
Server, the SQL Server APM will display only the SQL Server 2005/2008
instances by default. In this mixed environment, to configure the SQL Server 2000
instances, you must first remove all SQL Server 2005/2008 instances from NVBU,
and then add the SQL Server 2000 instances.
For the steps to remove an instance, see Removing a SQL Server Instance on
page 20. To add an instance again, reconfigure the authentication details and
specify the instance name in the Instance Name field. You can find the name of
the removed instance by looking at Administrative Tools > Services in the
Windows Control Panel.
6. Click OK to complete the configuration.
With the account properly configured, you can click the All Instances node to
display the specified instances.
20
Chapter 3
3.1.1
Removing a SQL Server Instance

To remove a SQL Server instance, follow these steps:
1. From the NVBU Console, open the Backup window (via either of the toolbar
buttons or by clicking Operations > Backup).
A list of NVBU Clients is displayed on the Selections tab.
2. Locate the Client configured as the SQL Server, and open it for a list of

4. Open the All Instances node to view all added instances.
5. To remove an instance, right-click it, and select Remove from the pop-up
menu.
Figure 3-3:
Remove
command
selected to
remove a SQL
Server
instance
3.2.0
Specifying a Default Configuration (Optional)

SQL Server APM provides the ability to set default options for backup and restore
jobs. You can override these options on a per job basis. You can set the default
options via the NVBU Remote Configurator.
To set these default options, perform the following steps:
1. From the NVBU Console, access the Client Management window.
2. In the Clients pane, locate the machine configured as the SQL Server, rightclick it, and select Configure from the pop-up menu.
NetVault: Backup
21
3. In the Remote configurator window, select the Plugin Options tab.

Figure 3-4:
SQL Server
APM-related
configuration
options
available in the
NVBU Remote
configurator
4. Select the SQL Server APM tab, where the following options are displayed:
Error Encountered During Checksum SQL Server lets you specify the
action that should be taken if an error is encountered when performing
checksums on backups and restores. You can specify the default action to
take on encountering checksum errors by selecting one of the following
two options from the drop-down list:
Continue after error This is the default action set during the APM
installation. With this value selected, the backup or restore job will
continue in spite of checksum errors.
Stop on error Select this option to set it as the default action. With
this value selected, the backup or restore job will stop when a
checksum error is encountered.
New Database Found in Differential/Incremental Backup If a new

database is found while performing Transaction Log or Differential
Database backups and the Instance Node is selected on the Selections
tab in the Backup window, you can choose to either ignore it or take a full
backup of it. You can set this action globally for all Transaction Log and
Differential Database backups by selecting the applicable action from the
drop-down list provided here:
Do full database backup This is the default action set during the
APM installation. Retaining this option will instruct the APM to perform
full backup of all the new databases that have been added since the
last Full Database or Database - Complete backup.
Ignore Selecting this option will request that the SQL Server APM
ignore any databases that have been created since the last Full
Database or Database - Complete backup (that is, any databases
that were created after the last backup will be left out of the
Transaction Log or Differential Database backup).
22
Chapter 3
Undo File for Standby Restores For performing Standby Restores the
SQL Server APM requires a temporary Undo File. It is required only when
the Action After Restore field on the Restore Options tab is set to With
STANDBY; More Transaction Logs can be Restored (SQL Server
2000) or With STANDBY (SQL Server 2005/2008).
By default, the path is blank. Specify the directory path for the temporary
UNDO.DAT file in this field.
Incomplete Backup of ALL Items Selected The SQL Server APM can
do one of the following when this error condition occurs:
Complete with Warnings Saveset Retained The job returns a

status of Backup Completed With Warnings and a backup saveset
is created that includes the items that were successfully backed up.
Complete without Warnings Saveset Retained The job

completes and returns a status of Backup Completed. While errors
are logged in the NVBU binary logs, the errors are essentially ignored
in the Job Management window and a backup saveset is created that
includes the items that were backed up successfully.
Fail Saveset Retained The job returns a status of Backup

Failed. However, a backup saveset is generated that includes the
items that were successfully backed up.
Fail No Saveset Retained The job returns a status of Backup

Failed and no saveset of backed up objects is kept. That is, even if
some of the objects were successfully backed up, the saveset is
discarded.
If either of the following occurs, the SQL Server APM overrides the
Incomplete Backup of ALL Items Selected setting and responds as
indicated:
If a fatal error occurs, the job returns a Backup Failed status.
If a Partial Database or Differential Partial Database backup is

performed on a database whose backup target contains a read-only
filegroup, the job returns a Backup Completed With Warnings
status.
5. Click the OK button to apply the settings, and close the Remote
configurator window.
Now, when the Backup Options tab is accessed for defining a job, each
option will be automatically set to the action type specified in this procedure.
Important: This only changes how these options are set by default on the Backup
Options and Restore Options tabs. You can still change the action type on a perjob basis.
NetVault: Backup
23
Chapter 4:
BACKING UP DATA
4.1.0
Defining a SQL Server Backup-and-Restore Strategy
Reviewing the Available Backup Methods
Reviewing SQL Server Recovery Models
Defining an Online VDI (or Named Pipe) Backup Strategy and Reviewing
Types
Examples of VDI Online (or Named Pipe) Backup Sequences
Defining a VSS Backup Strategy and Reviewing Types
Examples of VSS Backup Sequences
Backing Up System Databases
Backing Up Replicated Databases
Performing Backups in SQL Server 2000
Phase 1: Selecting Data for a Backup
Phase 2: Setting Backup Options
Phase 3: Finalizing and Submitting the Job
Performing Online VDI Backups in SQL Server 2005/2008
Performing VSS Backups in SQL Server 2005/2008
Defining a SQL Server Backup-and-Restore

Strategy
The purpose of creating SQL Server backups is to recover a database that is
damaged from media failure or data corruption. Reliable use of backup for
recovery requires a well-designed backup-and-restore strategy that maximizes
data availability and minimizes data loss, taking into account defined business
requirements.
24
Chapter 4
Backing Up Data
A backup-and-restore strategy is divided into two pieces: a backup piece and a
restore piece.
The backup piece defines the type and frequency of backups that are
required to meet the goals for availability of the database and for minimizing
data loss.
The restore piece defines who is responsible for performing restores, and
how restores should be performed to recover from the particular type of
damage or failure.
Important: If you use SQL Server APM, make sure that you are not using a thirdparty program to complete additional backups of SQL Server. Otherwise, a conflict
might occur during the restore or recovery process when the differential backups
do not match.
4.1.1
Reviewing the Available Backup Methods

SQL Server APM offers the following backup methods:
Online Virtual Device Interface (VDI)
Online Named Pipe SQL Server 2000 Only
Volume Shadow Copy Service (VSS) SQL Server 2005/2008
SQL Server APM supports implementing an Online VDI or a pure VSS backup
strategy; that is, your backup strategy should include either Online VDI backups or
VSS backups, not a combination of the two.
4.1.1.a
Online Virtual Device Interface (VDI)

Microsoft supports the ability to perform online backups that use the VDI
Application Program Interface (API) to integrate seamlessly with the wide range of
backup devices supported by NVBU. Online VDI backups provide maximum
reliability and flexibility when defining a backup strategy. This method supports the
full range of backup types and options available with SQL Servers Transact SQL
language along with the ability to handle a number of recovery scenarios.
The backup-and-restore strategies available with the Online via VDI Backup
Method are thoroughly discussed in the Backing Up and Restoring Databases
section of the SQL Server Books Online.
SQL Server APMs Online via VDI backup method is available for SQL Server
2000, 2005, and 2008 and is the preferred backup method.
4.1.1.b
Online Named Pipe

For SQL Server 2000, Microsoft also supports the ability to perform online
backups that use named pipes to integrate seamlessly with the wide range of
backup devices supported by NVBU. A named pipe is an Inter Process
NetVault: Backup
25
Communication construct that allows programmatic communication between a

client and a server.
Online Named Pipe backups provide reliability and flexibility when defining a
backup strategy. This method supports the full range of backup types and options
available with SQL Servers Transact SQL language along with the ability to
handle a number of recovery scenarios.
SQL Server APMs Online via Named Pipes method is only available for SQL
Server 2000.
4.1.1.c
Volume Shadow Copy Service (VSS)

Microsoft supports the ability to create snapshots of SQL Server data using VSS.
VSS allows volume backups to be performed while applications on the system
continue to write to the volumes. With SQL Server 2005/2008, Microsoft provides
a SQL Writer that permits backup programs such as SQL Server APM to copy
SQL Server data while SQL Server is running. VSS-based backups do not
negatively impact SQL Servers performance or stability.
The SQL Server APMs VSS backup method is available for SQL Server 2005/
2008.
Important: The most prominent disadvantage to the VSS backup method is that
the SQL Writer does not support the ability to restore a database to an alternate
SQL Server Instance whether that Instance is located on the same server and
host or an alternate server and host.
4.1.2
Reviewing SQL Server Recovery Models

When a database is created, a recovery model is enabled. Microsoft defines a
recovery model as a database property that controls the basic behavior of backup
and recovery of the database. The databases recovery model controls how its
transactions are logged, whether the transaction log can be backed up, and which
kinds of restores are supported. SQL Server provides three different recovery
models: Simple, Full, and Bulk-Logged.
Simple Recovery Model With a Simple Recovery Model, log backups are
not supported. Therefore, changes since the most recent backup are not
protected. In the unfortunate event of failure, these changes must be reexecuted. Point-in-time recovery is not allowed.
Full Recovery Model Full Recovery Model databases require log backups;
therefore, no work is lost due to a lost or damaged data file. Point-in-time
recovery is supported, assuming backups are complete up to the point-offailure.
Bulk-Logged Recovery Model Bulk-Logged Recovery Model databases

require log backups. The Bulk-Logged Recovery Model is a variation of the
26
Chapter 4
Backing Up Data
Full Recovery Model that permits high-performance bulk-copy operations.
This model reduces log space usage by bulk-logging most bulk operations. If
a log is damaged or bulk-operations have occurred since the most recent
Transaction Log backup, these changes must be re-executed. Point-in-time
recovery is not supported for bulk-logged databases.
4.1.2.a
Choosing the Best Recovery Model

Consider the following when choosing a recovery model for a database:
Simple Recovery Model The Simple Recovery Model should only be

enabled for databases that are not updated frequently such as test,
development, or databases mostly containing read-only data.
Full Recovery Model The Full Recovery Model should be enabled for
transactional databases where full recoverability and preventing work loss in
a full range of recovery scenarios is required.
Bulk-Logged Recovery Model The Bulk-Logged Recovery Model should

be used temporarily when bulk operations, such as bulk inserts or index
creation, are performed on Full Recovery Model databases. The Bulk-Logged
Recovery Model increases performance and reduces log space consumption
during these operations; you can switch databases back to full recovery
immediately after the bulk operations have completed.
For more information, refer to Recovery Models and Transaction Log

Management in the SQL Server Books Online.
4.1.3
Defining an Online VDI (or Named Pipe) Backup

Strategy and Reviewing Types
After selecting the recovery model that best meets your business requirements for
each database, you are ready to design and implement a corresponding backup
strategy. When defining a SQL Server Online VDI Backup strategy, the DBA must
answer the following questions:
Is there a predictable off-peak period for full backups?
What is the frequency of updates and changes?
Are changes confined to a small or large number of tables in a database?
Answering these questions will help the DBA define the type and frequency of
backups that should be implemented.
SQL Server APM provides the following types of Online VDI Backup:
Full Database
Differential Database
Copy-Only
Incremental Transaction Log
NetVault: Backup
4.1.3.a
Tail-Log
Full File and Filegroup
Differential File and Filegroup
Partial Database
Differential Partial Database
27
Full Database Backup

Full Database backups are supported by:
SQL Server Versions All
Recovery Models All
A Full Database backup is a backup of the entire database. In SQL Server 2005, a
Full Database backup also includes part of the transaction log, which enables
recovery of the database to the point at which the backup was completed.
Full Database backups consume more space and time per backup and are
typically supplemented by differential backups, which are created more frequently.
With Full Database backups, you can re-create an entire database in one step by
restoring the database.
4.1.3.b
Differential Database Backup

Differential Database backups are supported by:
Recovery Model All
With a Differential Database, back up only the data that has changed since the last
Full Database backup is backed up. Differential backups are smaller and faster to
create than the full backups.
A Differential Database backup is useful if some of the databases tables are
modified more frequently than others. In this case, Differential Database backups
allow you to back up frequently without the overhead of Full Database backups.
4.1.3.c
Copy-Only Backup
Copy-Only backups are supported by:
SQL Server Versions 2005 and 2008
Recovery Models All
Copy-Only backups are independent of the normal sequence of backups. A CopyOnly data backup does not impact the differential bitmap, so subsequent
differential backups are unaffected by the Copy-Only backup. These types of
backups are ideal for situations that require special purposes, such as creating
test environments or standby databases.
28
Chapter 4
Backing Up Data
4.1.3.d
Incremental Transaction Log Backup

Incremental Transaction Log backups are supported by:
Recovery Models Full or Bulk-Logged Only
SQL Server Transaction Logs are essential to data recovery and need to be
backed up regularly. With Transaction Log backups, you can recover the database
to a point-of-failure or specific point-in-time.
An Incremental Transaction Log backup captures all the transaction logs including
the transaction logs that have been generated since the last Full Database/File or
Filegroup, Differential Database/File or Filegroup, or Incremental Transaction Log
backup. An Incremental Transaction Log backup should not be performed in the
following conditions:
4.1.3.e
Until a Full Database or Full File and Filegroup backup has been created
because the transaction log contains changes made to the database after the
last backup was created.
After the transaction log has been manually truncated, until a Full Database
or Differential Database backup has been performed. Microsoft strongly
recommends against manually truncating transaction logs.
Tail-Log Backup
Tail-Log backups are supported by:
Recovery Models Full Only
A Tail-Log backup captures the transaction logs that have not yet been backed up
and is the last backup restored in a restore sequence. SQL Server 2005/2008
requires you to back up the tail of the log before restoring a database that is
currently attached to the SQL Server instance. Therefore, a Tail-Log backup is the
first step in most restore sequences.
A Tail-Log differs from an Incremental Transaction Log in the following ways:
If the database is damaged or offline, for example, the database does not
start, a Tail-Log backup can be attempted. However, taking a Tail-Log
backup succeeds only if the log files are undamaged, the database is in a
state that supports Tail-Log backups, and the database does not contain any
bulk-logged changes.
A Tail-Log might contain incomplete metadata if the database is damaged

because some of the metadata normally available for log backups may be
unavailable in a Tail-Log backup. However, the captured log is complete and
usable.
NetVault: Backup
4.1.3.f
29
Full File and Filegroup Backup

Full File and Filegroup backups are supported by:
Recovery Models All (2005/2008) or Full or Bulk-logged Only (2000)
A Full File and Filegroup backup backs up all the data in one or more files or
filegroups. A complete set of Full File and Filegroup backups is equivalent to a Full
Database backup.
Full File and Filegroup backups have the following advantages over Full Database
backups:
With a Full File and Filegroup backup, you can back up and restore the files
in a database individually. This can speed up the recovery process as it is
possible to restore only damaged files without restoring the rest of the
database.
Full File and Filegroup backups increase the flexibility in dealing with large
databases that contain data with varying update characteristics. For example,
consider the following recommendations:
Back up frequently modified data often.
Back up infrequently modified data less often.
Back up read-only data once.
The primary disadvantage of Full File and Filegroup backups is the risk that a
media failure can render an entire database unrecoverable if a damaged file lacks
a backup.
In SQL Server 2000, Full File and Filegroup backups are not supported for Simple
Recovery Model databases. In addition, Full File and Filegroup backups do not
contain log records, and you must explicitly apply a log backup to recover their
data.
In SQL Server 2005/2008, by default, file backups contain enough log records to
roll forward the file to the end of the backup operation. Under Simple Recovery
Model in SQL Server 2005/2008, the Full File and Filegroup backups are restricted
to read-only secondary filegroups. You can create a file backup of a read/write
filegroup, but before you can restore the read/write file backup, you must set the
filegroup to read-only and take a differential read-only file backup.
4.1.3.g
Differential File and Filegroup Backup

Differential File and Filegroup backups are supported by:
Recovery Models All (2005/2008)/ Full or Bulk-logged Only (2000)
A Differential File and Filegroup backup captures only the data changed since the
last file backup. In SQL Server 2005/2008, these backups are extremely fast
30
Chapter 4
Backing Up Data
because the Database Engine tracks changes made since the file was last backed
up, eliminating the need to scan the file.
For Simple Recovery Model databases, Differential File backups provide a quick
and space-saving way to create current file backups while dramatically reducing
recovery time for Full Recovery Model databases by reducing the number of
transaction logs that must be restored.
Differential File and Filegroup backups should be considered when:
4.1.3.h
You are backing up some files much less frequently than others.
Your files are large and the data is updated infrequently, or the same data is
updated repeatedly.
Partial Database Backup

Partial Database backups are supported by:
Recovery Models Simple
Designed to create more flexibility for Simple Recovery Model databases, a Partial
Database backup is similar to a Full Database backup except that a Partial
Database backup does not contain all the databases filegroups. A Partial
Database backup contains all the data in the primary filegroup and every readwrite filegroup. Optionally, specified read-only files can also be included. However,
a partial backup of a read-only database contains only the primary filegroup.
A Partial Database backup is useful when a database contains read-only files that
do not need to be included in every database backup. A Partial Database backup
can also be used as a basis for a piecemeal restore scenario, which will be
supported in a future release of the APM.
4.1.3.i
Differential Partial Database Backup

Differential Partial Database backups are supported by:
Recovery Models Simple
Used only with Partial Database backups, a Differential Partial backup contains
only those extents changed in the primary filegroup and read-write filegroups
since the previous partial backup. If only some of the data captured by a partial
backup has changed, using a Differential Partial backup lets you back up
frequently without the overhead of Full Database backups.
For more information on the effect of adding, deleting, or modifying Filegroups on
Partial Differential backups, refer to Differential Partial Backups in the SQL Server
Books Online.
NetVault: Backup
4.1.4
31
Examples of VDI Online (or Named Pipe) Backup

Sequences
Following are a few examples of backup sequences that support multiple restore
scenarios and that you can implement to meet your SQL Server data protection
requirements.
4.1.4.a
Simple Recovery Model Backup Sequences

Full Database Backups Only
When business requirements guarantee data protection up to the previous day,
performing Full Database backups nightly should be sufficient when one or more
of the following conditions exist:
Backup windows are large.
Databases are small.
Updates are infrequent across entire database.
Databases are only for testing or development purposes.
Entire database is read-only.
Full Database + Differential Database Backups

When business requirements guarantee data protection up to the previous day
and backups have to be as fast as possible, Full Database backups coupled with
Differential Database backups is a valid strategy. For example, Full Database
backups are performed every Sunday night at 11:00 P.M. while Differential
Database backups are performed Monday through Saturday at 11:00 P.M. Each
Differential Database backup will include all the changes since the last Full
Database backup, which is known as the differential base.
No matter when recovery is performed, the same number of restore jobs is
required. For example, if recovery is performed on Tuesday, Sundays Full
Database backup and Mondays Differential Database must be restored.
Whereas, if recovery is performed on Thursday, Sundays Full Database backup
followed by Wednesdays Differential Database backup must be restored.
Even though Differential Database backups will increase not only in size but in
duration, restores are quicker due to the fewer number of restore jobs that must be
executed.
Full File and Filegroup Backups + Partial Database Backups

When a Simple Recovery Model database includes secondary read-only
filegroups, a valid backup strategy might include Partial Database backups for the
primary and read-write filegroups and Full File and Filegroup backups for readonly secondary filegroups. This ensures recoverability of the entire database
without requiring the read-only filegroups to be unnecessarily backed up every
time the read-write filegroups are backed up.
32
Chapter 4
Backing Up Data
Secondary read-only filegroups only need to be backed up once after the initial
load and after subsequent updates. When business requirements guarantee data
protection up to the previous day for read-write filegroups, performing nightly
Partial Database backups should be sufficient.
Full File and Filegroup Backups + Partial Database + Differential

Partial Database Backups
When business requirements guarantee data protection for read-write data up to
the previous day and backups have to be as fast as possible, Partial Database
backups coupled with Differential Database Backups for the read-write data and
Full File and Filegroup backup for the secondary read-only filegroups is a valid
strategy.
For example, Full File and Filegroup backups are performed for read-only data
only after the initial load and subsequent updates, while Partial Database
backups, which include the primary filegroup and all read-write filegroups, are
performed every Sunday night at 11:00 P.M. In addition, Differential Partial
Database backups for the same read-write filegroups are performed Monday
through Saturday at 11:00 P.M. Each Differential Partial Database backup includes
all the changes since the last Partial Database Backup, which is known as the
differential base.
required. For example, if recovery is performed on Tuesday, Sundays Partial
Database backup and Mondays Differential Partial Database must be restored.
Whereas, if recovery is performed on Thursday, Sundays Partial Database
backup followed by Wednesdays Differential Partial Database backup must be
restored.
Even though Differential Partial Database backups will increase not only in size
but also in duration, restores are quicker due to the fewer number of restore jobs
that must be executed.
4.1.4.b
Full Recovery Model Backup Sequences

Full Database + Incremental Transaction Log Backups
When business requirements mandate point-in-time data protection, performing
Full Database backup nightly plus Incremental Transaction Log backups every
four to eight hours should be sufficient when one or more of the following
conditions exist:
Updates are infrequent across the entire database.
For example, Full Database backups are performed every night while Incremental
Transaction Log backups are performed every four to eight hours. Each
NetVault: Backup
33
Incremental Transaction Log backup includes the transaction logs since the last
Full Database or Incremental Transaction Log backup.
Restore sequences that use Incremental Transaction Log backups require that
every Incremental Transaction Log backup between the last Full Database backup
and the point-of-failure must be restored in succession. This can lead to longer
restores and increased DBA intervention to initiate multiple restore jobs. To speed
up restores, include Differential Database backups, which reduces the number of
Incremental Transaction Log backups that must be restored.
Full Database + Differential Database + Incremental Transaction Log

Backups
When business requirements mandate point-in-time data protection and restores
of the complete database have to be as fast as possible, Full Database plus
Differential Database plus Incremental Transaction Log backups is an ideal
strategy.
For example, Full Database backups are performed every Sunday night at
11:00 P.M. while Differential Database backups are performed Monday through
Saturday at 11:00 P.M., and Incremental Transaction Log backups are performed
every hour. Each Differential Database backup includes all the changes since the
last Full Database backup, and each Incremental Transaction Log backup
includes the transaction logs since the last Differential Database backup.
every Incremental Transaction Log backup between the last Full Database or
Differential Database backup and the point-of-failure must be restored in
succession. This can lead to longer restores and increased DBA intervention to
initiate multiple restore jobs. To speed up restores, increase the frequency of the
Differential Database backups to every four to eight hours, which reduces the
number of Incremental Transaction Log backups that must be restored. This
strategy provides complete protection of the entire database with the simplest
administration while supporting multiple restore scenarios.
Full File and Filegroup + Differential File and Filegroup + Incremental

Transaction Log Backups
When business requirements mandate point-in-time data protection and restores
have to be as fast as possible, Full File and Filegroup plus Differential File and
Filegroup plus Incremental Transaction Log backups is an ideal strategy. This
strategy offers the advantage of being able to restore a complete database or the
files or filegroups that are damaged. By being able to restore only what is needed,
restores are faster and data loss is minimized.
For example, Full File and Filegroup backups are performed every Sunday night at
11:00 P.M. while Differential File and Filegroup backups are performed Monday
through Saturday at 11:00 P.M., and Incremental Transaction Log backups are
34
Chapter 4
Backing Up Data
performed every hour. Each Differential File and Filegroup backup includes all the
changes since the last Full File and Filegroup backup, and each Incremental
Transaction Log backup includes the transaction logs since the last Differential
File and Filegroup backup.
every Incremental Transaction Log backup between the last Full File and
Filegroup or Differential File and Filegroup backup and the point-of-failure must be
restored in succession. This can lead to longer restores and increased DBA
intervention to initiate multiple restore jobs. To speed up restores, increase the
frequency of the Differential File and Filegroup backups to every four to eight
hours, which reduces the number of Incremental Transaction Log backups that
must be restored. This strategy provides complete protection of the entire
database with the flexibility to restore only the files or filegroups that are damaged
while supporting most restore scenarios.
4.1.5
Defining a VSS Backup Strategy and Reviewing Types

SQL Server APM provides the following types of VSS backups:
4.1.5.a
Full Database
Copy-Only
Full Database Backup

Full Database backups are supported by:
Recovery Models All
A VSS Full Database backup backs up database data and all the log files
necessary to bring the database up to a transactionally consistent state at restore
time. Full Database backups consume more space and time per backup and are
typically supplemented by differential backups, which are created more frequently.
With Full Database backups, you can re-create an entire database in one step by
restoring the database.
4.1.5.b
Differential Database Backup

Differential Database backups are supported by:
Recovery Model All
A VSS Differential Database backup backs up only the data that has changed
since the most recent base Full Database backup. A Differential Database backup
contains only those parts of the database files that have changed. Differential
Database backups are smaller and faster to create than the Full Database
NetVault: Backup
35
backups. A Differential Database backup is useful if some of the databases tables

are modified more frequently than others. In this case, Differential Database
backups allow you to back up frequently without the overhead of Full Database
backups.
4.1.5.c
Copy-Only Backup
Copy-Only backups are supported by:
Recovery Models All
VSS Copy-Only backups are independent of the normal sequence of backups. A

Copy-Only backup does not impact the differential bitmap, so subsequent
differential backups are unaffected by the Copy-Only backup. This type of backup
is ideal for situations that require special purposes, such as creating test
databases, because SQL Server will not update the backup history. The VSS
Copy-Only backup will not constitute a base backup for further differential backup
operations and also it does not disturb the history of the previous differential
backups.
4.1.6
Examples of VSS Backup Sequences

Following are few examples of backup sequences that support multiple restore
scenarios and that you can implement to meet your SQL Server data protection
requirements.
Full Database Backups Only

When business requirements guarantee data protection up to the previous day,
performing Full Database backups nightly should be sufficient when one or more
of the following conditions exist:
Updates are infrequent across entire database.
Databases are only for testing or development purposes.
Entire database is read-only.
Full Database + Differential Database Backups

When business requirements guarantee data protection up to the previous day
and backups have to be as fast as possible, Full Database backups coupled with
Differential Database backups is a valid strategy. For example, Full Database
backups are performed every Sunday night at 11:00 P.M., while Differential
Database backups are performed Monday through Saturday at 11:00 P.M. Each
Differential Database backup includes all the changes since the last Full Database
Backup, which is known as the differential base.
36
Chapter 4
Backing Up Data
required. For example, if recovery is performed on Tuesday, Sundays Full
Database backup and Mondays Differential Database backup must be restored.
Whereas, if recovery is performed on Thursday, Sundays Full Database backup
followed by Wednesdays Differential Database backup must be restored.
Even though Differential Database backups will increase not only in size but in
duration, restores are quicker due to the fewer number of restore jobs that must be
executed.
Copy-Only Backups
When business requirements demand that a backup be created without interfering
with regular scheduled backup sequences, Copy-Only backups is a valid strategy.
Often times, you must create a full backup outside of the regular backup schedule,
such as when refreshing your test databases. This could potentially interfere with
the regular backup schedule and throw off subsequent differential backups. The
Copy-Only backup allows administrators to run non-regular Full Database
backups at any time without interfering with scheduled backups.
4.1.7
Backing Up System Databases

The SQL Server system databases are essential for the operation of a server
instance and must be backed up after every significant update. These backups will
enable recovery of the SQL Server in the event of system failure, such as loss of a
hard disk.
The system databases that you must always back up include msdb, master, and
model. The master and msdb databases have a Simple Recovery Model while
the model database has a Full Recovery Model. In case of replicated databases,
it is also necessary to back up the distribution database.
master The master database records system-level information for a SQL

Server system, including login accounts, system configuration settings,
endpoints and credentials, information required to access the other
databases, and the initialization information.
For the master database, SQL Server supports only Full Database backups.
BakBone recommends that you schedule routine Full Database backups of
master, which you can supplement with an additional backup after a
substantial update.
msdb and model The msdb database is used by SQL Server, SQL Server
Management Studio, and SQL Server Agent to store data, including
scheduling information and backup and restore history information. The
model database is the template used by SQL Server when you create a user
database. The entire contents of the model database, including database
options, are copied to the new database.
NetVault: Backup
37
You can back up the model and msdb databases in the same way as user
databases. Back up the model and msdb databases whenever they are
updated. BakBone recommends that you create only Full Database backups
of the model database. As it is small and rarely changes, backing up the log
is unnecessary.
Note: The SQL Server APM cannot back up tempdb or Resourcedb databases.
For more information, refer to Backing Up and Restoring System Databases in
SQL Server Books Online.
4.1.8
Backing Up Replicated Databases

The SQL Server APM supports all three types of database replication offered for
use in SQL Server 2005/2008: Transactional Replication, Merge Replication, and
Snapshot Replication. (Replication is only supported in SQL Server 2005/2008.)
Replicated databases and their associated system databases should be backed
up regularly, including the following:
The publication database at the Publisher.
The distribution database at the Distributor.
The subscription database at each Subscriber.
The master and msdb system databases at the Publisher, Distributor, and all
Subscribers. These databases should be backed up at the same time as
each other and the relevant replicated database.
For example, back up the master and msdb databases at the Publisher at
the same time that you back up the publication database. If the publication
database is restored, ensure that the master and msdb databases are
consistent with the publication database in terms of replication configuration
and settings.
The replicated databases can be backed up in the same way as the non-replicated
databases with the APM. If you perform regular Incremental Transaction Log
backups, any replication-related changes should be captured in the Incremental
Transaction Log backups. If you do not perform Incremental Transaction Log
backups, a backup should be performed whenever a setting relevant to replication
is changed.
For more information, refer to Strategies for Backing Up and Restoring Snapshot
and Transactional Replication, Strategies for Backing Up and Restoring Merge
Replication, and Common Actions Requiring an Updated Backup in the SQL
Server Books Online.
38
Chapter 4
Backing Up Data
4.2.0
Performing Backups in SQL Server 2000

A backup using SQL Server APM in SQL Server 2000 can be divided into the
following phases:
4.2.1

1. From the NVBU Console running on the NVBU Server, access the Backup
Backup).
A list of machines successfully added as NVBU Clients is displayed on the
Selections tab.
Figure 4-1:
SQL Server
APM opened
to display
items available
for inclusion in
a backup job
(in SQL Server
2000)

4. Open the All Instances node to view the individual instances.
With the instances visible, you can do one of the following:
NetVault: Backup
39
Select the entire instance for inclusion.
Open an instance to display its individual databases, and select the

databases to be included in the backup.
Open an individual database to display its files and filegroups, and select
the items to be included in the backup.
Important: For the File and Filegroup backup type, a readonly filegroup must be selected explicitly in the selection tree to
include it in the backup. Though a green check mark will appear
against the read-only filegroups when you select the parentlevel database, these filegroups will not be actually backed up. When including a
read-only filegroup in a backup, select the individual items instead of selecting the
parent-level database.
4.2.1.a
Using Selection Sets

A Selection Set lets you save the frequently selected data items in a composite
set, which you can easily access for future backup jobs. This eliminates the need
to select these items manually each time a backup is required.
Moreover, Selection Sets are required for Database - Differential and
Transaction Log backups. If your backup strategy includes these backup types,
you must create a Selection Set when making a Database - Complete backup,
and use this Selection Set for the Database - Complete backup, as well as
Database - Differential and Transaction Log backups. The backup job will
report an error if a Selection Set is not used for Database - Differential and
Transaction Log backups.
Creating a Selection Set

To create a Selection Set, perform the following steps:
1. With the applicable items selected, click the Save As button in the Backup
Selection Set frame at the bottom of the Selections tab.
2. In the Save Backup Selection Set window that appears, enter a unique
name for the Selection Set, and click OK.
Loading a Selection Set

To use a Selection Set, perform the following steps:
1. Click the Load button in the Backup Selection Set frame at the bottom of
the Selections tab.
2. In the Load Backup Selection Set window that appears, select the required
set, and click OK.
Selection Sets are not unique to the SQL Server APM. For details on their creation
and use, refer to the NetVault: Backup Administrators Guide.
40
Chapter 4
Backing Up Data
4.2.2

The next phase in the backup procedure involves the following tasks:
Specifying the Backup Type
Setting Additional Options
Selecting the Backup Method
Select the Backup Options tab to perform these tasks.

Figure 4-2:
Backup
Options tab for
SQL Server
2000
4.2.2.a

The SQL Server APM provides following types of backups for use with SQL
Server 2000. For more information on the types of backups supported, see
Reviewing the Available Backup Methods on page 24.
Database - Complete Equivalent to a Full Database backup, a Database Complete backup backs up the entire database. In SQL Server 2000,
Database - Complete backups do not contain log records. Database Complete backups consume more space and time per backup, and are
typically supplemented by differential backups, which are created more
frequently. With Full Database backups, you can re-create an entire database
in one step by restoring the database.
NetVault: Backup
41
File and Filegroup A File and Filegroup backup backs up all the data in
one or more files or filegroups. A complete set of Full File backups is
equivalent to a Full Database backup.
File and Filegroup backups have the following advantages over Full
Database backups:
With a file backup, you can back up and restore the files in a database
individually. This can speed up the recovery process as you can restore
only damaged files without restoring the rest of the database.
File and Filegroup backups increase the flexibility in dealing with large
databases that contain data with varying update characteristics. For
example, consider the following recommendations:
Back up frequently modified data often.
Back up infrequently modified data less often.
Back up read-only data once.
The primary disadvantage of File and Filegroup backups is the risk that a
media failure can render an entire database unrecoverable if a damaged file
lacks a backup.
In SQL Server 2000, File and Filegroup backups do not contain log records
and you must explicitly apply a log backup to recover their data.
Database - Differential Equivalent to a Differential Database backup, a

Database - Differential backup backs up only the data that has changed
since the last Full Database backup. Differential Database backups are
smaller and faster than Full Database backups.
A Differential Database backup is useful if some of the databases tables are
modified more frequently than others. In this case, Differential Database
backups allow you to back up frequently without the overhead of Full
Database backups.
Transaction Log SQL Server Transaction Logs are essential to data

recovery and need to be backed up regularly. With Transaction Log
backups, you can recover the database to a point-of-failure or a specific
recovery point.
A Transaction Log backup captures all the transaction logs that have been
generated since the last Full Database/File and Filegroup, Differential
Database, or Transaction Log backup. A Transaction Log backup should
not be performed in the following conditions:
Until a Database - Complete or File and Filegroup backup has been

created. This is because the transaction log contains changes made to
the database after the last backup was created.
After the transaction log has been manually truncated, until a Database Complete or Database - Differential backup has been performed.
42
Chapter 4
Backing Up Data
Microsoft strongly recommends against manually truncating the
transaction logs.
4.2.2.b
Setting Additional Options

When performing Transaction Log or Database - Differential backups, you can
set certain additional options via the Transaction Log Options frame and If New
DB in Differential/Incremental Backup frame.
Transaction Log Options When backing up the transaction logs, you can
specify whether the inactive portion of the log must be truncated. Select one
of the following two options to set the action to be performed:
Normal Select this option if you want SQL Server APM to truncate the
inactive portion of the log file and make it available for re-use. This is the
default for Transaction Log backup.
No Truncate Select this option to avoid truncation of the log during

backup. Selecting this option is equivalent to performing a Tail-Log
backup.
Important: When the Normal option is enabled, SQL Server automatically

truncates the Transaction Logs after sending the backup Transaction Logs to the
APM. When the No Truncate option is enabled, the Transaction Logs are not
truncated. If the Normal option is used and the backup dies unexpectedly, the
Transaction Logs will be lost permanently. If the APM fails to write the index or
dies, the Transaction Logs cannot be restored and those transactions have
already been deleted from the SQL Server logs. This will result in errors when
attempting to restore Transaction Log backups that were created after the failed
backup job. If this situation occurs, make a full backup of your database to
eliminate the need for these logs during restoration. If the backup encounters
normal errors, the Transaction Logs are not lost.
If New Database Found in Differential/Incremental Backup Frame If the

Instance Node is selected and a new database is found while performing
Transaction Log or Database - Differential backup, you can choose to
either ignore it or take a full backup of it. You can set this action by selecting
the applicable option:
Ignore Selecting this option instructs the SQL Server APM to ignore any
databases that have been created since the last Database - Complete
backup (that is, any databases that were created after the last backup will
be left out of the Transaction Log or Database - Differential backup).
Do Full Backup This option instructs the APM to perform a full backup
of all new databases that have been added since the last Database Complete backup.
NetVault: Backup
43
Important: To change the default action for all subsequent jobs, see Specifying a
Default Configuration (Optional) on page 20.
4.2.2.c
Selecting the Backup Method

For SQL Server 2000, the SQL Server APM implements both Named Pipe and
VDI backup methods. The Backup Method frame lets you select the method
suited to your environment.
Figure 4-3:
Backup
Methods frame
Use Named Pipe With this backup method selected, the SQL Server APM
uses a named pipe for performing the backups. A named pipe is an Inter
Process Communication construct that allows programmatic communication
between a client and a server.
Use Virtual Device Interface (VDI) This method (the default) lets you take
advantage of Microsofts VDI Application Program Interface (API), which
provides maximum reliability and flexibility when defining a backup strategy.
You can set the following options for this backup method:
Block Size (Bytes) This field allows for the input of a device block size
(in bytes). The default value for this field is 64 kilobytes (KB), that is,
65536 bytes.
Transfer Multiple The value specified in this field is used as a multiplier

for the value specified in the Block Size field. The overall value of the two
serves as the maximum allowable data transfer size (that is, the Block
Size default of 65536 bytes multiplied by the default Transfer Multiple of
24, results in a maximum allowable transfer size of 1.6 megabytes [MB]).
Number of VDI Devices The value specified in this field determines the
number of VDI devices to use for storing the backup job. In the default
setting, all backup job options have one VDI device set to the job, when
Use Virtual Device Interface (VDI) is selected. You can add additional
VDI devices; however, the minimum number of VDI devices is 1, and the
maximum number cannot exceed 32.
Important: The number of VDI devices selected must be equal to or less than
the number of available media or tape drives. For example, if the number of VDI
devices selected is 5, a minimum of five media or tape drives must exist.
44
Chapter 4
Backing Up Data
4.2.3

With the applicable data items selected and the necessary Backup Options set,
perform the following steps to finalize the backup job and submit it.
1. Set the additional options that are available on the Schedule, Target, and
Advanced Options tabs, as required.
These options are not unique to the SQL Server APM. For more information
on these tabs and the options within, refer to the chapter dedicated to
Backup functionality in the NetVault: Backup Administrators Guide.
2. In the Job Title field, enter a suitable name for the job.
Specify a detailed name that lets you identify the job easily for monitoring its
progress or restoring data.
3. Click the Submit button.
You can monitor the backup job progress and log entries via the Job
Management, Status, and NVBU Logs windows. For details on accessing
these windows and their use, refer to the NetVault: Backup Administrators
Guide.
4.3.0
Performing Online VDI Backups in SQL Server

2005/2008
An online VDI backup using SQL Server APM in SQL Server 2005/2008 can be
divided into the following phases:
4.3.1

1. From the NVBU Console, access the Backup window (via either of the
toolbar buttons or by clicking Operations > Backup).
Selections tab.

NetVault: Backup
45
With the instances visible, you can do one of the following:

databases to include in the backup.
Open an individual database to display its files and filegroups, and select
the items to include in the backup.
Figure 4-4:
Selections tab
for SQL Server
2008 VDI
Important: For the backup types Full File and Filegroup, Differential File and
Filegroup, Partial Database, and Differential Partial Database, a read-only
filegroup must be explicitly selected in the selection tree to include it in the backup.
Though a green check mark will appear against the read-only filegroups when you
select the parent-level database, these filegroups will not actually be backed up.
When including a read-only filegroup in a backup, select the individual items
instead of the parent-level database.
46
Chapter 4
Backing Up Data
4.3.1.a

to select these items manually each time a backup is required. Moreover,
Selection Sets are necessary for incremental backup types (for example,
Differential Database, Incremental Transaction Log). If your backup strategy
includes these incremental backup types, you must create a Selection Set when
making a full backup of the corresponding type (for example, Full Database), and
use this Selection Set for the full backups and incremental backups. The backup
job will report an error if a Selection Set is not used for an incremental backup
type.


the Selections tab.
set, and click OK.
4.3.2

Specifying the Backup Method
Setting VDI Options
Setting Backup Options
Select the Backup Options tab for performing these tasks.
NetVault: Backup
47
Figure 4-5:
Backup
Options tab for
SQL Server
2008 VDI
4.3.2.a

The SQL Server APM provides following backup methods for use with SQL Server
2005/2008:
Virtual Device Interface (VDI)
Volume Shadow Copy Services (VSS)
Select the Use Virtual Device Interface (VDI) option to select the VDI backup
method.
4.3.2.b
Setting VDI Options

The VDI backup method lets you take advantage of Microsofts VDI API, which
provides maximum reliability and flexibility when defining a backup strategy. You
can set the following options for this backup method:
Block Size (Bytes) This field allows for the input of a device block size (in
bytes). The default value for this field is 64KB (that is, 65536 bytes).
48
Chapter 4
Backing Up Data
Transfer Multiple The value specified in this field is used as a multiplier for
the value specified in the Block Size field. The overall value of the two serves
as the maximum allowable data transfer size (that is, the Block Size default
of 65536 bytes multiplied by the default Transfer Multiple of 24, results in a
maximum allowable transfer size of 1.6MB).
Number of VDI Devices The value specified in this field determines the
number of VDI devices to be used for storing the backup job. In the default
setting, all backup job options have one VDI device set to the job, when Use
Virtual Device Interface (VDI) is selected. You can add additional VDI
devices; however, the minimum number of VDI devices is 1, and the
maximum number cannot exceed 32.
Important: The number of VDI devices selected must be equal to or less than
the number of available media or tape drives. For example, if the number of VDI
devices selected is 5, a minimum of five media or tape drives must exist.
4.3.2.c

Server 2005/2008:
Full Database
Copy-Only
Tail-Log
File and Filegroup
Partial Database
For information on these backup types, see Defining an Online VDI (or Named
Pipe) Backup Strategy and Reviewing Types on page 26.
4.3.2.d
Setting Backup Options

The SQL Server APM lets you set certain additional options for a backup, such as
specifying the action to take when a new database is found during incremental
type of backups, or whether to perform checksum on backups. You can set these
options from the Backup Options frame. This frame contains the following
options:
New Database Found in Differential/Incremental Backup If the Instance

Node is selected and a new database is found while performing a
Differential Database or Incremental Transaction Log backups, you can
NetVault: Backup
49
choose to either ignore it or take a full backup of it. You can set this action by
selecting the applicable option from the drop-down list provided here:
Do Full Database Backup This option will instruct the APM to perform
full backup of all the new databases that have been added since the last
Full Database backup.
Ignore Selecting this option will instruct the SQL Server APM to ignore
any databases that have been newly created since the last Full Database
backup (that is, any databases that were created after the last backup will
be left out of the Differential Database or Incremental Transaction Log
backup).
Transaction Log Options When backing up the transaction logs, you can
specify whether the inactive portion of the log must be truncated. Select one
of the following two options to set the action to be performed:
Normal Select this option if you want the SQL Server APM to truncate
the inactive portion of the log file and make it available for re-use. This is
the default for Incremental Transaction Log backups.
No Truncate Select this option to avoid truncation of the log during

backup. This option must be selected for performing Tail-Log backups.
Important: When the Normal option is enabled, SQL Server automatically

truncates the Transaction Logs after sending the backup Transaction Logs to the
APM. When the No Truncate option is enabled the Transaction Logs are not
truncated. If the Normal option is used and the backup dies unexpectedly, the
Transaction Logs will be lost permanently. If the APM fails to write the index or
dies, the Transaction Logs cannot be restored and those transactions have
already been deleted from the SQL Server logs. This will result in errors when
attempting to restore Transaction Log backups that were created after the failed
backup job. If this situation occurs, make a full backup of your database to
eliminate the need for these logs during restoration. If the backup encounters
normal errors, the Transaction Logs are not lost.
Enable Backup Checksum You can instruct the SQL Server APM to
perform checksum on the backups. Specifying this option tells SQL Server to
verify the page (checksum or torn page) if this information is present on the
page prior to writing a page to the backup media. Regardless of whether
page checksums are present, SQL Server generates a separate backup
checksum for the backup streams. Restore operations can optionally use the
backup checksum to validate that the backup is not corrupt. The backup
checksum is stored on the backup media, not on the database pages and can
affect workload and backup throughput. Select this check box to enable
backup checksum.
Error Encountered During Checksum If checksum is enabled (that is,

the Enable Backup Checksum check box is selected), you must indicate
50
Chapter 4
Backing Up Data
what the SQL Server APM should do if it encounters a checksum error.
Select one of the following options from the drop-down list:
Continue After Error This is the default action set during the APM
installation. With this value selected, the backup job will continue
despite encountering errors, such as invalid checksums.
Stop on Error With this value selected, the backup job will fail.
Important: To change the default action for this option for all subsequent jobs,
see Specifying a Default Configuration (Optional) on page 20.
SQL Server Backup Compression (SQL Server 2008 Enterprise Edition

Only) Specifying this option tells the SQL Server to use a compression
algorithm to compress the data stored on backup media.
Use Server Instance Setting If backup compression is enabled for this

SQL Server Instance, the APM will use backup compression for this
backup job. If it is disabled for this SQL Server Instance, the APM will not
use backup compression.
Enable Enable backup compression for this job regardless of the SQL
Server Instance setting.
Disable Disable backup compression for this job regardless of the SQL
Server Instance setting.
For more information on SQL Server Backup Compression refer to Backup

Compression (SQL Server) in the SQL Server 2008 Online Books at:
http://technet.microsoft.com/en-us/library/bb964719.aspx
Incomplete Backup of ALL Items Selected The SQL Server APM can do
one of the following when this error condition occurs:
Complete with Warnings Saveset Retained The job returns a status

of Backup Completed With Warnings and a backup saveset is
created that includes the items that were successfully backed up.
Complete without Warnings Saveset Retained The job completes

and returns a status of Backup Completed. While errors are logged in
the NVBU binary logs, the errors are essentially ignored in the Job
Management window and a backup saveset is created that includes the
items that were backed up successfully.
Fail Saveset Retained The job returns a status of Backup Failed.

However, a backup saveset is generated that includes the items that were
successfully backed up.
Fail No Saveset Retained The job returns a status of Backup

Failed and no saveset of backed up objects is kept. That is, even if some
of the objects were successfully backed up, the saveset is discarded.
NetVault: Backup
51
If either of the following occurs, the SQL Server APM overrides the
Incomplete Backup of ALL Items Selected setting and responds as
indicated:
4.3.3
If a fatal error occurs, the job returns a Backup Failed status.
If a Partial Database or Differential Partial Database backup is performed

on a database whose backup target contains a read-only filegroup, the job
returns a Backup Completed With Warnings status.

With the applicable data items selected and the necessary Backup Options set,
perform the following steps to finalize set up of the backup job and submit it.
1. Set the additional options that are available on the Schedule, Target, and
Backup functionality in the NetVault: Backup Administrators Guide.
Guide.
4.4.0
Performing VSS Backups in SQL Server 2005/

2008
Microsoft supports the ability to create snapshots of SQL Server data using VSS.
VSS allows volume backups to be performed while applications on the system
continue to write to the volumes.
With SQL Server 2005/2008, Microsoft provides a SQL Writer that permits
backup solutions such as SQL Server APM to copy SQL Server data while SQL
Server is running. VSS-based backups do not negatively impact SQL Servers
performance or stability.
The SQL Server APM supports SQL Writers Full Database backups including fulltext catalogs. Support for differential and Copy-Only backups will be provided in a
future release. The SQL Server APMs VSS backup method is available for SQL
Server 2005/2008.
52
Chapter 4
Backing Up Data
A VSS backup using SQL Server APM in SQL Server 2005/2008 can be divided
into the following phases:
Important: Prior to initiating VSS backups, make sure that the SQL Server VSS
Writer service is running on the SQL Server. The SQL Server VSS Writer is
automatically installed with SQL Server 2005/2008. However, the service is not
enabled to start automatically. For VSS backups, start this service from the
Windows Services panel (Start > Control Panel > Administrative Tools >
Services). BakBone recommends that you set the startup type for this service to
Automatic.
You can define a VSS backup job regardless of the state of this service. However,
the job will fail if it is run while the SQL Server VSS Writer service is not running.
The log for the failed backup job will contain a message stating Please ensure the
SQL Server Writer service is started.
4.4.1

Selections tab.

With the instances visible, you can do either of the following:

databases to be included in the backup.
NetVault: Backup
53
Figure 4-6:
Selections tab
for SQL Server
2008 VSS
4.4.1.a

to select these items manually each time a backup is required.

54
Chapter 4
Backing Up Data

the Selections tab.
set, and click OK.
4.4.2

Select the Backup Options tab for performing these tasks.

Note: During a VSS backup, the SQL Server APM will ignore all new databases
and perform only the differential backup of databases that have had a full VSS
backup first. An error message indicating that this has occurred will display in the
NVBU log.
NetVault: Backup
55
Figure 4-7:
Backup
Options tab for
SQL Server
2008 VSS
4.4.2.a

The SQL Server APM provides following backup methods for use with SQL Server
2005/2008:
Virtual Device Interface (VDI)
Volume Shadow Copy Services (VSS)
Select the Use Volume Shadow Copy Services (VSS) option to select the VSS
backup method.
4.4.2.b

Server 2005/2008:
Full Database
Copy-Only
56
Chapter 4
Backing Up Data
For information on these backup types, see Defining a VSS Backup Strategy and
Reviewing Types on page 34.
4.4.3

With the data selection task completed, the next steps involve setting VSS as the
backup method. This is done via the Backup Options tab.
1. Set the additional options that are available Schedule, Target, and
The options available in these tabs are not unique to the SQL Server APM.
For more information on these tabs and the options within, refer to the
chapter dedicated to Backup functionality in the NetVault: Backup
Administrators Guide.
Guide.
NetVault: Backup
57
Chapter 5:
RESTORING DATA
Restoring Data An Overview
Understanding the Online VDI Restore Process
5.1.0
Reviewing the Phases of the Restore Sequence
Understanding the Available Types of Online VDI Restores
Restoring System Databases
Restoring Databases Involved in Replication
Restoring Backups in SQL Server 2000
Phase 1: Selecting Data Items for a Restore
Phase 2: Setting Restore Options
Restoring Online VDI Backups in SQL Server 2005/2008
Restoring VSS Backups in SQL Server 2005/2008
Phase 1: Selecting Data for a Restore
Phase 2: Setting the Restore Options
Using Other Restore Procedures
Renaming or Relocating a Database
Restoring a Database to an Alternate Instance
Restoring to an Alternate SQL Server
Restoring Data An Overview

Restoring is the process of copying data from a backup and applying transaction
logs to the data to roll it forward to the target recovery point. A backup contains
sufficient transaction log records to allow rolling forward the active transactions as
part of restoring each backup. Each backup also contains sufficient transaction
logs to roll back any uncommitted transactions to bring the database to a
consistent, usable state. The process of rolling forward uncommitted transactions,
if any, and bringing the database online is known as Recovery.
58
Chapter 5
Restoring Data
5.2.0
5.2.1
Understanding the Online VDI Restore Process

Reviewing the Phases of the Restore Sequence
Each SQL Server restore scenario is implemented using one or more restore
operations, which is called a restore sequence. A restore sequence moves data
through one or more phases of restore. The possible phases of a restore include
the data copy, redo (roll forward), and undo (roll back) phases, which are detailed
in the following sections.
5.2.1.a
Data Copy Phase

The first phase in any restore process is the data copy phase. The data copy
phase involves copying all the data, log, and index pages from the backup media
to the database files. It involves copying data from one or more of the following
backup types:
5.2.1.b
Full Database
Copy-Only
Partial Database
Redo Phase (Roll Forward)

Redo or roll forward is the process of reapplying logged changes to the data in the
roll forward set to bring the data forward in time. To accomplish this, the SQL
Server Database Engine processes Transaction Log backups as they are
restored, beginning with the log contained in the data copy backups listed in the
preceding section and any Incremental Transaction Log backups that are
subsequently restored. Roll forward stops at the recovery point, which is either
the end of the transaction log or a point-in-time that is specified in the SQL Server
Restore Options for Incremental Transaction Log backups. The
SQL Server APM supports both time-based and marked transaction-based pointin-time recovery.
Important: After you have created a restore job, you cannot update the
information on the Restore Options tab located in the NVBU Restore window
until you select the Modify check box on the Selections tab. Additionally, you
cannot view the Transaction Log Options tab until you select Modify.
NetVault: Backup
5.2.1.c
59
Undo (Roll Back) Phase and Recovery

After the redo phase has rolled forward all the log transactions, a database
typically contains changes made by transactions that are uncommitted at the
recovery point. This makes the rolled forward data transactionally inconsistent.
The recovery process opens the transaction log and identifies uncommitted
transactions and rolls them back to bring the database into a transactionally
consistent state. This step is called the undo (or roll back) phase.
If the data is transactionally consistent at the start of the recovery process, the
undo phase is skipped.
After the database is transactionally consistent, recovery brings the database
online.
5.2.2
Understanding the Available Types of Online VDI

Restores
To perform a successful restore, you must have a full understanding of the types
of restores that are available for use. This section outlines the possible restore
scenarios supported for different recovery models:
5.2.2.a
Restoring Databases under Simple Recovery Model

The following restore scenarios are supported under Simple Recovery Model:
Complete Database Restore

With a Simple Recovery Model database, the goal of a complete database restore
is to restore the entire database. This type of restore typically involves restoring a
Full Database backup or a Full Database backup followed by a Differential
Database backup. The entire database is offline for the duration of a complete
database restore.
File Restore
In a file restore for a Simple Recovery Model database, the goal is to restore one
or more damaged read-only files without restoring the entire database. This type
of restore will involve a Full File and Filegroup backup.
Partial Database Restore (SQL Server 2005/2008 Only)

A partial restore for a Simple Recovery Model database includes restoring the
primary filegroup and all read-write filegroups that were included in a Partial
Database or Differential Partial Database backup. Restores of the read-only
filegroups with a Full File and Filegroup backup will be required only if the readonly filegroups are damaged.
60
Chapter 5
Restoring Data
5.2.2.b
Restoring Databases under Full and Bulk-Logged Recovery

Models
The following restore scenarios are supported under the Full and Bulk-Logged
Recovery Models:
Complete Database Restore

Under the Full and Bulk-Logged Recovery Models, the goal is to restore the entire
database to the point-of-failure. A complete database restore sequence will
typically include the following steps:
1. Perform Tail-Log backup.
2. Restore Full Database or Full File and Filegroup backup while selecting
With NO RECOVERY restore option.
3. Restore Differential Database or Differential File and Filegroup backup
while selecting With NO RECOVERY restore option.
4. Restore all subsequent Incremental Transaction Log backups in order
while selecting the With NO RECOVERY restore option.
5. Restore and recover the Tail-Log backup by selecting the With RECOVERY
restore option.
File Restore
In a file restore for a Full or Bulk-Logged Recovery Model database, the goal is to
restore the entire database while leaving the option available to restore one or
more damaged files without restoring the entire database. This type of restore will
involve the following restore sequence:
1. Perform Tail-Log backup.
2. Restore Full File and Filegroup backup with With NO RECOVERY restore
option.
3. Restore Differential File and Filegroup backup with With NO RECOVERY
restore option.
4. Restore all subsequent Incremental Transaction Log backups in order
while selecting the With NO RECOVERY restore option.
5. Restore and recover the Tail-Log backup while selecting the With
RECOVERY restore option.
NetVault: Backup
61
Point-in-Time (PIT) Recovery

You can perform a Point-in-Time recovery on the transaction logs that are restored
during an Incremental Transaction Log restore. The SQL Server APM supports
both time-based and marked-transaction-based point-in-time recovery. PIT
Recovery options are available when restoring Incremental Transaction Log and
Tail-Log backups.
5.2.3
Time-Based Point-in-Time Recovery Time-based PIT recovery is useful

when the time that the data corruption occurred is known. For example, if a
developer dropped a table at 6:00 A.M., PIT recovery can be performed with
a stop time of 5:55 A.M. Time-based PIT recovery can only be used for
unrelated databases; therefore, when multiple SQL Server 2005 databases
are required to be logically consistent, marked-transaction PIT recovery
should be used.
Marked-Transaction-Based Point-in-Time Recovery (SQL Server 2005/

2008 Only) SQL Server 2005/2008 supports the ability to insert named
marks into a transaction log to allow recovery to a specific mark. This
functionality is beneficial if you have two or more databases that must be
logically consistent. You can implement special procedures to ensure the
recoverability of these databases after a restore. Because you can only
recover related databases to a marked transaction, not to a specific point in
time, your application must be configured to insert named marks into the
transaction log prior to performing backups. For more information, refer to
Ensuring Recoverability of Related Databases and the Recovering to a
Marked Transaction in the SQL Server Books Online.
Restoring System Databases

You can only restore system databases from backups that are created on the
version of SQL Server that the server instance is currently running. For example,
to restore a system database on a server instance that is running on SQL Server
2005 SP1, you must use a database backup that was created after the SQL
Server Instance was upgraded to SQL Server 2005 SP1.
5.2.3.a
Restoring the master Database

The master database must be accessible and at least partly usable for starting a
SQL Server instance. If the master database becomes unusable, you can return
the database to a usable state by either restoring the master from a current
database backup or rebuilding the master completely.
It is possible to restore the master database from a Full Database backup only if
you are able to start the server instance. If severe damage to the master database
prevents you from starting the SQL Server, rebuilding the master is the only
option left. For more information, refer to Rebuilding the master Database in the
SQL Server Books Online.
62
Chapter 5
Restoring Data
The restoration of the master database will include the following steps:
1. Start the server instance in single-user mode.
2. Restore a Full Database backup of the master database.
The SQL Server instance will be stopped automatically on completion of the
data restoration process.
3. Because the changes made to master since the last backup were lost,
re-create them by executing those steps again.
4. After the master has been restored and changes reapplied, back up the
master immediately.
5.2.3.b
Restoring the model or msdb Databases

Restoring the model or msdb database from a backup will be required under the
following circumstances:
The master database has been rebuilt. In this case, it will be necessary to
restore model from a backup because rebuilding master re-creates model.
The model or msdb database has been damaged (for example, due to
media failure).
Restoring model or msdb is the same as performing a Complete Database

restore of a user database.
Before restoring msdb, the SQL Server Agent Service in the Control Panel must
be stopped. BakBone also recommends that you shut down applications, because
the restore procedure will disconnect users when necessary.
5.2.4
Restoring Databases Involved in Replication

It is possible to restore all databases in a replication topology if recent backups are
available and the proper steps are followed. The restore steps for the publication
database depend on the type of replication and options used, but the restore steps
for all other databases are independent of the type and options.
Replication supports restoring replicated databases to the same SQL Server
instance and database from which the backup was created. If you restore a
backup of a replicated database to another instance, replication settings cannot be
preserved. In this case, you must re-create all publications and subscriptions after
backups are restored.
For more information, refer to the Strategies for Backing Up and Restoring
Snapshot and Transactional Replication and Strategies for Backing Up and
Restoring Merge Replication sections in the SQL Server 2005/2008 Books Online.
NetVault: Backup
5.3.0
63
Restoring Backups in SQL Server 2000

A standard restore with the SQL Server APM in SQL Server 2000 can be divided
into the following phases:
This section outlines the various steps to be performed in these phases to

complete data restoration successfully.
5.3.1

1. From the NVBU Console running on the NVBU Server, launch the Restore
window by clicking either of the Restore buttons available on the command
toolbars (or by selecting Restore from the Operations menu).
You will see a list of NVBU Clients that have been the target of successful
backup jobs on the Selections tab.
Figure 5-1:
Selections tab
for SQL Server
2008 VDI
the APMs/plugins that have been used to back up data.
64
Chapter 5
Restoring Data
To open any node on the Selections tab in the Restore window, do either of
the following:
3. Locate SQL Server APM in the list, and open it to display the backup
savesets created with the APM.
Each saveset will be labeled with its given Job Title followed by its backup
type and the time that the backup was performed. The backup type identifiers
are outlined in the following table:
Backup Type
Backup Type Identifier
Database - Complete
VDI FULL
Database - Differential
VDI DIFFERENTIAL
File and Filegroup
VDI FILEGROUP
Transaction Log
VDI INCREMENTAL
4. Open the applicable backup saveset to display the SQL Server instance that
was the target of the backup.
5. From this level, double-click a node to open it (the right-click method is not
available).
The database name is displayed when you open this node. For the File and
Filegroup backup saveset, you can further open the database node and
select the individual files or filegroups. For other backup types, further drilldown will show items but you cannot select them.
Important: When restoring a read-only filegroup, the filegroup
must be explicitly selected in the selection tree. Though a green
check mark will appear against the read-only filegroup when you
select the parent-level database, the filegroup will not be
actually restored. When including a read-only filegroup in a restore, select the
individual items instead of selecting the parent-level database.
6. Select the applicable instance or the database for inclusion in the restore
procedure.
5.3.1.a
Additional Features Available on the Selections Tab

This section provides a brief description of the additional features present on the
Selections tab of the NVBU Restore window. These features are common to all
NVBU plugins. For more information, refer to the chapter dedicated to Restore
functionality in the NetVault: Backup Administrators Guide.
Sorting the Savesets To sort the savesets listed on the Selections tab,
select one of the following methods in the Selection Method list:
NetVault: Backup
65
Plugin This is the default method. The savesets are ordered according
to the plugin used to generate them.
Backup Set To sort the savesets by the Selection Set used for the
backup, select Backup Set in the Selection Method list.
Job To sort the savesets by the Job Title, select Job in the Selection
Method list.
Figure 5-2:
Selection
Method
options
Filtering the Savesets To filter the savesets displayed on the Selections

tab, configure the following parameters under Filter Options:
By Date Range Select the By Date Range check box, and enter or
select the From and To dates in the boxes provided to list the savesets
generated during a given period.
Show On-line Status Select the Show On-line Status check box to list
the savesets stored on the currently online media.
Click Apply Filter to set the filter.

Figure 5-3:
Filter Options
frame
Figure 5-4:
Search
command for
locating and
displaying data
Searching for Data Items To find a data item inside a saveset, right-click it
and select Search. Enter the item name in the Search String box, and click
Search.
66
Chapter 5
Restoring Data
Viewing Media List To view the media list for a saveset, right-click it and
select Media List.
Compressing Indexes To compress the online indexes to reduce the

space used by the NVBU Database (NVDB), right-click the target Client or
the saveset, and select Compress. The index is automatically
decompressed when you open a saveset to browse or restore the data.
Figure 5-5:
Media List
command for
displaying
media-related
information for
a saveset
Figure 5-6:
Compress
command for
compressing
an index
NetVault: Backup
5.3.2
67

With the applicable data items selected for a restore, select the Restore Options
tab. This tab contains options that you can set in conjunction with items selected
for a restore on the Selections tab.
Figure 5-7:
Restore
Options tab for
SQL Server
2000
The following options will be available.
Backup Type The type of backup that was performed, based on the
saveset chosen for a restore on the Selections tab, is displayed here.
Action After Restore Frame This frame contains the following options:
Set Database with RECOVERY; No More Transaction Logs can be

Restored Select this option if no further Transaction Log or Differential
Database backups are to be applied after the restore of the selected data
has completed. After SQL Server restores the final transaction logs
included in the backup, the database is brought online.
Set Database with NO RECOVERY; More Transaction Logs can be

Restored Select this option if another Transaction Log or Differential
Database backup is to be applied after this restore has completed.
68
Chapter 5
Restoring Data
Set Database with STANDBY; More Transaction Logs can be

Restored Select this option when restoring a Database - Complete or
Transaction Log backup to create or maintain a standby server.
Important: SQL Server 2000 supports creating standby servers only with
Database - Complete backups. Therefore, a restore will fail if the Set Database
With STANDBY; More Transaction Logs can be Restored option is enabled for
File or Filegroup backup types.
Undo File for Standby Restores For performing Standby Restores the
SQL Server APM requires a temporary Undo file. It is required only when the
Action After Restore field on the Restore Options tab is set to Set
Database with STANDBY; More Transaction Logs can be Restored.
By default, the path is blank. Specify the directory path for the temporary
UNDO.DAT file in this field. You can set a default path for field in the
Configurator. For more information, see Specifying a Default Configuration
(Optional) on page 20.
Figure 5-8:
Options for
performing a
time-based
point-in-time
recovery
Point in Time Restore Available only for Transaction Log backups, this
option lets you perform time-based point-in-time recovery. Select this option
and specify the date and time in the respective fields to apply the transactions
up to that point in the Transaction Log backup. The specified recovery point
must be contained in the Transaction Log backup.
Target Instance This field lets you restore the database to a different SQL
Server Instance. The procedure for performing this type of restore is outlined
in Restoring a Database to an Alternate Instance on page 83.
Leave this option blank for a standard restore of the database to the same
instance.
Restore Method This frame contains options that allow you to select the
restore method of the SQL Server APM.
Figure 5-9:
Restore
Method frame
Use Named Pipe Select this option to perform the restore of selected
data using the Named Pipe method, which is an Inter Process
Communication construct that allows programmatic communication
NetVault: Backup
69
between a client and a server. With this method selected, the other
options in this frame do not apply.
5.3.3
Use Virtual Device Interface (VDI) Select this option to take advantage
of Microsoft's VDI API, which provides offers the maximum reliability and
flexibility. You can set the following options for this method:
Block Size (Bytes) This field lets you specify the device block size
(in bytes). The default value for this field is 64KB (that is, 65536 bytes).
Transfer Multiple The value specified in this field is used as a

multiplier for the value specified in the Block Size field. The overall
value of the two serves as the maximum allowable data transfer size
(that is, the Block Size default of 65536 bytes multiplied by the default
Transfer Multiple of 24, results in a maximum allowable transfer size
of 1.6MB).

With all data items selected and the applicable Restore Options set, perform the
following steps to finish set up of the job and submit it to run.
1. Set the additional options that are available on the Schedule, Target Client,
and Advanced Options tabs, as required.
Restore functionality in the NetVault: Backup Administrators Guide.
progress.
You can monitor the restore job progress and log entries via the Job
Management, Status, and NVBU Logs windows. For more information on
accessing these windows and their use, refer to the NetVault: Backup
5.4.0
Restoring Online VDI Backups in SQL Server

2005/2008
A standard restore with the SQL Server APM in SQL Server 2005/2008 can be
divided into the following phases:
70
Chapter 5
Restoring Data
This section outlines the various steps to be performed in these phases to
complete data restoration successfully.
5.4.1

1. From the NVBU Console, launch the Restore window by clicking either of the
Restore buttons available on the command toolbars (or by selecting Restore
from the Operations menu). You will see a list of NVBU Clients that have
been the target of successful backup jobs on the Selections tab.
Figure 5-10:
Selections tab
for SQL Server
2008 VDI
the following:
NetVault: Backup
71
Backup Type
Full Database
VDI FULL
VDI DIFFERENTIAL
Copy - Only
VDI Copy - ONLY
VDI INCREMENTAL
Transaction Log
VDI INCREMENTAL
Tail-Log
VDI TAIL-LOG
VDI FILEGROUP
VDI FILEGROUP DIFFERENTIAL
Partial Database
VDI PARTIAL
VDI PARTIAL DIFFERENTIAL
available).
The database name is displayed when you open this node. For the Full File
and Filegroup, Differential File and Filegroup, Partial Database, and
Differential Partial Database backup types, you can further open the
database node and select the individual files or filegroups. For other backup
types, further drill-down will show items but you cannot select them.
Important: When restoring a read-only filegroup, the filegroup
must be explicitly selected in the selection tree. Though a green
check mark will appear against the read-only filegroup when you
select the parent-level database, the filegroup will not be
actually restored. When including a read-only filegroup in a restore, select the
individual items instead of selecting the parent-level database.
procedure.
72
Chapter 5
Restoring Data
5.4.1.a
Additional Features Available on the Selections Tab

This section provides a brief description of the additional features present on the
Selections tab of the NVBU Restore window. These features are common to all
NVBU plugins. For more information, refer to the chapter dedicated to Restore
functionality in the NetVault: Backup Administrators Guide.
Sorting the Savesets To sort the savesets listed on the Selections tab,
select one of the following methods in the Selection Method list:
Plugin This is the default method. The savesets are ordered according
to the plugin used to generate them.
Backup Set To sort the savesets by the Selection Set used for the
backup, select Backup Set in the Selection Method list.
Job To sort the savesets by the Job Title, select Job in the Selection
Method list.
Figure 5-11:
Selection
Method
options
Filtering the Savesets To filter the savesets displayed on the Selections

tab, configure the following parameters under Filter Options:
By Date Range Select the By Date Range check box, and enter or
select the From and To dates in the boxes provided to list the savesets
generated during a given period.
Show On-line Status Select the Show On-line Status check box to list
the savesets stored on the currently online media.
Click Apply Filter to set the filter.

Figure 5-12:
Filter Options
frame
NetVault: Backup
73
Searching for Data Items To find a data item inside a saveset, right-click it
and select Search. Enter the item name in the Search String box, and click
Search.
Viewing Media List To view the media list for a saveset, right-click it and
select Media List.
Compressing Indexes To compress the online indexes to reduce the

space used by the NVDB, right-click the target Client or the saveset, and
select Compress. The index is automatically decompressed when you open
a saveset to browse or restore the data.
Figure 5-13:
Search
command for
locating and
displaying data
Figure 5-14:
Media List
command for
displaying
media-related
information for
a saveset
Figure 5-15:
Compress
command for
compressing
an index
74
Chapter 5
Restoring Data
5.4.2

Figure 5-16:
Restore
Options tab
5.4.2.a
Setting the Standard Restore Options

The following restore options are available for all backup types:
Backup Method The backup method that was used for the backup that
was chosen to be restored on the Selections tab is displayed here.
Backup Type The type of backup that was performed for the backup that
Restore Type Frame This frame lets you specify the action that must be
performed after the restore operation. You can select from the following
options:
With RECOVERY Select this option if no further Transaction Log or

Differential Database backups are to be applied after the restore of the
selected data has completed.
NetVault: Backup
75
With NO RECOVERY Select this option if another Transaction Log or

Differential Database backup is to be applied after this restore has
completed.
With STANDBY Select this option when applying an Incremental

Transaction Log backup from the primary server in a warm standby
server scenario.
Verify-only Select this option if you want to perform a verification check

on a backup to determine if a backup set is complete and the entire
backup is readable. The data is not actually restored.
VDI Options The VDI restore method lets you take advantage of
Microsofts VDI API, which provides the maximum reliability and flexibility.
You can set the following options for this method:
Block Size (Bytes) This field lets you specify the device block size (in
bytes). The default value for this field is 64KB (that is, 65536 bytes).
Transfer Multiple The value specified in this field is used as a multiplier

for the value specified in the Block Size field. The overall value of the two
serves as the maximum allowable data transfer size (that is, the Block
Size default of 65536 bytes multiplied by the default Transfer Multiple of
24, results in a maximum allowable transfer size of 1.6MB).
Restore Options This frame contains the following options:
Target Instance This field lets you restore the database to a different
SQL Server Instance. The procedure for this type of restore is outlined in
Restoring a Database to an Alternate Instance on page 83. Leave this
option blank for a standard restore of the database to the same SQL
Server Instance.
Undo File for Standby Restores For performing Standby Restores

the SQL Server APM requires a temporary Undo File. It is required only
when the Restore Type is set to With STANDBY. By default, the path is
blank. Specify the directory path for the temporary UNDO.DAT file in this
field. You can set a default path for field in the Configurator. For more
information, see Specifying a Default Configuration (Optional) on page 20.
Enable Restore Checksum Specifies that backup checksums must be

verified and, if the backup lacks backup checksums, causes the restore
operation to fail with a message indicating that checksums are not
present. Select this check box to enable restore checksum.
Error Encountered During Checksum If checksum is enabled (that is,

the Enable Restore Checksum check box is selected), you must indicate
what the APM should do if it encounters a checksum error. Select one of
the following options from the drop-down list:
Continue After Error This is the default action set during the APM
installation. With this value selected, the restore job will proceed, if the
76
Chapter 5
Restoring Data
corruption permits, after returning a checksum error with the number of
the page containing the invalid checksum.
Stop on Error With this value selected, the restore job will report a
checksum error and stop if it encounters errors.
To change the default action for this option for all subsequent jobs, see Specifying
a Default Configuration (Optional) on page 20.
5.4.2.b
Setting the Point-in-Time Recovery Options
Figure 5-17:
Transaction
Log tab for
SQL Server
2008 VDI
The SQL Server APM supports time-based and marked transaction-based pointin-time recovery of a database. To set the recovery point for a log backup, access
the Transaction Log Options tab that is displayed on the Restore Options tab
when an Incremental Transaction Log or Tail-Log backup is selected for
restore. This tab contains the following options for setting the recovery point:
Enable Point-in-Time Restore Select this check box to enable point-intime recovery of the log backup.
Point-In-Time Options You can perform point-in-time recovery with either

the timestamp of the transaction or the named mark for the transaction.
Date and Time To perform recovery up to a specific point in time within

the log backup, select this option and set the Time and Date in the
respective fields.
NetVault: Backup
Marked Transaction To perform recovery up to a mark within the

Transaction Log backup, select this option and specify the mark in the
Mark field.
5.4.3
77
Mark Enter the string to identify the transaction mark. Select Stop
At from the drop-down list to perform recovery till this transaction
(the marked transaction will be included). Select Stop Before to
recover all transactions before this mark.

With all the data items selected and the applicable Restore Options set, perform
the following steps to finish set up of the job and submit it to run.
1. Set the additional options available on the Schedule, Target Client, and
Advanced Options tabs of the Restore window, as required.
progress.
accessing these windows and their use, refer to the NetVault: Backup
5.5.0
Restoring VSS Backups in SQL Server 2005/

2008
The Microsoft VSS restore process can be broken down into the following phases:
Important: The SQL Server Instance must be stopped when restoring the master
database.
5.5.1

1. From the NVBU Console, launch the Restore window by clicking either of the
Restore buttons available on the command toolbars (or by selecting Restore
from the Operations menu).
78
Chapter 5
Restoring Data
You will see a list of NVBU Clients that have been the target of successful
backup jobs on the Selections tab.
the following:
Backup Type
Full Database
VSS Full
VSS Differential
Copy-Only
VSS Copy Only
available).
Opening it further will display the database name. Though further drill-down
will show items, you cannot select them.
procedure.
NetVault: Backup
5.5.2
79

Figure 5-18:
Restore
Options tab for
SQL Server
2008 VSS
The following restore options are available for all VSS backup types:
Backup Method The backup method that was used for the backup that
Backup Type The type of backup that was performed, based on the
database chosen for a restore on the Selections tab, is displayed here.
Restore Type This frame lets you specify the action that must be
performed after the restore operation. You can select from the following
options:
With RECOVERY Select this option if no further Transaction Log or

Differential Database backups are to be applied after the restore of the
selected data has completed.
With NO RECOVERY Select this option if another Transaction Log or

Differential Database backup is to be applied after this restore has
completed.
80
Chapter 5
Restoring Data
5.5.3

With all the data items selected and the applicable Restore Options set, perform
the following steps to finish set up of the job and submit it to run.
1. Set the additional options available on the Schedule, Target Client, and
Advanced Options tabs of the Restore window, as required.
progress.
accessing these windows and their use, refer to the section dedicated to
5.6.0
Using Other Restore Procedures

This section describes other restore operations that you can perform with the
SQL Server APM.
5.6.1
Renaming or Relocating a Database

The SQL Server APM lets you restore a database to a different name during
restore. The renaming of a database can be useful if you do not want to overwrite
the existing version and want to create a copy of the database. You can also
relocate the database to a different directory while restoring it with the APM.
Important: To make a copy of a database using the Full File and Filegroup
Backup method, it must be restored to a different SQL Server Instance.
When renaming a database during a VSS-based restore, the database files must
also be relocated to an alternate directory. If the database file are not relocated to
an alternate directory, the restore will fail. This is because VSS does not let you
rename the database without moving the data and log files to a different directory.
When relocating data and log files for VSS-based restores, it is possible to
relocate the data files to one directory and the log files to a separate directory as
long as both directories are different than the original directory.
NetVault: Backup
81
To rename or relocate a database during restore, perform the following steps:

1. Select the database to be restored from the backup saveset by following the
instructions outlined in Restoring Backups in SQL Server 2000 on page 63 or
Restoring Online VDI Backups in SQL Server 2005/2008 on page 69 based
on your environment.
2. Right-click the database, and select Rename from the pop-up menu.
3. On the Restore Rename - <Database> dialog that appears, set the following
values:
Rename Database Select the Rename To check box, and enter the
new name for the database in the text box. The database will be restored
with the name specified in this field.
Important: When renaming a database during a VSS-based restore, the database

files must also be relocated to an alternate directory. If the database files are not
relocated to an alternate directory, the restore will fail. This is because VSS will not
allow you to rename the database without moving the data and log files to a
different directory. When relocating data and log files for VSS-based restores, it is
possible to relocate the data files to one directory and the log files to a separate
directory as long as both directories are different than the original directory.
Figure 5-19:
Restore
Rename <Database>
dialog
Relocate Database Select the Relocate To check box, and enter the
new path to which the database must be restored.
The SQL Server APM lets you relocate the log files to a directory other
than the data files directory. To restore to separate directories, type in the
paths to the directories where the data files and log files are to be
restored. The data file directory must be specified first, followed by the
path to the log file directory. The two directory paths must be separated by
comma (no space must exist before or after the comma). The directory
specified in this field must exist at job run-time.
82
Chapter 5
Restoring Data
Figure 5-20:
A database
marked with its
Rename/
Relocation
information on
the Selections
tab
4. Click OK to apply your changes.

The database will be accompanied by the rename/relocate information
displayed in the parenthesis.
5. Continue with the restore procedure as explained in Phase 2: Setting Restore
Options on page 67 and Phase 3: Finalizing and Submitting the Job on page
69 (Restoring Backups in SQL Server 2000), or on page 74 and on page 77
(Restoring Online VDI Backups in SQL Server 2005/2008) based on the
environment.
NetVault: Backup
5.6.2
83
Restoring a Database to an Alternate Instance

With the SQL Server APM VDI-based backup method, it is possible to restore a
database to an alternate Instance of SQL Server running on the database server.
The procedure for performing this type of a restore is outlined in the following
sections.
Figure 5-21:
Restoring to
alternate
instance
5.6.2.a
Prerequisites
Prior to initiating this type of restore, make sure that the following prerequisites are
met:
5.6.2.b
Same Version of SQL Server Both the source instance from which the
data was backed up and the target instance to which the data is to be
restored must be running the same version of SQL Server software.
Instance Configured for Access The instance to which the database is to

be restored must be accessible to the SQL Server APM. To set up the
instance for access, see Configuring Authentication Details on page 17.
Performing the Restore

1. Select the database to be restored from the backup saveset by following the
instructions outlined in Phase 1: Selecting Data Items for a Restore on page
63 (Restoring Backups in SQL Server 2000) or Restoring Online VDI
Backups in SQL Server 2005/2008 on page 69 based on your environment.
2. Set the Restore Options by following the instructions outlined in Phase 2:
Setting Restore Options on page 67 (Restoring Backups in SQL Server 2000)
or Restoring Online VDI Backups in SQL Server 2005/2008 on page 69
based on your environment.
3. In addition, set the Target Instance parameter in this tab.
To do so, specify the name of the instance to which the selected database is
to be restored. You can either specify the fully qualified name (that is,
<HostName>\<InstanceName> for example, WIN2K3\SQLINSTANCE2 or
the instance name (for example, SQLINSTANCE2) in this field.
4. Complete the procedure by following the instructions outlined in Phase 3:
Finalizing and Submitting the Job on page 69 (Restoring Backups in SQL
Server 2000) or Restoring Online VDI Backups in SQL Server 2005/2008 on
page 69 based on your environment.
84
Chapter 5
Restoring Data
Important: You can also rename or relocate a database while performing this type
of restore for VDI-based backups. For more information, see Renaming or
Relocating a Database on page 80.
5.6.3
Restoring to an Alternate SQL Server

Similar to SQL Server APMs ability to restore databases to a different SQL Server
Instance on the same database server, you can target a different SQL Server
during the restore process.
Figure 5-22:
Restoring to
alternate SQL
Server
This functionality is useful during disaster recovery operations. You can restore a
database to a different SQL Server by using the steps provided in the following
sections.
Important: Microsofts VSS backup method does not support restoring a VSSbased backup to an alternate Instance; therefore, restoring VSS-based backups to
an alternate instance with the SQL Server APM is not supported.
5.6.3.a
Prerequisites
The following requirements must be met on the new restore target before
attempting this procedure:
Same Version of SQL Server Installed The SQL Server version must be
the same as the version running on the existing database server.
NVBU Software and the SQL Server APM Installed The same version of
NVBU software and the SQL Server APM must be installed and configured
on the new restore target.
Client Added to the NVBU Server The target machine must be added to
the NVBU Server via the Client Management window of the NVBU Console.
Instance of SQL Server Must Exist on the New Restore Target An

instance of SQL Server must exist on the new restore target. This instance
will serve as the target of the relocation restore. Not only must this instance
be properly set up and configured in SQL Server, it must also be accessible
to the SQL Server APM on the new restore target. To set up the instance for
access, see Configuring Authentication Details on page 17.
NetVault: Backup
5.6.3.b
85
Performing the Restore

Important: In a disaster recovery scenario, you must use this Restore Procedure
to restore the master and the msdb database backups. After restoring the master
database, restart the server. Restore and recover each individual database.
1. Restore the master and the msdb database backups.
2. After restoring the master database, restart the server.
3. Restore and recover each individual database.
a. Select the database to be restored from the backup saveset by following
the instructions outlined in Phase 1: Selecting Data Items for a Restore on
page 63 (Restoring Backups in SQL Server 2000) or Restoring Online VDI
Backups in SQL Server 2005/2008 on page 69 based on your
environment.
b. Set the Restore Options by following the instructions outlined in Phase 2:
Setting Restore Options on page 67 (Restoring Backups in SQL Server
2000) or Restoring Online VDI Backups in SQL Server 2005/2008 on
page 69 based on your environment.
c. In addition, set the Target Instance parameter in this tab.
To do so, specify the name of the instance to which the selected database
is to be restored on the new database server.
Enter only the instance name in this field; the restore will fail if the server
name is included.
d. On the Target Client tab, select the new restore target from the list.
Figure 5-23:
New restore
target selected
on Target
Client tab
Additional options are available on the Schedule and Advanced Options

tabs of the Restore window.
These options are not unique to the SQL Server APM. For more
information on these tabs and the options within, refer to the chapter
dedicated to Restore functionality in the NetVault: Backup Administrators
Guide.
e. In the Job Title field, enter a suitable name for the job.
86
Chapter 5
Restoring Data
Specify a detailed name that lets you identify the job easily for monitoring
its progress.
f. Click the Submit button.
Management, Status, and NVBU Logs windows. For more information
on accessing these windows and their use, refer to the section dedicated
to Restore functionality in the NetVault: Backup Administrators Guide.
NetVault: Backup
87
Appendix A:
USING SQL SERVER APM IN A

FAILOVER CLUSTER
ENVIRONMENT
SQL Server Failover Clustering An Overview
About this Appendix
A.1.0
Installing the Software
Licensing SQL Server APM
Backing Up Data
Restoring Data
Using Multiple SQL Server Virtual Servers in the Same Failover Cluster
Installation Requirements
Configuration Requirements
Backup Requirements
Restore Requirements
SQL Server Failover Clustering An Overview

SQL Server Failover Clustering (Active/Passive) is designed to provide highavailability for an entire SQL Server instance. For example, you can configure a
SQL Server instance on one node of a failover cluster to fail over to any other
node in the cluster during a hardware failure, OS failure, or a planned upgrade.
A failover cluster is a combination of one or more nodes (hosts) with two or more
shared disks, known as a resource group. The combination of a resource group,
along with its network name, and an IP address that makes up the clustered
application or server is referred to as a Virtual Server. A Virtual Server appears
on the network as if it were a single computer, but provides failover from one node
to another node if the current node becomes unavailable.
88
Important: In NVBU terminology, a cluster node is referred to as a Virtual Client.
The references to Virtual Client in the SQL Server APM are basically references
to the Virtual Server in the SQL Server Failover Cluster environment.
The SQL Server APM provides support for SQL Server Failover Clustering. Using
the failover cluster network name, the SQL Server APM is able to identify the
current node that is in control of the SQL Server Virtual Server and target it for
backup.
The installation, configuration, backup, and restore procedures differ slightly in a
SQL Server Failover Cluster environment.
A.2.0
About this Appendix

This appendix points out differences between the setup and usage of the
SQL Server APM in a Failover Cluster environment vs. a traditional one. It mirrors
the sections found in the standard instructions, as follows:
A.2.1
Backing Up Data
Restoring Data
Unless outlined in the sections that follow, backups and restores performed
with the SQL Server APM of clustered data are the same as those performed
with traditional Microsoft SQL Server data.
NVBUs Encryption functionality is not supported for use in a SQL Server

Failover Cluster environment. If you intend to use Application Cluster Support
in conjunction with the SQL Server APM, NVBUs Encryption functionality
must be disabled. For details on disabling this functionality, refer to the
NetVault: Backup Administrators Guide.
The following sections only offer information on Microsoft SQL-specific

settings required for the use of this APM in a Failover Cluster environment.
They do not offer instructions on how to set up NVBUs Application Cluster
Support to administer backups and restores of non-SQL Server-related data
and files. This process is not APM-specific, and you can find complete details
in the NetVault: Backup Administrators Guide.
Before you continue, BakBone strongly recommends that you review all
cluster-related information provided in the NetVault: Backup Administrators
Guide to understand how the following information works in conjunction with
SQL Server Failover Cluster functionality.
NetVault: Backup
A.3.0
A.3.1
89

The following prerequisites must be met before you install the SQL Server APM in
a clustered environment:
A.3.2
Microsoft SQL Failover Clustering Environment in Place You must

have a properly configured Failover Clustering environment. Failover
Clustering is only supported with SQL Server Standard and Enterprise
Editions. For more information on installing Failover Clustering, refer to the
Failover Clustering section of SQL Server 200x Books Online.
Separate NVBU Server Machine The machine that is to serve as the

NVBU Server must be properly configured and it must exist outside the
SQL Server cluster, but have network connectivity to the nodes (hosts) within
the cluster.
Installing the Software

Installation of the SQL Server APM for a clustered environment is different than
the traditional installation of this APM. This process is completed through the
creation of a Virtual Client on the NVBU Server. A Virtual Client is a group of
nodes within the cluster that are seen by the NVBU Server as a single client that
is created to back up a single clustered resource (for example, a SQL Server
Virtual Server). During the Virtual Client creation process, the SQL Server APM is
transferred from the NVBU Server to selected nodes within a cluster and installed
there.
A.3.2.a
Creating a Virtual Client

As noted earlier, the Virtual Client creation process is not APM-specific, and you
can find complete details in the NetVault: Backup Administrators Guide. However,
consider the following points during the Virtual Client creation process:
Assign a Name to the Virtual Client BakBone strongly recommends that

the Virtual Server network name assigned to the SQL Server be used as the
NVBU Virtual Client name. When a Virtual Client is browsed, NVBU will
locate the node currently in control of the clustered application, and reveal the
SQL Server instance (for example, on the Selections tab in the Backup
window). With a Virtual Client name set up as the SQL Server Virtual Server
network name, it will be easy to recognize the SQL Server instance for which
the Virtual Client was created.
90
Figure A-1:
Virtual client
set up with
same name as
its associated
instance
Only Include Relevant Cluster Nodes in the Virtual Client The hosts that
are to be included in the creation of a Virtual Client should only be those
nodes within the cluster that are relevant to the SQL Server Virtual Server
that is to be backed up and restored.
After the creation of the Virtual Client, the APM is transferred to all designated
cluster nodes and installed locally. You can use the installed SQL Server APM via
the Virtual Client to back up and restore shared data (you can only perform
backups and restores of data established as shared within the cluster).
A.4.0

Another difference between using the SQL Server APM in a clustered
environment is how it is licensed for use.
For information on the licensing process, including how to obtain the proper
license keys, refer to the NetVault: Backup Installation Guide.
The SQL Server APM supports backup and restore of shared data only. Hence,
for a SQL Server Failover Cluster environment, only a single license would be
needed a clustered application license for the Virtual Client.
A.5.0

This section assumes that a Virtual Client has already been created for use with
the SQL Server APM.
Note: Configuration of the APM in a clustered environment that houses multiple
instances of SQL Server requires additional steps. For more information, see
Configuration Requirements on page 94.
You must configure the actual Virtual Client from the NVBU Server by performing
the following steps on the primary node:
1. From the NVBU Console running on the NVBU Server, access the Backup
Backup).
2. On the Selections tab, locate the newly created Virtual Client and open it.
NetVault: Backup
91
4. Right-click the All Instances node, and select Configure from the pop-up
menu.
5. In the window that appears, set the applicable configuration options.
The options available are the same as those covered in Configuring
Authentication Details on page 17.
Important: You must add each cluster instance in the Instances field of the
Configure window. To add an instance, specify the SQL Server cluster name as
VIRTUAL SERVER NAME\INSTANCE NAME.
6. If you anticipate having to create additional backup jobs or modify existing
backup jobs on the secondary node, perform the following steps:
a. Fail over the primary node to the secondary node.
b. Repeat Step 1 through Step 5.
c. Fail back to the primary node.
7. With the applicable options set, click the OK button to confirm the settings
and close this window.
A.6.0
Backing Up Data
Backing up data using the SQL Server APM that has been set up for use in a
Virtual Client is relatively simple. Open the SQL Server APM node on the
Selections tab in the Backup window, and select the SQL Server Virtual Server
(or the items contained within) for inclusion in the backup.
Figure A-2:
Shared
instance
running on
Virtual Client
(SQL Server
Virtual Server)
Note that the instance name displayed in this window is actually the SQL Server
Virtual Server that is established as the Virtual Client during the installation
process (as outlined in Creating a Virtual Client on page 89). If other SQL Server
Virtual Servers are running on this node, those instances will also be displayed
within the SQL Server APM node. Data from these other instances must not be
selected for inclusion in the backup.
Note: When you back up or restore data, make sure that you execute the process
using the Virtual Client and not from one of the nodes. If you open or expand one
of the nodes and drill down through the hierarchy, you might see a dimmed SQL
Server instance identified as local. While the system might use this instance in
92
maintaining log information, you should not be attempting to execute any
processes at this level.
A.7.0
Restoring Data
Restoring a backup of a Virtual Client is conducted in the same manner as a
restore performed to a traditional NVBU Client. All options available for a restore
with the SQL Server APM are also available for Failover Clustering environments,
and data selection is performed in the same way as well. The only difference is
that restorable backups of a Virtual Client are displayed on the Selections tab in
the Restore window under the name of the Virtual Client, not the specific NVBU
Client or node that was active during each backup. When a restore job is initiated,
NVBU will communicate with all member Clients to determine which machine is
currently in control of the failover cluster, and then target this machine for the
restore.
Figure A-3:
Restore
classified
under the
name of the
Virtual Client
even though
individual
client was
used for each
backup
All the instructions offered in this guide in reference to performing a restore can be
used in the recovery of a Virtual Client. For more information on restoring a
SQL Server APM backup, see Restoring Data on page 57.
NetVault: Backup
A.8.0
93
Using Multiple SQL Server Virtual Servers in

the Same Failover Cluster
SQL Server Failover Clustering supports the ability to create multiple Virtual
Servers in a cluster. However, each Virtual Server can have only one instance of
SQL Server running. The following special provisions, in addition to those outlined
in the previous section, must be taken into account when using the
SQL Server APM in this configured environment.
A.8.1
Installation Requirements
In this scenario, you must create an NVBU Virtual Client for each SQL Server
Virtual Server. Each Virtual Server will have its own network name and IP address,
and it will be displayed as a separate Virtual Client in NVBU.
Create an Individual NVBU Virtual Client for Each SQL Server Virtual
Server For each SQL Server Virtual Server in the failover cluster, create a
separate Virtual Client. During the creation process, ensure that the following
are included:
IP Address of the SQL Server Virtual Server In the Application IP

Address field of the NetVault Virtual Client Installation window, enter
the IP Address assigned to the appropriate SQL Server Virtual Server. For
example, if creating the first of the two SQL Server Virtual Servers in a
failover cluster for a clustered environment, the IP address assigned to
the first Virtual Server would be entered.
Give a Name to the Virtual Client that Corresponds to the Network

Name of the SQL Server Virtual Server Enter the network name
associated with the SQL Server Virtual Server in the Virtual Client Name
field.
Figure A-4:
Creation of
Virtual Client
for first SQL
Server Virtual
Server in
clustered
environment
that contains
Virtual Servers
Copy the nvsqlserver.cfg file before creating the next NVBU Virtual
Client Because creating a new Virtual Client overwrites the configuration
94
file, which includes the Logon Detail information, BakBone recommends that
you perform the following steps:
1. Store a copy of the first nvsqlserver.cfg file in a safe location.
You can find this file in: \\<NVBUinstallDirectory>\config
2. Create the next Virtual Client, store a copy of the its nvsqlserver.cfg
file in a safe location, and repeat this step for every new Virtual Client that
you need to create.
Ensure that the correct network name for the SQL Server Virtual Server
and IP address is provided for each.
3. When you are finished creating Virtual Clients, copy the applicable
information from the [Security-<instanceName>] and [ServerList:List]
sections in each nvsqlserver.cfg file to the same sections in the
nvsqlserver.cfg file on the primary node.
4. If you have browsed the Virtual Client, close and reopen the Backup
window.
A.8.2
Configuration Requirements
After the proper installation steps for this environment have been followed, you
must set configuration options for each individual Virtual Client created.
2. On the Selections tab, all the newly created Virtual Clients will be revealed;
locate the one that was set up for the first SQL Server Virtual Server, and
open it.
All the SQL Server Virtual Servers within the failover cluster will be revealed.
4. Locate the first SQL Server Virtual Server in the tree, right-click it, and select
Configure from the pop-up menu.
5. In the window that appears, set the applicable configuration options.
The options available are the same as those covered in Configuring
Authentication Details on page 17.
With the configuration set for the first SQL Server Virtual Server in its
corresponding Virtual Client, it is now necessary to repeat the process for all
remaining SQL Server Virtual Servers.
6. Repeat steps Step 2 through Step 5 for all remaining Virtual Clients, ensuring
that the proper SQL Server Virtual Server is selected for each Virtual Client.
NetVault: Backup
A.8.3
95
Backup Requirements
While performing backups in this scenario, it is important to select the correct SQL
Server Virtual Server on the Selections tab. For example, using the same sample
setup illustrated in the configuration section, for a backup of the first SQL Server
Virtual Server, perform the following steps:
1. Open the Virtual Client created for the first SQL Server Virtual Server, which
is SQL_Virtual_Server_1.
3. With the correct SQL Server Virtual Server selected, perform the backup in
the same manner as a traditional SQL Server APM backup (that is, use the
instructions provided in Backing Up Data on page 23).
Important: It is not necessary to select an entire SQL Server Virtual Server when
backing up in this manner. You can select individual databases within. However,
the correct SQL Server Virtual Server must be identified and then opened to
select its individual contents.
A.8.4
Restore Requirements
There are no specific requirements for the restore of data in a multiple instance
environment. Provided the previous three sections were followed correctly, backed
up data of this type should be restored the same as any other SQL Server APM
data.
96
NetVault: Backup
97
Appendix B:
TROUBLESHOOTING
B.1.0
Troubleshooting
Troubleshooting
The following table describes commonly encountered problems and possible
solutions. In cases where an error occurs and it is not described in this table, view
the job log to extract the Microsoft SQL Server error number, and then refer to the
relevant Microsoft SQL Server documentation for the resolution.
Symptom
Reason/Symptom
Solution
Transaction
Log backup
failed
Transaction Log backups are not For taking Transaction Log backups,
allowed for Simple Recovery
the recovery model for the database
Model databases.
must be set to Full Recovery Model.
Or clear the Simple Recovery Model
databases.
Backup failed The File and Filegroup backup

fails and the following error
message appears in the logs:
The primary filegroup cannot be
backed up as a file backup
because the database is using
the SIMPLE recovery model.
Consider taking a partial backup
by specifying
READ_WRITE_FILEGROUPS.
Either modify the selection set to

include only secondary filegroups for
the Simple Recovery Model databases
or select the Partial Database or
Differential Partial Database backup
type.
Backup failed Login failed for user

<username>.
Make sure that the password for the

APM has been entered correctly.
98
Symptom
Reason/Symptom
Solution
Backup
Completed
with
Warnings
After this status is revealed for

backup, check the NVBU Log
entries for the job to see if they
display one or both of the
following messages:
Failed to add backup
record
Failed to write index of
backup to the database
These messages indicate that
the selected data was actually
backed up, but the jobs index
information was not properly
added by NVBU to its database.
Without this index information,
the data cannot be properly
restored.
Method 1:
Access the Device Management
window of the NVBU Console, and
perform a scan of the media targeted by
the job (that is, by right-clicking the
target media and selecting Scan from
the pop-up menu). NVBU stores index
information for backup jobs in two
locations: in the NVBU Database and
on the media targeted by the backup.
By performing this scan, the index
information will be added to the NVBU
Database. To verify this, open the
Restore window and locate the specific
job.
If you can browse it and set up a restore
job, the scan process has corrected the
problem.
Method 2:
If the previous method failed, it will be
necessary to re-run the backup job.

NetVault Backup APM For SQL Server Users Guide

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

NetVault Backup APM For SQL Server Users Guide

Hochgeladen von

Copyright:

Verfügbare Formate

NetVault: Backup

Application Plugin Module (APM)

for SQL Server

NetVault: Backup APM for SQL Server At a Glance ................................................... 7

Chapter 2: Installing and Removing SQL Server APM

Installation Prerequisites ............................................................................................... 11

Installing SQL Server APM ............................................................................................ 13

Chapter 3: Configuring SQL Server APM

Configuring Authentication Details .............................................................................. 17

Specifying a Default Configuration (Optional) ............................................................. 20

Chapter 4: Backing Up Data

Defining a SQL Server Backup-and-Restore Strategy ................................................ 23

Reviewing the Available Backup Methods ..................................................................................... 24

Performing Backups in SQL Server 2000 .....................................................................38

Performing Online VDI Backups in SQL Server 2005/2008 .........................................44

Performing VSS Backups in SQL Server 2005/2008 ....................................................51

Chapter 5: Restoring Data

Restoring Data An Overview .......................................................................................57

Reviewing the Phases of the Restore Sequence ........................................................................... 58

Restoring Backups in SQL Server 2000 ........................................................................63

Restoring Online VDI Backups in SQL Server 2005/2008 ............................................69

Restoring VSS Backups in SQL Server 2005/2008 .......................................................77

Using Other Restore Procedures ...................................................................................80

- Restoring to an Alternate SQL Server ........................................................................................... 84

Appendix A: Using SQL Server APM in a Failover Cluster

SQL Server Failover Clustering An Overview ........................................................... 87

Installing SQL Server APM ............................................................................................ 89

Licensing SQL Server APM ........................................................................................... 90

Installation Requirements .............................................................................................................. 93

NetVault: Backup APM for SQL Server At a Glance

Recommended Additional Reading

NetVault: Backup APM for SQL Server At a

Increases Confidence and Reduces Risk While Deploying SQL Server

Online VDI- or VSS-based backups

Full, Differential Database backups while data is online and accessible

Incremental Transaction Log and Tail-Log backups

Protection for Filestreams

Protection down to the datafile level

Creation of backup checksums that are used during restores to detect

By relying on SQL Server APM to implement backup policies, DBAs can be

Speeds Up Restores to Reduce Downtime With SQL Server APM, DBAs

Restores of complete databases, partial databases, or individual datafiles

Restore VDI-based backups to an alternate server

Ensure Business Continuity with Automatic Integration of Backup

Online VDI- or VSS-based backups

Full, Differential Database backups while data is online and accessible

Incremental Transaction Log and Tail Log backups

Protection for Filestreams

Protection down to the datafile level

Creation of backup checksums that are used during restores to detect

Full, differential, incremental, and time and marked transaction point-in-time

Verify-only restore option

Restores of complete databases, partial databases, or individual datafiles

Restore VDI-based backups to alternate server

Recommended Additional Reading

SQL Server 2008 Books Online

SQL Server 2005 Books Online

SQL Server 2000 Books Online

Volume Shadow Copy Service

INSTALLING AND REMOVING

Deploying SQL Server APM

Installing SQL Server APM

Removing SQL Server APM