CA ARCserve Backup for Windows Microsoft Volume

CA ARCserve® Backup for
Windows
Microsoft Volume Shadow Copy Service Guide
r15
This documentation and any related computer software help programs (hereinafter referred to as the
"Documentation") are for your informational purposes only and are subject to change or withdrawal by CA at any time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part,
without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may
not be used or disclosed by you except as may be permitted in a separate confidentiality agreement between you and
CA.
Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation,
you may print a reasonable number of copies of the Documentation for internal use by you and your employees in
connection with that software, provided that all CA copyright notices and legend s are affixed to each reproduced copy.
The right to print copies of the Documentation is limited to the period during which the applicable license for such
software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify
in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION "AS IS" WITHOUT
WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER
OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOC UMENTATION,
INC LUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR
LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and
is not modified in any way by the terms of this notice.
The manufacturer of this Documentation is CA.
Provided with "Restricted Rights." Use, duplication or disclosure by the United States Government is subject to the
restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section
252.227-7014(b)(3), as applicable, or their successors.
Copyright © 2010 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein
belong to their respective companies.
CA Product References
This documentation set references the following CA products:
■
BrightStor® Enterprise Backup
■
CA Antivirus
■
CA ARCserve ® Assured Recovery™
■
CA ARCserve ® Backup Agent for Advantage™ Ingres ®
■
CA ARCserve ® Backup Agent for Novell Open Enterprise Server for Linux
■
CA ARCserve ® Backup Agent for Open Files on NetWare
■
CA ARCserve ® Backup Agent for Open Files on Windows
■
CA ARCserve ® Backup Client Agent for FreeBSD
■
CA ARCserve ® Backup Client Agent for Linux
■
CA ARCserve ® Backup Client Agent for Mainframe Linux
■
CA ARCserve ® Backup Client Agent for NetWare
■
CA ARCserve ® Backup Client Agent for UNIX
■
CA ARCserve ® Backup Client Agent for Windows
■
CA ARCserve ® Backup Enterprise Option for AS/400
■
CA ARCserve ® Backup Enterprise Option for Open VMS
■
CA ARCserve ® Backup for Microsoft Windows Essential Business Server
■
CA ARCserve ® Backup for Windows
■
CA ARCserve ® Backup for Windows Agent for IBM Informix
■
CA ARCserve ® Backup for Windows Agent for Lotus Domino
■
CA ARCserve ® Backup for Windows Agent for Microsoft Exchange Server
■
CA ARCserve ® Backup for Windows Agent for Microsoft SharePoint Server
■
CA ARCserve ® Backup for Windows Agent for Microsoft SQL Server
■
CA ARCserve ® Backup for Windows Agent for Oracle
■
CA ARCserve ® Backup for Windows Agent for Sybase
■
CA ARCserve ® Backup for Windows Agent for Virtual Machines
■
CA ARCserve ® Backup for Windows Disaster Recovery Option
■
CA ARCserve ® Backup for Windows Enterprise Module
■
CA ARCserve ® Backup for Windows Enterprise Option for IBM 3494
■
CA ARCserve ® Backup for Windows Enterprise Option for SAP R/3 for Oracle
■
CA ARCserve ® Backup for Windows Enterprise Option for StorageTek ACSLS
■
CA ARCserve ® Backup for Windows Image Option
■
CA ARCserve ® Backup for Windows Microsoft Volume Shadow Copy Service
■
CA ARCserve ® Backup for Windows NDMP NAS Option
■
CA ARCserve ® Backup for Windows Serverless Backup Option
■
CA ARCserve ® Backup for Windows Storage Area Network (SAN) Option
■
CA ARCserve ® Backup for Windows Tape Library Option
■
CA ARCserve ® Backup Patch Manager
■
CA ARCserve ® Backup UNIX and Linux Data Mover
■
CA ARCserve ® D2D
■
CA ARCserve ® High Availability
■
CA ARCserve ® Replication
■
CA VM:Tape for z/VM
■
CA 1 ® Tape Management
■
Common Services™
■
eTrust® Firewall
■
Unicenter® Network and Systems Management
■
Unicenter® Software Delivery
■
Unicenter® VM:Operator®
Contact CA
Contact Technical Support
For your convenience, CA provides one site where you can access the
information you need for your Home Office, Small Business, and Enterprise CA
products. At CA ARCserve Backup Support, you can access the following:
■
Online and telephone contact information for technical assistance and
customer services
■
Information about user communities and forums
■
Product and documentation downloads
■
CA Support policies and guidelines
■
Other helpful resources appropriate for your product
Provide Feedback
If you have comments or questions about CA product documentation, you can
send a message to techpubs@ca.com.
If you would like to provide feedback about CA product documentation, complete
our short customer survey, which is also available on the CA Support website,
found at http://ca.com/docs.
Contents
Chapter 1: Introducing VSS Support
9
Introduction ............................................................................ 9
How CA ARCserve Backup Achieves VSS Support............................................ 10
How VSS Support Works ................................................................ 11
How VSS Support Works ............................................................. 12
Shadow Copy Creation Methods ....................................................... 15
How the Agent Works ................................................................... 16
Full Copy Method ....................................................................... 18
How the Enterprise Option for VSS Hardware Snap-Shot Works ............................... 18
How Transportable Shadow Copies are Created ............................................. 19
Chapter 2: Installing the Client and the Option
21
How to Install the Client and the Option ................................................... 21
Prerequisites........................................................................... 21
System Requirements ................................................................... 22
Installation of the Client and Option ....................................................... 22
Prepare for VSS Shadow Copies .......................................................... 22
Chapter 3: Performing Backups
23
Backup Options ........................................................................ 23
Set Writer Options .................................................................. 24
Writer Options Dialog ................................................................ 25
Set Global Options .................................................................. 27
File System Backup Options .......................................................... 29
Writers and Components Options ...................................................... 29
Create Transportable VSS Backups........................................................ 30
File System Backups .................................................................... 33
How Backup Jobs are Submitted .......................................................... 33
How the VSS Backup Works.............................................................. 34
How to Back Up Data Using the Option .................................................... 35
Perform File System Backups............................................................. 36
Perform Writer Backups ................................................................. 37
VSS and the Backup Manager ............................................................ 39
Writer Backups......................................................................... 39
Writer Exclusion During Backups.......................................................... 40
Contents 7
Chapter 4: Performing Restores
41
VSS and the Restore Manager ............................................................ 41
Restoration of File Systems .............................................................. 42
Restoration of Writers Backup ............................................................ 42
Restore Locations ................................................................... 42
Restore Methods .................................................................... 43
Set Restore Options ................................................................. 44
Restore VSS Writer Backups .......................................................... 44
Chapter 5: Best Practices
47
Develop Your Backup Strategy ........................................................... 47
Amount of Data to Back Up ........................................................... 48
Files Not Supported by Writers ........................................................ 48
Appendix A: Application-Specific Guidelines
51
Microsoft Exchange Writer ............................................................... 51
General Guidelines .................................................................. 52
Non-Transportable VSS Backup and Restore - Microsoft Exchange Writers ................... 52
Transportable VSS Backup and Restore - Microsoft Exchange Writers ....................... 53
Restore Transportable VSS Backups Using Microsoft Exchange Writers ...................... 53
Microsoft Hyper-V VSS Writer ............................................................ 55
Windows System State Writer Components................................................. 55
MSDE Writer........................................................................... 56
General Guidelines .................................................................. 56
Non-Transportable VSS Backup and Restore - MSDE Writers .............................. 57
Transportable VSS Backup and Restore - MSDE Writers................................... 57
Restore Transportable VSS Backups Using MSDE Writers ................................. 58
SQL Server Writer ...................................................................... 59
General Guidelines SQL 2005 ......................................................... 59
Non-Transportable VSS Backup and Restore - SQL Server Writers.......................... 59
Transportable VSS Backup and Restore - SQL Server Writers .............................. 60
Restore Transportable VSS Backups Using SQL Server Writers ............................. 60
Oracle VSS Server Writer ................................................................ 61
General Guidelines Oracle 11g ........................................................ 62
Non-Transportable VSS Backup and Restore - Oracle VSS Writers .......................... 62
Restore Transportable VSS Backups Using Oracle VSS Writers ............................. 63
Miscellaneous Supported Writers.......................................................... 64
Index
8 Microsoft Volume Shadow Copy Service Guide
65
Chapter 1: Introducing VSS Support
This section contains the following topics:
Introduction (see page 9)
How CA ARCserve Backup Achieves VSS Support (see page 10)
How VSS Support Works (see page 11)
How the Agent W orks (see page 16)
Full Copy Method (see page 18)
How the Enterprise Option for VSS Hardware Snap-Shot Works (see page 18)
How Transportable Shadow Copies are Created (see page 19)
Introduction
CA ARCserve Backup is a comprehensive storage solution for applications,
databases, distributed servers, and file systems. It provides backup and restore
capabilities for databases, business-critical applications, and network clients.
Among the agents CA ARCserve Backup offers is the CA ARCserve Backup Agent
for Microsoft Volume Shadow Copy Service.
Using the Volume Shadow Copy Service (VSS) feature provided with Microsoft
Windows Server 2003, Windows Server 2008, and Microsoft Windows XP, CA
ARCserve Backup enables you to take advantage of the point-in-time backup
feature of VSS that allows open files to be backed up. Applications and large
VSS-aware databases can also be backed up, ensuring transactional consistency
during the backup process.
Chapter 1: Introducing VSS Support 9
How CA ARCserv e Backup Achieves VSS Support
How CA ARCserve Backup Achieves VSS Support
CA ARCserve Backup provides VSS backup and restore support through the
following solutions:
■
CA ARCserve Backup Agent for Open Files--Works with VSS-aware
applications to provide point-in-time backup and restore of files and data
sets on Windows Server 2003, Windows Server 2008, and Windows 7
operating systems. As changes are made to the original information,
intermediate shadow copies are created to ba ck up only those changes. The
Agent for Open Files (the agent) creates software -based shadow copies as
well as hardware-based shadow copies on devices that support this
functionality; however, these hardware -based shadow copies are not
transportable.
The CA ARCserve Backup Agent for Open Files lets you perform open file
backups and VSS-based backups.
Note: You must install the CA ARCserve Backup Client Agent for Windows on
the system where you will perform VSS-based backups.
■
CA ARCserve Backup Enterprise Option for VSS Hardware
Snap-Shot--Works with the agent and VSS interfaces supplied by specific
vendors of disk array equipment to create transportable hardware -based
shadow copies. Transportable shadow copies allow greater flexibility for the
backup and restore of your critical applications and files by enabling the
shadow copy to be imported onto other backup servers within the same
system. You can then use the transported shadow copy volumes for
additional tape backups, or for other uses such as data mining and software
development testing. The Enterprise Option for VSS Hardware Snap -Shot
(the option) is available with the CA ARCserve Backup for Windows
Enterprise Module and supports Microsoft Exchange Server 2003, Microsoft
SQL Server 2000, Microsoft SQL 2005, and Microsoft SQL 2008.
When used in a remote backup and restore configuration, both of these
solutions use the CA ARCserve Backup Client Agent for Windows to provide
communication between workstations and the CA ARCserve Backup server.
10 Microsoft Volume Shadow Copy Serv ice Guide
How VSS Support W orks
How VSS Support Works
Microsoft Volume Shadow Copy Service (VSS) is built into the Microsoft Windows
XP Professional, Windows Server 2003, and Windows Server 2008 operating
systems. VSS works with CA ARCserve Backup, the Agent for Open Files, the
Enterprise Option for VSS Hardware Snap-Shot, and VSS-aware applications and
services to create shadow copies of single volumes or multiple volumes.
Note: CA ARCserve Backup does not support Writers under W indows XP. This is
because some of the necessary Writer support in Windows Server 2003 is not
included in the Windows XP operating system.
A shadow copy is a read-only, frozen view of a volume's file system as it exists
when the copy is taken, and can reside on a volume separate from the one that
was copied. The shadow copy volume can exist on the same server as the
original data but in a different share or mount point, or on another
network-attached volume.
The shadow copy of the volume is created at a s ingle point in time and is
synchronized across the whole volume set. To avoid inconsistencies, shadow
copies cannot be taken of individual files.
Regardless of where the shadow copy volume is created, CA ARCserve Backup
uses the shadow copy as the source for the backup. Shadow copy volumes can
also be backed up (migrated) to another disk or tape device.
Using the shadow copy method to perform backups has two distinct advantages
over other traditional backup methods:
Open files are backed up
Files that are open when a shadow copy is created appear closed on the
shadow volume. When the shadow copy data is backed up, these open files
are included.
Workflow is not interrupted
Since the data backed up by CA ARCserve Backup exists on the shadow
volume, work can continue on the original volume without affecting the
integrity of the backup data.
In traditional backup operations, open files are skipped and do not appear in the
backup. To get a better quality backup, administrators often implemented
backup windows when the applications being backed up are unavailable to users.
Unavailable applications prevented work from continuing, forcing users to wait
until after the backup completed to finish their tasks.
Chapter 1: Introducing VSS Support 11
How VSS Support W orks
If applications included in a VSS backup are not enabled for VSS, all of the
application’s data (including open files) is written to the shadow copy. However,
because the application cannot prepare its files before the backup begins, the
data may not be consistent and a ny transactions may be incomplete.
A shadow copy of a volume, even in a crash-consistent state, still contains all
files. A backup set created without a shadow copy does not contain the files that
were open at the time of the backup. These open files are e xcluded from the
backup.
How VSS Support Works
For a VSS backup to be successful, the following entities must work together and
with VSS to prepare and perform the backup:
■
Requestors (see page 12)
■
Providers (see page 14)
■
Writers (see page 13)
■
Components (see page 14)
Requestors
The Requestor is a piece of software (typically a backup application) responsible
for the following tasks:
■
Initiating the request for a VSS backup
■
Processing the backup instructions from the Writers, including which files are
selected for backup and the methods that should be used to back up those
files
■
Backing up the shadow copy data to media
■
Signaling the completion of the backup by deleting the shadow copy data
from the disk
CA ARCserve Backup is designed to function as the Requestor in VSS backups.
12 Microsoft Volume Shadow Copy Serv ice Guide
How VSS Support W orks
Writers and Components
The keys to shadow copy technology are the Writers and their Components.
Writer
Part of an application or service that works with VSS to prepare the
application’s data into a consistent state at the time of the shadow copy
backup request.
Component
A group of files or folders, selected for backup, that are controlled by the
application or service under the Writer's control.
While an application or service is frozen, the Writer suspends writes on the
original volume, so that the files selected for backup (the Components) remain in
a consistent state during the creation of the shadow copy. Although writes are
suspended during this time, the process is transparent to the user working on
the selected files.
Writers
A Writer is part of a VSS-aware application or service that participates in a VSS
backup in the following ways:
■
Works with VSS to prepare the application or service’s data to be frozen
■
Suspends writes to the original volume while the shadow copy is created
■
Supplies a list of Components to include in the backup (and the restore) to
VSS and the Requestor
To ensure that the data used to create the shadow copy is internally consistent,
VSS informs the applications or services that control the files included in the
backup to freeze. When an application or service is frozen, the state of the files
under its control is consistent. It is the responsibility of the Writer to let VSS
know when an application or service’s files are in a consistent state.
To ensure that this state does not change during the creation of a shadow copy,
the Writers suspend the ability of the application or service to make changes to
the volume serving as the source of the shadow copy. The application (or its
Writer) ensures the consistency of its data at the time of the shadow copy. Work
can continue as usual on the original volume, but no changes are actually made
to the data until after the shadow copy has been created .
Chapter 1: Introducing VSS Support 13
How VSS Support W orks
A Writer is also responsible for supplying a list of Components to VSS and to the
Requestor in the form of a writer metadata document. A writer metadata
document is an XML file produced by a Writer that contains instructions for the
Requestor, such as which Components are to be backed up, the backup and
restore methods to be used, and a list of any files that should be excluded from
the backup.
Note: CA ARCserve Backup does not support Writers under Windows XP. This is
because some of the necessary Writer support in Windows Server 2003 is not
included in the Windows XP operating system.
Comp onents
A Component is a group of file s treated as a single unit by the Writers and VSS.
The files that make up a Component are grouped together because they are
mutually dependent on one another. For example, in a database, each file serves
an important function in the context of the database as a whole, but on its own,
a single file from a database has no use. By grouping all of these essential files
into a Component, you ensure that all the data needed to successfully back up an
application and its related files is backed up and can be resto red later.
Each VSS backup must consist of at least one Writer, and each Writer must
consist of at least one Component. An individual file cannot be backed up on its
own. A file can only be backed up if it is part of a Component. Furthermore, if any
of the files comprising a Component are inaccessible when the shadow copy is
being created, the backup of the Component will fail.
Providers
The Provider is responsible for managing the volumes involved in the shadow
copy backup, as well as for creating the shadow copy. The Provider interfaces
with the shadow copy creation capabilities that are either part of the operating
system (software-based) or on the disk array (hardware -based).
The Windows Server 2003 operating system has a built-in (system) Provider that
uses a copy-on-write scheme to create the shadow copies. It can create shadow
copies of any NTFS, FAT32, or RAW volume on the Windows Server 2003 system.
The system provider only creates shadow copies on NTFS. Third -party Providers
are also available.
Hardware disk array vendors can supply their own Providers to interface with the
VSS framework, and direct where and how to create the shadow copies.
The Agent for Open Files works with the Windows Server 2003 system provider,
but if a hardware-based provider is available, it is used instead. When the
Enterprise Option for VSS Hardware Snap-Shot is installed, hardware-based
providers work with VSS to create a transportable shadow copy.
14 Microsoft Volume Shadow Copy Serv ice Guide
How VSS Support W orks
There are two types of Providers:
Software-based Providers
Typically implemented as a DLL and a filter to manage storage. The shadow
copies are created by software. Shadow copies created with this type of
Provider include a point-in-time view of the original volume as it existed
before the shadow copy, and the subsequent shadow copies of only the
changed data.
Hardware-based Providers
Are implemented at the hardware level and work with a hardware controller
or storage adapter. Shadow copies are created by a storage appliance, host
adapter, or RAID device outside the operating system. Shadow copies
created with a hardware-based Provider are of an entire volume (a full copy),
and are typically mirrored views of the original volume . Additionally, if a
transportable shadow copy is created, it can be imported onto other servers
within the same system.
Shadow Copy Creation Methods
There are two methods to create shadow copies : making a full copy (or clone) of
all data on the volume or making a copy of only the data and files that have
changed (known as copy-on-write). The method used to create the shadow copy
and where the shadow copy is created are specified by the Provider associated
with a volume.
■
Hardware-based Providers are supplied by a disk array hardware vendor or
storage virtualization provider (for example, XIOtech, HDS, EMC, and HP),
and work only with their own arrays.
■
Software-based Providers that use the copy-on-write method have been
developed by a variety of vendors to instantly create a shadow copy of file
systems. In some cases, applications like Microsoft Exchange Server 2003
use this method for high-performance, low -impact backup or duplication.
The Agent for Open Files uses the system Provider included with Windows Server
2003. This Provider uses a copy-on-write scheme to create shadow copies. If a
hardware provider is installed, the Agent for Open Files uses it to create a full
shadow copy of the entire volume. When the Enterprise Option for VSS Hardware
Snap-Shot and a hardware provider are installed, the full shadow copy created is
also transportable.
Chapter 1: Introducing VSS Support 15
How the Agent W orks
Copy-on-Write Method
A copy-on-write shadow copy is a mapping of all the data blocks at a designated
point in time. As the original data set changes, the pointers to data that has
changed then replicate the original data, enabling the point-in-time restore.
Because of the way it works, copy-on-write shadow copies typically only take up
a small percentage of the disk space of the original data set.
VSS coordinates with the application Writers, the Agent for Open Files, and CA
ARCserve Backup to create shadow copies of applications and their files and the
file system.
Note: Copy-on-write shadow copy data block map is created on (and must stay
within), a particular server.
How the Agent Works
The Client for VSS Software Snap-Shot works with VSS to back up Writers,
Components and file systems. It uses the system Provider included with
Windows Server 2003 that uses a copy-on-write scheme to create the shadow
copies. If a hardware provider is installed, the client uses it to create a full
shadow copy of the entire volume.
Using the Backup Manager and the Restore Manager in CA ARCserve Backup,
you can select Writers on local or remote computers. The Client Agent for
Windows must also be installed if you plan to perform backups and restores on
remote computers.
The Client for VSS Software Snap-Shot can be used to back up Writers and
Components on local or remote computers. In local VSS backups, the production
server contains the original data to be backed up, and is also used as the location
where the shadow copy data is created. In remote VSS backups, the Client Agent
for Windows reads the data from the shadow copy instead of from the original
volume.
16 Microsoft Volume Shadow Copy Serv ice Guide
How the Agent W orks
The following illustration displays local configuration of the supported Client for
VSS Software Snap-Shot:
The following illustration displays remote configuration of the supported Client
for VSS Software Snap-Shot:
More information:
How the Enterprise Option for VSS Hardware Snap-Shot Works (see page 18)
How Transportable Shadow Copies are Created (see page 19)
Chapter 1: Introducing VSS Support 17
Full Copy Method
Full Copy Method
Hardware-based Providers use the full copy method to create a complete,
point-in-time shadow copy of the data set to another disk array (or another
section of the same disk array). This shadow copy can then be used as the
backup copy for restore operations, or it can be transported to another disk or
tape device for longer-term retention or archival use. Because the shadow copy
is an exact full copy of the original data set, the required disk space for the first
shadow copy is double, and so on.
How the Enterprise Option for VSS Hardware Snap-Shot Works
Intended for use with extremely large data sets on various disk array enterprise
environments, the Enterprise Option for VSS Hardware Snap -Shot works with
the Agent for Open Files and hardware -based providers to create a transportable
shadow copy of entire volumes. This shadow copy is a mirror of an entire LUN;
however, the data can be restored for specific volumes of the LUN.
The transportable shadow copy can be imported to a different server where it
can be backed up to tape. This leaves the production system running while the
data is backed up on the secondary (or backup) server. Data on the shadow copy
volume can also be mounted on another server to be used in the following ways:
■
As the basis for restores in the event of system failure
■
By developers to test applications
■
For archive or longer term storage when transported to another location
Note: The Enterprise Option for VSS Hardware Snap-Shot does not support
disaster recovery. The hardware-based Provider is not functional during disaster
recovery.
Two servers are involved in the creation of a transportable VSS backup: a
production server and a backup server:
■
The production server contains the database and connects to the original
volumes in the disk array. The Client Agent for Windows must also be
installed.
■
The backup server connects to the shadow copy volumes in the disk array
and to the tape library. CA ARCserve Backup must be installed on the server.
More information:
How the Agent Works (see page 16)
How Transportable Shadow Copies are Created (see page 19)
18 Microsoft Volume Shadow Copy Serv ice Guide
How Transportable Shadow Copies are Created
How Transportable Shadow Copies are Created
Typically, a production server uses some leve l of disk storage fault tolerance to
protect critical data. Fault tolerance can be provided through disk mirroring or by
a level of RAID striping. Using transportable shadow copies does not affect the
level of fault tolerance. The production data remains on the configured LUNs with
full fault tolerance, while the shadow copy is cloned to another transportable
LUN. For example, in the following figure, the dashed line represents the logical
connection between a Microsoft Exchange 2003 Server and the cloned data on
the transportable shadow copy volume.
During backup operations, CA ARCserve Backup (the Requestor) contacts VSS
on the production server and informs it to begin the transportable shadow copy
process. VSS tells the Writer to prepare the data for the shadow copy.
Chapter 1: Introducing VSS Support 19
How Transportable Shadow Copies are Created
After the Writer finishes preparing the data, VSS instructs the Provider to split
the volume containing the transportable shadow copy away from the production
server and to present this volume on the backup server. Continuing with the
previous example, the following figure shows the dashed line that now
represents the logical attachment between the CA ARCserve Backup server and
the cloned data on the transportable shadow copy volume.
CA ARCserve Backup can then perform a backup of the shadow copy without
impacting the production server.
After the backup is complete, the Provider disconnects the transportable volume
from the backup server and resynchronizes the volume back with the production
server in preparation for the next backup.
More information:
How the Agent Works (see page 16)
How the Enterprise Option for VSS Hardware Snap-Shot Works (see page 18)
20 Microsoft Volume Shadow Copy Serv ice Guide
Chapter 2: Installing the Client and the
Option
This section contains the following topics:
How to Install the Client and the Option (see page 21)
Prerequisites (see page 21)
System Requirements (see page 22)
Installation of the Client and Option (see page 22)
Prepare for VSS Shadow Copies (see page 22)
How to Install the Client and the Option
The Enterprise Option for VSS Hardware Snap-Shot can be installed locally or
remotely on a CA ARCserve Backup client machine.
This chapter includes the information that you need to install the client and
option. The information in this chapter assumes you are familiar the general
characteristics and requirements of Windows Server 2003, Windows Server
2008, and Windows 7 operating systems, and with the administrator
responsibilities in particular.
After the client and the option are installed, you can begin your first VSS backup.
No configuration of either solution is necessary.
Prerequisites
Consider the following installation prerequisites:
■
You must install the Client Agent for Windows on the agent computers to
provide communication capabilities between the agents and the CA
ARCserve Backup server. To back up the VSS writers on the agent
computers, you must license the Agent for Open files on the CA ARCserve
Backup server.
■
To install the Enterprise Option for VSS Hardware Snap-Shot, you must
verify that you have installed, or will be installing, the CA ARCserve Backup
Server and Manager packages.
Note: The Enterprise Option for VSS Hardware Snap-Shot is one of the
options included in the Enterprise Module, and requires a separate license for
each computer on which the option is installed.
Chapter 2: Installing the Client and the Option 21
System Requirements
System Requirements
Ensure that you have met all of the prerequisites and have all of the information
you need to complete the installation before you begin:
■
Verify that your system meets the minimum requirements to install the
client and the option. For a list of system requirements, see the readme file.
Check the CA web site for any updates to the requirements, as well as a list
of the currently supported hardware -based Providers and disk array devices
used by the option.
■
Verify that you have root user privileges or the proper authority to install
software on the computer on which you are installing the client or the option.
Note: Contact your CA ARCserve Backup administrator to obtain the proper
rights if you do not have them.
■
Make a note of the name and password of the computer on which you are
installing the client or the option.
Installation of the Client and Option
There is no separate installation for the Enterprise Option for VSS Hardware
Snap-Shot. The Enterprise Option for VSS Hardware Snap-Shot is one of the
options included in the CA ARCserve Backup Enterprise Module, and requires a
separate license for each computer on which the option is installed. After you
install and license the Agent for Open Files, the Client Agent for Windows, and
the Enterprise Module, the transportable VSS functionality is available.
Prepare for VSS Shadow Copies
The amount of disk space you must allow for shadow copies depends on how
often an application writes file changes and how much information is written. For
example, if an application rewrites the entire file when the file is modified,
changes to the application require much more shadow copy disk space than if the
application wrote only the changed data.
Determine how much space is needed for the shadow copies and verify that the
space is available.
22 Microsoft Volume Shadow Copy Serv ice Guide
Chapter 3: Performing Backups
This section contains the following topics:
Backup Options (see page 23)
Create Transportable VSS Backups (see page 30)
File System Backups (see page 33)
How Backup Jobs are Submitted (see page 33)
How the VSS Backup Works (see page 34)
How to Back Up Data Using the Option (see page 35)
Perform File System Backups (see page 36)
Perform Writer Backups (see page 37)
VSS and the Backup Manager (see page 39)
Writer Backups (see page 39)
Writer Exclusion During Backups (see page 40)
Backup Options
Writer and global options are available from the Backup Manager. With VSS
support, local Writer options enable to you customize backup settings for specific
Writers for drives, directories, and files that you want to back up. Global VSS
options affect all Writers and their drives, directories, and files.
Chapter 3: Performing Backups 23
Backup Options
Set Writer Options
Options set at the Writer level affect only the selected Writer and override any
global options set for VSS backups. For information about setting global VSS
options, see Set Global Options (see page 27).
To set options for a specific Writer
1. Open the Backup Manager.
2. On the Source tab, right-click the Writer in the Source tree, and select Writer
Options from the pop-up window:
The Writer Options dialog for VSS opens:
24 Microsoft Volume Shadow Copy Serv ice Guide
Backup Options
Writer Options Dialog
The following options are available on the Writer Options dialog:
■
Use Writer Options: Select this option to direct the VSS backup process to
use the options provided by the selected Writer and to enable the other
options available on this dialog.
If this option is not selected, the options set in the Volume Shadow Copy
Service tab of the Global Options dialog are used. For an explanation of the
global options, refer to the section Set Global Options (see page 27).
■
Use Transportable snap-shot: Select this option to create a transportable
VSS backup. When this option is selected, the only available Backup Method
is Full Backup.
This option is available only when the Enterprise Option for VSS Hardware
Snap-Shot is installed as part of the Enterprise Module.
■
Retain Shadow Copy After Backup: This option is enabled when you
select Use Transportable snap-shot. Select this option to specify that CA
ARCserve Backup should not delete the shadow copy volume after the
backup. Because the shadow copy volume is transportable, retaining it after
the backup enables the volume to be imported onto another system for other
uses.
■
Backup Method: Select one of the following methods to indicate the backup
method to use for the backup of the selected Writer:
–
Use Method Selected for Job: Uses the backup method indicated in
the Schedule tab of the Backup Manager.
–
Use Full Backup: Backs up all the files associated with the selected
Writer, regardless of when the data last changed. When the Use
Transportable snap-shot option is selected, this is the only option
available.
–
Use Incremental Backup: Backs up only those files that have changed
since the last full or incremental backup was performed. After each
backup, backed up files are marked so that they are not backed up
during the next incremental backup job unless they have changed. It
takes less time to process backup jobs using this method. However, to
restore files from an incremental backup, you must supply both the most
recent full backup and all subsequent incremental backup jobs.
–
Use Differential Backup: Backs up only those files that have changed
since the last full backup was performed. Because differential backup
jobs do not mark files as having been backed up, the files that were
backed up in the last differential job are backed up again. It takes longer
to process backup jobs using this method. However, to restore files from
a differential backup, you must supply only the most recent full backup
and the most recent differential backup.
Chapter 3: Performing Backups 25
Backup Options
–
Use Log Backup: Backs up only the log files associated with the
selected Writer.
–
Use Copy Backup: Backs up all the files included by the Writer, but
does not mark the files as having been backed up. Select this option to
make a full backup of your data without disrupting any existing
incremental or differential backups.
Note: Not all Writers support all types of backups. Depending on the Backup
Method selected, the CA ARCserve Backup behavior is different. For
example, if Incremental or Differential is selected at the job level and the
Global Options dialog for VSS has the Use Full Backup option set at the
Writer level, a full backup is performed. However, if the Global Options dialog
for VSS has the Use Log Backup option set at the Writer level and the Writer
does not support Log backup, the backup fails.
■
Files Included in this Writer Will be Excluded from Any File System
Backups: This option prevents files that belong to a Writer component from
being backed up by a traditional file system backup. This option offers the
following advantages:
–
Avoids backing up files that have already been backed up by VSS.
–
Ensures that fewer files are processed and that traditional backups take
less time to complete by excluding files from traditional backups,.
–
Helps achieve successful backups by eliminating problems associated
with files processed as a group (for example, files associated with a
database application). In a traditional backup, there is no mechanism to
ensure that the files are processed together.
This option is not available if the Use Transportable snap -shot option is
selected.
26 Microsoft Volume Shadow Copy Serv ice Guide
Backup Options
■
Files that are Specifically Excluded by this Writer Will be Excluded
from Any File System Backups: Select this option to exclude files
associated with an application that should never be backed up (the Windows
page file, for example) from any file system backups. Each Writer is aware of
whether its associated application maintains any such files. This option
enables CA ARCserve Backup to use this information when performing
traditional backups.
This option is not available if the Use Transportable snap -shot option is
selected.
■
If One or More Files of a Component of this Writer Fail to Backup
Successfully, the Entire Writer Backup Will be Terminated: Select this
option to cancel the backup of the selected Writer if the backup of any of its
Components fails. Component backups fail if one or more of the files that are
part of the Component cannot be backed up successfully.
Select this option to ensure that all of the files associated with a Writer are
backed up before the backup is considered successful, regardless of how
many Components are associated with the Writer.
This option is not available if the Use Transportable snap -shot option is
selected.
Set Global Options
Options set at the global level affect all Writers for VSS backups. You can
override global options for a selected Writer by setting Writer level options. For
information on setting options for selected Writers, refer to the section Set
Writer Options (see page 24).
Note: Global options do not apply to transportable VSS backups.
Chapter 3: Performing Backups 27
Backup Options
To set global options for non-transportable VSS backups
1. Open the Backup Manager.
2. Click Options
The Global Options dialog opens.
3. Select the Volume Shadow Copy Service tab.
28 Microsoft Volume Shadow Copy Serv ice Guide
Backup Options
File System Backup Options
The File System Backup fields let you specify how you want CA ARCserve Backup
to handle open files during file system backups. These options do not affect
Writers and Components.
■
Use VSS: Select this option to direct CA ARCserve Backup to use VSS to
back up open files. If this option is not selected, VSS support is not used and
the Agent for Open Files (if available) is used to handle open files. If the
Agent for Open Files is not available and Use VSS is not selected, a
traditional backup is performed. However, the backup will be marked as
incomplete if there are any open files that cannot be backed up.
■
Revert to traditional backup if VSS fails: Select this option to direct CA
ARCserve Backup to execute a traditional backup if an attempt to create a
VSS backup fails. If the Agent for Open Files is available, it is used to handle
open files if this option is selected and the VSS backup fails. If this option is
not selected and the VSS backup fails, the backup job fails.
Writers and Components Options
The Writers and Components options let you specify how you want CA ARCserve
Backup to treat Writers and Components. These global options affect all Writers
except for those with Writer-specific options in place. For information about
setting Writer-specific options, refer to the section Set Writer Options (see page
24).
■
Files included by a Writer will be excluded from file system backups:
Select this option to prevent files that belong to a Component from being
backed up by a traditional file system ba ckup. This option offers the following
advantages:
–
Avoids backing up files that have already been backed up by VSS.
–
Ensures that fewer files are processed and traditional backups take less
time to complete by excluding files from traditional backups.
–
Helps achieve successful backups by eliminating problems associated
with files that must be processed as a group (for example, files
associated with a Writer or database application). In a traditional
backup, there is no mechanism to ensure that the files are processed
together.
Chapter 3: Performing Backups 29
Create Transportable VSS Backups
■
Files excluded by a Writer will be excluded from file system
backups: Select this option to prevent files that have been excluded from
being backed up by a Component from being backed up by a traditional file
system backup. This option excludes files associated with an application that
should never be backed up (the Windows page file, for example) from any
file system backups. Each Writer is aware if its associated application
maintains such files. This option enables CA ARCserve Backup to use this
information when performing traditional backups.
■
If a Component file fails to back up the Writer backup will
terminate: Select this option to cancel the backup of a Writer if the backup
of any of its Components fails. Component backups fail if one or more of its
files cannot be successfully backed up. This option ensures that the backup is
consistent and that all of the files associated with a Writer are backed up
before the backup is considered successful, regardless of how many
Components are associated with the Writer.
Create Transportable VSS Backups
For transportable backups, VSS coordinates with the Writer, the Enterprise
Option for VSS Hardware Snap-Shot, CA ARCserve Backup, and the disk array
Provider to create a shadow copy of the LUN. When a request is initiated from CA
ARCserve Backup (the Requestor) to back up the Writer, the Enterprise Option
for VSS Hardware Snap-Shot communicates with VSS to contact the Writer. VSS
freezes all processing in the Writer’s application and contacts the disk-array
Provider to create the shadow copy on its volumes. After the shadow copy is
created, VSS thaws the application, allowing database writes to resume.
Note: At this time, CA ARCserve Backup supports transportable backup and
restore of the Microsoft Exchange Writer, MSDE Write r, Microsoft SQL Server
Writer, and Microsoft Hyper-V Writer for ETERNUS disk arrays.
You must use the Backup Manager to submit transportable VSS backup jobs.
30 Microsoft Volume Shadow Copy Serv ice Guide
Create Transportable VSS Backups
To create a transportable VSS
1. From the Source tab of the Backup Manager, expand the node of the
computer where the Writer is located.
If the computer does not appear in the Source tree, perform the following
steps to add the computer:
a. Open the Backup Manager in the Classic View or Group View.
b. If you opened the Backup Manager in the Classic View, right-click
Windows Systems in the Source tree.
If you opened the Backup Manager in the Group View, right-click Client
Agent in the Source tree.
c.
Select Add Machine/Object from the pop-up menu.
d. Enter the required information in the Add Agent dialog.
Chapter 3: Performing Backups 31
Create Transportable VSS Backups
2. You can back up the entire Writer or select individual storage groups:
■
To back up the Writer, click the green marker next to its name.
■
To back up individual storage groups, expand the Writer node to view its
storage groups and components. Click the green marker next to the
name of each storage group you want to include in the backup.
3. Right-click the Writer in the Source tree and select Writer Options from the
pop-up menu to specify Writer options. The Writer Options dialog opens.
4. Select Use Writer Options and select Use Transportable snap -shot. By
default, the shadow copy is deleted after the backup finishes. To retain the
shadow copy after the backup, select the Retain Shadow Copy after Backup
option. Click OK.
5. From the Destination tab of the Backup Manager, select Multi Stream and set
any other destination options for the backup.
Note: Multiplexing is not supported for transportable VSS backups.
For information about multistreaming jobs, see the Administration Guide.
6. From the Schedule tab of the Backup Manager, choose the appropriate
options to schedule your backup.
7. Click the Submit button on the Backup Manager to begin the backup. A
Security dialog opens.
Important! Ensure that all storage groups are on line before the backup job
starts.
8. In the Security dialog, enter the authentication information for the
production server and click OK. The Submit Job dialog opens.
9. In the Submit Job dialog, select Run Now or select Run On and specify a
specific date and time. Click OK to add the backup job to the job queue. Use
the Job Status Manager to monitor the progress of the backup job.
More information:
Develop Your Backup Strategy (see page 47)
Perform Writer Backups (see page 37)
Perform File System Backups (see page 36)
32 Microsoft Volume Shadow Copy Serv ice Guide
File System Backups
File System Backups
You can use VSS without Writers to back up open files on the file system. This
option is useful, for example, when backing up file servers where all the files are
independent. However, this method of backing up files is not as reliable as a
Writer backup.
Important! When you use VSS to back up the file system, the Writers are not
involved in the process. Unless the data on the selected volumes is relatively
static, using VSS to back up the file syste m could result in a corrupt backup.
How Backup Jobs are Submitted
You must submit transportable VSS backup jobs as multistreaming jobs. When
you start the backup job, the Backup Manager packages it as a master job. The
master job creates child jobs for each storage group selected; each child job
represents one storage group. The master job also saves the exported metadata
it received from the production server for child jobs.
Use the Job Status Manager to view the progress of the master and each child
job, as in the following example:
Chapter 3: Performing Backups 33
How the VSS Backup W orks
How the VSS Backup Works
The following diagram illustrates the series of steps involved in using CA
ARCserve Backup to perform a VSS backup.
Note: To read this diagram, start at the top with the icon of the CA ARCserve
Backup server (the Requestor) and follow the steps clockwise.
Each step in the diagram is explained in the following process:
1. The Requestor (CA ARCserve Backup) asks VSS to tell the Writers involved in
the backup to gather their writer metadata documents (XML files that
contain instructions for the backup) and send them to the Requestor.
CA ARCserve Backup communicates directly with VSS in local configurations .
In remote configurations, the communication between VSS and CA
ARCserve Backup is handled by the Client Agent for Windows, which must be
installed on the target computer.
2. VSS contacts the Provider responsible for managing the volumes involved in
creating the shadow copy. In the simplest case, one Provider is responsible
for all of the volumes involved in creating the shadow copy, but in some
situations, multiple Providers may be involved.
34 Microsoft Volume Shadow Copy Serv ice Guide
How to Back Up Data Using the Option
3. VSS contacts the Writers that are part of the backup and asks them to gather
their writer metadata documents and send them to the Requestor. The
Writers also begin preparing for the freeze by ensuring that the files to be
backed up are in a consistent state .
4. The Writers send their writer metadata documents to the Requestor. Do not
edit these files directly. Use the Backup Manager in CA ARCserve Backup to
indicate the files you want to back up, and the backup and restore methods
to use.
5. After collecting all the writer metadata documents from the Writers, the
Requestor issues another command to VSS, asking it to begin the creation of
the shadow copy.
6. VSS freezes the Writer's applications, ensuring that the data to be used for
the creation of the shadow copy remains consistent and has internal
integrity. While an application is frozen, Writers suspend any changes to the
files on the original volume, allowing the application and its files to remain
available while the shadow copy is created. However, because a VSS backup
is a point-in-time backup, any changes made to files after the freeze are not
reflected in the shadow copy and are not backed up.
7. VSS issues a command to the Provider, telling it to create a shadow copy of
the current disk state.
8. The Provider creates the shadow copy on the shadow copy volume.
9. VSS thaws the frozen Writers, returning them to their normal state. Any
changes that were queued by the Writer while the shadow copy was being
created are written to the original volume at this time. The thaw occurs after
the shadow copy has been created and before the data is backed up. This
allows the applications to start using the original volumes while the backup is
made using the shadow copy volume.
10. The backup data is sent to the Requestor (CA ARCserve Backup) by the
Client Agent for Windows.
11. The Requestor backs up the data to media. The Writer metadata is stored
with the shadow copy data so that recovery information is available when the
data is restored.
How to Back Up Data Using the Option
You can perform VSS backups from CA ARCserve Backup using the Backup
Manager. The VSS backup procedures in this chapter use the Backup Manager
interface of CA ARCserve Backup. For more information about the Backup
Manager and all of its features, see the Administration Guide.
Note: For information about backing up files and components controlled by a
Microsoft Exchange writer or an MSDE writer, see the appendix
"Application-Specific Guidelines."
Chapter 3: Performing Backups 35
Perform File System Backups
More information:
Develop Your Backup Strategy (see page 47)
Perform Writer Backups (see page 37)
Perform File System Backups (see page 36)
Create Transportable VSS Backups (see page 30)
Perform File System Backups
To perform a non- transportable VSS backup of the file system
1. From the Backup Manager, click the Options button to open the Global
Options dialog.
2. Select the Volume Shadow Copy Service tab.
3. On the Volume Shadow Copy Service tab, select the Use VSS option and click
OK. For more information about the options available on this tab, refer to the
section Set Global Options (see page 27).
4. From the Source tree of the Backup Manager, select the volumes you want to
back up.
5. From the Destination tab of the Backup Manager, choose the appropriate
options for your backup.
6. From the Schedule tab of the Backup Manager, choose the appropriate
options to schedule your backup.
7. Click the Submit button on the Backup Manager to begin the backup. A
Security dialog opens.
8. In the Security dialog, enter the authentication information for the
production server, and click OK. The Submit Job dialog opens.
9. In the Submit Job dialog, select Run Now or select Run On and specify a
specific date and time. Click OK to add the backup job to the job queue. Use
the Job Status Manager to monitor the progress of the backup job.
More information:
Develop Your Backup Strategy (see page 47)
Perform Writer Backups (see page 37)
Create Transportable VSS Backups (see page 30)
36 Microsoft Volume Shadow Copy Serv ice Guide
Perform Writer Backups
Perform Writer Backups
To perform a non- transportable VSS backup
1. From the Source tab of the Backup Manager, expand the node of the
computer where the Writer is located.
If the computer does not appear in the Source tree, perform the following
steps to add the computer:
a. Open the Backup Manager in the Classic View or Group View.
b. If you opened the Backup Manager in the Classic View, right-click
Windows Systems in the Source tree.
If you opened the Backup Manager in the Group View, right-click Client
Agent in the Source tree.
Chapter 3: Performing Backups 37
Perform Writer Backups
c.
Select Add Machine/Object from the pop-up window.
d. Enter the required information in the Add Agent dialog. For help with the
Add Agent dialog, click the Help button.
2. Select the Writer you want to back up by clicking the green marker next to its
name.
If necessary, you can expand the Writer node to view its Components. If a
Writer has only one component, the marker next to its name is gray,
indicating that it cannot be removed from the backup. If a Writer has
multiple Components, you can, typically, choose the Components to back
up. The Writer decides whether the backup of a Component is optional.
Some Writers may require all Components to be backed up.
3. Right-click the Writer in the Source tree and select Writer Options from the
pop-up menu to specify options for the selected Writer or to use the global
options. The Writer Options dialog appears.
4. In the Writer Options dialog, perform one of the following:
■
Select Use Writer Options and choose other options to set local options.
■
Clear the Use Writer Options option to direct the backup to use the
options specified on the Volume Shadow Copy Service tab of the Global
Options dialog to use global options.
5. From the Schedule tab of the Backup Manager, choose the appropriate
options to schedule your backup.
6. From the Destination tab of the Backup Manager, choose the appropriate
options for your backup.
7. Click the Submit button on the Backup Manager to begin the backup. A
Security dialog opens.
8. In the Security dialog, enter authentication information for the production
server and click OK. The Submit Job dialog opens.
9. In the Submit Job dialog, select either Run Now or Run On and enter a
specific date and time. Click OK to add the backup job to the job queue. Use
the Job Status Manager to monitor the progress of the backup job.
More information:
Develop Your Backup Strategy (see page 47)
Perform File System Backups (see page 36)
Create Transportable VSS Backups (see page 30)
38 Microsoft Volume Shadow Copy Serv ice Guide
VSS and the Backup Manager
VSS and the Backup Manager
When used to manage VSS backups, the Backup Manager lets you browse
Writers and Components on local or remote computers. The Writers appear at
the same level as volumes, system state, and other agents . Expanding a Writer
reveals its associated Components.
Any Writer displayed in the Backup Manager can be selected for backup, but
Components can only be selected if they can be backed up separately. The Writer
is always part of the backup when any of its Components are selected.
Writer Backups
VSS is able to safely back up open files by using application-specific Writers and
their Components. A Writer is a process of an application or a service that works
with VSS to freeze the application or service in preparation for a VSS backup. A
Component is a group of files selected for backup, that are controlled by the
application or service that is under the control of the Writer. An
application-specific Writer understands how the application works, and what files
and structures the application needs.
While an application is frozen, the Writer suspends writing activities on the
original volume so that the files selected for backup (the Components) remain in
a consistent state during the creation of the shadow copy. Although write
activities are suspended during this time, the process is completely transparent
to a user working on the selected application.
Note: For additional information about Writers and VSS backups and restores,
see Application-Specific Guidelines (see page 51).
Chapter 3: Performing Backups 39
Writer Exclusion During Backups
Writer Exclusion During Backups
If you select the whole computer during a backup and there is a CA ARCserve
Backup application-specific agent installed, the corresponding Writer is excluded
from the backup. Excluding the Writer from the backup avoids backing up Writer
data twice. Currently this applies to the Microsoft Exchange Writer, the Microsoft
SQL Server Desktop Engine Writer (MSDE Writer), and the SQL Server Writer for
SQL 2005.
■
If the CA ARCserve Backup Agent for Microsoft Exchange is installed, the
Microsoft Exchange Writer is e xcluded.
■
If the CA ARCserve Backup Agent for Microsoft SQL Server is installed, the
MSDE Writer and SQL Server Writer are excluded.
The Writers are only excluded from a whole machine backup. You can still select
individual Writers for backup if required.
40 Microsoft Volume Shadow Copy Serv ice Guide
Chapter 4: Performing Restores
This section includes information on the various options CA ARCserve Backup
offers to let you safely and efficiently restore your data from VSS backups. The
instructions in this chapter provide the general steps for using the Restore
Manager. For additional information about how to complete the restore process,
consult the documentation supplied by each Writer application.
Note: For information about restoring files and components controlled by a
Microsoft Exchange writer or an MSDE writer, see Application-Specific Guidelines
(see page 51).
This section contains the following topics:
VSS and the Restore Manager (see page 41)
Restoration of File Systems (see page 42)
Restoration of Writers Backup (see page 42)
VSS and the Restore Manager
CA ARCserve Backup allows you to restore data to most computers attached to
your Windows network. When used to manage Writer restore jobs, the Restore
Manager lets you browse Writers and Components available on local and remote
computers. The Writers appear at the same level as volumes, system state, and
other agents. Expand a Writer to reveal its associated Components.
Any Writer displayed in the Restore Manager can be selected to be restored but
Components can only be selected if they can be restored separately. The valid
restore methods for the Writer are specified in the writer metadata document
created at the time of the restore operation.
Each restore job requires a source and destination. The files selected as your
source must originate from media controlled by CA ARCserve Backup, and the
destination must be a hard drive.
The Restore Manager dialog provides three tabs to customize your restore job:
■
Source
■
Destination
■
Schedule
For procedural information on how to submit a basic restore job, see the online
help.
Chapter 4: Performing Restores 41
Restoration of File Systems
Restoration of File Systems
A non-Writer file backed up using VSS is no different than a file backed up by a
traditional backup. This means that files in a VSS backup can be restored using
any of the methods available for any file. For information about the d ifferent
methods, refer to the section Restore Methods (see page 43).
Restoration of Writers Backup
The process for restoring common Writer VSS backups, transportable or
non-transportable, is essentially the same. However, you should have a working
knowledge of the application whose files and components are to be restored.
While in many cases the VSS Writer specifies the backup and restore methods for
its application files and components, there may be some additional manual steps
and procedures required for the restore process. For example, Microsoft
Exchange Server 2003 requires that its stores are dismounted before the restore
job begins. For more guidelines for specific applications and VSS, see
Application-Specific Guidelines (see page 51).
See the documentation for the application associated with the VSS Writer or
contact the application’s vendor for additional information about restoring from
the Writer.
Writers that allow custom restore jobs may need extra processing to complete
the restore process. These steps are application specific and not part of CA
ARCserve Backup functionality. To restore these Writers, the data should be
restored to an alternate location and the necessary files and extra processing
should be carried out according to the application’s specification. CA ARCserve
Backup does not support restoring Writers declaring themselves to be custom
restore jobs to the original location. For more information about alternate
locations, refer to the section Restore Locations (see page 42).
Restore Locations
When restoring a Writer to an alternate location (if, for example, the Writer is not
available on the original location or the Components and files to be restored
already exist in the original location), the restore location you choose determines
whether the Writer is involved in the restore process:
■
When restoring to the original location, the Writer is always involved.
■
When restoring to an alternate location, the Writer is never involved.
When you use the Restore by Tree, Restore by Session, or Restore by Backup
Media methods to restore a Writer, and you restore the files to their original
location, the Writer is always involved in the restore operation. If you restore the
files to an alternate location, the Writer is not involved.
42 Microsoft Volume Shadow Copy Serv ice Guide
Restoration of W riters Backup
When you use the Restore by Query method to restore a Writer's files, the Writer
is not involved in the restore operation. Additionally, the files are restored as if
they had been backed up as part of the file system and CA ARCserve Backup uses
the restore options set in the Destination tab of the Global Options dialog when
restoring the files.
Because the Writer can also determine how to restore its files, keeping the Writer
out of the restore process enables you to:
■
Access an individual file from a Writer backup
■
Restore the files associated with a Writer to a computer on which the Writer
is not available
Restore Methods
You can use any of the following methods from the Restore Manager to restore
files backed up using a VSS Writer:
■
Restore by Tree: Writer backups are visible in the tree of the Restore
Manager at the same level as volume and system state backups. Click the
marker next to the Writer's name to restore all of its Components. To restore
an individual Component, expand the Writer in the tree and click the marker
next to the Component's name.
Note: Not all Components can be restored individually. The Writer decides
whether a Component can be restored individually. When an SQL Server
instance is stopped, restoring only one individual custom database is not
supported, even though the restore job is successful.
Use this method if you do not know which media contains the data you need,
but you know which computer it came from.
■
Restore by Session: Writer backups are listed as separate sessions. Click
the marker next to the session's name to re store all of the Components
included in the session. To restore an individual Component, expand the
session and click the marker next to the Component's name.
Note: Not all Components can be restored individually. The Writer decides
whether a Component can be restored individually. When an SQL Server
instance is stopped, restoring only one individual custom database is not
supported, even though the restore job is successful.
Use this method if you know the media name, but are not certain about the
session you want to restore.
■
Restore by Backup Media : Writer backups are listed as separate sessions.
You must restore the entire session. Components cannot be restored
individually using this method even though they may be selectable.
Use this method if media was created by a different version of CA ARCserve
Backup or if the database does not recognize it.
Chapter 4: Performing Restores 43
Restoration of W riters Backup
■
Restore by Query: Files that were backed up as part of a Writer can be
restored individually using this method.
Use this method if you know the name of the file or directory you want to
restore, but do not know the machine it was backed up from or the media it
was backed up to.
Important! While this option does allow a single file to be restored, the
Writer is not notified of the restore operation and cannot properly prepare
the application. By restoring a single file, you can create inconsistencies in
your data. You should only use the Res tore by Query method if you have
in-depth knowledge about the files you are restoring.
Set Restore Options
By default, CA ARCserve Backup uses the Non-authoritative method to restore
the DFS (Distributed File System) Replication Service writer.
To set the restore method to Authoritative
1. Right-click the DFS Replication Service writer in the Restore By Tree or
Restore By Session view in the Restore Manager.
The VSS Restore Options dialog appears.
Note: The DFS Replication Service writer will not appear on Windows Server
2008 systems as this is part of system state. You need to backup the system
state, if you want to backup DFS Replication.
2. Select the option Use Authoritative Restore in the VSS Restore Options
dialog and click OK.
Restore VSS Writer Backups
Before beginning a restore job, consult the documentation for the specific
application whose files and Components you are restoring. CA ARCserve Backup
only restores the files to disk, and there may be some additional steps or
procedures necessary to recover the application completely.
Note: The instructions for restoring common Writer VSS backups
(non-transportable) and restoring transportable VSS backups using CA
ARCserve Backup are essentially the same. For guidelines for specific
applications and VSS, see Application-Specific Guidelines (see page 51).
44 Microsoft Volume Shadow Copy Serv ice Guide
Restoration of W riters Backup
To restore a VSS Writer
1. From the Source tab of the Restore Manager, choose the restoration type.
For a description of each type, see Restore Methods (see page 43).
2. Click the green marker next to the name of the Writer to be restored to select
it. To restore individual components, expand the Writer node and select the
Components you want to restore.
3. From the Destination tab of the Restore Manager, choose the restore
location. Choose either of the following options:
■
Restore files to their original location
■
Restore to user-shared directories and drives (alternate location)
The default method is to restore files to their original location. If you choose
to restore files to an alternate location, a list of computers, directories, and
files displays so that you can select your specific destination. For more
information about restore locations, see Restore Locations (see page 42).
4. From the Schedule tab of the Restore Manager, choose the appropriate
options to schedule your restore job.
5. Click Submit on the Restore Manager to begin the restore. A Security dialog
opens.
6. Enter the authentication information for the production server and click OK.
The Submit Job dialog opens.
7. Select Run Now or select Run On and enter a specific date and time. Click OK
to add the restore job to the job queue. Use the Job Status Manager to
monitor the progress of the restore job.
Chapter 4: Performing Restores 45
Chapter 5: Best Practices
Open files can cause significant problems when backing up data. CA ARCserve
Backup provides the following solutions to back up files that are in use by other
applications or users:
■
CA ARCserve Backup Agent for Open Files
■
CA ARCserve Backup Enterprise Option for VSS Hardware Snap-Shot
This section describes when it is most appropriate to use each solution.
This section contains the following topics:
Develop Your Backup Strategy (see page 47)
Develop Your Backup Strategy
When developing your backup strategy, consider the following points:
■
Amount of data to be backed up (see page 48).
■
Files that are not supported by a Writer (see page 48).
Chapter 5: Best Practices 47
Dev elop Your Backup Strategy
Amount of Data to Back Up
Both the Agent for Open Files and the Enterprise Option for VSS Hardware
Snap-Shot operate on a per-volume basis (VSS must prepare the entire volume
for the backup before the backup operation can begin). The Agent for Open Files
operates on a per-file basis (each open file is processed as it is encountered). For
example, for a backup job consisting of 10 GB of critical database files that reside
on a full 120 GB hard disk:
■
Using the VSS solutions, a shadow copy of the entire 120 GB volume must be
taken, and each Writer with data on that volume must prepare its files (both
open and closed) before the backup job can begin. While the initial shadow
copy may take some time, subsequent shadow copies are almost
instantaneous.
■
Using the Agent for Open Files, if the files to be backed up are closed when
the request for the backup job is made, the backup operation can begin
immediately. If there are any open files, the agent synchronizes them and
allows CA ARCserve Backup to back them up.
For these reasons, when you are backing up a small amount of data (relative to
the size of the volume on which it resides), using the Agent for Open Files to
handle open files results in a much faster backup. When the amount of data to
back up is large, you should use either the Agent for Open Files or the Enterprise
Option for VSS Hardware Snap-Shot.
Files Not Supported by Writers
When backing up open files, VSS relies on VSS-aware applications and their
Writers to prepare the associated files for backup (for example, the Microsoft
Exchange Writer is responsible for preparing Microsoft Exchange files and the
MSDE Writer is responsible for preparing Microsoft SQL files). If no Writer is
available for a certain application, any open files of that type cannot be reliably
backed up.
Use the Client for VSS Software Snap-Shot or the Enterprise Option for VSS
Hardware Snap-Shot when the files you are backing up are associated with a
Writer. Because of the way in which Writers communicate with their applications
and the application’s files, VSS can obtain an in-depth knowledge of the
transactional behavior of a Writer's files. When file activity is very high, the
Agent for Open Files may take much longer than VSS to find a transactionally
safe period in which to back up the open files.
48 Microsoft Volume Shadow Copy Serv ice Guide
Dev elop Your Backup Strategy
Use the Agent for Open Files to guarantee that all open files not associated with
a Writer are reliably backed up. If open files not associated with a Writer are
backed up using VSS, there is no guarantee of transactional integrity and you
run the risk of invalidating the entire backup.
The Agent for Open Files operates independently of other applications. An
application does not need to know about the agent to back up open files, and an
application can write to its files during a backup job without having to
communicate with the agent. Everything is handled by the agent.
Chapter 5: Best Practices 49
Appendix A: Application-Specific
Guidelines
The information in this section appendix presents guidelines and other
information to keep in mind when backing up and restoring files and components
controlled by applications that support a VSS Writer.
This section contains the following topics:
Microsoft Exchange Writer (see page 51)
Microsoft Hyper-V VSS Writer (see page 55)
Windows System State Writer Components (see page 55)
MSDE Writer (see page 56)
SQL Server Writer (see page 59)
Oracle VSS Server Writer (see page 61)
Miscellaneous Supported Writers (see page 64)
Microsoft Exchange Writer
This section details some considerations to be aware of when using VSS to back
up and restore Microsoft Exchange Server 2003 or 2007. For complete restore
and recovery information, see the Microsoft Exchange Server 2003 or 2007
documentation or contact Microsoft directly.
Note: The Microsoft Exchange Writer cannot support some important features of
Microsoft Exchange Server 2007, which can only be protected by the Exchange
Agent. The Microsoft Exchange Writer will not be displayed in the Backup
Manager whether the Exchange Agent is installed or not.
Appendix A: Application-Specific Guidelines 51
Microsoft Exchange W riter
General Guidelines
The following are general guidelines for backup and restore operations involving
Microsoft Exchange databases:
■
Microsoft Exchange databases backed up using VSS must be restored using
VSS and the Microsoft Exchange Writer.
■
All storage groups must be on line before a backup job starts.
■
All the databases in the same storage group must be dismounted before a
restore job starts, even if you are restoring only one database in the storage
group, to allow Microsoft Exchange Server 2003 or 2007 to access all of the
log files and bring the databases back on line. After the data has been
restored, the databases can be mounted and the storage group can be
brought back on line.
■
CA ARCserve Backup works with VSS to restore only the backed up data. To
completely recover the databases to a consistent s tate, you must perform
Exchange-specific procedures to recover the logs.
Non-Transportable VSS Backup and Restore - Microsoft Exchange Writers
A non-transportable Microsoft Exchange Writer session can be restored in the
same way as any other Writer session. For a description of the types of restore
available in the Restore Manager, refer to the section Restore Methods (see page
43).
For a non-transportable Microsoft Exchange Writer backup operation, because all
of the data is in a single session, the whole Writer can be selected for restore if
the whole Writer was selected during the backup operation.
When you use the Agent for Open Files and select the Microsoft Exchange Writer
for backup, all of the data is written to a single session on the backup media. To
restore the whole Microsoft Exchange Writer, select only that one session to
restore all the data. If there is more than one storage group, all data for the
storage groups is in one session.
52 Microsoft Volume Shadow Copy Serv ice Guide
Microsoft Exchange W riter
Transportable VSS Backup and Restore - Microsoft Exchange Writers
To perform backup jobs for Transportable Shadow Copies using the Microsoft
Exchange Server writer, you must have Microsoft Exchange Server installed on
your ARCserve backup server. Backups of this type will fail if the Microsoft
Exchange Server is not installed on the ARCserve backup server.
Transportable VSS backups of the Microsoft Exchange Writer can only be
restored by Tree or by Session. Refer to the section Restore Methods (see page
43) for a description of the types of restore available in the Restore Manager.
Because transportable VSS backups are run as multistreaming jobs and, for the
Microsoft Exchange Writer, each storage group has been backed up to a different
session, to restore the entire Microsoft Exchange Writer, you must individually
restore each storage group session. Each session is one storage group.
Restore Transportable VSS Backups Using Microsoft Exchange Writers
To restore a transportable VSS backup of the Microsoft Exchange Writer
1. On the Source tab of the Restore Manager, choose the restoration type:
■
Restore by Tree: Microsoft Exchange backups are visible in the tree at
the same level as volume and system state backups. Click the marker
next to the storage group’s name to restore all of its Components.
One storage group, the last storage group in the multistreaming backup
job, appears in the tree.
To see the other storage groups, click Version History. From the Version
History window, select the version that represents the stream of the
storage group you want to restore and click Select.
The Restore Manager displays the selected storage group.
Appendix A: Application-Specific Guidelines 53
Microsoft Exchange W riter
■
Restore by Session: Microsoft Exchange backups are listed as
separate sessions. Click the green icon next to the session's name to
restore all of the Components included in the session. To restore an
individual Component, expand the session and select the Component's
name.
Note: Not all Components can be restored individually. The Writer
decides whether a Component can be restored individually. When an
SQL Server instance is stopped, restoring only one individual custom
database is not supported, even though the restore job is successful.
The following example displays individual sessions and the series of
steps involved in using CA ARCserve Backup to perform a VSS backup.
2. On the Destination tab of the Restore Manager, choose the destination to
which to restore the files. Choose one of the following:
■
Restore files to their original location
■
Restore to user-shared directories and drives (alternate location)
By default, files are restored to their original location. If you choose to
restore files to an alternate location, a list of computers, directories, and files
appears, from which you can select a specific destination. For more
information about restore locations, refer to the section Restore Locations
(see page 42).
3. From the Schedule tab of the Restore Manager, choose the appropriate
options to schedule your job.
54 Microsoft Volume Shadow Copy Serv ice Guide
Microsoft Hyper-V VSS Writer
4. Click Submit on the Restore Manager to begin the restore operation. A
Security dialog opens.
Important! Ensure that all storage groups are off line before the restore job
starts.
5. In the Security dialog, enter the authentication information for the
production server and click OK. The Submit Job dialog appears.
6. In the Submit Job dialog, select Run Now or sele ct Run On and specify a
specific date and time. Click OK. The restore job is added to the job queue.
Use the Job Status Manager to monitor the progress of the restore job.
Microsoft Hyper-V VSS Writer
CA ARCserve Backup lets you protect Hyper-V VMs using the ARCserve Volume
Shadow Copy Service (VSS) agent. The agent is designed to protect Microsoft
Hyper-V data with VSS Writers using Volume Shadow Copy Service technologies
without installing the Agent for Virtual Machines. For more information on
protecting Hyper-V virtual machines using the Microsoft Hyper-V VSS Writer, see
the CA ARCserve Backup Agent for Virtual Machines Guide.
Windows System State Writer Components
The Microsoft Windows System State Writer consists of the following writer
components:
■
System Writer
■
Registry Writer
■
COM+ Class Registration Database Writer
■
NTDS Writer
■
File Server Resource Manager (FSRM) Writer
■
Certificate Authority Writer
■
Cluster Service Writer
■
IIS Metabase Writer
■
Microsoft Writer (bootable state)
Appendix A: Application-Specific Guidelines 55
MSDE W riter
■
IIS Configuration Writer
Note: This writer is available only on Windows Server 2008.
■
DFS Replication Service Writer
■
Remote Desktop Services (Terminal Services) Licensing VSS Writer
(TermServLicensing)
Note: This writer is available only on Windows Server 2008 r2.
■
Remote Desktop Services (Terminal Services) Gateway VSS Writer
Note: This writer is available only on Windows Server 2008 r2.
■
Performance Counters Writer
Note: This writer is available only on Windows Server 2008 r2.
■
Task Scheduler Writer
Note: This writer is available only on Windows Server 2008 r2.
■
VSS Metadata Store Writer
Note: This writer is available only on Windows Server 2008 r2.
MSDE Writer
This section details considerations to keep in mind when using VSS to back up
and restore Microsoft SQL 2000. For complete restore and recovery information,
see the Microsoft SQL 2000 documentation or contact Microsoft directly.
General Guidelines
The following are general guidelines for backup and restore operations involving
Microsoft SQL databases:
■
Microsoft SQL databases backed up using VSS must be restored using VSS
and the MSDE Writer.
■
All databases must be off line or detached before a restore job starts.
56 Microsoft Volume Shadow Copy Serv ice Guide
MSDE W riter
Non-Transportable VSS Backup and Restore - MSDE Writers
A non-transportable MSDE Writer session can be restored in the same way as
any other Writer session. For a description of the types of restore available in the
Restore Manager, refer to the section Restore Methods (see page 43).
For a non-transportable MSDE Writer backup, because all of the data is in a
single session, the whole Writer can be selected for restore if the whole Writer
was selected during the backup operation.
When you use the Agent for Open Files and select the MSDE Writer for backup, all
of the data is written to a single session on the backup media. To restore the
whole MSDE Writer, select only that one session to restore all the data. If there
is more than one database, all data for the databases is in one session.
Transportable VSS Backup and Restore - MSDE Writers
Transportable VSS backups of the MSDE Writer can only be restored by Tree or
by Session. Refer to the section Restore Methods (see page 43) for a description
of the types of restore available in the Restore Manager.
Because transportable VSS backups are run as multis treaming jobs and, for the
MSDE Writer, each database is backed up to a different session, to restore the
entire MSDE Writer, you must individually restore each database session. Each
session is one database.
Appendix A: Application-Specific Guidelines 57
MSDE W riter
Restore Transportable VSS Backups Using MSDE Writers
To restore a transportable VSS backup of the MSDE Writer
1. On the Source tab of the Restore Manager, choose the restoration type:
■
Restore by Tree: Microsoft SQL backups are visible in the tree at the
same level as volume and system state backups. Click the icon next to
the appropriate database to select it. One database, the last database in
the multistreaming backup job appears in the tree.
To see other databases, click Version History. From the Version History
window, select the version that represents the stream of the database
you want to restore and click Select. The Restore Manager displays the
new database.
■
Restore by Session: Microsoft SQL backups are listed as separate
sessions. Click the icon next to the session's name to restore all of the
Components included in the session. To restore an individual
Component, expand the session and select the Component's name.
Note: Not all Components can be restored individually. The Writer decides
whether a Component can be restored individually. When an SQL Server
instance is stopped, restoring only one individual custom database is not
supported, even though the restore job is successful.
2. On the Destination tab of the Restore Manager, choose the destination to
which to restore. Choose one of the following:
■
Restore files to their original location
■
Restore to user-shared directories and drives (alternate location)
By default, files are restored to their original location. If you choose to
restore files to an alternate location, a list of computers, directories, and files
appears, from which you can select a specific destination. For more
information about restore locations, see Restore Locations (see page 42).
3. From the Schedule tab of the Restore Manager, choose the appropriate
options to schedule your job.
58 Microsoft Volume Shadow Copy Serv ice Guide
SQL Server Writer
4. Click Submit on the Restore Manager to begin the restore operation. A
Security dialog opens.
Important! Ensure that all databases are off line or detache d before the
restore job starts.
5. In the Security dialog, enter the authentication information for the
production server and click OK. The Submit Job dialog appears.
6. In the Submit Job dialog, select Run Now or select Run On and specify a
specific date and time. Click OK. The restore job is added to the job queue.
Use the Job Status Manager to monitor the progress of the restore job.
SQL Server Writer
This section details considerations to keep in mind when using VSS to back up
and restore Microsoft SQL 2005. For complete restore and recovery information,
see the Microsoft SQL 2005 documentation or contact Microsoft directly.
General Guidelines SQL 2005
The following are general guidelines for backup and restore operations involving
Microsoft SQL 2005 databases:
■
Microsoft SQL databases backed up using VSS must be restored using VSS
and the SQL Server Writer.
■
All databases must be offline or detached before a restore job starts.
Non-Transportable VSS Backup and Restore - SQL Server Writers
A non-transportable SQL Server 2005 Writer session can be restored in the same
way as any other Writer session. For a description of the types of restore
available in the Restore Manager, refer to the section Restore Methods (see page
43).
For a non-transportable SQL Server 2005 Writer backup, because all of the data
is in a single session, the whole Writer can be selected for restore if the whole
Writer was selected during the backup operation.
When you use the Agent for Open Files and select the SQL Server 2005 Writer for
backup, all of the data is written to a single session on the backup media. To
restore the whole SQL Server 2005 Writer, select only that one session to restore
all the data. If there is more than one database, all data for the databases is in
one session.
Appendix A: Application-Specific Guidelines 59
SQL Server Writer
Transportable VSS Backup and Restore - SQL Server Writers
Transportable VSS backups of the SQL Server Writer can only be restored by
Tree or by Session. Refer to the section Restore Methods (see page 43) for a
description of the types of restore available in the Restore Manager.
Because transportable VSS backups are run as multistreaming jobs and, for the
SQL Server Writer, each database is backed up to a different session, to restore
the entire SQL Server Writer, you must individually restore each database
session. Each session is one database.
Note: Though SQL Server Writer supports differential backups, differential and
incremental backup functionality is not supported at this time.
Restore Transportable VSS Backups Using SQL Server Writers
To restore a transportable VSS backup of the SQL Server Writer
1. On the Source tab of the Restore Manager, choose one of the following:
■
Restore by Tree: Microsoft SQL backups are visible in the tree at the
same level as volume and system state backups. Click the icon next to
the appropriate database to select it.
One database, the last database in the multistreaming backup job
appears in the tree.
To see other databases, click Version History. From the Version History
window, select the version that represents the stream of the database
you want to restore and click Select. The Restore Manager displays the
new database.
■
Restore by Session: Microsoft SQL backups are listed as separate
sessions. Click the icon next to the session's name to restore all of the
Components included in the session. To restore an individual
Component, expand the session and select the Component's name.
Note: Not all Components can be restored individually. The Writer decides
whether a Component can be restored individually. When an SQL Server
instance is stopped, restoring only one individual custom database is not
supported, even though the restore job is successful.
60 Microsoft Volume Shadow Copy Serv ice Guide
Oracle VSS Server Writer
2. On the Destination tab of the Restore Manager, choose the destination to
which to restore. Choose one of the following:
■
Restore files to their original location
■
Restore to user-shared directories and drives (alternate location)
By default, files are restored to their original location. If you choose to
restore files to an alternate location, a list of computers, directories, and files
appears, from which you can select a specific destination. For more
information about restore locations, refer to the section Restore Locations
(see page 42).
3. From the Schedule tab of the Restore Manager, choose the appropriate
options to schedule your job.
4. Click Submit on the Restore Manager to begin the restore operation.
A Security dialog opens.
Important! Ensure that all databases are off line or detached before the
restore job starts.
5. In the Security dialog, enter the authentication information for the
production server and click OK.
The Submit Job dialog appears.
6. In the Submit Job dialog, select Run Now or select Run On and specify a
specific date and time.
7. Click OK.
The restore job is added to the job queue.
8. Use the Job Status Manager to monitor the progress of the restore job.
Oracle VSS Server Writer
This section details considerations to keep in mind when using VSS to back up
and restore Oracle 11g VSS Writer. For complete restore and recovery
information, see the CA ARCserve Backup for Windows Agent for Oracle Guide or
contact Oracle directly.
Note: The VSS Writer only supports backup and restore of Oracle 11g.
Appendix A: Application-Specific Guidelines 61
Oracle VSS Server Writer
General Guidelines Oracle 11g
The following are general guidelines for backup and restore operations involving
Oracle 11g databases:
■
Oracle 11g databases backed up using VSS must be restored using VSS and
the Oracle Server Writer.
■
Oracle VSS Writer supports backup in both ARCHIVELOG mode and
NOARCHIVELOG mode.
Note: To use the NOARCHIVELOG mode, the database must be in a
consistent state. For more information, refer to Oracle documentation.
Non-Transportable VSS Backup and Restore - Oracle VSS Writers
A non-transportable Oracle VSS Writer session can be restored in the same way
as any other Writer session. For a description of the types of restore available in
the Restore Manager, refer to the section Restore Methods (see page 43).
For a non-transportable Oracle VSS Writer backup, because all of the data is in a
single session, the whole Writer can be selected for restore if the whole Writer
was selected during the backup operation.
When you use the Agent for Open Files and select the Oracle VSS Writer for
backup, all of the data is written to a single session on the backup media. To
restore the whole Oracle VSS Writer, select only that one session to restore all
the data. If there is more than one database, all data for the databases is in one
session.
62 Microsoft Volume Shadow Copy Serv ice Guide
Oracle VSS Server Writer
Restore Transportable VSS Backups Using Oracle VSS Writers
To restore a transportable VSS backup of the Oracle VSS Writer
1. On the Source tab of the Restore Manager, choose one of the following:
■
Restore by Tree: Oracle VSS backups are visible in the tree at the
same level as volume and system state backups. Click the icon next to
the appropriate database to select it.
One database, the last database in the multistreaming backup job
appears in the tree.
To see other databases, click Version History. From the Version History
window, select the version that represents the stream of the database
you want to restore and click Se lect. The Restore Manager displays the
new database.
■
Restore by Session: Oracle VSS backups are listed as separate
sessions. Click the icon next to the session's name to restore all of the
Components included in the session. To restore an individual
Component, expand the session and select the Component's name.
Note: Not all Components can be restored individually. The Writer decides
whether a Component can be restored individually.
2. On the Destination tab of the Restore Manager, choose the destination to
which to restore. Choose one of the following:
■
Restore files to their original location
■
Restore to user-shared directories and drives (alternate location)
By default, files are restored to their original location. If you choose to
restore files to an alternate location, a list of computers, directories, and files
appears, from which you can select a specific destination. For more
information about restore locations, refer to the section Restore Locations
(see page 42).
3. From the Schedule tab of the Restore Manager, choose the appropriate
options to schedule your job.
Appendix A: Application-Specific Guidelines 63
Miscellaneous Supported W riters
4. Click Submit on the Restore Manager to begin the restore operation.
A Security dialog opens.
Important! Ensure that all databases are off line or detached before the
restore job starts.
5. In the Security dialog, enter the authentication information for the
production server and click OK.
The Submit Job dialog appears.
6. In the Submit Job dialog, select Run Now or select Run On and specify a
specific date and time.
7. Click OK.
The restore job is added to the job queue.
8. Use the Job Status Manager to monitor the progress of the restore job.
Miscellaneous Supported Writers
In addition to the writers described in this appendix, CA ARCserve Backup lets
you protect data using the following writers:
■
WMI Writer
■
Windows Internet Name Service (WINS) Writer
■
Network Policy Server (NPS) VSS Writer
■
Active Directory Application Mode (ADAM) Writer
■
Dynamic Host Configuration Protocol (DHCP) Writer
■
Background Intelligent Transfer Service (BITS) Writer
64 Microsoft Volume Shadow Copy Serv ice Guide
Index
A
Amount of Data to Back Up • 47, 48
Application-Specific Guidelines • 39, 41, 42, 44,
51
B
Backup Options • 23
Best Practices • 47
C
CA Product References • iii
Components • 12, 14
Contact CA • v
Copy-on-Write Method • 16
Create Transportable VSS Backups • 30
D
Develop Your Backup Strategy • 47
F
File System Backup Options • 29
File System Backups • 33
Files Not Supported by Writers • 47, 48
Full Copy Method • 18
I
Installation of the Client and Option • 22
Installing the Client and the Option • 21
Introducing VSS Support • 9
Introduction • 9
M
Microsoft Exchange Writer • 51
Microsoft Hyper-V VSS Writer • 55
Miscellaneous Supported Writers • 64
MSDE Writer • 56
N
Non-Transportable VSS Backup and
Microsoft Exchange Writers • 52
Non-Transportable VSS Backup and
MSDE Writers • 57
Non-Transportable VSS Backup and
Oracle VSS Writers • 62
Non-Transportable VSS Backup and
SQL Server Writers • 59
Restore Restore Restore Restore -
O
Oracle VSS Server Writer • 61
G
P
General Guidelines • 52, 56
General Guidelines Oracle 11g • 62
General Guidelines SQL 2005 • 59
Perform File System Backups • 36
Perform Writer Backups • 37
Performing Backups • 23
Performing Restores • 41
Prepare for VSS Shadow Copies • 22
Prerequisites • 21
Providers • 12, 14
H
How Backup Jobs are Submitted • 33
How CA ARCserve Backup Achieves VSS
Support • 10
How the Agent Works • 16
How the Enterprise Option for VSS Hardware
Snap-Shot Works • 18
How the VSS Backup Works • 34
How to Back Up Data Using the Option • 35
How to Install the Client and the Option • 21
How Transportable Shadow Copies are Created
• 19
How VSS Support Works • 11, 12
R
Requestors • 12
Restoration of File Systems • 42
Restoration of Writers Backup • 42
Restore Locations • 42, 45, 54, 58, 61, 63
Restore Methods • 42, 43, 45, 52, 53, 57, 59,
60, 62
Restore Transportable VSS Backups Using
Microsoft Exchange Writers • 53
Index 65
Restore Transportable VSS Backups Using MSDE
Writers • 58
Restore Transportable VSS Backups Using
Oracle VSS Writers • 63
Restore Transportable VSS Backups Using SQL
Server Writers • 60
Restore VSS Writer Backups • 44
S
Set Global Options • 24, 25, 27, 36
Set Restore Options • 44
Set Writer Options • 24, 27, 29
Shadow Copy Creation Methods • 15
SQL Server Writer • 59
System Requirements • 22
T
Transportable VSS Backup and Restore Microsoft Exchange Writers • 53
Transportable VSS Backup and Restore - MSDE
Writers • 57
Transportable VSS Backup and Restore - SQL
Server Writers • 60
V
VSS and the Backup Manager • 39
VSS and the Restore Manager • 41
W
Windows System State Writer Components • 55
Writer Backups • 39
Writer Exclusion During Backups • 40
Writer Options Dialog • 25
Writers • 12, 13
Writers and Components • 13
Writers and Components Options • 29
66 Microsoft Volume Shadow Copy Serv ice Guide