Snapshot Agents User Guide

8/10/2019 Snapshot Agents User Guide

1/84

FalconStor

Snapshot AgentsUSER GUIDE


2/84

FalconStorSnapshot Agents User Guide

FalconStor Software, Inc.2 Huntington Quadrangle, Suite 2S01Melville, NY 11747Phone: 631-777-5188Fax: 631-501-7633Web site: www.falconstor.com

Copyright 2001-2013 FalconStor Software. All Rights Reserved.

FalconStor Software, IPStor, TimeView, and TimeMark are either registered trademarks or trademarks of FalconStor Software,

Inc. in the United States and other countries.

Linux is a registered trademark of Linus Torvalds.

Windows is a registered trademark of Microsoft Corporation.

All other brand and product names are trademarks or registered trademarks of their respective owners.

FalconStor Software reserves the right to make changes in the information contained in this publication without prior notice. The

reader should in all cases consult FalconStor Software to determine whether any such changes have been made.

This product is protected by United States Patents Nos. 7,093,127 B2; 6,715,098; 7,058,788 B2; 7,330,960 B2; 7,165,145 B2;

7,155,585 B2; 7.231,502 B2; 7,469,337; 7,467,259; 7,418,416 B2; 7,406,575 B2, and additional patents pending.

122313

User Guide content for individual agents may change between major product versions of FalconStor CDP/NSS

in order to reflect agent updates released via patches. In this guide and its table of contents, the heading for

changed content will be followed by (updated Month Year).

The document code at the bottom of the page shows the guide publication date.


3/84

Snapshot Agents User Guide i

Snapshot Agents User Guide

Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

General installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Additional resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Snapshot Agent for Microsoft VSS. . . . . . . . . . . . . . . . . . . . . . . . 4

Storage configuration guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4Install the snapshot agent (updated November 2013) . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Silent install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Configure the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Snapshot options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Advanced options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Batch file options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Manage the Trace Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Snapshot process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Writers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

History and event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Remove snapshot agent software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Snapshot Agent for Microsoft Exchange . . . . . . . . . . . . . . . . . 12

Storage configuration guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Install the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Silent install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Configure snapshot agent options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Batch file options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Monitor tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Manage the Trace Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Configure service-enabled devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Test the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Confirm snapshot status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Purge log utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Remove snapshot agent software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Snapshot Agent for Microsoft SQL Server . . . . . . . . . . . . . . . 20

Install the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Silent install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Configure the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Database Security options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Database Options tab (updated October 2013) . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Advanced Options tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Batch Files tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Monitor tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Manage the Trace Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29


4/84

Snapshot Agents User Guide ii

.hisu file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Test the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Transaction Log Backup best practice (updated October 2013) . . . . . . . . . . . . . . . . . . .31Recover a database manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Diagnostic X-ray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Remove snapshot agent software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Snapshot Agent for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Support for file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Install the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Install on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Silent install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Install on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Install on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Install on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Install on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Configure the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Configure the snapshot agent on a Windows machine (updated October 2013) . .41

Database Security options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Batch file options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Monitor options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Manage the Trace Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Configure the snapshot agent on a Solaris machine . . . . . . . . . . . . . . . . . . . . . . . .46Configure ASM disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Configure the Oracle Listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Configure the snapshot agent on a Linux or AIX machine (updated October 2013) 48

Configure the snapshot agent on an HP-UX machine . . . . . . . . . . . . . . . . . . . . . . .49(Unix only) Add root user to database groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50(Unix only) Set root users PATH and LD_LIBRARY_PATH . . . . . . . . . . . . . . . . . . . . .51Turn on Oracle archive logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Test the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Remove snapshot agent software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Protect and recover Oracle databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Database design with virtual devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Data backup and protection scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54TimeMark Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55TimeView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56TimeMark rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Complete backup using a TimeView or TimeMark Copy . . . . . . . . . . . . . . . . . . .57

Recovery scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Disk failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57User failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Operator failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Restore backed-up Oracle databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Automatic recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59


5/84

Snapshot Agents User Guide ii i

Manual recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Snapshot Agent for FileSystems . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Install the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Install on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Silent install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Install on Linux and AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Configure snapshot agent options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Batch file options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Monitor tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Manage the Trace Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Update registry for service-enabled devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Test the file system agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Remove snapshot agent software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Snapshot Agent for MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Install the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Silent install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Configure the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Confirm snapshot status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Remove snapshot agent software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Snapshot Agent for IBM DB2 Universal Database . . . . . . . . . 68

Install the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Install on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68Silent install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69Install on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Add root user to database groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70Set root users PATH and LD_LIBRARY_PATH . . . . . . . . . . . . . . . . . . . . . . . . .71

Install on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71Test the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Remove snapshot agent software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Snapshot Agent for Lotus Notes/Domino . . . . . . . . . . . . . . . . 73

Install the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Install on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73Silent install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Install on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Test the snapshot agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Confirm snapshot status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Remove snapshot agent software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77


6/84

Snapshot Agents User Guide 1

Introduction

Todays businesses put increasing demands on information and databases,resulting in the need for 24x7 availability and high performance. However, ever-growing capacity presents significant challenges to meeting these requirements.

One of the most important issues identified by system administrators is the amountof time associated with backup - and more important, recovery. Extreme downtime,sometimes in the range of hours or days, is often experienced while recoveringcorrupted or lost data.

Because it takes a significant amount of time to copy large amounts of data to tape(or other media), the source data can change before the copying is complete.Therefore, the data written to tape represents changes over a period of time anddoes not have point-in-time referential integrity. This means that there is noguarantee that the data written to tape can be meaningfully restored.

This is where FalconStor snapshot agents come in. Snapshot agents installed on

host machines coordinate the snapshot process for databases and messagingapplications, safely and reliably taking snapshots of data for point-in-time copypurposes, third-party backup applications, and disaster recovery planning. Snapshotagents ensure that the resulting copy of data not only has point-in-time consistency,but also transactional integrity.

Snapshot agents work seamlessly with options for replication, snapshot copy,HyperTrac, and ZeroImpact Backup Enabler, all of which are based on the built-insnapshot engine.

Using the Replicationoption in conjunction with snapshot agents maintainsreplicated data for off-host processing. Not only can backups be performed on thereplica, but data can be changed for testing, what if analyses, or training purposes.

Systems can be resynchronized quickly and easily with no impact to the productionserver.

Snapshot agents help simplify many data management tasks, meeting therequirements of high availability and high performance in todays workplace. Thefollowing agents are available:

Snapshot Agent for Microsoft VSS

Snapshot Agent for Microsoft Exchange

Snapshot Agent for Microsoft SQL Server

Snapshot Agent for Oracle

Snapshot Agent for FileSystems

Snapshot Agent for MySQL Snapshot Agent for IBM DB2 Universal Database

Snapshot Agent for Lotus Notes/Domino

FalconStorContinuous Data Protector (CDP) and Network Storage Server (NSS)support use of snapshot agents on most major platforms. For specific supportinformation, refer to the Certification Matrix on the FalconStor website.


7/84

Introduction


Each agents configuration utility includes a menu that you can display by clickingthe icon in the upper left corner of the utility window. General options include thefollowing:

X-ray All Microsoft Windows-based snapshot agents include an X-ray feature that allows

you to collect technical information - such as storage server messages and asnapshot of the servers current configuration and environment - from your storageservers for diagnostic purposes. The X-ray function generates a .cab file that youcan send to FalconStor Technical Support for analysis.

Log files Log file content varies with each snapshot agent. Refer to individual agentdescriptions for details.

General installation requirements

The items below apply to installation of any snapshot agent as part of an in-band

solution. Silent install is supported for all agents. Additional requirements andInstallation details are included in agent-specific sections of this guide.

On the client machine, you must be an administrator or have administratorprivileges in order to install the snapshot agent.

You can install a snapshot agent on any client machine that has the ability toconnect to your storage server. Install and configure an iSCSI initiator or

Fibre Channel HBA on the client machine. Launch the iSCSI initiator andidentify the storage server as the target server.

On the storage server, make sure the client machine has been added as a

SAN Client.

On the storage server, create SAN Resources(logically mapped storagedevices on the storage network) for each clients database/messagingsystem files, and assign them to the related SAN Client.

Before you do this, assess the requirements of each database or messagingsystem in order to determine how many resources are required. Forinstance, databases typically require data files to be on a separate disk fromlog files; in this case, two resources are required.

Create a Snapshot Resourceon each SAN Resource. Continuing on the storage server, create a Group(under the Logical

Resourcesobject in the management console) for each client machinesSAN Resources. This is sometimes referred to as a snapshot group.

Doing this ensures transactional integrity for database and messaging filesthat reside on multiple disks. Whenever a snapshot is triggered, a snapshotis taken for each resource in the group.

Note: In this guide, storage serverrefers to the FalconStor Storage Server;associated storage is managed by FalconStor CDP/NSS, using the FalconStorManagement Console. Refer to the CDP/NSS User Guidefor details about SANClients, SAN Resources, Snapshot Resources, and Groups.


8/84

Introduction


Migrate the database/messaging system files you want to protect to the newresources.

Before you install the snapshot agent, install the FalconStorIntelligentManagement Agent (IMA). IMA enables the client machine to access storageserver resources and manages notifications from the storage server.

If IMA is not detected when snapshot agent installation begins, an errormessage will be displayed. You will need to cancel the procedure, installIMA, and then repeat snapshot agent installation.

The SAN Disk Manager (SDM) user interface is provided on Windowsmachines. The Intelligent Management Agent User Guideincludes detailsfor operating IMA on Windows and Linux clients.

Install and configure the snapshot agent that corresponds to your database/application (such as Microsoft Exchange, SQL, or Oracle).

For in-band solutions, install the Snapshot Agent for FileSystems with allsnapshot agents except the Snapshot Agent for VSS.

For information about snapshot agent installation as part of an out-of-band

solution such as FalconStor DiskSafe, refer to the user guide for thatsolution.

Download software builds, patches, and other documentation related toyour FalconStor product from the FalconStor Customer Support Portal atsupport.falconstor.com(account required). Click the View Builds, Patches,& Documentationlink in the GA Releasesarea to complete a simple searchform and display available downloads.

Additional resources

This guide supports the latest version of each snapshot agent.

Snapshot agents are designed to work with FalconStorContinuous Data Protector(CDP) and FalconStor Network Storage Server (NSS). For more information, refer tothe CDP/NSS User Guide.

Snapshot agents are supported on various platforms. For specific versioninformation, refer to the Certification Matrix on the FalconStor website.

Note that the product release notes and patch descriptions can include informationthat may not appear in the user guide. Be sure to review all available documents.

If you need technical support, create a support ticket on the FalconStor CustomerSupport portal.


9/84


Snapshot Agent for Microsoft

VSS

The FalconStor Snapshot Agent for MicrosoftVolume Shadow Copy Service(VSS) protects VSS-aware application drives with full point-in-time consistency whilestill allowing non-stop access to the data.

Microsoft VSS provides the backup infrastructure for Microsoft Windows operating

systems, using a set of extensible application programming interfaces (APIs) tocreate consistent point-in-time copies of application data (shadow copies) acrossmultiple volumes, regardless of the snapshot technology or application, bycoordinating with business applications, filesystem services, backup applications,fast recovery solutions, and storage hardware.

Microsoft VSS consists of four components:

Requestors - Start the VSS backup or restore operation and managemetadata.

Writers - Prepare applications for backups and restores.

Hardware Providers - Create the snapshot shadow copies by

communicating with hardware. VSS Service - Windows service that controls VSS operations by

coordinating the other components.

The FalconStor Snapshot Agent for VSS takes consistent point-in-time snapshots ofVSS-aware application data and communicates with FalconStorContinuous DataProtector (CDP) and FalconStorNetwork Storage Server (NSS) using its ownrequestor and hardware provider. The hardware provider creates snapshot volumesand is compatible with any third-party VSS requestor.

In order to use the VSS snapshot agent inside a VMware virtual machine, you musteither assign the data LUN directly to the virtual machine from NSS, or protect local

data storage using with FalconStor

DiskSafe.

Storage configuration guidelines

Microsoft VSS requires that devices are formatted in NTFS.

Microsoft VSS limits the number of volumes in a group to 64.

All devices in a snapshot group must be assigned to the client.

In the FalconStor Management Console, the TimeMarkoption must beenabled on both primary and replica disks.

When Continuous Replicationis enabled on a device assigned to theclient, the Create Primary TimeMark and Synchronize Replica TimeMark

options must be selected in order to ensure synchronous VSS TimeMarkson both the primary and replica resources. This is necessary because VSSTimeMarks contain additional VSS TimeView data that will not be replicatedunless these options are selected.

Dynamic disks are not supported.


10/84



Install the snapshot agent (updated November 2013)

Complete required steps described in General installation requirements.

Installation requires the following:

The client machine must support Microsoft VSS.

The storage array used by the client must be compliant with the SCSIcommands required by Microsoft VSS, such as page 0x80 and 0x83 SCSIinquiry commands. Contact your storage array provider to verify.

To install the snapshot agent:

1. Run the installation file.

2. When prompted, enter your license keycode.

The snapshot agent license must be activated (registered with FalconStor). If

your computer has an Internet connection, the license is activated as soon asyou enter your keycode and click Next. However, if your Internet connection istemporarily unavailable or if your computer has no Internet connection, yourlicense will not be activated. You must activate your license within 30 days.

If your Internet connection is temporarily unavailable, your license will beactivated automatically the next time the snapshot agent is invoked, assumingyou have an Internet connection then. You can also add your license throughIMA.

If your computer has no Internet connection, you can perform offline activationusing IMA (refer to the Intelligent Management Agent User Guide).

3. When done, click Finish.

The snapshot agent will be installed to the same directory as IMA.

After the installation completes, the configuration utility launches automatically.

Silent install

Silent install is supported for snapshot agents. To install the agent in silent mode,complete the following steps:

1. Download the package from the FalconStor Support Portal and extract the agentpackage.

2. From the command line, navigate to the folder to which you extracted thepackage.

3. Install the Intelligent Management Agent:

cd i maset up. exe / scd . .


11/84



4. Install the snapshot agent:

set up / s

or

set upsi l ent . bat

When installing the snapshot agent in silent mode on any 64-bit platform, runset upsi l ent . bat from the AMD64 directory.


12/84



Configure the snapshot agent

After the installation completes, a configuration utility launches.

Complete configuration as described below. When you are done, click OKto save

the changes you made in all tabs and either keep the utility open or exit. ClickCancel to exit the utility and discard any changes.

To access this utility at a later time, select Start-->All Programs--> FalconStor -->Configuration forSnapshot Agent for VSS, which runs vsscfg.exe.

Snapshot options

Perform a fullbackup

The Snapshottab allows you to configure or disable full and copy backups. Eachwriter decides how to handle a copy backup, but tlog files are not usually truncated.

Always (the default)- Always perform a full backup.

Between the following times- If a snapshot notification occurs between thetimes you specify, the snapshot will be a full backup.

Every Nth snapshot - Snapshots are counted, with the first snapshotfollowing a full backup designated as 1. When the count reaches thenumber you specify, that snapshot will be a full backup. For example, if youset the value to 5, every fifth snapshot will be a full backup.

Note that if you revise this value to a lower number and the count is currently

higher, the next backup will be a full backup, after which the count will restart. Never- Always perform a copy backup.

Run databaseor application

verification

You can specify when the Snapshot View should be verified during the snapshotprocess. Currently, verification is compatible only with Microsoft Exchange, andchecks to see if Exchange is involved after snapshot creation is finished. You candisable this option if the process takes too much time. For Exchange snapshots, thesnapshot agent will verify the checksum of the database and log files on theSnapshot View, similar to IntegrityTrac.


13/84


14/84



Batch file options

On the Batch Filestab, indicate if you want to run batch files before and/or aftereach snapshot.

In order to run batch files, you must enter an administrative user name andpassword for the local computer.

Click the Create/Editbutton and use Notepad to generate batch files.

Manage the Trace Log

The Trace Log is a diagnostic tool used by Technical Support to help solve systemproblems. Each Trace Log contains technical information about your system as wellas system messages and is updated whenever a snapshot occurs. Some of themessages that appear in the Trace Log are also sent to the Windows Event Log.

Do not adjust Trace Log settings unless you are requested to do so by a TechnicalSupport representative. The configuration utility lets you maximize the level of detailthat is displayed.

1. Click the icon in the upper left corner of the configuration utility and selectSettingsin the menu.


15/84



2. Select Set Agent Trace Onto maximize the level of detail displayed for agentactivity in the Trace Log.

The value in the text box will change to 10and is not editable. Increasing thelevel of detail will display a list of the databases that have been backed up, plus,at higher levels, information that can be used to provide support. The log will

reflect the change after the next snapshot is taken.

Other options in this dialog are not supported.

Snapshot process

The Snapshot Agent for VSS will be triggered automatically whenever a snapshotoperation occurs on an CDP/NSS-managed disk.

You can test the snapshot agent by manually initiating a snapshot of a virtual drivefrom the FalconStor Management Console. Click the TimeMarktab to verify that aVSS snapshot has been created. You should see Yes with VSSin the Quiescentcolumn.

After the VSS snapshot agent creates a snapshot of application data, the snapshotis mounted as a temporary device and assigned to the host. (A snapshot may bereferred to as a TimeMark; a mounted snapshot may be referred to as a SnapshotViewor TimeView.) The snapshot agent requestor clears read-only and hidden flagsand saves writer metadata to each volume. The hardware provider performsadditional cleanup and then tells CDP/NSS to unassign and delete the mountedsnapshot; data from the mounted snapshot is then saved.

When you select a SAN Resource in the FalconStor Management Console,snapshots (referred to as TimeMarksin that console) created using the VSS

snapshot agent show Yes with VSSin the Quiescentcolumn. Values in theTimeViewcolumn can be available(data is present), none (there is no data), or inuse(the mounted snapshot is active).


16/84



WritersThe VSS snapshot agent is designed to make backups uniform across applications.Some writers have distinct behaviors:

MicrosoftExchange

For snapshots of Exchange databases and log files on shadow copy devices, thesnapshot agent can verify the checksum of the database and log files on theSnapshot View, similar to the way this occurs for FalconStorIntegrityTrac.Snapshot verification may take a long time to complete and can be disabled in thesnapshot agent configuration tool (refer to Configure the snapshot agent).

Refer to the Certification Matrix on the FalconStor website to determine supportedversions of Exchange supported by the Snapshot Agent for VSS.

Microsoft Hyper-V

In order for a virtual machine to take part in the VSS process, Hyper-V integrationtools must be installed; otherwise, the virtual machine is temporarily suspended andsaved to the disk while a snapshot is being created. When Snapshot View devicesare assigned to the host during a full backup, the Hyper-V writer will roll back eachvirtual machine to the same point in time.

History and event logs

Snapshot agent events/history are recorded in the Microsoft Windows Event Log as

Snapshot Agentevents.

If you are using a VSS snapshot agent build higher than 600, the hardware provideralso logs events through the snapshot agent.

Remove snapshot agent software

Remove the snapshot agent usingAdd/Remove Programsfrom the Control Panel.


17/84


Snapshot Agent forMicrosoft

Exchange

The FalconStorSnapshot Agent for Microsoft Exchange enables FalconStor CDP/NSS to protect Exchange databases with point-in-time consistency while allowingfull speed, non-stop access to databases.

Microsoft Exchange requires quiescent snapshots. In order for this to occur, the

Snapshot Notificationoption must be enabled on the Snapshot Resource (refer tothe CDP/NSS User Guide). When a snapshot is triggered and snapshot notificationis enabled, the FalconStor system notifies the application server running thesnapshot agent to stop writing in order for the snapshot to be taken. The snapshot

agent briefly puts the database into backup mode and notifies the FalconStorsystem that the snapshot can be performed. The application server is again notifiedonce the snapshot has completed, and the snapshot agent takes the database outof backup mode.

Using backup software, a backup of the snapshot image can be performed at highspeed while Microsoft Exchange operates in normal mode. While the backupsoftware is reading data from the snapshot image, changes that occur to thedatabase will not affect what gets written. Users are always able to see the databasewith full access at all times while the backup software sees a stable, read-onlysnapshot image of the database taken an instant before the backup began.

The snapshot agent will be triggered automatically whenever a snapshot operationoccurs on the Microsoft Exchange drive.

Storage configuration guidelines

Before you install the snapshot agent, apply Microsoft's best practice for Exchangestorage configuration.

These items should be on the same disk:

Exchange log

System path

These items should be together, on a separate disk: Exchange database

Exchange streaming database

Note: If you are using Microsoft Exchange 2010 or Exchange 2013, you must usethe Snapshot Agent for Microsoft VSS.


18/84



Install the snapshot agent



Install the snapshot agent on the machine where Exchange Server isrunning.

Start the Exchange Server before you install the snapshot agent.

Only one active Exchange Virtual Server per node is supported; a snapshotgroup should not include multiple virtual servers on the same node.




The snapshot agent license must be activated (registered with FalconStor). Ifyour computer has an Internet connection, the license is activated as soon asyou enter your keycode and click Next. However, if your Internet connection istemporarily unavailable or if your computer has no Internet connection, yourlicense will not be activated. You must activate your license within 30 days sothat you can continue to use the snapshot agent.

If your Internet connection is temporarily unavailable, your license will be activatedautomatically the next time the snapshot agent is invoked, assuming you have anInternet connection then. You can also add your license through IMA.




Silent install







19/84




set up / s

or



Configure snapshot agent opt ions

Configuration is not required. The snapshot agent includes a utility that lets youconfigure optional features.

To run the utility, select Start-->All Programs--> FalconStor --> Configuration forSnapshot Agent for Microsoft Exchange.

When you are done, click OKto save the changes you made in all tabs and eitherkeep the utility open or exit. Click Cancel to exit the utility and discard any changes.

Batch file options


In order to run batch files, you must enter an administrative user name and

password for the local computer.

You can then click the Create/Editbuttons and use Notepad to generate the batchfiles.


20/84



Monitor tab

By default, the snapshot agent looks for databases based on information passedfrom IMA. This tab allows you to identify the drives on which databases are located.



Do not adjust Trace Log settings unless you are requested to do so by a TechnicalSupport representative. The configuration utility lets you maximize the level of detail

that is displayed.

1. Click the icon in the upper left corner of the configuration utility and selectSettingsin the menu.


The value in the text box will change to 10and is not editable. Increasing thelevel of detail will display a list of the databases that have been backed up, aswell as information that can be used to provide support. The log will reflect thechange after the next snapshot is taken.



21/84



Configure service-enabled devices

If you are using a service-enabled device (SED) and you have preserved thephysical devices inquiry string (this is set when you create the SED in theFalconStor Management Console), you need to modify the ExAgent.inifile that is

created under the directory when the snapshot agent is installed. In the ExAgent.inifile, you must use the DriveOverrideoption to specify the drive letter(s) to which theSED is mounted. For example: Dr i veOver r i de=E: ; orDr i veOver r i de=E: ; F: ;

Also, if you want to send snapshot results to a third-party management system, youwill have to use the Exchange configuration utility to enter the User Name andPasswordof a member of the local administrators group. This user account does notneed permission from the Exchange Administrator; it is only used to run the pre-script (exchpre.bat) and post-script (exchpost.bat) that are saved in the IMAinstallation folder. You do not need to run these scripts unless you want to sendsnapshot results to a third-party management system.

Test the snapshot agent

To test the snapshot agent, you can perform a Snapshot Copy of a virtual drive fromthe FalconStor Management Console.

Confirm snapshot status

To confirm the Exchange snapshot process, you can check the Windows Event log.The snapshot agent will send the backup command to each storage group on theprotected disk. You can find these logs after the appctrlevent:

1. The snapshot agent sends the full backup command to the storage group andthen Exchange Extensible Storage Engine (ESE) starts the full backup process.

2. Exchange ESE checks the log files and the checkpoint.

3. Exchange ESE processes the log files. The snapshot agent will not request totruncate the log to affect other Exchange backup processes.


22/84



4. Exchange ESE completes the backup process on a storage group. You may seethe same process on another storage group.


23/84



Purge log util ity

If you are using the Snapshot Agent for MS Exchange to protect your Exchangeenvironment but do not have third-party backup software to help purge theExchange log files, you can use the ISPurgeExLog utility to clean up Exchange log

files.

Before you run the utility, check the Windows Application Event Log to make surethe latest snapshot was taken successfully. You can also dump the MS ExchangeCheckpoint file using ESEUTI L. exeand check the timestamp of FullBackup Timeto view the record of the last snapshot date and time.

The Microsoft Exchange log file is generated based on each Exchange StorageGroup; run the utility on each group. In addition, you can schedule a batch job withthe following command inside the batch file:

For Microsoft Exchange 2003:

I SPur geExLog "F: \ Exchsr vr \ System\ E00. chk" "F: \ Exchsr vr \ l og" v

For Microsoft Exchange 2007:

I SPur geExLog64 "F: \ Exchsr vr\ System\ E00. chk" "F: \ Exchsr vr\ l og" v

You must specify the location of the checkpoint file and log directory.

Syntax: I SPurgeExLog "" "" [ Opt i ons] ]

Option Description

- b#hour The number of hour(s) before the recordedcheckpoint time, maximum 96 hours. For example, -b04, -b16, default is -b24.

- c Use the last checkpoint log file date/time if it is earlierthan the last full backup date/time

- hHour From 00 to 23. For example, -h04, -h16. Executepurge only when run within a specific hour (hh:00-hh:59)

- i Ignore the last full backup timestamp on CCRpassive node. Works with - coption.

- p Preview the purge list without actually deleting thelog(s).

- r " r epor t Fi l eName Additional report file is generated.

-s"St or ageGr oupName"

Storage Group Name in Report File.

- v verbose mode.


24/84



It is recommended that you run the purge utility once a day, maintaining 24 hours oflog files after each log purge. After the purge, you can examine the log file directoryand make sure older log files are deleted. There is also an ISPurge.log file createdcontaining the history of each ISPurgeExLog execution.




25/84

20


The Snapshot Agent for Microsoft SQL Server protects Microsoft SQL Serverdatabases on protected disks with point-in-time consistency while still allowing fullspeed, non-stop access to the databases. Users always have full access to thedatabase, while backup software sees a stable, read-only snapshot image of thedatabase taken an instant before backup began.

Before the snapshot process begins, a request is sent to the server running theSnapshot Agent for Microsoft SQL Server to quiesce databases or applications. Bydefault, the snapshot agent performs a full backup of all databases. The configurationutility allows you to choose different backup options for different SQL instances, andlets you exclude less critical databases from snapshots.

Backup software can back up the snapshot image at high speed while MicrosoftSQL Server operates in normal mode. Because the contents of the snapshot image

are guaranteed never to change, the backup is consistent, ensuring transactionalintegrity. When backup software reads data from the snapshot image, changes thatoccur in the database do not affect what gets written.

The snapshot agent will be triggered automatically whenever a snapshot operationoccurs on the Microsoft SQL Server drive.

The snapshot agent includes a utility that allows you to recover a single database,as well as a command line interface.

The Snapshot Agent for Microsoft SQL Server is supported for various WindowsServer platforms. For specific version information, refer to the Certification Matrix onthe FalconStor website.




You need to know the database instance name.

You need to know the database administrator password if the default policyis Windows authenticationand the current Windows login account does nothave enough access rights.

Start SQL Server before you install the snapshot agent. Install the snapshot agent on the machine on which the SQL Server

database is running.


26/84


21

The following items are required for VMware environments

If the virtual machine is not protected by DiskSafe, you must installFalconStorSnapshot Director for VMwarevSphere on the virtual host thatyou want to protect.

You must configure IMA to specify override drives.These are the drives onthe virtual host that you want to protect using IMA. If you do not do this,applications may not be quiesced correctly.

Override drives should include any other drives that contain databases orother application data that should be quiesced before snapshots are taken.

To manage override drive settings, execute the following commands in thecommand line on the virtual host:

To specify override drives:

i scmcl i set over r i dedr i ve - d ""

where is a list of drive letters separated by semi-colons.

For example:

i scmcl i set over r i dedr i ve - d "C: ; E: ; F: ; " To view the list of current override drives:

i scmcl i get over r i dedr i ve

If no override drives have been set, the command returns no output.

To delete current override drive settings:

i scmcl i del over r i dedr i ve




You must activate the snapshot license (register it with FalconStor). If yourcomputer has an Internet connection, this will occur automatically after you enteryour keycode and click Next. However, if your Internet connection is temporarilyunavailable or if your computer has no Internet connection, automatic activationis not possible. You must activate your license within 30 days so that you cancontinue to use the snapshot agent.

If your Internet connection is temporarily unavailable, automatic activation willoccur the next time the snapshot agent is invoked, assuming you have anInternet connection then. You can also add your license through IMA.

If your computer has no Internet connection, you can perform offline activation

using IMA.

3. When installation is complete, click Finish.


After the installation completes, the configuration utility launches automatically.


27/84


22

Silent install







set up / s

or




28/84


23


Complete configuration as described below. When you are done, click OKto savethe changes you made in all tabs and either keep the utility open or exit. Click

Cancel to exit the utility and discard any changes.

To run the utility at a later time, select Start-->All Programs--> FalconStor -->Configuration forSnapshot Agent for Microsoft SQLServer.

Database Security options

The snapshot agent supports multiple instances of Microsoft SQL on the sameserver. In order for the snapshot agent to communicate with an instance, you haveto register the instance with the snapshot agent from this utility tab.

The Database Securitytab displays the databases whose snapshots will bemanaged by the snapshot agents.


29/84


24

1. ClickAdd to add a SQL instance. The Database Loginscreen displays.

2. Select the virtual server or host on which the instance is located. If the SQLserver is in a cluster, select the name of the virtual server on which the SQLinstance was created. If the server is not in a cluster, select the local host name.The drop-down list displays the virtual server name and the host name detectedin the registry.

3. In the Instancefield, MSSQLSERVER will be displayed if the server uses thedefault instance. If the SQL instance is not displayed, enter it here or select it inthe drop-down list.

You can use the Servicesconsole (Control Panel-->Administrative Tools-->Services) to check instance names. In this console, the instance name will be

listed in parentheses. For example, if the service name is shown as SQL Server(MSSQLSERVER), its instance name is MSSQLSERVER. If you have anotherinstance, another service, such as SQL Server (INSTANCE1), will be listed. In thisexample, the SQL instance name is INSTANCE1.

4. Provide connection credentials:

For Windows Authentication mode, user name and password are not required.Select the Trusted Connection - Windows Authenticationcheckbox to avoidstoring credentials in connection strings.

OR, for SQL Serverauthentication mode, enter the database user name andpassword of an account that has access to the database.

5. When you are done, click Verifyto allow the snapshot agent to attempt toconnect to the instance using the provided credentials.

If connection is successful, the Verifybutton changes to OK.

After you have added a SQL instance, you can change its information or remove it.To do this, select a SQL instance in the list and then:

Click Editto modify its information in the Database Logindialog.

Click Removeto delete it.


30/84


25

Database Options tab (updated October 2013)

For each database in a selected instance, the Database Optionstab providesinformation and lets you specify a location for the Transaction Log backup directory.

1. Select an instance from the drop-down list.

The Database countand Totalvalues are displayed.

2. Select a database from the drop-down list.

The Database directory,Transaction log directory, and storage server ID aredisplayed automatically.

If the database is not on a direct CDP/NSS device, Not on Storage ServerDevicewill be displayed in the Storage Serverfield.

3. The utility is designed to let you specify a Transaction Log Backup directory forall databases in the selected instance, or for individual databases. It isrecommended that you store transaction log backups separately from thetransaction log and the database.

In addition, it is recommended that if you have two database instances, choose adifferent backup directory for each.

Note: If the disk on which a database resides is not protected, snapshots will notbe taken.

Note: Ensure there is enough disk space for transaction log backups, basedon the amount of data changes to record.


31/84


26

Click the Browsebutton next to the Transaction Log Backup directory field andselect a backup directory location. Manually entering a directory location is notrecommended.

To specify this directory as the Transaction Log Backup directory for alldatabases, respond Yesto the Change entry for all databases in thisinstance? message.

To specify this directory as the Transaction Log Backup directory only for theselected database, respond Noto the change entry message.

If you do not see the change entry message, the directory selection willapply only to the selected database.

Additional options for transaction log backup are available (refer to Transaction LogBackup best practice).

Advanced Options tab

TheAdvanced Optionstab allows you to choose a backup option for all databases inthe selected instance and lets you exclude individual databases from that option.

Note: Make sure that you have selected a database before you do this; this isnecessary in order for the selected location to be saved.

Note: If you click in the Transaction log backupfield but do not make a

selection, the message Change entry for all databases in this instance? maybe displayed when you continue with another action. Click Noto close themessage box.

Note: Snapshots are taken only if the disk on which a database resides isprotected.


32/84


27

To do this:

1. Select one backup option. Full backupis selected by default:

Full backup of all databases- The snapshot agent performs a full SQL Serversnapshot backup of selected databases, regardless of their recovery model.

Full backup, but checkpoint only on databases when recovery model set toSimple - The snapshot agent performs a full backup on selected databasesexcept for those whose recovery model is set to Simple; for those, a checkpointis performed.

Do checkpoint only on all databases- If the instance includes a large number ofdatabases, choose this option to save time. Do not exclude any databases.

Copy-only, full backup of all databases- The snapshot agent performs a fullbackup of selected databases but does not notify SQL that backup has occurred.

2. Select Perform a transaction log backup for every snapshotto enable this

option. This option is disabled if you choose the checkpoint only or copy onlyoption.

3. The Database Selectionarea lists all databases discovered in the selectedinstance. You can exclude specific databases from the selected backupoperation.

To do this, select a SQL instance from the drop-down list, which includes onlythose instances that have been registered with the snapshot agent using thisutility.

All databases in the instance are selected by default. Uncheck any database(s)that the snapshot agent should excludefrom the selected backup operation.

If the full backup or copy-only option is selected, the snapshot agent willperform a checkpoint flush on the excluded databases for overall snapshotconsistency.

If checkpoint only is selected, excluded databases will be ignored.

Use the Select All/Deselect All checkbox to select or deselect all databases atthe same time.

Notes for the copy-only opt ion:

Applies only to databases configured for Fullrecovery.

Copy-only snapshots can be taken several times a day, providingmore frequent data protection points.

Does not interfere with third-party backup software operations.

You can perform Rollback recovery using a TimeMark or file copyrecovery from a TimeView.

You cannotchoose a point-in-time recovery option betweenTimeMarks.


33/84


28

If you create additional databases after completing initial agent configuration andwant to exclude any of them from the selected backup option, run theconfiguration utility again and deselect them here.

Batch Files tab

Use this tab to indicate if you want to run batch files before and/or after eachsnapshot, and allows you to create a pre- or post-batch file in Notepad.

1. Select the checkbox if you want to run batch files before and/or after the

snapshot agent.

2. Enter an administrative user name and password for the local computer.

3. Click the appropriate Create/Editbutton to open Notepad and create/save thebatch file.


34/84


29

Monitor tab

By default, the snapshot agent looks for databases based on information passedfrom IMA. If the default drives (as seen in the Database Optionstab) are incorrect orif no drives are listed, this tab allows you to identify the drives on which databases

are located.

1. Select the option if you want the snapshot agent to look for databases elsewherethan in the default drive(s).

For example, if a database is located on a SAN disk that is mounted to an NTFS

folder such as E:\database, you need to identify that drive here.

2. Type the drives on which your databases are located; separate multiple drivenames with a semicolon (for example D:;E:;F:).




1. Launch the configuration utility.

2. Click the icon in the upper left corner of the configuration utility and select

Settingsin the menu.


35/84


30

3. The Settingsdialog lets you specify the level of detail to be displayed.

Click the checkbox for Specify Trace Log level.The value in the text box sets thelevel of detail to be displayed. 0is the default. Increasing the detail value willdisplay a list of the databases that have been backed up, plus, at higher levels(maximum 10), information that can be used to provide support. If you changethis value, the log will adjust to the change after the next snapshot.

.hisu file

The.hisu file contains a list of all files since the time the applicationstarted and resides in the transaction log directory. An example is shown below:

db1. mdf ; 20120703144715; 0; 1db1- 20120705102206. l ogdb1- 20120705102208. l ogdb1- 20120705102210. l ogdb1. mdf ; 20120705102213; 0; 1

This sample log file indicates that a full backup was done, followed by threeTransaction Log backups, and then another full backup.

* Transaction log backup, then full database backup if option to Perform a transaction log backup for every snapshot

option is checked.


36/84


31

Test the snapshot agent

To test the snapshot agent, perform a Snapshot Copy of a virtual drive from theFalconStor Management Console for CDP/NSS.

Transaction Log Backup best practice(updated October 2013)

Transaction log backups make it possible to perform a point-in-time restore. Whenyou install FalconStor Database Recovery for Microsoft SQL Server, you canconfigure a transaction log backup to occur immediately before a full backup (referto the Database Recovery for Microsoft SQL Server section in the Recovery AgentsUser Guide).

Best practice recommendations include:

1. Put the transaction log backup command in a batch file called . bat .

For example:

f sssr est . exe - t l b - d "*" - i "ESX40W2K8DEVHAR"

2. Schedule the snapshot agent to perform a normal full backup during a SQLserver non-peak period.

3. Use the Windows Task Scheduler to run your transaction log backup morefrequently but make sure the two processes do not execute at the same time.

For example:

If the snapshot agent is scheduled to perform a full backup at 2am every day,use the Microsoft Task Scheduler to run the . bat file everyhour on the half hour.

4. Make sure the directory to which transaction log backups are saved has enoughdisk space, based on the amount of data changes.

Note: Transaction Log Backup can occur only after the first full backup hasoccurred.


37/84


32

Recover a database manually

The snapshot agent includes a recovery utility that can either perform a Rollbackrestore to the latest TimeMark snapshot or complete the recovery process after yourecover the data from a TimeView using the FalconStor Management Console.

To do this:

1. Launch the recovery utility by selecting Start-->All Programs--> FalconStor-->Single Database Recovery for Microsoft SQL Server.

2. The Restoretab lists all databases for which snapshots have been taken.

Select the instance and database to be restored.

At any point, you can click Refreshto update all fields.

3. Click Restore.

4. In the Command Linedialog, click the Runbutton to begin the restore process orcopy and paste the command to a command line.

Note: Use FalconStor Database Recovery for Microsoft SQL Serverif you wantto perform automatic recovery from a point-in-time snapshot image of your SQLdatabase.


38/84


33

5. Follow the instructions displayed at the command prompt.

a. Detach the database you are restoring.

b. Do one of the following:

If you want the utility to complete a TimeView restore, use IMA or theFalconStor Management Console for CDP/NSS to perform a TimeViewrestore from a Time Mark.

Find the database files *.mdf, *.meta, *.ldf (if recovery model is full) onthe TimeView.

Rename or delete the original files.

Copy the files from the TimeView to original location.

If you want the utility to perform a Rollback restore, make sure theselected database is the only database on this device; otherwise, performa TimeView restore. Press Enterto continue with Rollback restore.

c. Press Enter to continue.

When the recovery process is complete, verify that the database has been restored.

Command line interface

The snapshot agent also includes a command line interface (fsssrest.exe).

Usage: f sssr est [ acti on] [ opt i ons]Actions:

- f r o- Perform full restore only.- t l b- Perform Transaction Log backup.- f b- Perform full backup.- cp- Perform checkpoint.- l i s t - List databases in instance.- backupl i st - List databases backed up in instance.

Note: Double-byte database names may display as question marks (????) orspaces. This is OK.


39/84


34

Options:

- t - Speci f y a dest i nat i on pat h andf i l e name f or t he Trace Log.- d- Specify the database name - applies to f b, t l b, andcp.- i - Specify server name and instancename.- di r - Specify the Transaction Log backup directory.- en- Display text in English.

Note that if you do not include the - t option in the command, level 1 detail will besaved to the Trace Log. If you include the - t option, level 10 detail (the maximum)will be saved.

Examples:

Perform transaction log backup for a single database after a storage serversnapshot has been taken:

f sssr est - t l b - d

This command enables you to perform additional transaction log backupsafter a full backup and before the last transaction log backup. The commandrecords the date and time, which makes it easier to identify the transactionlogs that are needed during restore. You can run this command as needed,based on your backup schedule.You can also use other utilities to scheduleadditional transaction log backups between snapshots.

Configure Transaction Log backup for all databases in one instance:

f sssrest. exe - t l b - d * - i"ESX40W2K8DEVHAR\ SQLI NSTANCE1"

Configure Transaction Log backup for all databases in all instances on theserver:

f sssr est . exe - t l b - d * - i "ESX40W2K8DEVHAR"

Configure Transaction Log backup for all databases in one instance andgenerate the Trace Log:

f sssrest. exe - t l b - d * - i"ESX40W2K8DEVHAR\ SQLI NSTANCE1" - t

Configure Transaction Log backup for all databases in one instance;generate the Trace Log and save it to drive C: as test.log:

f sssrest. exe - t l b - d * - i

"ESX40W2K8DEVHAR\ SQLI NSTANCE1" - t C: \ t est . l og

Transaction Log backups are recorded in history files for use by the SQL Recoverytool. Transaction Log backups can be used by any Microsoft SQL recovery utility.

Note: If you use another utility to perform transaction log backups, you will need tomanually enter the transaction records into FalconStor Database Recovery forMicrosoft SQL Recovery.


40/84


35

Diagnostic X-ray

An X-ray feature allows you to collect technical information - such as storage servermessages and a snapshot of the servers current configuration and environment -for diagnostic purposes. To capture an X-ray, launch the agents configuration utility

and select Take X-ray in the utility menu. The X-ray function generates a .cab filethat you can send to FalconStor Technical Support for analysis.




41/84



The FalconStorSnapshot Agent for Oracle enables FalconStor CDP/NSS toprotect Oracle databases with point-in-time consistency while still allowing fullspeed, non-stop access to the databases.

Prior to starting the snapshot process, a request is sent to the application server

running the Snapshot Agent for Oracle. The snapshot agent places the Oracledatabase in "backup" mode and notifies the server that the snapshot can beperformed. While in backup mode, the database is frozen and Oracle sends allnew incoming data to the Oracle online redo logs. Once the snapshot hascompleted, the server notifies the application server and the snapshot agent placesthe database back into normal mode, synchronizing all data back to the database.

Using backup software, a backup of the snapshot image can be performed at highspeed while Oracle operates in normal mode. Because the contents of the snapshotimage are guaranteed never to change, what is backed up is consistent, ensuringtransactional integrity. While the backup software is reading data from the snapshotimage, changes that occur to the database will not affect what gets written. Users

are always able to see the database with full access at all times while the backupsoftware sees a stable, read-only snapshot image of the database taken an instantbefore the backup began.

The snapshot agent will be triggered automatically whenever a snapshot operationoccurs on the Oracle drive.

Support for file systems

The Snapshot Agent for Oracle supports the following file systems:

ASM - Automated Storage Management - the disk are raw LUNs. OCFS - Oracle Cluster File System.




You need to know the database instance name and the databaseadministrator password.

Start your Oracle database before you install the snapshot agent. After the snapshot agent is installed, you must turn on Oracle archive

logging before running the snapshot agent (refer to Turn on Oracle archivelogging).


42/84



Install on Windows

1. Run the installation file.The snapshot agent will be installed to the samedirectory as IMA.

2. Select which version(s) of Oracle you are using.You must have a separate license for each.


The snapshot agent license must be activated (registered with FalconStor). Ifyour computer has an Internet connection, the license is activated as soon asyou enter your keycode and click Next. However, if your Internet connection istemporarily unavailable or if your computer has no Internet connection, yourlicense will not be activated. You must activate your license within 30 days sothat you can continue to use the snapshot agent.

If your Internet connection is temporarily unavailable, your license will be

activated automatically the next time the snapshot agent is invoked, assumingyou have an Internet connection then. You can also add your license throughIMA.



After installation completes, a configuration utility launches. Refer to Configure thesnapshot agent on a Windows machine.

Silent install Silent install is supported for snapshot agents. To install the agent in silent mode,

complete the following steps:






For Oracle 11

Run setup /sor setupsilent.bat.

For Oracle 10

a.Copy setup10.issto setup.iss.

b.Run setup /s or setupsilent.bat.


43/84



For Oracle 9

a.Copy setup9.issto setup.iss.

b.Run setup /s or setupsilent.bat.

Install on Solaris

You must be root(or rootequivalent) in order to install the snapshot agent.

1. Download the tarfile to the local drive of your Solaris client (/tmp is used in theexample).

2. Install the snapshot agent software.

For example: pkgadd - d / t mp/ or acl e8i 9i 10gagent - 4. 50- 906. pkg

3. Select the Snapshot Agent for Oracle package.

After installation completes, a configuration utility launches. Refer to Configure thesnapshot agent on a Solaris machine.

Install on Linux


1. Download the installation file to the local drive of your Linux client.


Oracle 9i example: r pm - i - - nodeps or acl e9i agent - 4. 50-898. i 386. r pm

Oracle 10g example: r pm - i - - nodeps oracl e10gagent - 4. 50-899. i 386. r pm

3. Enter the Oracle lib directory.

The default is $ORACLE_HOME/lib

After installation completes, a configuration utility launches. Refer to Configure thesnapshot agent on a Linux or AIX machine.

Note: If your Oracle server is running a 64-bit operating system, perform

these steps from the AMD64 directory.

pkgadd -d /tmp/oracle8i9i10gagent--.pkg

rpm -i --nodeps oracleniagent--.i386.rpm


44/84



Install on AIX


1. Download the tarfile to the local drive of your AIX client.

2. Type the following command to untar the agent package:

t ar - xvf oracl eni agent - - . t ar

Oracle 9i example: t ar - xvf or acl e9i agent - 4. 50- 901. t ar

Oracle 10g example: t ar - xvf or acl e10gagent - 4. 50- 901. t ar

3. Install the package:

i nst al l p - aFX - d I PSt or . Or aAgent . bf f al l

After installation completes, a configuration utility launches. Refer to Configure thesnapshot agent on a Linux or AIX machine.

Install on HP-UX


1. Download the tarfile to the local drive of your HP-UX client (/tmpis used in theexample).

2. Type the following command to untar the agent package:

# cd . t mp

# t ar xvf oracl eni agent - - . t arOracle 9i example: t ar xvf or acl e9i agent - 4. 50- 896. t ar

Oracle 10g example: t ar xvf or acl e10gagent - 4. 50- 897. t ar


# swi nst al l - s pwd / package or acl e

4. As the Oracle User, view the .profile or type the envcommand to determine thelibrary path.

Oracle requires several environment variables, one of which is the SHLIB_PATH

(this is the same as the LD_LIBRARY_PATH on other UNIX boxes, such asSolaris).

$ cat ~/ . pr of i l e | gr ep SHLI B_PATH

SHLI B_PATH=$ORACLE_HOME/ l i b: $ORACLE_HOME/ l i b64: / l i b: / usr /l i b: / usr / l ocal / l i b

- or -

$ env | grep SHLI B_PATH


45/84



SHLI B_PATH=/ oracl e8/ Or aHome1/ l i b: / or acl e8/ Or aHome1/ l i b64: /l i b: / usr / l i b: / usr / l ocal / l i b

In these examples, there are two directories: lib and lib64. One or more of thesedirectories contain the library (libclntsh.sl.8.0) needed for the Oracle8i Database

Agent to work correctly.

5. As root user, issue a findcommand to make sure one or more of thesedirectories contain the necessary library path.

# f i nd / or acl e8/ Or aHome1/ l i b - name "l i bcl nt sh. sl . 8. 0" - pr i nt

/ or acl e8/ Or aHome1/ l i b/ l i bcl nt sh. sl . 8. 0

# f i nd / or acl e8/ Or aHome1/ l i b64 - name " l i bcl nt sh. sl . 8. 0" -pr i nt

/ or acl e8/ Or aHome1/ l i b64/ l i bcl nt sh. sl . 8. 0

In this example, the file exists in both Oracle directories. If this occurs on yourmachine, enter both paths when configuring the agent.

After installation completes, a configuration utility launches. Refer to Configure thesnapshot agent on an HP-UX machine.


46/84




Configuration details for each type of installation are provided below.

Additional configuration steps are required for Unix platforms (refer to (Unix only)

Add root user to database groupsand (Unix only) Set root users PATH andLD_LIBRARY_PATH).

Configure the snapshot agent on a Windows machine(updated October 2013)

After the installation completes, a configuration utility launches.

Complete configuration as described below. When you are done, click OKto savethe changes you made in all tabs and either keep the utility open or exit. Click

Cancel to exit the utility and discard any changes.

To access this utility at a later time, select Start --> Programs --> FalconStor -->Configuration for Snapshot Agent for Oracle.

Select Oracleversion

To begin, select the version of Oracle you are using, then click Edit.

The Configuration screen displays.

Note: When you are running a backup software application on the machinewhere the Snapshot Agent for Oracle is installed, you may see conflicts when thedatabase is set in backup or non-backup mode. In this case, you can use flagBACKUPCHECKin configuration file snapagt . i ni to indicate whether thesnapshot agent can set the database mode. The default value is 0, whichindicates the snapshot agent will always set the mode. If you set

BACKUPCHECK=1, the snapshot agent does not set the mode and will let thebackup application set the database mode.


47/84



DatabaseSecurityoptions

The Database Securitytab displays the databases whose snapshots will bemanaged by the snapshot agents.

Add database

To add a database whose snapshots will be managed by the snapshot agent, click

Add Login. The Database Logindialog is displayed.

1. Enter the login credentials for the database you are adding:

Database SID- Enter the Oracle instance name.

User Nameand Password- Enter the user name and password of an Oracleaccount with the DBA role (system, for example). This is the user and passwordthat the storage server needs to access your database. When the Oracledatabase is set up initially, the default system user password is usually manager.Do not use the user name sys.

Note: If you ever need to change the Database SID, User Name,orPassword, click Removeto remove the existing SID and then re-add it.


48/84



2. Verify that the credentials you entered are correct:

Click Verify to allow the agent to verify the SID by attempting to connect to thedatabase with the provided information. If connection is successful, the databasewill be added to the list.

Edit database credentials

Use this function to validate the security credentials for the selected database.

1. Select a database in the list and click Edit. Login credentials are displayed.

2. Click Verifyto allow the agent to attempt to connect to the database with thecurrent information.

Verify binpath

Use this function to enter or verify the Oracle binpath for the selected database.

1. Select a database in the list and click Bin Path.

2. Enter the Oracle binpath, typically %ORACLE_HOME%/bin.

You can either click the button next to the field to have the agent search for thepath or you can manually enter the path. If you click the button and the SID iscorrect, the path will be discovered automatically. If the SID is incorrect, the pathwill not be found. You should then either enter the correct SID or, if the databaseis not running, start the specified database.

Remove database

Use this function to remove a database from the list.

1. Select a database in the list.

2. Click Remove.

Batch fileoptions



49/84



1. Select the checkbox if you want to run batch files before and/or after thesnapshot agent.

2. Enter an administrative user name and password for the local computer.

3. Click the appropriate Create/Editbutton to open Notepad and create/save thebatch file.

Monitor options By default, the snapshot agent looks for databases based on information passed fromIMA. The Monitortab allows you to identify the drives on which databases are located.

Use the Monitortab to override the default drives and then specify the drive(s) onwhich you want the agent to look for databases.

1. The snapshot agent assumes a default location for databases on the clientmachine. If your Oracle database(s) are located on any other drive(s), you needto tell the agent to monitor those drives as well. To do this, select the Overridethe default drives option.

2. Type the drive letter(s) on which your database(s) is/are located, separated bysemicolons: for example, D;E;.

Click OKto save the changes you made in all tabs and either keep the utility open orexit. Click Cancel to exit the utility and discard any changes.


50/84



Manage theTrace Log


In the Trace log, you can see the connection to Oracle system and theALTERtablespace begin backupandALTER tablespace end backup commandto alltablespaces on the protected disk. For Linux installations, trace log messages arelogged to the system message file.



51/84



1. Click the icon in the upper left corner of the configuration utility and select

Settingsin the menu.


The value in the text box will change to 10and is not editable. Increasing thelevel of detail will display a list of the databases that have been backed up, aswell as information that can be used to provide support. The log will reflect the

change after the next snapshot is taken.


Configure the snapshot agent on a Solaris machine

If you have more than one Oracle SID, make sure all database instances arerunning before you configure the agent.

1. Run / usr/ l ocal / i pstor cl i ent / agent s/ or acl e/ bi n/ or a_set up. sh.

2. Select the version of the Oracle agent you are setting up.

Select 1for the Oracle 8 agent, 2for the Oracle 9 agent, or 3for the Oracle 10agent.

3. Enter the Oracle library path.

Note: If you are using the 64-bit version of Oracle, enter the path of the 32-bitversion of the Oracle libraries. [Should 32-bit be 64-bit here?]

Oracle 9i example: /export/home/ora9i/OraHome1/lib32

Oracle 10g example: /export/home/ora10g/OraHome1/lib32

4. Answer the questions that are asked by the setup program:

Is Oracle started?-- Since the setup program needs to verify the Oracleuser ID and password, the Oracle database must be started before theora_setupprogram continues.

What is the Oracle SID? -- In order to turn on Oracle archive logging, thesetup program needs to know the Oracle instance name.

What is the Oracle home path for SID xxx? -- This is the ORACLE_HOMEenvironment variable. Type the path in the format /oracle/OraHome1.


52/84



What is the Oracle admin user id for SID xxx? (system) -- Type the adminuser name needed to access the database. The user name should not be

sys.

What is the Oracle admin password for SID xxx? (manager)-- Type thepassword needed to access the database. The setup program will attempt

to verify that the user ID and password are valid.

What is the login name of the UNIX user account that owns Oraclesoftware? (ora10)-- Type the name of the Oracle user.

Would you like to enter another Oracle SID?-- Indicate if you want toconfigure more Oracle instances.

5. Shut down the cli

Documents

Snapshot Agents User Guide