Professional Documents
Culture Documents
Snapshot Agents
USER GUIDE
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.
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
General installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Additional resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
ii
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Snapshot Agents User Guide
iii
Introduction
Todays businesses put increasing demands on information and databases,
resulting in the need for 24x7 availability and high performance. However, evergrowing capacity presents significant challenges to meeting these requirements.
One of the most important issues identified by system administrators is the amount
of time associated with backup - and more important, recovery. Extreme downtime,
sometimes in the range of hours or days, is often experienced while recovering
corrupted 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 and
does not have point-in-time referential integrity. This means that there is no
guarantee 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 messaging
applications, safely and reliably taking snapshots of data for point-in-time copy
purposes, third-party backup applications, and disaster recovery planning. Snapshot
agents 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-in
snapshot engine.
Using the Replication option in conjunction with snapshot agents maintains
replicated data for off-host processing. Not only can backups be performed on the
replica, 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 production
server.
Snapshot agents help simplify many data management tasks, meeting the
requirements of high availability and high performance in todays workplace. The
following 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
FalconStor Continuous Data Protector (CDP) and Network Storage Server (NSS)
support use of snapshot agents on most major platforms. For specific support
information, refer to the Certification Matrix on the FalconStor website.
Introduction
Each agents configuration utility includes a menu that you can display by clicking
the icon in the upper left corner of the utility window. General options include the
following:
X-ray
Log files
All Microsoft Windows-based snapshot agents include an X-ray feature that allows
you to collect technical information - such as storage server messages and a
snapshot of the servers current configuration and environment - from your storage
servers for diagnostic purposes. The X-ray function generates a .cab file that you
can send to FalconStor Technical Support for analysis.
Log file content varies with each snapshot agent. Refer to individual agent
descriptions for details.
Introduction
Migrate the database/messaging system files you want to protect to the new
resources.
Before you install the snapshot agent, install the FalconStor Intelligent
Management Agent (IMA). IMA enables the client machine to access storage
server resources and manages notifications from the storage server.
If IMA is not detected when snapshot agent installation begins, an error
message will be displayed. You will need to cancel the procedure, install
IMA, and then repeat snapshot agent installation.
The SAN Disk Manager (SDM) user interface is provided on Windows
machines. The Intelligent Management Agent User Guide includes details
for 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 all
snapshot 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 that
solution.
Download software builds, patches, and other documentation related to
your FalconStor product from the FalconStor Customer Support Portal at
support.falconstor.com (account required). Click the View Builds, Patches,
& Documentation link in the GA Releases area to complete a simple search
form and display available downloads.
Additional resources
This guide supports the latest version of each snapshot agent.
Snapshot agents are designed to work with FalconStor Continuous Data Protector
(CDP) and FalconStor Network Storage Server (NSS). For more information, refer to
the CDP/NSS User Guide.
Snapshot agents are supported on various platforms. For specific version
information, refer to the Certification Matrix on the FalconStor website.
Note that the product release notes and patch descriptions can include information
that 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 Customer
Support portal.
The FalconStor Snapshot Agent for Microsoft Volume Shadow Copy Service
(VSS) protects VSS-aware application drives with full point-in-time consistency while
still 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) to
create consistent point-in-time copies of application data (shadow copies) across
multiple volumes, regardless of the snapshot technology or application, by
coordinating with business applications, filesystem services, backup applications,
fast recovery solutions, and storage hardware.
Microsoft VSS consists of four components:
The FalconStor Snapshot Agent for VSS takes consistent point-in-time snapshots of
VSS-aware application data and communicates with FalconStor Continuous Data
Protector (CDP) and FalconStor Network Storage Server (NSS) using its own
requestor and hardware provider. The hardware provider creates snapshot volumes
and is compatible with any third-party VSS requestor.
In order to use the VSS snapshot agent inside a VMware virtual machine, you must
either assign the data LUN directly to the virtual machine from NSS, or protect local
data storage using with FalconStor DiskSafe.
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 agent
package.
2. From the command line, navigate to the folder to which you extracted the
package.
3. Install the Intelligent Management Agent:
cd ima
setup.exe /s
cd ..
Snapshot options
Perform a full
backup
The Snapshot tab allows you to configure or disable full and copy backups. Each
writer decides how to handle a copy backup, but tlog files are not usually truncated.
Run database
or application
verification
You can specify when the Snapshot View should be verified during the snapshot
process. Currently, verification is compatible only with Microsoft Exchange, and
checks to see if Exchange is involved after snapshot creation is finished. You can
disable this option if the process takes too much time. For Exchange snapshots, the
snapshot agent will verify the checksum of the database and log files on the
Snapshot View, similar to IntegrityTrac.
Snapshot Agents User Guide
Advanced options
Use the advanced options to further refine snapshot configuration.
VSS mount point directory - the directory on which Snapshot View volumes
are mounted. Drive letters are not assigned to these volumes.
VSS metadata directory - the directory where requestor and writer metadata
is stored. You can also specify a file share in order to allow another host to
access the metadata.
CDP/SafeCache timeout - set to 180 seconds (3 minutes) by default.
Specify the number of seconds the hardware provider should wait for the
storage server to flush the CDP/SafeCache resource when asked to import
(create) a Snapshot View. Since this process is potentially time consuming,
the maximum setting is 86400 seconds (24 hours).
Exchange object verification timeout in minutes - set to 360 minutes by
default. If this timeout is exceeded before the agent has verified the
Exchange database, the agent will stop the verification process the
snapshot will fail.
Allow snapshot of mount point volumes - enabled by default, which sets a
registry value for IMA. When this option is enabled, the snapshot agent can
identify path information for volumes mounted to directories.
Storage Server for import operations - set to Automatic by default. In most
cases this option should not be changed. However, if the client is registered
to both source and target of a replication pair, specify the storage server to
which the hardware provider should send RPCs for Snapshot View
assignment when multiple storage servers are used.
In order to run batch files, you must enter an administrative user name and
password for the local computer.
Click the Create/Edit button and use Notepad to generate batch files.
2. Select Set Agent Trace On to maximize the level of detail displayed for agent
activity in the Trace Log.
The value in the text box will change to 10 and is not editable. Increasing the
level 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 snapshot
operation occurs on an CDP/NSS-managed disk.
You can test the snapshot agent by manually initiating a snapshot of a virtual drive
from the FalconStor Management Console. Click the TimeMark tab to verify that a
VSS snapshot has been created. You should see Yes with VSS in the Quiescent
column.
After the VSS snapshot agent creates a snapshot of application data, the snapshot
is mounted as a temporary device and assigned to the host. (A snapshot may be
referred to as a TimeMark; a mounted snapshot may be referred to as a Snapshot
View or TimeView.) The snapshot agent requestor clears read-only and hidden flags
and saves writer metadata to each volume. The hardware provider performs
additional cleanup and then tells CDP/NSS to unassign and delete the mounted
snapshot; data from the mounted snapshot is then saved.
When you select a SAN Resource in the FalconStor Management Console,
snapshots (referred to as TimeMarks in that console) created using the VSS
snapshot agent show Yes with VSS in the Quiescent column. Values in the
TimeView column can be available (data is present), none (there is no data), or in
use (the mounted snapshot is active).
10
Writers
The VSS snapshot agent is designed to make backups uniform across applications.
Some writers have distinct behaviors:
Microsoft Exchange
For snapshots of Exchange databases and log files on shadow copy devices, the
snapshot agent can verify the checksum of the database and log files on the
Snapshot View, similar to the way this occurs for FalconStor IntegrityTrac.
Snapshot verification may take a long time to complete and can be disabled in the
snapshot agent configuration tool (refer to Configure the snapshot agent).
Refer to the Certification Matrix on the FalconStor website to determine supported
versions 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 integration
tools must be installed; otherwise, the virtual machine is temporarily suspended and
saved to the disk while a snapshot is being created. When Snapshot View devices
are assigned to the host during a full backup, the Hyper-V writer will roll back each
virtual machine to the same point in time.
11
Note: If you are using Microsoft Exchange 2010 or Exchange 2013, you must use
the Snapshot Agent for Microsoft VSS.
The FalconStor Snapshot Agent for Microsoft Exchange enables FalconStor CDP/
NSS to protect Exchange databases with point-in-time consistency while allowing
full speed, non-stop access to databases.
Microsoft Exchange requires quiescent snapshots. In order for this to occur, the
Snapshot Notification option must be enabled on the Snapshot Resource (refer to
the CDP/NSS User Guide). When a snapshot is triggered and snapshot notification
is enabled, the FalconStor system notifies the application server running the
snapshot 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 FalconStor
system that the snapshot can be performed. The application server is again notified
once the snapshot has completed, and the snapshot agent takes the database out
of backup mode.
Using backup software, a backup of the snapshot image can be performed at high
speed while Microsoft Exchange operates in normal mode. While the backup
software is reading data from the snapshot image, 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 backup software sees a stable, read-only
snapshot image of the database taken an instant before the backup began.
The snapshot agent will be triggered automatically whenever a snapshot operation
occurs on the Microsoft Exchange drive.
12
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 agent
package.
2. From the command line, navigate to the folder to which you extracted the
package.
3. Install the Intelligent Management Agent:
cd ima
setup.exe /s
cd ..
13
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/Edit buttons and use Notepad to generate the batch
files.
14
Monitor tab
By default, the snapshot agent looks for databases based on information passed
from IMA. This tab allows you to identify the drives on which databases are located.
2. Select Set Agent Trace On to maximize the level of detail displayed for agent
activity in the Trace Log.
The value in the text box will change to 10 and is not editable. Increasing the
level of detail will display a list of the databases that have been backed up, as
well as 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 Agents User Guide
15
16
4. Exchange ESE completes the backup process on a storage group. You may see
the same process on another storage group.
17
You must specify the location of the checkpoint file and log directory.
Syntax: ISPurgeExLog "<Checkpoint File>" "<Exchange Log
directory>" [Options]]
Option
Description
-b#hour
-c
-hHour
-i
-p
-r"reportFileName
s"StorageGroupName"
-v
verbose mode.
18
It is recommended that you run the purge utility once a day, maintaining 24 hours of
log files after each log purge. After the purge, you can examine the log file directory
and make sure older log files are deleted. There is also an ISPurge.log file created
containing the history of each ISPurgeExLog execution.
19
The Snapshot Agent for Microsoft SQL Server protects Microsoft SQL Server
databases on protected disks with point-in-time consistency while still allowing full
speed, non-stop access to the databases. Users always have full access to the
database, while backup software sees a stable, read-only snapshot image of the
database taken an instant before backup began.
Before the snapshot process begins, a request is sent to the server running the
Snapshot Agent for Microsoft SQL Server to quiesce databases or applications. By
default, the snapshot agent performs a full backup of all databases. The configuration
utility allows you to choose different backup options for different SQL instances, and
lets you exclude less critical databases from snapshots.
Backup software can back up the snapshot image at high speed while Microsoft
SQL Server operates in normal mode. Because the contents of the snapshot image
are guaranteed never to change, the backup is consistent, ensuring transactional
integrity. When backup software reads data from the snapshot image, changes that
occur in the database do not affect what gets written.
The snapshot agent will be triggered automatically whenever a snapshot operation
occurs 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 Windows
Server platforms. For specific version information, refer to the Certification Matrix on
the FalconStor website.
You need to know the database administrator password if the default policy
is Windows authentication and the current Windows login account does not
have enough access rights.
Install the snapshot agent on the machine on which the SQL Server
database is running.
20
You must configure IMA to specify override drives. These are the drives on
the 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 or
other application data that should be quiesced before snapshots are taken.
To manage override drive settings, execute the following commands in the
command line on the virtual host:
To specify override drives:
iscmcli setoverridedrive -d "<drive_list>"
where <drive_list> is a list of drive letters separated by semi-colons.
For example:
iscmcli setoverridedrive -d "C:;E:;F:;"
To view the list of current override drives:
iscmcli getoverridedrive
If no override drives have been set, the command returns no output.
To delete current override drive settings:
iscmcli deloverridedrive
21
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 agent
package.
2. From the command line, navigate to the folder to which you extracted the
package.
3. Install the Intelligent Management Agent:
cd ima
setup.exe /s
cd ..
4. Install the snapshot agent:
setup /s
or
setupsilent.bat
When installing the snapshot agent in silent mode on any 64-bit platform, run
setupsilent.bat from the AMD64 directory.
22
23
1. Click Add to add a SQL instance. The Database Login screen displays.
2. Select the virtual server or host on which the instance is located. If the SQL
server is in a cluster, select the name of the virtual server on which the SQL
instance 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 detected
in the registry.
3. In the Instance field, MSSQLSERVER will be displayed if the server uses the
default instance. If the SQL instance is not displayed, enter it here or select it in
the drop-down list.
You can use the Services console (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 another
instance, another service, such as SQL Server (INSTANCE1), will be listed. In this
example, 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 Authentication checkbox to avoid
storing credentials in connection strings.
OR, for SQL Server authentication mode, enter the database user name and
password of an account that has access to the database.
5. When you are done, click Verify to allow the snapshot agent to attempt to
connect to the instance using the provided credentials.
If connection is successful, the Verify button 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:
25
Click the Browse button next to the Transaction Log Backup directory field and
select a backup directory location. Manually entering a directory location is not
recommended.
Note: Make sure that you have selected a database before you do this; this is
necessary in order for the selected location to be saved.
To specify this directory as the Transaction Log Backup directory for all
databases, respond Yes to the Change entry for all databases in this
instance? message.
To specify this directory as the Transaction Log Backup directory only for the
selected database, respond No to the change entry message.
If you do not see the change entry message, the directory selection will
apply only to the selected database.
Note: If you click in the Transaction log backup field but do not make a
selection, the message Change entry for all databases in this instance? may
be displayed when you continue with another action. Click No to close the
message box.
Additional options for transaction log backup are available (refer to Transaction Log
Backup best practice).
26
To do this:
1. Select one backup option. Full backup is selected by default:
Full backup of all databases - The snapshot agent performs a full SQL Server
snapshot backup of selected databases, regardless of their recovery model.
Full backup, but checkpoint only on databases when recovery model set to
Simple - The snapshot agent performs a full backup on selected databases
except for those whose recovery model is set to Simple; for those, a checkpoint
is performed.
Do checkpoint only on all databases - If the instance includes a large number of
databases, choose this option to save time. Do not exclude any databases.
Copy-only, full backup of all databases - The snapshot agent performs a full
backup of selected databases but does not notify SQL that backup has occurred.
Notes for the copy-only option:
2. Select Perform a transaction log backup for every snapshot to enable this
option. This option is disabled if you choose the checkpoint only or copy only
option.
3. The Database Selection area lists all databases discovered in the selected
instance. You can exclude specific databases from the selected backup
operation.
To do this, select a SQL instance from the drop-down list, which includes only
those instances that have been registered with the snapshot agent using this
utility.
All databases in the instance are selected by default. Uncheck any database(s)
that the snapshot agent should exclude from the selected backup operation.
If the full backup or copy-only option is selected, the snapshot agent will
perform a checkpoint flush on the excluded databases for overall snapshot
consistency.
If checkpoint only is selected, excluded databases will be ignored.
Use the Select All/Deselect All checkbox to select or deselect all databases at
the same time.
27
If you create additional databases after completing initial agent configuration and
want to exclude any of them from the selected backup option, run the
configuration utility again and deselect them here.
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/Edit button to open Notepad and create/save the
batch file.
28
Monitor tab
By default, the snapshot agent looks for databases based on information passed
from IMA. If the default drives (as seen in the Database Options tab) are incorrect or
if 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 elsewhere
than 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 drive
names with a semicolon (for example D:;E:;F:).
29
3. The Settings dialog 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 the
level of detail to be displayed. 0 is the default. Increasing the detail value will
display 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 change
this value, the log will adjust to the change after the next snapshot.
<databasename>.hisu file
The <databasename>.hisu file contains a list of all files since the time the application
started and resides in the transaction log directory. An example is shown below:
db1.mdf;20120703144715;0;1
db1-20120705102206.log
db1-20120705102208.log
db1-20120705102210.log
db1.mdf;20120705102213;0;1
This sample log file indicates that a full backup was done, followed by three
Transaction 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.
30
31
32
If you want the utility to complete a TimeView restore, use IMA or the
FalconStor Management Console for CDP/NSS to perform a TimeView
restore from a Time Mark.
Find the database files *.mdf, *.meta, *.ldf (if recovery model is full) on
the 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 the
selected database is the only database on this device; otherwise, perform
a TimeView restore. Press Enter to continue with Rollback restore.
Options:
-t <trace path and file> - Specify a destination path and
file name for the Trace Log.
-d <databasename> - Specify the database name - applies to fb, tlb, and
cp.
-i <Server Name><Instance Name> - Specify server name and instance
name.
-dir <backup directory> - 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 be
saved 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 server
snapshot has been taken:
fsssrest -tlb -d <databasename>
This command enables you to perform additional transaction log backups
after a full backup and before the last transaction log backup. The command
records the date and time, which makes it easier to identify the transaction
logs that are needed during restore. You can run this command as needed,
based on your backup schedule. You can also use other utilities to schedule
additional transaction log backups between snapshots.
Configure Transaction Log backup for all databases in all instances on the
server:
fsssrest.exe -tlb -d * -i "ESX40W2K8DEVHAR"
Configure Transaction Log backup for all databases in one instance and
generate the Trace Log:
fsssrest.exe -tlb -d * -i
"ESX40W2K8DEVHAR\SQLINSTANCE1" -t
Transaction Log backups are recorded in history files for use by the SQL Recovery
tool. 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 to
manually enter the transaction records into FalconStor Database Recovery for
Microsoft SQL Recovery.
34
Diagnostic X-ray
An X-ray feature allows you to collect technical information - such as storage server
messages 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 file
that you can send to FalconStor Technical Support for analysis.
35
You need to know the database instance name and the database
administrator 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 archive
logging).
36
Install on Windows
1. Run the installation file.The snapshot agent will be installed to the same
directory as IMA.
2. Select which version(s) of Oracle you are using.
You must have a separate license for each.
3. 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 as
you enter your keycode and click Next. However, if your Internet connection is
temporarily unavailable or if your computer has no Internet connection, your
license will not be activated. You must activate your license within 30 days so
that 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, assuming
you have an Internet connection then. You can also add your license through
IMA.
If your computer has no Internet connection, you can perform offline activation
using IMA (refer to the Intelligent Management Agent User Guide).
4. When done, click Finish.
After installation completes, a configuration utility launches. Refer to Configure the
snapshot 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:
1. Download the package from the FalconStor Support Portal and extract the agent
package.
2. From the command line, navigate to the folder to which you extracted the
package.
3. Install the Intelligent Management Agent:
cd ima
setup.exe /s
cd ..
4. Install the snapshot agent:
For Oracle 11
Run setup /s or setupsilent.bat.
For Oracle 10
a. Copy setup10.iss to setup.iss.
b. Run setup /s or setupsilent.bat.
Snapshot Agents User Guide
37
For Oracle 9
a. Copy setup9.iss to setup.iss.
b. Run setup /s or setupsilent.bat.
Note: If your Oracle server is running a 64-bit operating system, perform
these steps from the AMD64 directory.
Install on Solaris
You must be root (or root equivalent) in order to install the snapshot agent.
1. Download the tar file to the local drive of your Solaris client (/tmp is used in the
example).
2. Install the snapshot agent software.
pkgadd -d /tmp/oracle8i9i10gagent-<version number>-<build number>.pkg
Install on Linux
You must be root (or root equivalent) in order to install the snapshot agent.
1. Download the installation file to the local drive of your Linux client.
2. Install the snapshot agent software.
rpm -i --nodeps oracleniagent-<version number>-<build number>.i386.rpm
38
Install on AIX
You must be root (or root equivalent) in order to install the snapshot agent.
1. Download the tar file to the local drive of your AIX client.
2. Type the following command to untar the agent package:
tar -xvf oracleniagent-<version number>-<build number>.tar
Oracle 9i example: tar -xvf oracle9iagent-4.50-901.tar
Oracle 10g example: tar -xvf oracle10gagent-4.50-901.tar
3. Install the package:
installp -aFX -d IPStor.OraAgent.bff all
After installation completes, a configuration utility launches. Refer to Configure the
snapshot agent on a Linux or AIX machine.
Install on HP-UX
You must be root (or root equivalent) in order to install the snapshot agent.
1. Download the tar file to the local drive of your HP-UX client (/tmp is used in the
example).
2. Type the following command to untar the agent package:
# cd .tmp
# tar xvf oracleniagent-<version number>-<build number>.tar
Oracle 9i example: tar xvf oracle9iagent-4.50-896.tar
Oracle 10g example: tar xvf oracle10gagent-4.50-897.tar
3. Install the snapshot agent software.
# swinstall -s pwd/package oracle
4. As the Oracle User, view the .profile or type the env command to determine the
library 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 as
Solaris).
$ cat ~/.profile | grep SHLIB_PATH
SHLIB_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/lib64:/lib:/usr/
lib:/usr/local/lib
- or $ env | grep SHLIB_PATH
39
SHLIB_PATH=/oracle8/OraHome1/lib:/oracle8/OraHome1/lib64:/
lib:/usr/lib:/usr/local/lib
In these examples, there are two directories: lib and lib64. One or more of these
directories contain the library (libclntsh.sl.8.0) needed for the Oracle8i Database
Agent to work correctly.
5. As root user, issue a find command to make sure one or more of these
directories contain the necessary library path.
# find /oracle8/OraHome1/lib -name "libclntsh.sl.8.0" -print
/oracle8/OraHome1/lib/libclntsh.sl.8.0
# find /oracle8/OraHome1/lib64 -name "libclntsh.sl.8.0" print
/oracle8/OraHome1/lib64/libclntsh.sl.8.0
In this example, the file exists in both Oracle directories. If this occurs on your
machine, enter both paths when configuring the agent.
After installation completes, a configuration utility launches. Refer to Configure the
snapshot agent on an HP-UX machine.
40
To begin, select the version of Oracle you are using, then click Edit.
41
Database
Security
options
The Database Security tab displays the databases whose snapshots will be
managed by the snapshot agents.
Add database
To add a database whose snapshots will be managed by the snapshot agent, click
Add Login. The Database Login dialog is displayed.
1. Enter the login credentials for the database you are adding:
Database SID - Enter the Oracle instance name.
User Name and Password - Enter the user name and password of an Oracle
account with the DBA role (system, for example). This is the user and password
that the storage server needs to access your database. When the Oracle
database 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, or
Password, click Remove to remove the existing SID and then re-add it.
42
On the Batch Files tab, indicate if you want to run batch files before and/or after
each snapshot.
43
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/Edit button to open Notepad and create/save the
batch file.
Monitor options
By default, the snapshot agent looks for databases based on information passed from
IMA. The Monitor tab allows you to identify the drives on which databases are located.
Use the Monitor tab to override the default drives and then specify the drive(s) on
which you want the agent to look for databases.
1. The snapshot agent assumes a default location for databases on the client
machine. If your Oracle database(s) are located on any other drive(s), you need
to tell the agent to monitor those drives as well. To do this, select the Override
the default drives option.
2. Type the drive letter(s) on which your database(s) is/are located, separated by
semicolons: for example, D;E;.
Click OK to save the changes you made in all tabs and either keep the utility open or
exit. Click Cancel to exit the utility and discard any changes.
44
Manage the
Trace Log
The Trace Log is a diagnostic tool used by Technical Support to help solve system
problems. Each Trace Log contains technical information about your system as well
as system messages and is updated whenever a snapshot occurs. Some of the
messages that appear in the Trace Log are also sent to the Windows Event Log.
In the Trace log, you can see the connection to Oracle system and the ALTER
tablespace begin backup and ALTER tablespace end backup command to all
tablespaces on the protected disk. For Linux installations, trace log messages are
logged to the system message file.
Do not adjust Trace Log settings unless you are requested to do so by a Technical
Support representative. The configuration utility lets you maximize the level of detail
that is displayed.
45
1. Click the icon in the upper left corner of the configuration utility and select
Settings in the menu.
2. Select Set Agent Trace On to maximize the level of detail displayed for agent
activity in the Trace Log.
The value in the text box will change to 10 and is not editable. Increasing the
level of detail will display a list of the databases that have been backed up, as
well as 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.
46
What is the Oracle admin user id for SID xxx? (system) -- Type the admin
user name needed to access the database. The user name should not be
sys.
What is the Oracle admin password for SID xxx? (manager) -- Type the
password 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 Oracle
software? (ora10) -- Type the name of the Oracle user.
Would you like to enter another Oracle SID? -- Indicate if you want to
configure more Oracle instances.
5. Shut down the client (ipstorclient) and log out.
6. Log in again as root and restart ipstorclient.
Note: If you ever add another Oracle instance and need to configure it for the
snapshot agent, you can run ora_setup.sh add. Conversely, if you ever
need to remove an Oracle instance from your snapshot agent configuration,
you can run ora_setup.sh remove.
Configure ASM
disks
The snapshot agent includes a utility that helps you configure Oracle Automatic
Storage Management (ASM) disks. The utility is /asm10config and its usage is as
follows:
asm10config -a | -d | -m | -l | -D
-a : add an ASM disk group
-d : delete an ASM disk group
-m : modify an ASM disk group
-l : list ASM disk groups
-D : delete all ASM disk groups
To add an ASM disk group:
1. Run /asm10config -a .
2. Indicate if Oracle is started.
3. Enter the IP address of the storage server.
4. Enter the password for the root user on the storage server.
5. Enter the Oracle SID.
6. Set ORACLE_HOME.
A list of virtual devices will be displayed.
7. Select the virtual device(s) for your disk group by entering the appropriate line
numbers.
47
For multiple virtual devices, separate numbers with semicolons. For example:
1;2;5.
8. If you have multiple disk groups, select the virtual device(s) for each group.
9. Indicate if you want to save the displayed VGList information.
It will be saved to /usr/local/ipstorclient/agents/oracle10/etc/agt.ini.
Configure the
Oracle Listener
The snapshot agent needs the Oracle Listener, which should be configured to use
the TCP/IP protocol and port number 1521.
Each version of Oracle has its own Listener. If you have more than one version of
Oracle running on the same machine, do the following:
1. Determine which version was installed first; for example, you have 9i and 10g
installed on the same machine and 10g was installed first.
2. Run the Listener that came with the version that was installed first.
For the purposes of our example, run the Listener that came with 10g.
3. Configure the other Oracle versions to use this Listener.
For the purposes of our example, configure the 9i version of Oracle to use the
10g Listener.
Refer to your Oracle documentation for information about how to use and configure
the Oracle Listener.
Configure the snapshot agent on a Linux or AIX machine (updated October 2013)
Note for Linux only: When you are running a backup software application on the
machine where the Snapshot Agent for Oracle is installed, you may see conflicts
when the database is set in backup or non-backup mode. In this case, you can
use flag BACKUPCHECK in configuration file snapagt.ini to indicate whether
the snapshot agent can set the database mode. The default value is 0, which
indicates the snapshot agent will always set the mode. If you set
BACKUPCHECK=1, the snapshot agent does not set the mode and will let the
backup application set the database mode.
1. Once the package is installed, re-login as root.
su -
48
What is the Oracle home path? -- Type the path in the format /oracle/
OraHome1.
Enter the Oracle SID: -- In order to turn Oracle archive logging on, the setup
program needs to know the Oracle instance name.
What is the Oracle admin user id for SID xxx? (system) -- Type the admin user
name needed to access the database. The user name should not be sys.
What is the Oracle admin password for SID xxx? (manager) -- Type the
password needed to access the database. The setup program will attempt
to verify that the user ID and password are valid.
Once the Snapshot Agent for Oracle is set up successfully, the configuration file /
usr/local/ipstorclient/agents/oracle/etc/oracle.conf will be created and the following
file will be updated: /usr/local/ipstorclient/etc/isdb.conf
49
50
/home/bin:/usr:/usr/bin:/usr/local/bin
51
= true
log_archive_dest
= /mount_point/oradata/SID/ARCHIVE/
log_archive_format = _%s.arc
52
Command/Instructions
Windows
Linux
pkgrm isora
HP-UX
installp -u IPStor.OraAgent.rte
53
We recommend that you create each tablespace on a separate virtual disk. If there
are sufficient resources, the virtual disk should be created on a dedicated physical
device. It this is not possible, the virtual disks should be created such that disk
access is balanced across the available physical resources.
Fault tolerance
and
performance
considerations
For fault tolerance, mirroring can be done at the operating system level or you can
use the Mirroring feature. Other fault-tolerance configurations can be implemented
at the operating system level. When creating virtual devices, keep in mind that the
operating system might configure the virtual disks in a RAID configuration. For RAID
configurations, you should make sure the disks are from different physical disks.
If the database is very active and changes are made randomly, the Snapshot
Resource should be created with sufficient size, and the storage server should have
enough free disk space to allow the snapshot resource to grow when needed. It is
better to define which physical disk should be used when expanding the snapshot
resource.
Using groups
Most Oracle databases use more than one virtual disk. In order to guarantee
database integrity, use the FalconStor Management Console to create a group on
the storage server (refer to the CDP/NSS User Guide for details):
1. Create a group; be sure to select the option to enable TimeMark (snapshots) for
the group; you can also enable CDP Journal option.
2. Select the SAN resources (virtual disks) that are used by the Oracle database to
join the group.
3. Assign the group to the client that runs the Oracle database.
4. Perform all snapshot-related functions using the group.
Oracle control
file
If a raw device is used for the Oracle database, you must store the Oracle control file
on another virtual disk, which should be in the same group as the raw devices
virtual disk. Otherwise, snapshots of the raw device database may be inconsistent.
54
Use TimeMark Copy to create a physical copy of the disks that are used by the
Oracle database. The set of TimeMark Copy disks should be created with the same
TimeMark. The set of TimeMark Copy disks is exactly what the online Oracle disks
looked like at the moment you created the TimeMark. This set of disks can be
mounted on the Oracle Server and the Oracle database instance can be started with
minimal recovery steps. Make sure there is enough free physical space for creating
the TimeMark Copy.
To create a TimeMark Copy:
1. Launch the FalconStor Management Console.
2. Connect to the server that is serving the virtual disks for the Oracle database.
3. Expand Logical Resources --> SAN Resources.
4. Right-click on the first virtual device of the group.
5. Select TimeMark --> Copy.
6. Select the desired TimeMark to be copied.
7. Repeat the last two steps for all virtual devices in the group.
The TimeMark Copy disks can be assigned and mounted by the client using the
Oracle database. When you start the Oracle database using the TimeMark Copy
disks, the tablespaces are still in backup mode. Refer to the Disk failure section for
information about how to recover a database with TimeMark Copy disks.
TimeView
Instead of recreating the Oracle disks with physical storage, you can create a
TimeView that is mountable and works exactly like the TimeMark, except that the
original set of disks for the production database have to be working. You can use
TimeView to retrieve lost data without rolling back changes on the product database.
TimeView does not require physical storage.
To create a TimeView of the database disks:
55
TimeMark
rollback
You can set up replication of the Oracle database disks to protect the database in
case of site failure. In the event that the primary site fails, the replica disks on the
secondary site can be promoted, assigned to the Oracle server, mounted, and the
database will be back and running with minimal down time. The database will be at
the state of the last complete replication.
This feature rolls back a disk back to the point in time at which you took the
TimeMark. This is useful if you need to roll back changes to the disks to a known
good stage, such as before a major update to the table that contains customer
information.
To perform a rollback:
1. Stop the Oracle database.
2. Stop the client on the Oracle database server.
3. Launch the Console.
4. In IMA, unassign the device(s) that the Oracle database resides on.
5. Connect to the server that is serving the virtual disks for the Oracle database.
6. Expand Logical Resources --> Groups.
7. Right-click on the group that was created for the Oracle database.
8. Select TimeMark --> Rollback.
9. Select the TimeMark that you want to roll back to.
56
You can perform a complete tape backup of your database using a TimeView or
TimeMark Copy. The TimeView or the TimeMark Copy disks contains the Oracle
database files as regular files and can be backed up with your normal backup
software.
Recovery scenarios
Disk failure
You can quickly recover from disk failure by using a TimeMark Copy you created.
The database can be brought back online in a matter of minutes. However, the data
entered after the TimeMark was created cannot be restored.
To recover using a TimeMark Copy:
1. Stop the client on the Oracle database.
2. Launch the Console.
3. Unassign all of the disks used for the Oracle database from the client.
4. Assign the set of TimeMark Copy disks for the Oracle database to the client.
5. Restart the client on the Oracle database server.
6. Start the Oracle database.
7. Recover the database, if necessary.
8. Open the database for normal access.
User failure
User failure can occur when users executes DDL commands, such as drop table,
that they need to undo. The TimeMark option and the snapshot agent provide a
quick and painless way to recover tables and records that were accidentally
dropped.
To recover from user failure:
1. Create a TimeView of the database disk using the desired TimeMark.
2. Assign the TimeView virtual disks to a backup Oracle database server. This
could be the on same server as the production database server.
57
If the system administrator or DBA accidentally deleted some files that are important
to the Oracle database, you can quickly retrieve the files from a TimeView.
To recover files from a TimeView:
1. Create a TimeView of the database disk using the desired TimeMark.
2. Assign the TimeView virtual disks to the Oracle database server.
3. Rescan the client to discover the new disks.
4. Mount the new disks and copy the files from the TimeView disks.
If a disk for the database is accidentally formatted, you can recover it using rollback.
Follow the steps inTimeMark rollback.
58
Automatic
recovery
1. When you see this message, you can run the recover database command
which will find all tablespaces and take each out of backup mode.
SQL> recover database;
Media recovery complete.
2. Afterwards, you can open the database.
SQL> alter database open;
Database altered.
Manual
recovery
You can also manually issue the Oracle commands to find each tablespace and then
end the backup:
1. Instead of issuing the recover database command, check to see if the
tablespaces are in the backup mode by issuing the following command.
SQL> select * from v$backup;
FILE# STATUS
CHANGE# TIME
-------- ------------------ ---------- --------1
ACTIVE
107569 23-AUG-00
2
ACTIVE
107573 23-AUG-00
3
ACTIVE
107577 23-AUG-00
4
ACTIVE
107581 23-AUG-00
5
ACTIVE
107585 23-AUG-00
6
ACTIVE
107589 23-AUG-00
6 rows selected.
Since the file status is active, the tablespaces are still in the backup mode.
2. Find out what the names of the tablespaces are.
SQL> select * from v$tablespace;
TS#
NAME
INC
-------- ------------------------------ --0
SYSTEM
YES
1
UNDOTBS
YES
2
DRSYS
YES
3
INDX
YES
4
TEMP
YES
5
TOOLS
YES
6
USERS
YES
7 rows selected.
59
60
Install on Windows
1. Run the installation file.
2. When prompted, enter your license keycode.
For Windows installations, the snapshot agent license must be activated
(registered with FalconStor). If your computer has an Internet connection, the
license is activated as soon as you enter your keycode and click Next. However,
if your Internet connection is temporarily unavailable or if your computer has no
Internet connection, your license will not be activated. You must activate your
license within 30 days so that 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, assuming
you have an Internet connection then. You can also add your license through
IMA.
If your computer has no Internet connection, you can perform offline activation
using IMA (refer to the Intelligent Management Agent User Guide).
3. When done, click Finish.
The snapshot agent will be installed into the same directory as the IMA.
4. 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.
The snapshot agent will start automatically each time the client is started.
61
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 agent
package.
2. From the command line, navigate to the folder to which you extracted the
package.
3. Install the Intelligent Management Agent:
cd ima
setup.exe /s
cd ..
4. Install the snapshot agent:
setup /s
or
setupsilent.bat
When installing the snapshot agent in silent mode on any 64-bit platform, run
setupsilent.bat from the AMD64 directory.
62
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/Edit buttons and use Notepad to generate the batch
files.
63
Monitor tab
By default, the snapshot agent looks for databases based on information passed
from IMA. This tab allows you to identify the drives on which databases are located.
2. Select Set Agent Trace On to maximize the level of detail displayed for agent
activity in the Trace Log.
The value in the text box will change to 10 and is not editable. Increasing the
level of detail will display a list of the databases that have been backed up, as
64
well as 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.
Command/Instructions
Windows
Linux
AIX
65
Install the snapshot agent on the same machine where the MySQL
database is running.
Start MySQL server before installing the agent.
To install:
1. Run the installation file.
2. When prompted, enter your license keycode.
The snapshot agent license must be registered with FalconStor and activated. If
your computer has an Internet connection, the license is activated as soon as
you enter your keycode and click Next. However, if your Internet connection is
temporarily down or if your computer has no Internet connection, your license
will not be activated. You must activate your license within 30 days so that you
can continue to use the snapshot agent.
If your Internet connection is temporarily down, your license will be activated
automatically the next time the snapshot agent is invoked, assuming you have
an Internet connection then. You can also add your license through IMA.
If your computer has no Internet connection, you can perform offline activation
using IMA (refer to the Intelligent Management Agent User Guide).
3. When done, click Finish.
66
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 agent
package.
2. From the command line, navigate to the folder to which you extracted the
package.
3. Install the Intelligent Management Agent:
cd ima
setup.exe /s
cd ..
4. Install the snapshot agent:
setup /s
or
setupsilent.bat
When installing the snapshot agent in silent mode on any 64-bit platform, run
setupsilent.bat from the AMD64 directory.
67
The FalconStor Snapshot Agent for DB2 protects DB2 databases with full point-intime consistency while still allowing full speed, 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 DB2. The snapshot agent suspends all DB2
database writes and notifies the server that the snapshot can be performed. Once
the snapshot has completed, the agent resumes all database writes.
Using backup software, a back up of the snapshot image can be performed at high
speed while DB2 operates in normal mode. Because the contents of the snapshot
image are guaranteed never to change, what is backed up is consistent, ensuring
transactional integrity. While the backup software is reading data from the snapshot
image, 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 backup
software sees a stable, read-only snapshot image of the database taken an instant
before the backup began.
The snapshot agent will be triggered automatically any time a snapshot operation
occurs on the DB2 drive.
You need to know the database instance name and the database
administrator password.
Start the DB2 database before installing the agent.
Install on Windows
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 as
you enter your keycode and click Next. However, if your Internet connection is
temporarily down or if your computer has no Internet connection, your license
will not be activated. You must activate your license within 30 days so that you
can continue to use the snapshot agent.
If your Internet connection is temporarily down, your license will be activated
automatically the next time the snapshot agent is invoked, assuming you have
an Internet connection then. You can also add your license through IMA.
68
If your computer has no Internet connection, you can perform offline activation
using IMA (refer to the Intelligent Management Agent User Guide).
3. When prompted, enter the user ID and password of the DB2 administrator.
This is the system user and password that the storage server needs to access
your database. When the DB2 database is set up initially, the default system
user password is usually DB2adm.
4. Enter the home path where DB2 is installed.
5. Enter the database instance.
Separate multiple instances with a space.
The snapshot agent will be installed to the same directory as IMA.
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 agent
package.
2. From the command line, navigate to the folder to which you extracted the
package.
3. Install the Intelligent Management Agent:
cd ima
setup.exe /s
cd ..
4. Install the snapshot agent:
setup /s
or
setupsilent.bat
When installing the snapshot agent in silent mode on any 64-bit platform, run
setupsilent.bat from the AMD64 directory.
69
Install on AIX
You must be root (or root equivalent) in order to install the snapshot agent.
1. Make sure that your DB2 database is up and running.
2. Copy the tar file to the local drive of your AIX client.
3. Type the following command to untar the agent package.
tar xvf db2agent-<version number>-<build number>.tar
The root user is the user that the storage server uses to trigger the agent and run
agent commands. Therefore, in order for the storage server to be able to execute
database commands, you need to add the root user to your database groups.
1. Use an editor to edit the /etc/group file.
2. Add root to each database group.
When you are done, your file should look something like this:
system:!:0:root
sys:!:3:root,bin,sys
...
...
db2iadm1:!:999:db2inst1,db2as,root
db2fadm1:!:998:db2inst1,db2fenc1,db2as,root
db2asgrp:!:997:db2inst1,db2as,db2fenc1,root
70
You need to set the root users PATH and LD_LIBRARY_PATH to include the
database users PATH and LD_LIBRARY_PATH variables.
Example:
root users PATH is:
/home/bin:/usr:/usr/bin:/usr/local/bin
You have to add the DB2 users environment variables to the roots variables.
1. Log in as the root user and edit the /.profile file.
2. Add the DB2 paths to the end of the root paths.
Using the example above:
PATH=/home/bin:/usr:/usr/bin:/usr/local/bin:/home/
db2inst1/bin ; export PATH
LD_LIBRARY_PATH=/home/lib:/usr/lib:/usr/local/lib:/home/
db2inst1/lib ; export LD_LIBRARY_PATH
Install on Linux
You must be root (or root equivalent) in order to install the snapshot agent.
1. Copy the installation file to the local drive of your Linux client.
2. Install the snapshot agent software.
rpm -ivh db2agent-<version number>-<build number>.i386.rpm
For example: rpm -ivh db2agent-4.50-0.900.i386.rpm
3. Shut down the client and log out.
4. Run the setup program.
/usr/local/ipstorclient/agents/db2/bin/isdb2_setup
5. When prompted, answer the following questions:
What is the DB2 bin path?
What is the current db2 instance name?
If there is more than one db2 instance, enter all the db2 instance names and
separate them by a space.
71
dasadm1:!:101:db2inst2,root
db2grp1:!:102:root
Command/Instructions
Windows
Linux
AIX
72
The FalconStor Snapshot Agent for Lotus Notes/Domino protects databases with
full point-in-time consistency while still allowing full speed, almost 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 Lotus Notes/Domino. The snapshot agent syncs the
database while the server takes a snapshot of the database.
Using backup software, a back up of the snapshot image can be performed at high
speed while Lotus Notes/Domino operates in normal mode. Because the contents of
the snapshot image are guaranteed never to change, what is backed up is
consistent, ensuring transactional integrity. While the backup software is reading
data from the snapshot image, 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 backup software sees a stable, read-only snapshot image of the
database taken an instant before the backup began.
The snapshot agent will be triggered automatically any time a snapshot operation
occurs on the Lotus Notes drive.
Install on Windows
Installation requires the following:
To install:
1. Verify that the Lotus Notes path is set in the PATH environment variable.
If it is not set, add the path (such as C:\Lotus\Notes) to the PATH environment
variable and then reboot the machine.
2. Shut down the Domino server and stop IMA.
3. Run the installation file.
4. 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 as
you enter your keycode and click Next. However, if your Internet connection is
temporarily down or if your computer has no Internet connection, your license
73
will not be activated. You must activate your license within 30 days so that you
can continue to use the snapshot agent.
If your Internet connection is temporarily down, your license will be activated
automatically the next time the snapshot agent is invoked, assuming you have
an Internet connection then. You can also add your license through IMA.
If your computer has no Internet connection, you can perform offline activation
using IMA (refer to the Intelligent Management Agent User Guide).
5. When done, click Finish.
The snapshot agent will be installed to the same directory as IMA.
6. Start the client and your Domino Server.
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 agent
package.
2. From the command line, navigate to the folder to which you extracted the
package.
3. Install the Intelligent Management Agent:
cd ima
setup.exe /s
cd ..
4. Install the snapshot agent:
setup /s
or
setupsilent.bat
When installing the snapshot agent in silent mode on any 64-bit platform, run
setupsilent.bat from the AMD64 directory.
Install on Linux
Installation of the snapshot agent has the following requirements:
To install:
1. Install the snapshot agent software.
rpm -i notesagent-<version number>-<build number>.i386.rpm
For example: rpm -i notesagent-4.50-896.i386.rpm
Snapshot Agents User Guide
74
For Linux installations, trace log messages are logged to the system message file.
On the Domino server, you can check the snapshot agent communication from the
system log.
75
Command/Instructions
Windows
Linux
76
Index
D
DB2
Install
AIX 70
Linux 71
Requirements 68
Windows 68
Silent install 69
Silent install l 69
Licensing 68
Remove 72
Root user
Database groups 70
PATHs 71
Downloads 3
Lotus Notes
Install
Windows
Silent install 74
Lotus Notes/Domino
Agent trace log 75
Install
Linux 74
Windows 73
Licensing 73
Remove 76
E
Exchange
Batch file options 14
Exchange and VSS 12
Install 13
Silent install 13, 22, 37, 62
Licensing 13
Options 14
Override efault drives 15, 44, 64
Purge Log utility 18
Remove 19
Service-enabled devices 16
Status 16
Trace Log 15
F
FileSystems
Batch file options 63
Install
HP-UX 62
Linux 62
Solaris 62
Windows 61
Licensing 61
Remove 65
Service-enabled devices 65
Trace log 64
H
HyperTrac 1
M
MySQL
Configure 67
Install 66
Windows
Silent install 67
Licensing 66
Remove 67
Trace log 67
O
Oracle
Archive logging 52
Configure
AIX 48
Batch file options 43
Database security 42
HP-UX 49
Linux 48
Override drives 44
Solaris 46
ASM disk utility 47
Listener 48
Windows 41
Data backup and protection scenarios 54
Complete tape backup 57
Replication 56
TimeMark 54
TimeMark Copy 55
TimeMark rollback 56
TimeView 55
Database design-virtual devices 54
Database mode conflicts
Linux 48
Snapshot Agents User Guide
77
Windows 41
File system support 36
Install 36
AIX 39
HP-UX 39
Linux 38
Requirements 36
Solaris 38
Windows 37
License 37
License 37
Protect and recover databases 54
Protect databases 54
Recover databases 54
Recovery scenarios 57
Disk failure 57
Manual recovery 59
Operator failure 58
User failure 57
Remove software 53
Restore backed-up database 58
Restore databases 58
Automatic recovery 59
Snapshot Copy 53
Test
Snapshot Copy 53
Trace Log
Windows 45
Unix
Add root user 50
Database groups 50
PATHs 51
Solaris 50
Oracle Listener
Solaris 48
P
Patches 3
R
Release Notes 3
Replication 1
S
Snapshot agents
and DiskSafe 3
In-band solutions 2
Installation overview 2
Out-of-band solutions 3
SQL Server 20
Command line interface 33
Configure 23
Add instance 24
Advanced options 26
Backup options 26
Batch files 28
Change instance information 24
Checkpoint only 27
Copy only 27
Database options 25
Database security 23
Database selection/exclusion 27
Default drives 29
Full backup 27
Full backup plus checkpoint 27
Remove instance 24
Snapshot Copy test 31
Transaction log backup 27
Transaction Log Backup directory 25
Windows authentication 24
Diagnostic X-ray 35
Install 20, 21
Licensing 21
Offline activation 21
Manual recovery 32
Remove 35
Status
.hisu file 30
Transaction Log Backup best practice 31
VMware 21
VMware environment 21
Support Portal 3
V
VSS
Advanced options 8
batch file options 9
Configure 7
Events 11
Install 2, 5
Silent install 5
Licensing 5
Remove 11
Run 10
Snapshot options 7
Snapshot View/TimeView 10
Snapshots/TimeMarks 10
Storage guidelines 4
78
Trace log 9
VMware 4
Writers 11
Z
ZeroImpact Backup Enabler 1
79