snap creator

NetApp® Snap Creator™ Framework 3.5.0

Installation and Administration Guide

NetApp, Inc.495 East Java DriveSunnyvale, CA 94089 USATelephone: +1 (408) 822-6000Fax: +1 (408) 822-4501Support telephone: +1 (888) 4-NETAPPDocumentation comments: [email protected] Web: http://www.netapp.com

Part number: 215-06466_A012 January 2012

Contents

Snap Creator overview ................................................................................ 7Architecture of Snap Creator ....................................................................................... 7

New features of Snap Creator ..................................................................... 9Security features of Snap Creator ............................................................ 11Snap Creator Integration .......................................................................... 15Snap Creator Policies ................................................................................. 17What Snap Creator Agent is ..................................................................... 19Snap Creator Agent Multithreading ........................................................ 21Preparing to install Snap Creator ............................................................. 23

Downloading Snap Creator software ........................................................................ 23

Creating a Data ONTAP user .................................................................................... 23

Installing Java on Snap Creator Server ..................................................................... 24

Pre-installation steps for Domino plug-in ................................................................. 24

Linux/Solaris/AIX specific settings .............................................................. 25

Pre-installation steps for Domino plug-in on Windows ................................ 25

Installing Snap Creator on Windows ....................................................... 27Installing Snap Creator on UNIX ............................................................. 29

Installing Snap Creator Server .................................................................................. 29

Installing Snap Creator Agent ................................................................................... 30

Uninstalling Snap Creator from Windows .............................................. 31Upgrading Snap Creator ........................................................................... 33

Upgrading from Snap Creator 3.4.0 .......................................................................... 33

Upgrading from Snap Creator 3.3.0 .......................................................................... 34

Upgrading Snap Creator GUI .................................................................................... 35

Information required to configure Snap Creator ................................... 37Oracle plug-in ............................................................................................................ 41

MySQL plug-in ......................................................................................................... 42

DB2 plug-in ............................................................................................................... 42

VMware (VIBE) plug-in ........................................................................................... 43

vCloud vApp backup and restore using VMware plug-in ............................. 45

VM backup and restore using VMware plug-in ............................................ 46

Sybase plug-in ........................................................................................................... 46

Table of Contents | 3

MaxDB plug-in ......................................................................................................... 49

Lotus Domino plug-in ............................................................................................... 51

SnapManager for Microsoft Exchange plug-in ......................................................... 53

SnapManager for Microsoft SQL Server plug-in ...................................................... 54

Archive log plug-in ................................................................................................... 55

Configuring Snap Creator Server ............................................................. 57Creating a configuration file using CLI .................................................................... 57

Creating a configuration file using GUI .................................................................... 57

Referencing ............................................................................................................... 58

Snap Creator Agent configuration ........................................................... 85Snap Creator Backup process ................................................................... 87

List of commands ...................................................................................................... 87

Running Snap Creator Server using CLI ................................................ 89Running Snap Creator Agent using CLI ................................................. 99Running Snap Creator using GUI .......................................................... 101

Creating a schedule ................................................................................................. 101

Creating multiple users ............................................................................................ 102

Job monitoring ......................................................................................................... 103

Viewing data and log details ................................................................................... 103

Performing restore using Snap Creator ................................................. 105Performing Volume restore ..................................................................................... 105

Performing Single file restore ................................................................................. 106

Performing VMware restore .................................................................................... 106

Performing restore with Domino plug-in ................................................................ 107

Performing Volume restore for Domino using CLI .................................... 108

Performing Volume restore for Domino using GUI ................................... 109

Performing Single file restore for Domino using CLI ................................ 109

Performing Single file restore for Domino using GUI ................................ 111

Using the Plug-in Framework to create custom plug-ins ..................... 113Troubleshooting Snap Creator issues ..................................................... 115

Logs ......................................................................................................................... 115

Troubleshooting Snap Creator GUI error ................................................................ 117

Troubleshooting Network issues ............................................................................. 118

Error messages ........................................................................................................ 119

Snap Creator examples ............................................................................ 189Copyright information ............................................................................. 195

4 | Snap Creator 3.5.0 Installation and Administration Guide

Trademark information ........................................................................... 197How to send your comments .................................................................... 199

Table of Contents | 5

Snap Creator overview

Snap Creator is a backup and recovery software solution that enables you to integrate Snapshottechnology with any application that is not supported by SnapManager products.

Snap Creator is platform and operating system independent. It provides application integrationthrough plug-ins that enable it to support any application on a storage system. Snap Creator uses theplug-ins to handle quiesce and unquiesce actions for a given application or database.

Snap Creator supports application plug-ins for Oracle, DB2, MySQL, Sybase ASE (Sybase), LotusDomino (Domino), SnapManager for Microsoft SQL Server, SnapManager for Microsoft Exchange,MaxDB, and VMware (vSphere and vCloud Director). Additional application plug-ins are availablethrough the Snap Creator Community.

Snap Creator provides a management interface for Snapshot technology, SnapVault, Open SystemsSnapVault, SnapMirror, Protection Manager, Operations Manager, and FlexClone technology.

Architecture of Snap CreatorSnap Creator consists of a server and agent layer. The GUI, configuration, and CLI reside in theserver layer. The agent runs remotely or locally and allows the Snap Creator Server to send quiesceor unquiesce operations to a given database.

The communication layer from the agent to the server is Simple Object Access Protocol (SOAP) overHTTP.

The following illustration shows the Snap Creator architecture:

7

New features of Snap Creator

Snap Creator 3.5.0 introduces new features such as support for MaxDB plug-in, GUI support formultiple users.

The following are the new features:

• Compatibility with Data ONTAP 8.1 Cluster-Mode and 7-Mode• Data ONTAP 8.1 Cluster-Mode support for the following plug-ins:

• Oracle• DB2• Domino• Sybase• MaxDB• MySQL• VMware

• Enhancements to Domino plug-in

• Support for IBM-AIX (64-bit)• Ability to disable replication• Up to the minute restore• No log option

• Open Systems SnapVault support with Snap Creator Agent• Support for recursive archive log deletion within subdirectories• DataFabric Manager server proxy through GUI• GUI support for job monitoring• Ability to set all configuration parameters through GUI• UNIX services• GUI support for Data ONTAP 8.1 Cluster-Mode

• GUI prompts the user to enter cluster credentials if it discovers that the storage system detailsentered are of a Cluster-Mode Vserver.

• GUI detects SnapMirror relationships and prompts the user to enter destination Vserver andcluster authentication details.

• Users can see volume, volume clone, and Snapshot data for Cluster-Mode configurations.

• EMS logging for ASUP data mining• Cluster-Mode EMS logging for ASUP data mining• Operating system or File System plug-in

9

Security features of Snap Creator

Snap Creator provides security features, such as RBAC for Storage controller, Host security for SnapCreator Agent, and RBAC for Snap Creator users through GUI.

RBAC for Storage controllerIf you are not using DataFabric Manager server proxy, you need a user name and password tocommunicate with storage controllers. Passwords can be encrypted so that they are not saved in cleartext.

The following are the minimum permissions that Snap Creator might require:

• login-* (for all login access) or login-http-admin (to only allow API login)• api-snapshot-* (always required)• api-system-* (always required)• api-ems-* (always required)• api-snapvault-* (required only for SnapVault management)• api-snapmirror-* (required only for SnapMirror management)• api-volume-* (required for volume clones)• api-lun-* (required for volume and LUN clones)• api-cg-* (required for Consistency Group Snapshot copies)• api-nfs-* (required for exporting cloned volumes by using NFS)• api-file-* (required for listing the files during single file restore)• api-license-* (required for retrieving license information)• api-net-* (required for the VMware plug-in)

Note: Do not use the root user. You should create a backup user with only the necessary APIpermissions.

Network communications are done through HTTP (80) or HTTPS (443), so you must have one orboth of these ports open between the host where Snap Creator runs and the storage controllers. Auser must be created on the storage controllers for authentication purpose. In the case of HTTPS,ensure that the user is enabled and configured on the storage controllers.

Snap Creator Agent securitySnap Creator uses host security to allow only authorized hosts to access the agent. Additionally, itchecks the user name or password if you are not using a Snap Creator Server to communicate withthe agent. This feature allows you to specify multiple host lines. To restrict access for third partyapplications through SOAP, the agent offers a user/password authentication.

If a command contains the path of the Snap Creator installation directory, it is blocked.

RBAC for Snap Creator users through GUIYou can create and manage multiple user accounts within Snap Creator GUI. The existing user in theGUI (which is created during installation or profile setup) acts as a super user and has access to the

11

complete system. The ability to assign a set of profiles restricts a user to operate in a defined area.This is useful in a multi-tenant environment.

There are four types of users:

• Super user: Has access to everyone's work space and is the only user that can create users andprofiles. The super user can perform actions, such as the following:

• Adding new user by providing user name and password• Changing password for a user• Assigning a set of GUI actions to the user• Reviewing the list of users and the profiles and actions that they can perform

• Admin user: Has access only to a set of profiles and can perform all actions without anyrestrictions only on those profiles.

• Read-only user: Has access to a set of profiles but can only perform a set of read-onlyoperations. This user cannot perform write or execute operations like creating a Snapshot copy orcreating a configuration.

• Custom user: Has access to a set of profiles and a set of actions.

The user can be assigned the following list of GUI actions:

• Add Schedule• Administrator• Archive Log• Create Configuration• Delete Configuration• Delete Schedule• Delete Snapshot• Discover• Download Configuration• LUN Clone• Quiesce• Read Only• Rename Configuration• Rename Snapshot• Restore• Run Schedule• Scdump• Snapshot• Unquiesce• Update Configuration• Update Schedule• Upload Configuration• Volume Clone


Note: Multiple users can simultaneously sign in to the GUI and perform operations but it isrecommended that not more than 10 users are signed in at the same time.

Security features of Snap Creator | 13

Snap Creator Integration

Snap Creator integrates either fully or optionally with other software products and technologies.

• Optionally integrates with both SnapDrive for UNIX (SDU) and SnapDrive for WindowsIf SnapDrive is used instead of Manage ONTAP Solution, which sends a call to the storagecontroller for the Snapshot copy, Snap Creator runs SnapDrive.

• Optionally uses SnapVault directly instead of Protection Manager to transfer Snapshot copies tosecondary

• Snapshot, SnapVault, SnapMirror, LUN cloning, volume cloning, and igroup mapping using DataONTAP API.

• Any application or database that runs in an open systems environment (you can write theapplication backup script or plug-in if one does not exist)

• NetBackup, CommVault, or any backup software with CLI commands• Optionally integrates with Operations Manager for monitoring (the ability to create events in

Operations Manager)• Optionally integrates with Protection Manager to perform secondary backup (Snap Creator

backup copies can be registered in Protection Manager)• Optionally integrates with Open Systems SnapVault

Note: Snap Creator 3.5.0 does not support SnapVault, Operations Manager, Protection Manager,and Open Systems SnapVault on Data ONTAP 8.1 Cluster-Mode.

15

Snap Creator Policies

A policy defines the number of Snapshot copies that you want to keep and the Snapshot copy age.Snap Creator policies are user-defined Snapshot copy retentions that apply to Snapshot copies onprimary storage and SnapVault Snapshot copies on secondary storage.

You must define at least one policy in the NTAP_SNAPSHOT_RETENTIONS configurationparameter. For SnapVault, you can associate the same policy with different SnapVault retention.

For example, if you want to create daily Snapshot copies and retain them for seven days on primarystorage and one month on secondary storage, use the following options:

NTAP_SNAPSHOT_RETENTIONS=daily:7

NTAP_SNAPVAULT_RETENTIONS=daily:28

You can also specify the minimum age of a Snapshot copy (in days) to ensure that Snapshot copiesare deleted only if they are older than the minimum age, regardless of how many Snapshot copiesexist in a given volume. Using the preceding example of seven days for Snapshot copies and onemonth for SnapVault Snapshot copies, use the following options:

NTAP_SNAPSHOT_RETENTION_AGE=7

NTAP_SNAPVAULT_RETENTION_AGE=28

Additionally, you can specify the Snapshot copy deletion by age only using the following option:

NTAP_SNAPSHOT_DELETE_BY_AGE_ONLY=Y

Note: Although you can define multiple policies, Snap Creator can run only one policy at a time.

The maximum age value is a global parameter and it applies to all the policies. To configure anadditional weekly policy, define it and then call it in Snap Creator once a week using Cron or taskmanager with SNAP_TYPE set to Weekly.

17

What Snap Creator Agent is

The Snap Creator Agent is a lightweight daemon which runs remotely or locally and allows the SnapCreator Server to send quiesce or unquiesce operations to a given database.

The Snap Creator Agent remotely handles operations on application through the plug-ins. All SnapCreator configurations are stored centrally on the Snap Creator Server and all backup jobs can bescheduled from the same host. This provides a single pane of glass (SPOG) for backup and restore.

The following illustration shows the Snap Creator Agent architecture:

Snap Creator uses the Snap Creator Agent, which runs as a daemon, to quiesce the application. Thedefault port used is 9090, but any other port can also be used.

SOAP is used over the HTTP for communication. Based on a WSDL, any SOAP client can interactwith the agent. Currently, Apache CXF (for Java) and PowerShell (for Windows) can be used. Thesupported application plug-ins are built into the agent.

Other community plug-ins are available as source codes and can be added to the /plug-insdirectory. In addition to the application plug-ins, all PRE commands, POST commands, and APPcommands can be executed remotely through the agent. This provides the ability to mount filesystems or to perform additional application processing remotely. The agent has an access fileunder /path/so/scAgent_v<#>/config/agent.conf where certain commands are allowed torun. By default, all commands are denied. This means that only the built-in or community plug-ins

19

can execute commands through the agent. PRE or POST scripting commands or scripts must beallowed in the agent.conf.

Note: Snap Creator 3.5.0 does not support Snap Creator 3.3.0 agent.

The following illustration shows the Snap Creator Agent communication:


Snap Creator Agent Multithreading

The Snap Creator Agent can handle parallel requests by allowing the Snap Creator Agent todistribute requests coming from the agent itself.

The following illustration shows the different types of deployment:

Simple deployment

In simple deployment, Snap Creator Server opens a connection to the Snap Creator Agent and sendsthe requests. Unless Snap Creator Server stops, the connection is open and the agent is blocked fromaccepting further requests.

Deployment using a Watchdog

After accepting the Snap Creator request to quiesce the database, Snap Creator Agent creates aseparate process (watchdog). This watchdog inherits the environment and all the settings of theparent process and unquiesces the database after a configured timeout.

In this scenario, the agent is blocked until the Snap Creator Server stops or explicitly closes theconnection.

Multithreaded deployment using Watchdog

21

In the intended multithreaded deployment, the Snap Creator Agent immediately creates an additionalprocess (SC-A') and passes the "communication responsibility" (req') to this process. This newlycreated process inherits the basic Snap Creator Agent settings. Snap Creator Server communicateswith this process. If configured, this process creates a watchdog when the quiesce operation is called.

After the additional process is created, the Snap Creator Agent is able to accept additional requests.

Note: Multi-threaded agent is not supported on Windows platform


Preparing to install Snap Creator

Before installing Snap Creator, you must perform certain tasks, such as downloading the SnapCreator software, creating a Data ONTAP user, and installing Java on Snap Creator.

Downloading Snap Creator softwareYou can download the Snap Creator software from the NetApp Support Site. Snap Creator is listed inthe Software Download section under Snap Creator Framework.

Steps

1. Select the version of Snap Creator to download by selecting View & Download.

2. At the bottom of the page under the Software download instructions, click CONTINUE.

3. Read and accept the End User License Agreement by clicking Accept.

4. Select the operating system and bit level of the software package(s) to download.

Related information

The NetApp Support Site-support.netapp.com

Creating a Data ONTAP userSnap Creator uses the Data ONTAP API to communicate with the storage system. Therefore, it isrequired to create a new role, group, and user. The role is assigned to the group and the groupcontains the user.

About this task

These tasks must be completed using the Data ONTAP CLI (SSH, console connection, or telnet).

Note: Copy and paste the given commands into a text editor and verify before pasting it in the CLIconsole.

Steps

1. Create a role defining the rights required for Snap Creator on the storage system by entering thefollowing command:

23

http://support.netapp.com/

useradmin role add rolename -a login-*,api-snapshot-*, api-system-*,api-ems-*,api-snapvault-*,api-snapmirror-*, api-volume-*,api-lun-*,api-cg-*,api-nfs-*,api-file-*, api-license-*, api-net-*

2. Create a new group on the storage system and assign the previously created role to the group byentering the following command:

useradmin group add groupname -r rolename

3. Create a user account in the previously created group that will be used for Snap Creator byentering the following command:

useradmin user add username -g groupname

4. Enter the password for the account.

Note: These steps must be performed once for each controller where Snap Creator is used.

Installing Java on Snap Creator ServerFor the Snap Creator GUI to function, Java must be installed on the Snap Creator Server. The SnapCreator GUI is Java based and uses the NetApp Web Framework (NWF). Java Runtime Environment(JRE) 1.6 or higher must be installed on the Snap Creator Server.

Steps

1. Download Java from the Java website.

Note: The version of Java installed must match the version of Snap Creator installed.

2. Verify the version of java by entering the following command: java -version

Example

C:\Documents and Settings\Administrator>java -versionjava version "1.7.0_04-ea"Java(TM) SE Runtime Environment (build 1.7.0_04-ea-b01)Java HotSpot(TM) Client VM (build 23.0-b03, mixed mode, sharing)

The output of the command lists the installed version of Java. If the Java installation is 64-bit thatwill be listed. If there is no mention of the bit-level then the installation is 32-bit.

Pre-installation steps for Domino plug-inThe Domino plug-in is included as part of the Snap Creator installation. There are a few pre-installation steps to be performed depending on the operating system used.


Linux/Solaris/AIX specific settingsLotus Domino for Linux is available only as a 32-bit application, so regardless of the server bit-levelthe 32-bit version of Snap Creator must be used to support Lotus Domino.

Domino on Linux and Solaris cannot be run as root. As a result Snap Creator, Snap Creator Server,Agent, and GUI cannot be run as root. It is recommended that Snap Creator is run using the sameaccount that was used to install Domino.

For the Domino plug-in to work properly, there are a series of symbolic links that must be created.These three symbolic links (symlinks) must be made to Domino's shared object files for the plug-into work properly. After installing Domino to the default location, you can copy and paste thefollowing commands into the environment:

ln -s /opt/ibm/lotus/notes/latest/linux/libxmlproc.so /usr/lib/

libxmlproc.so

ln -s /opt/ibm/lotus/notes/latest/linux/libndgts.so /usr/lib/libndgts.so

ln -s /opt/ibm/lotus/notes/latest/linux/libnotes.so /usr/lib/libnotes.so

Pre-installation steps for Domino plug-in on WindowsThe path to the Domino binary files must be added into the Environmental Variables for Windows.This should be the same path as the Notes_ExecDirectory listed in the Domino options table.

About this task

Note: If you perform these steps after Snap Creator is installed you must restart the Snap Creatorservice(s).

Steps

1. Right-click My Computer and select Properties (If My Computer is not on the Desktop it canusually be found in the Start menu).

2. Click the Advanced tab in Windows 2003 or the Advanced system settings task in Windows2008.

3. Click Environmental Variables.

4. Use a system variable. There are two sections: User variables and System variables. With a uservariable the Snap Creator service must be run as that particular user.

5. Locate and select PATH, then click Edit.

6. Append ; after the last value then add the Domino path.

7. Click Ok on each window until you exit to the Desktop.

Preparing to install Snap Creator | 25

Installing Snap Creator on Windows

You can install Snap Creator Server and Snap Creator Agent on Windows using the Windowsinstaller.

Steps

1. Extract the .exe file to C:\.

2. Run the install package executable and proceed through the installation wizard.

If you want to enable job monitoring, select the Enable Job monitor checkbox. The Job monitorsize should be between 1 and 1000.

Note: Do not close any window until the installation is complete.

Related tasks

Downloading Snap Creator software on page 23

Installing Java on Snap Creator Server on page 24

Creating a Data ONTAP user on page 23

27

Installing Snap Creator on UNIX

Snap Creator installation for UNIX differs from Windows in that the software package is anexecutable that when extracted contains both the Snap Creator Server and the Snap Creator Agent.

UNIX Services (agent/server) feature offers a start script for the Snap Creator Agent and SnapCreator Server. The start scripts are written in UNIX shell script (bourne shell) and are designed torun on all UNIX environments supported by Snap Creator.

Installing Snap Creator ServerYou can install Snap Creator Server on UNIX. The Snap Creator Server is designed to run on anyopen systems platform.

Steps

1. Extract the .tgz file to /usr/local. Change directory to the Snap Creator Server rootdirectory/path/to/scServer_v<#>.

2. Run Snap Creator setup by entering the following command:

./snapcreator --profile setup.

Note: The Snap Creator executable should already be configured upon extraction with theproper permissions to be executed. If profile setup command does not work, the permissionsmust be added by running following command:chmod 755 snapcreator

3. Accept the EULA license agreement.

4. Optional: Enter the serial number of the storage system that will be used with Snap Creator.

Note: The intent is to add the controller serial number applicable to the Snap Creatorapplication. The Snap Creator application archives this information for later use. The user canrun -version command to retrieve this serial number information when contacting technicalsupport to open a Snap Creator case.

5. To enable GUI job monitoring, enter

y

6. Enter the job monitor size.

Note: The Job monitor size should be between 1 and 1000.

7. Enter the user name and password for the administrative user for the GUI.

8. Start the Snap Creator GUI by following the instructions provided on the screen.

29

9. To start Snap Creator GUI, type the following URL in the web browser: http://<HostName>:<port> where:

• HostName is the host name or IP address of the Snap Creator Server• Port is the port number where the Snap Creator Server is running. By default this is port 8080.

Related tasks

Downloading Snap Creator software on page 23

Installing Java on Snap Creator Server on page 24

Creating a Data ONTAP user on page 23

Installing Snap Creator AgentThe Snap Creator Agent is designed to run on any open systems platform. If the agent is not required,you can choose to run the Snap Creator Server on the application server locally.

Steps

1. Extract the .tgz file to /usr/local.

2. Change directory to the Snap Creator Server root directory /path/to/scAgent_v<#>.

3. Run Snap Creator setup by entering the following command:

./snapcreator --profile setup

Snap Creator Agent setup on UNIX configures the /path/to/scAgent_v<#>/xscript andprints usage information.

4. Install the agent.

The Snap Creator Agent has the ability to run as a daemon under UNIX. The agent uses either thedefault port 9090 or a user-specified port. To set a non-default port number, configure thefollowing environment variable: SC_AGENT_PORT.

If the SC_AGENT_PORT environment variable is not set, then the agent defaults to port 9090.

To ensure that the agent starts when rebooting, a start script must be set up under /path/to/rc2.d. Start scripts must begin with S9x (S99scagent). The start script should contain thefollowing:

• /path/to/scAgent_v<#>/bin/scAgent start

This command is run to start the agent manually.• /path/to/scAgent_v<#>/bin/scAgent stop

This command is run to stop the agent manually.• /path/to/scAgent_v<#>/bin/scAgent status

This command is run to query the agent status.


Uninstalling Snap Creator from Windows

You can uninstall Snap Creator from the Windows start menu.

Before you begin

• You must have backed up the log and config files to retain the existing configuration.• If the server is manually started from the console, you must have stopped it.

Step

1. Select All programs > Snap Creator > Uninstall NetApp Snap Creator Framework.

31

Upgrading Snap Creator

You can upgrade to Snap Creator 3.5.0 by adding parameters to the Snap Creator configuration file.You can also upgrade the Snap Creator GUI after installing Snap Creator 3.5.0.

Upgrading from Snap Creator 3.4.0You can upgrade to Snap Creator 3.5.0 by adding parameters to the Snap Creator 3.4.0 configurationfile.

Step

1. Add the following parameters to the Snap Creator 3.4.0 configuration file:

LOG_TRACE_ENABLE=Y

ALLOW_IP_ADDR=N

CMODE_CLUSTER_USERS=

CMODE_CLUSTER_NAME

CMODE_SNAPSHOT_FORCE_DELETE=Y

FS_NAME=

META_DATA_VOLUME=

JAVA_HOME=

JVM_ARGS=

JAVA_CLASSPATH=

PERL_HOME=

PERL_OPTS=

PYTHON_HOME=

PYTHON_OPTS=

ARCHIVE_LOG_RECURSIVE_SEARCH

33

Upgrading from Snap Creator 3.3.0You can upgrade to Snap Creator 3.5.0 by adding parameters to the Snap Creator 3.3.0 configurationfile.

Step

1. Add the following parameters to the Snap Creator 3.3.0 configuration file:

CONFIG_TYPE - PLUGIN|STANDARD

USE_PROXY - (Y|N)

NTAP_CONSISTENCY_GROUP_WAFL_SYNC - (Y|N)

NTAP_SNAPSHOT_RESTORE_AUTO_DETECT - (Y|N)

MOUNT_CMD<##>

UMOUNT_CMD<##>

APP_DEFINED_CLONE - (Y|N)

LOG_TRACE_ENABLE=Y

ALLOW_IP_ADDR=N

CMODE_CLUSTER_USERS=

CMODE_CLUSTER_NAME=

CMODE_SNAPSHOT_FORCE_DELETE=Y

FS_NAME=

META_DATA_VOLUME=

JAVA_HOME=

JVM_ARGS=

JAVA_CLASSPATH=

PERL_HOME=

PERL_OPTS=

PYTHON_HOME=

PYTHON_OPTS=


Note: To upgrade from versions prior to Snap Creator 3.3.0, contact technical support.


Upgrading Snap Creator GUIYou can upgrade the Snap Creator GUI by running the upgrade command.

Before you begin

• You must have stopped Snap Creator Server .• You must have backed up the profiles in the scServerX.Xx/configs folder.• You must have backed up the Snap Creator database folder scServerX.Xx/gui/

snapcreator.• If using Windows, you must have uninstalled the current Snap Creator version.

Steps

1. Install new Snap Creator version.

2. Stop the Snap Creator Server service on Windows.

3. Copy the backed up profiles to the new scServerX.Xx/configs folder.

4. Delete the newly created Snap Creator database folder scServerX.Xx/gui/snapcreator.

5. Copy and paste the backed up Snap Creator database folder to scServerX.Xx/gui directory.

6. Open CLI and change to directory scServerX.Xx/gui.

7. Run the upgrade command java -jar snapcreator.jar -upgrade.

8. Start Snap Creator Server.

Upgrading Snap Creator | 35

Information required to configure Snap Creator

Snap Creator 3.5.0 supports Oracle, MySQL, DB2, VMware, Sybase ASE, Domino, MaxDB,SnapManager for SQL Server, and SnapManager for Exchange plug-ins. Community plug-ins are notincluded in the package and must be downloaded separately.

The following table lists the plug-in parameters, settings, and the description:

Parameters Setting Description

APP_NAME oracle, db2, mysql, vibe,sybase, domino, smsql, sme,maxdb <plug-in>

Determines which applicationis being backed up. SnapCreator has built-in support forthe listed applications. You caneither use APP_NAME orconfigureAPP_QUIESCE_CMDXX,APP_UNQUIESCE_CMDXX,and PRE_EXIT_CMDXX. Ifthe application is not directlysupported in Snap Creator, youcan use a plug-in or run yourown application quiesce/unquiesce commands or scripts.<PLUG-IN>: Copy the plug-into the /path/to/scServer|scAgent/plug-ins directoryand specify your plug-in in theAPP_NAME parameter.Commands or Scripts:APP_QUIESCE_CMD01=/

path/to/quiesceCMD

APP_UNQUIESCE_CMD01=/

path/to/unquiesceCMD

PRE_EXIT_CMD01=/

path/to/unquiesceCMD

37


APP_IGNORE_ERROR (Y|N) Determines if Snap Creatorshould ignore errors fromapplication plug-ins. This isuseful when the user wants toback up multiple databases anddoes not want to stop thebackup based on quiesce orunquiesce of single databasefailing.

APP_DEFINED_RESTORE (Y|N) Enables application basedrestores. In the event of arestore, Snap Creator sends arequest to the application plug-in and the plug-in handles therequest.

APP_AUTO_DISCOVERY (Y|N) Enables application autodiscovery. Snap Creator sendsdiscover request to applicationplug-in and the plug-in is thenresponsible for the discovery ofthe storage configuration. Thiscan be done dynamically orpersistent with theAPP_CONF_PERSISTENCEparameter if information is tobe saved to the config file. Thisparameter is similar toVALIDATE_VOLUMES butallows one through plug-inframework to add discoverfunctionality to any applicationplug-in.

APP_CONF_PERSISTENCY (Y|N) Enables auto discovery to bepersistent, which meanschanges are dynamicallyupdated in config file.



VALIDATE_ VOLUMES DATA Snap Creator validates that allvolumes where the databaseresides are part of the backup.Currently, there are somelimitations. Only NFS issupported. Currently, thisoption checks data files only forthe supported databases.

FS_NAME <plug-in> Determines which plug-in isbeing used for file systemoperations.

META_DATA_VOLUME Allows for Snapshot copy ofspecified volume to occur afterunquiesce. This can be valuablefor certain plug-ins whereSnapshot copy of data must betaken at different times. Themeta data volume must not beonly volume specified:controller1:volume1

APP_DEFINED_CLONE (Y|N) The built-in cloning abilities ofSnap Creator will be ignored.Instead the plug-in isresponsible for handling allclone activities including vol orLUN clone creation anddeletion. The built-in plug-insdo not this type of clone.

JAVA_HOME Text Setting which points to the JavaVirtual Machine which shouldbe used for executing .classand .jar files. If set,$JAVA_HOME/bin/java willbe used, otherwise just java torun the .class/.jar file #

Information required to configure Snap Creator | 39


JVM_ARGS Text Setting to control the JavaVirtual Machine whenexecuting native Java .classor .jar files. The defaultsetting is -Xms32M -Xmx128M

JAVA_CLASSPATH Text Setting which defines the Javaclasspath. Per default,plugins/native isconfigured and can becompleted with thisenvironment variable, whichwill be appended to the default.

PERL_HOME Text Setting which points to the Perlinterpreter which should beused for executing .pl files. Ifset, $PERL_HOME/bin/perlwill be used, otherwise just perlto run the .pl file

PERL_OPTS Text Setting to control the Perlinterpreter when executingnative Perl files. Options forsettings additional includedirectories (-I) etc. can bepassed to the Perl interpreter.

PYTHON_HOME Text Setting which points to thePython interpreter which shouldbe used for executing .py files.If set, $PYTHON_HOME/pythonwill be used, otherwise justpython to run the .py file

PYTHON_OPTS Text Setting to control the Pythoninterpreter when executingnative Python files.


Oracle plug-inThe Oracle plug-in supports only Oracle 10g database or higher. The Oracle plug-in uses SQL*Plusto communicate with the database.

The following table lists the Oracle plug-in parameters, the settings, and the description:

Parameter Settings Description

APP_NAME oracle The application name

ORACLE_DATABASES A list of Oracle databases andthe user name, that is,db1:user1;db2:user2.

SQLPLUS_CMD The path to the sqlpluscommand.

CNTL_FILE_BACKUP_DIR The path to the directory wherethe user should store backupcontrol files (Oracle user musthave permissions).

ORA_TEMP The path to a directory to storetemp file, that is, /tmp (Oracleuser must have permissions).

ARCHIVE_LOG_ONLY (Y|N ) Informs Oracle Plug-in to onlyperform a switch log. Thissetting is useful if you arehandling archive logs separatefrom data backup.

ORACLE_HOME The path to the oracle homedirectory

ORACLE_HOME_<SID> PATH to Oracle homedirectory for a given SID.When backing up multipledatabases it might be importantto specify more than one Oraclehome.



ORACLE_EXPORT_PARAMETERS

(Y|N ) The ORACLE_HOME andORACLE_SID environmentparameters are exported usingthe export command. This isapplicable only in UNIX orLinux based environment.

MySQL plug-inThe MySQL plug-in supports MySQL 5.x. The MySQL plug-in uses Net-MySQL to communicatewith the database.

The following table lists the MySQL plug-in parameters, the settings, and the description:


APP_NAME mysql The application name

MYSQL_DATABASES A list of MySQL database(s)and the user name/passwordthat is, db1:user1/pwd1;db2:user2/pwd2

HOST Name of the host where thedatabases are located: localhost

PORTS (Y|N) A list of database(s) and theports they are listening on, thatis, db1:3307;db2:3308

MASTER_SLAVE Specifies the database(s) to bepart of the MASTER/SLAVEenvironment.

DB2 plug-inThe DB2 plug-in supports DB2 9.x. The DB2 plug-in uses the db2 command to communicate withthe database.

The following table lists the DB2 plug-in parameters, the settings, and the description:


APP_NAME db2 The application name



DB2_DATABASES A list of db2 database(s) andthe user name, that is,db1:user1;db2:user2

DB2_CMD The path used by the db2command to interact with thedatabase.

Note: For Windows, youmust first give a path todb2cmd.exe For example

UNIX:DB2_CMD=/ibm/sqllib/bin/db2

Windows: DB2_CMD= Z:\IBM\SQLLIB\BIN

\db2cmd.exe -c -w -i

Z:\IBM\SQLLIB\BIN

\db2.exe

VMware (VIBE) plug-inSnap Creator supports back up of VMware VMs and vApps through VMware plug-in. VMware plug-in is an integrated plug-in for both VMs with vSphere and vApps with vCloud.

Snap Creator 3.5.0 supports VMware vSphere 4.x, 5 and VMware vCloud Director 1.0, 1.5.

You should be aware of the following considerations when using VMware plug-in:

• The VMware plug-in is supported only on Windows and Linux. If the user is using a non-Windows or non-Linux Snap Creator Server, they need a Snap Creator Windows/Linux agent torun the VMware plug-in.

• VMware HA with VMware plug-in is not tested and is not supported.• Consistency group Snapshot copies with VMware plug-in is not tested and is not supported.• VMware plug-in does not support Raw Device Mapping.• After restore operations are complete, user must run a Snap Creator backup of the restored VMs

and vApps to ensure the new environment is cleaned up appropriately and all VMware Snapshotcopies are removed.

• If the plug-in is not able to clean up VMware Snapshot copies and displays an error, user mustremove the VMware Snapshot copies manually. Plug-in cannot guarantee 100% VMwareSnapshot copy removal and it is a known VMware issue.

• VMware plug-in supports only 32-bit Snap Creator with 32-bit Linux system and 64-bit SnapCreator with 64-bit Linux system.


The following table lists the VMware plug-in parameters, the settings, and the description:

Parameter Description

VIBE_VCLOUD_IPADDR IP addresses or hostname(s) of the vCloudDirector to log into (vCloud ONLY)

VIBE_VCLOUD_USER User name to log in to the vCloud Director(vCloud ONLY). You must set @<org> or@system (top level vCloud database) Example:VIBE_VCLOUD_USER=administrator@system

Note: vCloud Director system administratoruser name must be used to perform backup orrestore. Backup or restore fails if the user isan organization admin or any other user.

VIBE_VCLOUD_PASSWD Password associated to the VCLOUD_USERspecified (vCloud ONLY)

VIBE_VCENTER_USER User name to use toog in to vCenter

VIBE_VCENTER_PASSWD Password associated to the VCENTER_USERspecified

VIBE_VCLOUD_NAMES List of Organization, vDC and vApp objectnames to backup (vCloud ONLY)

Example:VIBE_VCLOUD_NAMES=ORG:VDC1,VDC2:VAPP1,VAPP2;ORG2:VDC3:;ORG3::VAPP6

VIBE_VSPHERE_NAMES List of Datastores and VMs to backup pervCenter (vSphere ONLY) Example:VIBE_VSPHERE_NAMES=VCENTER1:DS1:VM1;VCENTER2;DS2,DS3:;VCENTER3::VM4

VIBE_TRIM_VSPHERE_NAMES List of VMs to remove from backup per vCenter(vSphere ONLY) Example:VIBE_TRIM_VSPHERE_NAMES=VCENTER1:VM99;VCENTER2:VM5,VM12

VIBE_RESTORE_INTERVAL Time between each restore check (default: 30seconds)

VIBE_RESTORE_TIME Total time to wait for complete restore (default:3600 seconds)



VIBE_VMWARE_SNAPSHOT Take a VMware Snapshot copy during backup(default: Y)

VIBE_NOPING Do not ICMP ping VMware or storagecontrollers (default: N)

VIBE_DYNAMIC_VOLUMES_UPDATE If set to 'N', does not perform dynamic volumeupdate, which you have to set VOLUMES,SNAPVAULT_VOLUMES,SNAPMIRROR_VOLUMES andNTAP_DFM_DATA_SET manually (default:not set)

vCloud vApp backup and restore using VMware plug-inSnap Creator 3.5.0 supports backup of vCloud vApps through VMware plug-in. vApp / VM backupsare taken by this plug-in through the vCloud Director (vCD) API and vSphere API which areinvoked on the VMware vCloud Director and VMware vCenter server respectively.

For vApp backup or restore, the user must provide the following details in the configuration file:

• vCloud IP and credentials• vCloud Organizations, vDCs and vApp names

Note: If more than one vCenter is attached to vCloud, then the password for the all vCentersshould be same.

The following are important data points regarding vCloud backup and restore processes:

• The backup and restore processes for both VMware and vCloud are very similar except thediscovery process, where vCloud backups require additional discovery of the vCloud Director(vCD) metadata using REST APIs.

• You should provide with details of the vCloud with the organizations, vDCs or vApps to bebacked up.

• If a vDC is listed, all the vApps in the vDC are backed up.• The vCloud module discovers VMs associated to any vApp that need to be backed up and puts

them on a backup list.• If a vApp selected for backup is contained within an Organization or vDC also selected for

backup, it will be backed up only once.

Note: For Virtual Machine File System(VMFS) restore operations through the VMware plug-in,there must be enough space in the volume to create a LUN clone that is equal to the size of theLUN.

Note: User must close and reopen the config file in the GUI before running restore on a VMwareconfiguration because volumes discovered are not updated automatically.


VM backup and restore using VMware plug-inSnap Creator supports backup of VMware VMs through VMware plug-in. VM backups are takenthrough the vSphere API which are invoked on the VMware vCenter server.

For VM backup, the user must provide the following details in the configuration file:

• vCenter IP/hostname and credentials• vSphere VM(s) and datastore names

For restore operations, you should provide the backup parameters and the Snapshot copy name to beused for the restore.

You should keep the following points in mind when performing VMware backup and restoreprocesses:

• If a VM is listed and is not available, the plug-in displays an error message. It will not be able torestore a lost VM even if it is backed up.

• If a Datastore is listed, all the VMs in the Datastore will be backed up.• Only the listed VMs or VMs located on the Datastores specified will be backed up.• If a VM selected for backup is contained within a Datastore that is also selected for backup, it

will be backed up only once.• This plug-in supports both NFS and VMFS Datastores.• VM restores on an NFS Datastore use a Single File SnapRestore (SFSR) on the storage system,

which avoids host copies.• To restore VM on a VMFS Datastore, perform the following steps:

1. Use FlexClone or LUN clone of the LUN contained in a specific restore Snapshot copy.

2. Map that to the cluster.

3. Use vCenter API calls to copy contents from the Snapshot VMFS datastore to the originalVMFS datastore.

Sybase plug-inThe Sybase plug-in uses the isql command to interact with the Sybase database. The Sybase plug-incan quiesce one or more databases. The Sybase ASE plug-in supports Sybase ASE 12.5.x, SybaseASE 15.0.x, and Sybase ASE 15.5.

The following table lists the Sybase plug-in parameters, the settings, and the description:

Parameter Setting Description

SYBASE_SERVER The Sybase data server name (-S option on isql) Example:SYBASE_SERVER=p_test



SYBASE_DATABASES The list of databases within theinstance to back up. Format isDB1:USER:PASSWD;DB2:USER:PASSWD. The masterdatabase is added. If a databasenamed"+ALL" is used, thendatabase autodiscovery is usedand the sybsyntax,sybsystemdb, sybsystemprocsand tempdb databases areexcluded. Encrypted passwordsare supported ifNTAP_PWD_PROTECTIONis set.

Example:SYBASE_DATABASES=DBAtest2:sa/53616c7465645f5f76881b465ca8ce3745c239b60e04351e

Example:SYBASE_DATABASES=+ALL:sa/53616c7465645f5f76881b465ca8ce3745c239b60e04351e

SYBASE_DATABASES_EXCLUDE

(Y|N ) Allows databases to beexcluded if the +ALL constructis used, use ';' to allow multipledatabases. Example:SYBASE_DATABASES_EXCLUDE=pubs2;test_db1.

SYBASE_TRAN_DUMP Allows post Snapshot Sybasetransaction dump to beperformed. Each databaserequiring a txn dump needs tobe specified. Format is"DB1:PATH;DB2:PATH"where path is a directory.Example:SYBASE_TRAN_DUMP=pubs2:/sybasedumps/pubs2



SYBASE_TRAN_DUMP_FORMAT

Allows the user to specify thedump naming convention.Three "keys" can be specified,%S = Instance name fromSYBASE_SERVER %D isdatabase fromSYBASE_DATABASES and%T is a unique timestamp.Default format is %S_%D_%T.cmn Example:SYBASE_TRAN_DUMP_FORMAT=%S_%D_%T.log

SYBASE_TRAN_DUMP_COMPRESS

Allows native Sybasetransaction dump compressionto be enabled. Example:SYBASE_TRAN_DUMP_COMPRESS=Y

SYBASE_ISQL_CMD Defines the path to the "isql"command to be used. Example:SYBASE_ISQL_CMD=/opt/sybase/OCS-15_0/bin/

isql

SYBASE The location of the Sybaseinstall. Example: SYBASE=/sybase

SYBASE_LOGDIR Defines the directory whereSnap Creator logs are placed.Example:SYBASE_LOGDIR=/usr/local/ntap/

scServer3.3.0/logs

SYBASE_MANIFEST Specifies the databases forwhich the manifest file shouldbe created along with thelocation where the manifest fileshould be placed. Example:SYBASE_MANIFEST=DBAtest2:/t_inf_nzl_devs/



SYBASE_MANIFEST_FORMAT

Allows the user to specify themanifest file namingconvention. Three "keys" canbe specified: %S = Instancename fromSYBASE_SERVER, %D isdatabase fromSYBASE_DATABASES, and%T is a unique timestampwhich is the same as used forSnapshot naming. Defaultformat is %S_%D_%T.manifest Example:SYBASE_MANIFEST_FORMAT=%S_%D_%T.manifest

SYBASE_MANIFEST_DELETE

(Y|N ) Allows the manifest to bedeleted once the Snapshot hasbeen performed. The manifestfile should be captured withinthe Snapshot so it is alwaysavailable with the backup.Example:SYBASE_MANIFEST_DELETE=Y

MaxDB plug-inThe MaxDB plug-in supports MaxDB 7.8.

The following table lists the MaxDB plug-in parameters, the settings, and the description:


APP_NAME maxdb The application name

XUSER_ENABLE (Y|N) Enables the use of an xuser formaxdb so password is notrequired for db user

HANDLE_LOGWRITER (Y|N) Executes suspend logwriter/resume logwriter if set to Y



DBMCLICMD The path to the MaxDB dbmclicommand, if not set dbmcli onthe search path is used

SQLCLICMD The path to the MaxDB sqlclicommand, if not set sqlcli onthe search path is used

MAXDB_UPDATE_HIST_LOG

(Y|N) Tells the maxdb backupprogram if it should updatemaxdb history log

MAXDB_DATABASES List of database(s) and theirusername/password separatedby a comma of which you wantto backup Example:MAXDB_DATABASES=db1:user1/password;db2:user2/password

MAXDB_CHECK_SNAPSHOT_DIR

Setting to check, if a SnapCreator Snapshot copyoperation was successful andthe Snapshot copy has beentaken. NFS only. Directorymust point to the directorywhich contains the .snapshotdirectory. Multiple directoriescan be specified as a commaseparated list Multipledatabases can be specified as asemicolon separated list In caseof MaxDB 7.8 and newer, thedatabase backup request will bemarked as Failed in the backuphistory. The shown error codeidentifies the number ofmissing snapshots. Example:MAXDB_CHECK_SNAPSHOT_DIR=SID:directory[,directory...][SID2:directory[,directory...]


Lotus Domino plug-inThe Lotus Domino plug-in supports Lotus Domino 8.0, Lotus Domino 8.0.x, Lotus Domino 8.5, andLotus Domino 8.5.x.

The IBM Lotus Domino application consistency feature ensures application consistency byinterfacing with the Domino APIs through the Domino plug-in. This plug-in is supported onWindows, Linux, AIX, and Solaris.

The Domino plug-in collects a list of all databases, templates, and mailboxes in the Dominoenvironment. Each file is then placed in a quiesced state. When the databases are quiesced, allchanges to the databases are stored in a temporary area known as change info. When the Snapshotcopy is taken, the quiesce is released and the change info is written back to the database.

The change info must be stored on a volume that is not a part of the Snapshot copy. The change infois also written back to a database after a restore. The DOMINO_RESTORE_DATA_PATH must beset to the path where the Domino data is being restored –this path might change depending on thetype of the restore being performed. A volume restore must be set to the same path as the Dominodata, while a single database restore is set to an alternate path on the same volume as the Dominodata. If the DOMINO_RESTORE_DATA_PATH is not set properly, the change info is not appliedto the database which can result in some data loss.

A new log folder is created under DOMINO_CHANGE_INFO_PATH. All the archived logs arestored under this folder. To delete the archived logs, enable archive log options.

Example:

ARCHIVE_LOG_ENABLE=YARCHIVE_LOG_DIR=/home/domino/changeinfo/logsARCHIVE_LOG_RETENTION=30ARCHIVE_LOG_EXT=TXN

If any database is corrupt, then the Domino plug-in continues with the backup of the remainingdatabases if APP_IGNORE_ERROR option is enabled. This is useful in a scenario where the userwants to back up multiple databases and does not want to stop the backup based on quiesce orunquiesce of single database failing.

The following table lists the Domino plug-in parameters, the settings, and the description:


DOMINO_DATA_PATH Path to Domino Data directory.Example: /notes/notesdata

DOMINO_INI_PATH Path to notes.ini file (includenotes.ini in path) Example: /notes/notesdata/

notes.ini



DOMINO_CHANGE_INFO_PATH

Path where change info filesshould be saved. Use a differentvolume than Domino Data orLog paths. Change info shouldnot be captured in the sameSnapshot copy. Example:/notes/changeinfo

Note: To delete the oldchange info files, enablearchive log option

DOMINO_DATABASE_TYPE

Can be any of the followingvalues: 0 = Backup everything( 1+2+3 below) 1 = Backuponly for *.BOX files 2 =Backup only for *.NSF, *.NSGand NSH files. 3 = Backup onlyfor *.NTF files.

LOTUS Path where Domino is installed.Example: /opt/ibm/lotus

Notes_ExecDirectory Path that contains Dominoshared object (.so or .dll) files.Example: /opt/ibm/lotus/notes/latest/linux/

DOMINO_RESTORE_DATA_PATH

The Domino plug-in applieschange information todatabases after a restore. Inorder to do this properly, thisparameter must be set to thelocation where Domino Data isbeing restored. Use the samepath asDOMINO_DATA_PATH ifrestoring to the same location.If performing a single filerestore, provide the path whereyou are restoring yourdatabases. Example: /notes/notesdata


SnapManager for Microsoft Exchange plug-inThe SnapManager for Microsoft Exchange plug-in supports SnapManager 6.0 with MicrosoftExchange Server 2007 and Microsoft Exchange Server 2010.

Note: SnapManager for Microsoft Exchange plug-in requires Snap Creator Agent to be installed.

Note: SnapManager for Microsoft Exchange plug-in is not supported with Data ONTAP 8.1Cluster-Mode.

The following table lists the SnapManager for Microsoft Exchange plug-in parameters, the settings,and the description:


SME_PS_CONF Path to the Powershellconfiguration file forSnapManager for MicrosoftExchange.

Example: SME_PS_CONF=C:\Program Files\NetApp

\SnapManager for

Exchange\smeShell.psc1

SME_BACKUP_OPTIONS SnapManager for MicrosoftExchange backup options. SnapCreator uses a Powershellcmdlet for new-backup.

Example:SME_BACKUP_OPTIONS=-Server 'EX2K10-DAG01' -GenericNaming -ManagementGroup 'Standard' -NoTruncateLogs $False -RetainBackups 8 -StorageGroup 'dag01_db01' -BackupCopyRemoteCCRNode$False

SME_SERVER_NAME SnapManager for MicrosoftExchange server name

SME_32bit (Y|N) Setting to enable use of 32-bitversion of Powershell.


SnapManager for Microsoft SQL Server plug-inThe SnapManager for Microsoft SQL Server plug-in supports SnapManager 6.0 with Microsoft SQLServer 2007 and Microsoft SQL Server 2008.

Note: SnapManager for Microsoft SQL Server plug-in requires Snap Creator Agent to be installed.

Note: SnapManager for Microsoft SQL Server plug-in is not supported with Data ONTAP 8.1Cluster-Mode.

The following table lists the SnapManager for Microsoft SQL Server plug-in parameters, the settings,and the description:


SMSQL_PS_CONF Path to the Powershellconfiguration file forSnapManager for MicrosoftSQL Server.

Example:SMSQL_PS_CONF=C:\Program Files\NetApp

\SnapManager for SQL

Server\smsqlShell.psc1

SMSQL_BACKUP_OPTIONS SnapManager for MicrosoftSQL Server backup options.Snap Creator uses a Powershellcmdlet for new-backup.

Example:SMSQL_BACKUP_OPTIONS=-svr 'SQL' -d 'SQL\SHAREPOINT', '1','WSS_Content' -RetainBackups7 -lb -bksif -RetainSnapofSnapInfo 8 -trlog-gen -mgmt standard

SMSQL_SERVER_NAME SnapManager for MicrosoftSQL Server name

SMSQL_32bit (Y|N) Setting to enable use of 32-bitversion of Powershell.


Archive log plug-inThe Archive log plug-in works for any database. This plug-in does not communicate with thedatabase. It deletes archive logs that are older than the configured threshold value (in days).

The following table lists the Archive log parameters, the settings and the description:


ARCHIVE_LOG_ENABLE (Y|N) Enables archive logmanagement (deletion of oldarchive logs).

ARCHIVE_LOG_RETENTION

Numbers of days the archivelogs are retained. Epoch time isused and is precise to thesecond.

ARCHIVE_LOG_DIR Path to the directory thatcontains the archive logs.Optionally, for multiple archivelog directories,ARCHIVE_LOG_DIR<##>can be used.

ARCHIVE_LOG_EXT File extension of the archivelogs, that is, if the archive logsare 10192091019.log, youwould set this to "log"; thesearch pattern used is:<something>.<extension>


Setting allows to managearchive logs within subdirs. Ifarchive logs are located undersubdirs this option should beused.


Configuring Snap Creator Server

The Snap Creator configuration file is located in /path/to/scServer_v<#>/configs/<profile>/<config>.conf. You can create multiple configurations, but Snap Creator Server runsonly one configuration at a time.

You can edit this file by using Visual Interactive (VI) (UNIX) or any text editor in Windows.Additionally, you can use the Snap Creator GUI to edit and manage configuration files.

Creating a configuration file using CLIYou can create a new directory or profile for your configuration under /path/to/scServer_v<#>/configs. It is a best practice to name it after the host or application that is backedup.

About this task

This example uses the name oraprod01. The default template is located in /path/to/scServer_v<#>/configs/default/default.conf.

Steps

1. Create the following directory:

mkdir /path/to/scServer_v<#>/configs/oraprod01

2. Copy or rename the following default template to your new configuration directory:

cp /path/to/scServer_v<#>/configs/default/default.conf

/path/to/scServer_v<#>/configs/oraprod01/oraprod01.conf

3. Edit your configuration file by using VI (UNIX) or any text editor in Windows.

Creating a configuration file using GUIYou can create a configuration file using the GUI.

Steps

1. Open the web browser to the following URL: http://myserver.mydomain.com:8080 and login.

2.In the Management Configurations screen, click Add backup profile and enter the newprofile name.

57

The profile name should relate to the application being backed up. Adding a profile creates adirectory under the/path/to/scServer_v<#>/configs directory.

The new backup profile is created.

3.Right click the backup profile and select New Configuration.

4. Proceed through the configuration wizard.

5. Review the summary and click Finish.

Note: You can view configuration files listed under the profile. It contains all the configurationspecific details. You can rename and delete a configuration by right-clicking and selectingDelete or Rename. The GUI creates the same configuration files you would create by using theCLI. You can update and edit configuration files created by the GUI from the CLI or from theCLI to the GUI.

ReferencingReferencing is the ability to define variables within the configuration file. The configuration file isdynamic, which means that you can create and set variables within the configuration itself.

This is done by using the % character. For example, use of SnapDrive instead of Data ONTAP API tocreate the Snapshot copies. As the Snapshot copy names need to be unique, you must set a dynamicvariable. The following is an example from a Windows SnapDrive configuration:

NTAP_SNAPSHOT_CREATE_CMD1="c:/Program Files/NetApp/SnapDrive/sdcli" snap

create -m fx1b4 -s %SNAME-%SNAP_TYPE_%SNAP_TIME-D E:

or

NTAP_SNAPSHOT_CREATE_CMD1="c:/Program Files/NetApp/SnapDrive/sdcli" snap

create -m fx1b4 -s %SNAME-%SNAP_TYPE_recent -D E:

The following table lists the built-in variables that can be referenced:

Variables Description

%SNAP_TYPE This is given when you run Snap Creator and itis your retention policy, that is, daily, weekly,monthly.

%SNAP_TIME This is a timestamp (YYYYMMDDhhmmss)used in the naming of Snapshot copies to createa guaranteed unique name for every Snapshotcopy. It is also used to name the backup reportsand Sybase transaction logs.


Variables Description

%ACTION This is the given action when you run SnapCreator: (snap|clone_vol|clone_lun|arch|restore|delete|snaplist|

clonelist|pmsetup|ossv)

%MSG This is used to send an error message to anotherprogram such as e-mail or Tivoli. It can only beused with the SENDTRAP function.

%USER_DEFINED This passes a user-defined argument to the SnapCreator configuration file. For example, Tointegrate with a backup application likeNetBackup, CommVault, or Legato NetWorkeryou might have to pass the desired backupproduct's schedule into the configuration filewhen you have multiple schedules and want tocall NetBackup, CommVault, or LegatoNetWorker with a certain schedule. You couldalso achieve this by having multipleconfiguration files for the different scenarios.

The following table lists the parameters required in a basic configuration:


SNAME (REQUIRED) Snapshot copy namingconvention should be unique.Snapshot copies are deletedaccording to the namingconvention and retention policyused.

SNAP_TIMESTAMP_ ONLY(REQUIRED)

(Y|N ) If set to Y, Snapshot copies endwith YYYYMMDDHHMMSS.Otherwise, new Snapshotcopies are renamed to end withYYYYMMDDHHMMSS.

VOLUMES (REQUIRED) List of primary storagecontrollers and volumes youwant to create a Snapshot copyof, that is,controller1:vol1,vol2,vol3;controller2:vol1;controller3:vol2,vol3.

Configuring Snap Creator Server | 59


NTAP_SNAPSHOT_RETENTIONS (REQUIRED)

Determines the number ofSnapshot copies you want toretain for a given policy, that is,daily:7,weekly:4,monthly:1.

NTAP_USERS (REQUIRED) This is the list of appliancesand their corresponding usernames/passwords, that is,controller1:joe/password1;controller2:bob/password2;controller3:ken/password3.

Note: If you want to useprotected passwords, first run

./snapcreator-

cryptpasswd

and then save the scrambledpassword in the config file.

NTAP_PWD_ PROTECTION(REQUIRED)

(Y|N) Enables password protection.You must encrypt all passwords(storage system andapplications or plug-ins) andsave encrypted passwords inconfig file when this option isset to Y.

TRANSPORT (REQUIRED) HTTP|HTTPS This allows you to choose theprotocol for APIcommunications.

Note: HTTPS may requireopenssl-devel libraries.

PORT (REQUIRED) This is the used tocommunicate with the storagecontroller(s), normally(80/443).

LOG_NUM (REQUIRED) This is the number of .debugand .out reports that SnapCreator has to retain.



CONFIG_TYPE (REQUIRED) PLUGIN|STANDARD We can have two types ofconfiguration: plug-in,standard. We can use multipleplug-in configs to build upcomplex quiesce and unquiescebackup workflows.

CMODE_CLUSTER_USERS(REQUIRED FOR CLUSTER-MODE)

List of primary/secondaryCluster-Mode clusters and theircorresponding usernames/passwords Example:cluster1:joe/password1;cluster2:bob/password2 #

CMODE_CLUSTER_NAME(REQUIRED FOR CLUSTER-MODE)

Name of the primary Cluster-Mode cluster

CMODE_SNAPSHOT_FORCE_DELETE

(Y|N) Setting which forces deletion ofSnapshot copies which shouldbe deleted based on Snapshotpolicy

LOG_TRACE_ENABLE (Y|N) (Y|N) Setting which enablestrace messages. Trace messagesare an extra level of debug

The following table lists the parameters required to connect to vFiler units and interfaces:


VFILERS This is the list of vFiler unitsand their hosting appliances orvolumes, that is,vFiler1@controller1:vol1,vol2,vol3;vFiler2@controller2:vol1;vFiler3@controller3:vol2,vol3.

Note: HTTPS is notsupported with vFilers



MANAGEMENT_INTERFACES

This is an interface that you canspecify for every physicalappliance. All Data ONTAPAPI communications betweenSnap Creator and the controlleroccur through this interface.For example:MANAGEMENT_INTERFACES=controller1:controller1-mgmt;controller2:controller2-mgmt

SECONDARY_INTERFACES

For every appliance or vFilerunit, you can specify asecondary interface source/destination pair (name or IP). Itis used for SnapMirror andSnapVault updates. Forexample,controller1:controller1-backup/controller2-backup. Where:controller1 - Storage controlleror VFiler unit namecontroller1-backup - Secondaryinterface for controller1/vFiler1controller2-backup - Secondaryinterface for controller1/vFiler1's SnapMirror orSnapVault destination

Note: The SnapVault/SnapMirror relationshipsmust be configured to usethis secondary interface.Snap Creator does notmanage SnapMirror/SnapVault relationships.



USE_PROXY (Y|N) Setting which allows API callsto go through DataFabricManager server proxy insteadof storage controller directly. Ifthis option is used,NTAP_USERS is no longerrequired.

ALLOW_IP_ADDR (Y|N) Setting which allows IP addressto be used for storage system.This applies to SnapVault,SnapMirror, and ProtectionManager. Using IPs can createproblems and should only beused under certain conditions.

The following table lists the parameters required to set up Snapshot copy:


NTAP_SNAPSHOT_RETENTION_AGE

Allows you to define aretention age (in days) forSnapshot copies. If configured,Snapshot copies are deletedonly if they exceed the numberdefined inNTAP_SNAPSHOT_RETENTIONS and if they areolder than the retention age (indays).

SNAPDRIVE (Y|N) Allows you to use SnapDriveinstead of Data ONTAP API tocreate a Snapshot copy.

SNAPDRIVE_DISCOVERY (Y|N) Enables use of SnapDrive forthe discovery feature. RequiresSnapDrive to be configured andworking on host wherediscovery is performed.



NTAP_SNAPSHOT_DISABLE

(Y|N) Disables the Snap Creator fromcreating a Snapshot copy sothat Snap Creator can handleSnapVault or SnapMirror forSnapManager. For this settingto work, the SnapManagerSnapshot copies need to followthis naming convention:<snapshot copy name>-<policy>_recent.

NTAP_SNAPSHOT_NODELETE

(Y|N) OverridesNTAP_SNAPSHOT_RETENTIONS and prevents Snapshotcopies from being deleted.Leaving this variable on canmake the volume full.

NTAP_SNAPSHOT_DELETE_BY_AGE_ONLY

(Y|N) RequiresNTAP_SNAPSHOT_RETENTION_AGE and forces deletionbased on Snapshot copy agerather than the number ofSnapshot copies.

NTAP_SNAPSHOT_DEPENDENCY_IGNORE

(Y|N) Applies only to Snapshot copydeletion menu "-action delete".Manually deleting Snapshotcopies with a dependency is notpermitted.

NTAP_SNAPSHOT_CREATE_CMD<#>

This SnapDrive commandcreates a Snapshot copy andflushes the file system buffers.< #> is a number from 01-99.

Note: This is required if youenable the SNAPDRIVEoption.

Data ONTAP API is still usedto perform everything else, butthe SNAPDRIVE optioncreates Snapshot copies.



NTAP_CONSISTENCY_GROUP_SNAPSHOT

(Y|N) Enables use of consistencygroups. By using this setting,you can take a consistent (I/Ofencing) Snapshot copy acrossmore than one volume andmultiple storage controllers.

Note: Enabling this optionrequiresNTAP_CONSISTENCY_GROUP_TIMEOUT

NTAP_CONSISTENCY_GROUP_TIMEOUT

urgent |medium |relaxed Specifies the wait time for I/Ofencing between volumes.Before we can create aSnapshot consistency group, allvolumes must be quiesced (I/Ofencing). The default settingand recommendation is medium(7 seconds); however, thisdepends on the number ofvolumes you have and thenumber of appliances that areinvolved. Urgent is 2 seconds,Medium is 7 seconds, Relaxedis 20 seconds.

NTAP_CONSISTENCY_GROUP_WAFL_SYNC

(Y|N) Setting which can improveperformance of the CGSnapshot by forcing a CPthrough a wafl-sync before thecg-start.

NTAP_SNAPSHOT_RESTORE_AUTO_DETECT

(Y|N) Setting which if disabledalways forces a SFSR whendoing a single file restore.

The following table lists the parameters required to set up SnapVault:


NTAP_SNAPVAULT_UPDATE

(Y|N) Allows you to turn off and turnon the SnapVault updatefunction.



SNAPVAULT_ VOLUMES This is the list of sourceappliances and volumes onwhich you want to perform aSnapVault update, that is,controller1:vol1,vol2,vol3;controller2:vol1;controller3:vol2,vol3.

Note: For SnapVault andSnapMirror updates to work,the relationships must exist.Snap Creator does not createthe relationships.

Note: The host name(s) inthe SnapMirror or SnapVaultrelationship must be thesame as specified in theVOLUMES,SNAPMIRROR_VOLUMES, andSNAPVAULT_VOLUMESoptions. Also, the host whereSnap Creator runs must beable to resolve thehostname(s).

Note: For vSphere/vCloudplug-in, set the value toauto:detect

Note: Host names should bethe short host name (namethat appears on storagecontroller command prompt),not the FQDN.



SNAPVAULT_QTREE_INCLUDE

This is the list of sourceappliances and qtree paths thatshould be included in theSnapVault update. Without thisoption, all qtrees under avolume are vaulted bySnapVault if a relationshipexists. Qtrees listed in thefollowing example are vaultedby SnapVault and the rest areignored by SnapVault:controller1:/vol/qtree/qtree1,/vol/volume/qtree2;controller2:/vol/volume/qtree1.

NTAP_SNAPVAULT_RETENTIONS

Determines the number ofSnapshot copies on theSnapVault secondary that youwant to retain for a givenpolicy, that is, daily:21,weekly:12,monthly:3.

NTAP_SNAPVAULT_RETENTION_AGE

Allows you to define aretention age (in days) forSnapVault Snapshot copies. Ifconfigured, SnapVaultSnapshot copies are deletedonly if they exceed the numberdefined inNTAP_SNAPVAULT_RETENTIONS and if they areolder than the retention age (indays).



NTAP_SNAPVAULT_SNAPSHOT

(Y|N) Enables use of SnapVaultSnapshot copies; that is,Snapshot copies that arecompatible with the StorageController SnapVaultscheduler. When using thisoption, Snapshot delete ishandled by the Storagecontroller and not by the SnapCreator. Additionally, Snapshotcopies are named as follows:sv_<POLICY>.<##>. Thepolicy name comes from theNTAP_SNAPSHOT_RETENTIONS parameter and theretention set is also applied tothe Storage ControllerSnapVault schedule.

NTAP_SNAPVAULT_NODELETE

(Y|N) OverridesNTAP_SNAPVAULT_RETENTIONS and prevents Snapshotcopies from being deleted.Leaving this on can cause yourvolume to fill up.

NTAP_SNAPVAULT_RESTORE_WAIT

(Y|N) In the case of SnapVaultrestore, it forces Snap Creatorto wait for the operation tocomplete. This is recommendedbecause after the SnapVaultrestore completes, Snap Creatorprompts the user to delete therestore Snapshot copies that getcreated on primary storage andare no longer needed.

NTAP_SNAPVAULT_ WAIT This is the wait time (inminutes) for the SnapVaultupdate process to completebefore taking a Snapshot copyon the SnapVault secondary.



NTAP_SNAPVAULT_MAX_TRANSFER

This is the maximumbandwidth SnapVault isallowed to use in kbps. If it isnot set, SnapVault uses themaximum available bandwidth.

The following table lists the parameters required to set SnapMirror:


NTAP_SNAPMIRROR_UPDATE

(Y|N) Allows you to turn off and turnon the SnapMirror updatefunction.

NTAP_SNAPMIRROR_CASCADING_UPDATE

Y/N Allows you to turn off and turnon the cascading SnapMirrorupdate function. This is aSnapMirror update using aSnapVault destination volume.

Note: This is not supportedfor Data ONTAP 8.1 Cluster-Mode

SNAPMIRROR_ VOLUMES This is the list of sourceappliances and volumes onwhich you want to perform aSnapMirror update, that is,controller1:vol1,vol2,vol3;controller2:vol1;controller3:vol2,vol3. Note: For vSphere/vCloudplug-in set the value toauto:detect

SNAPMIRROR_CASCADING_VOLUMES

List of SnapVault destinationappliances and volumes where,after a SnapVault update, youwant to perform a SnapMirrorupdate, that is, sec-controller1:vol1-sec,vol2-sec.



NTAP_SNAPMIRROR_WAIT

This is the wait time (inminutes) for the SnapMirrorupdate process to completebefore creating a clone on theSnapMirror destination. IfNTAP_CLONE_SECONDARY=Y, Snap Creator waits untilthe SnapMirror update iscomplete before proceeding.

Note: This can only be usedwithNTAP_CLONE_SECONDARY and ACTION clone_vol(only volume clones arecurrently supported).

NTAP_SNAPMIRROR_USE_SNAPSHOT

(Y|N) If enabled, the SnapMirrorupdate uses the newly createdSnapshot copy, thus creating aSnapshot copy on theSnapMirror destination.

Note: This is required forNTAP_CLONE_SECONDARY because a Snapshot copyis needed in order to create aclone on the SnapMirrordestination.

NTAP_SNAPMIRROR_MAX_TRANSFER

This is the maximumbandwidth SnapMirror isallowed to use in kbps. If it isnot set, SnapMirror uses themaximum available bandwidth.

The following table lists the parameters required to set up cloning:


NTAP_VOL_CLONE_RESERVE

none | file volume This is the space guarantee fora cloned volume.



NTAP_LUN_CLONE_RESERVATION

true | false If set to true, space is reservedfor the cloned LUNs if theclone_lun Action is selected.Otherwise, space is notreserved.

NTAP_CLONE_IGROUP_MAP

Specify the appliance, sourcevolume, and an IGROUP. TheIGROUP is then mapped tocloned LUNs that reside in thesource volume or cloned LUNsthat reside in the volume clone,that is,controller1:src_volume1/igroup1;controller2:src_volume2/igroup2.

Note: LUN clones assumethe same name as their parentvolume or LUN and end with_CLONE, that is, if thevolume is called myvol, itsclone would bemyvol_CLONE

Note: Volume clones startwith "cl_" and end with "-YYYYMMDDHHMMSS".

NTAP_CLONE_FOR_BACKUP

(Y|N) If enabled, clones (volume andLUN) are created and thendeleted after the otheroperations are complete.Otherwise, clones are deletedbefore operations complete.

Note: If you are backing upclones to tape, this should beset to Y. If you are doingdatabase refreshes, then youshould set it to N.



NTAP_CLONE_SECONDARY

(Y|N) If enabled, clones are createdon the SnapMirror destinationafter the SnapMirror update iscomplete.

Note: This setting should beused withNTAP_SNAPMIRROR_USE_SNAPSHOT,NTAP_SNAPMIRROR_WAIT,NTAP_CLONE_SECONDARY_VOLUMES , andACTION clone_vol.

NTAP_CLONE_SECONDARY_VOLUMES

This is a mapping of primary/secondary appliances and thesecondary volumes. This isrequired so that Snap Creatorcan find the secondaryvolumes, that is,controller1:controller1-sec/vol1,vol2,vol3;controller2:controller2-sec/vol1;controller3:controller3-sec/vol2,vol3.

NTAP_NUM_VOL_CLONES This is the number of volumeclones you want to retain. Thisworks in a similar way to theSnapshot retention policy.

Note: This only works forvolume clones that require aFlexClone license on thestorage controller.

NTAP_NFS_EXPORT_HOST Host IP The hostname or IP addresswhere the clone should beexported. This is the host wherethe user wants to mount theclone volume by using NFS.



NTAP_NFS_EXPORT_ACCESS

root | read-write | read-only The host specified inNTAP_NFS_EXPORT_HOSTreceives access or permission tothe clone volume. root - Rootaccess is granted read-only -Read-only access is grantedread-write - Read/Writeaccess is granted.

NTAP_NFS_EXPORT_PERSISTENT

true | false Determines if NFS export ispersistent. If true is selected,the clone volume is exportedand the /etc/exports file onthe Storage Controller isupdated.

The following table lists the parameters required to set up Protection Manager:


NTAP_PM_UPDATE (Y|N) Allows you to turn off and onthe Protection Manager updatethat registers Snap CreatorSnapshot copies in ProtectionManager.

Note: IfNTAP_PM_UPDATE isenabled, you must configureNTAP_DFM_DATA_SET.

NTAP_DFM_DATA_SET This is a list of appliances andProtection Manager data sets tovolume correlations, that is,controller1:dataset1/vol1,vol2;controller1:dataset2/vol3.

NTAP_PM_RUN_BACKUP (Y|N) Starts the Protection Managerbackup, checks the progressand status, and waits for it tocomplete.



NTAP_DFM_SNAPSHOT_FORMAT

Optional setting for the formatof the secondary Snapshotcopies when using ProtectionManager. This option requiresOnCommand 5.0 (DataFabricManager) or higher. Requiredvariable: %T - timestamp

Optional variables are:

%R - retention type

%L - dataset label %H - storagecontroller %N - volume name %A- application specific data.

If this option is not set then thedefault Protection Managernaming convention will beused. The naming conventioncan only be set at the time ofdataset creation.

The following table lists the parameters required to set up Open Systems SnapVault:


NTAP_OSSV_ENABLE (Y|N) Enables the Open SystemsSnapVault integration. Thisoption must be used incombination with theNTAP_OSSV_HOMEDIRparameter. Open SystemsSnapVault is also required onthe host running Snap Creator.

Note: When Open SystemsSnapVault option is enabled,the path is specified asvolumes. When specifyingpaths in windows for OpenSystems SnapVault : shouldnot be used. For example, ifthe path is E:\DB then itshould used as E\DB.



NTAP_OSSV_HOMEDIR /usr/snapvault The path to the Open SystemsSnapVault home directory, thatis, /usr/snapvault

NTAP_OSSV_FS_SNAPSHOT

(Y|N) This setting also requires theNTAP_OSSV_FS_SNAPSHOT_CREATE_CMD<##> andallows to create a file systemSnapshot copy using OS /Filesystem command. The Filesystem Snapshot copy is thentransferred to the storagesystem using SnapVault.

NTAP_OSSV_FS_SNAPSHOT_CREATE_CMD<##>

These are scripts or commandsto be executed during or beforethe Open Systems SnapVaultbackup process, where ## is anumber from 01- 99. This canbe used to perform backup filesystem Snapshot copies byusing Open SystemsSnapVault.

The following table describes the Operations Manager settings:


OM_HOST The name or IP address of theOperations Manager host.

OM_USER The user name of an OperationsManager user who haspermission to create events.

OM_PWD The password for theOperations Manager user.

OM_PORT The port to use forcommunications withOperations Manager; 8080 isthe default http port that theOperations Manager uses.



OM_EVENT_GENERATE (Y|N) Enables or disables eventcreation in OperationsManager.

The following table describes the different APP commands:

Command Setting Description

APP_CLONE_FOLLOW_ UP_CMD<##>

These are scripts or commandsto be executed after thedatabase is cloned, where ## isa number between 01- 99. Thiscan be used to performapplication-specific follow-upactivities on SAP systems, suchas, installing a SAP license,adjusting database tables,deleting or updating content,and starting up the application.

APP_QUIESCE_CMD<##> These are scripts or commandsthat put your application intobackup mode where, "##" is anumber between 01-99.

Note: This is ignored if youuse APP_NAME because itis handled internally in SnapCreator.

APP_UNQUIESCE_CMD<##>

These are scripts or commandsthat take your application out ofbackup mode, where "##" is anumber from 01-99.


ARCHIVE_CMD<##> Handles database archiving. Itcan also be used as a wrapper torun other scripts. The archivecommand, where ## is anumber from 01-99.


The following table describes the different PRE commands:


PRE_APP_QUIESCE_CMD<##>

This is the pre applicationbackup start command,where##is a number from01-99.

PRE_NTAP_CMD<##> This is the pre Snapshotcommand, where##is a numberfrom 01-99; it runs before alloperations.

PRE_APP_UNQUIESCE_CMD<##>

This is the pre applicationbackup stop command,where##is a number from01-99.

PRE_NTAP_CLONE_DELETE_CMD<##>

This is the pre clone deletecommand, where## is anumber from 01-99.

Note: The purpose of clonedelete command(s) is to calla mount script or commandsso that cloned LUNs can bemounted for the purpose ofbacking up (probably totape).

PRE_EXIT_CMD<##> This is an optional commandthat is run after a fatal erroroccurs but before Snap Creatorexits. This is useful to revert tothe state it was before SnapCreator ran.

Note: This command returnsan application into normaloperation mode before SnapCreator exits due to an error.




PRE_RESTORE_CMD<##> This is an optional commandthat can be run before you enteran interactive restore. Thisallows you to interact with theapplication being restored. Forexample, you might want toshut down the applicationbefore performing a restore.

Note: This is not supportedwith MySQL plug-in.

PRE_CLONE_CREATE _CMD<##>

This is an optional commandthat can be run before DataONTAP API cloning operationsoccur, where##is a numberfrom 01-99.

The following table describes the different POST commands:


POST_APP_QUIESCECMD<##>

This is a post applicationbackup start command,where##is a number from01-99.

POST_NTAP_CMD<##> This is a post command,where##is a number from01-99. This runs after alloperations are complete.

POST_APP_UNQUIESCE_CMD<##>

This is a post applicationbackup stop command,where##is a number from01-99.

POST_NTAP_DATA_TRANSFER_CMD<##>

This is a post data transfercommand that runs afterSnapVault or SnapMirrortransfer, where##is a numberfrom 01-99.



POST_RESTORE_ CMD<##> This is an optional commandthat can be run after youcomplete an interactive restore.It allows you to interact withthe application being restored.After your restore is complete,you might want to start theapplication.

Note: This is not supportedwith MySQL plug-in.

POST_CLONE_CREATE_CMD<##>

This is an optional commandthat can be run after DataONTAP API cloning operationsoccur, where##is a numberfrom 01-99. The commands areused to perform operations suchas mounting cloned filesystems.

The following table describes the mount and Umount commands:


MOUNT_CMD<##> Mount commands are used tomount file system for cloningor mount actions where##is anumber starting from 01 - 99.

UMOUNT_CMD<##> Umount commands are used tomount file system for cloningor mount actions where##is anumber starting from 01 - 99.

Note: You should use MOUNT_CMDS and UMOUNT_CMDS for mount/umount commandsinstead of Snap Creator pre/post commands for cloning.

The following table lists the parameters required to set up event management:



NTAP_ASUP_ERROR_ENABLE

(Y|N) Enables Snap Creator errormessages to also log an autosupport message on the storagecontroller. Snap Creator alwayscreates an info auto supportmessage when the backup hasstarted and is complete.

SENDTRAP This command interfaces withyour monitoring software or e-mail allowing you to pass alertsgenerated from Snap Creatorinto your own monitoringinfrastructure. The %MSGvariable is the message sentfrom Snap Creator. Thefollowing is an example of howto send an email on a UNIXsystem:SENDTRAP=/usr/bin/mailx

-s %MSG

[email protected]

</dev/null

SUCCESS_TRAP This command interfaces withyour monitoring software or e-mail allowing you to pass thesuccess message generatedfrom Snap Creator into yourown monitoring infrastructure.The %SUCCESS_MSG variable isthe success message for SnapCreator. The following is anexample of how to send anemail on UNIX system:SUCCESS_TRAP=/usr/bin/

mailx -s %SUCCESS_MSG

[email protected]

</dev/null



SUCCESS_MSG After a successful Snap Creatorbackup, this setting logs themessage defined and also sendsit to SUCCESS_TRAP, ifdefined, or to SENDTRAP, ifSENDTRAP is defined.

The following table lists the parameters required for client/server configuration:


SC_AGENT <hostname or IP >:<port> Snap Creator has the capabilityto perform tasks on remotehosts. A task is either a definedplug-in (parameterAPP_NAME) or a commandspecified with the parameters_CMD , for example,NTAP_SNAPSHOT_CREATE_CMD01. To specify a remotehost, enter its name or IPaddress followed by a colonand the port the Snap CreatorAgent is listening on. On theremote host, start the SnapCreator Agent by running thecommand:

<path to scAgent_v<#>>/

snapcreator-start-agent

<port>

SC_CLONE_ TARGET <hostname or IP of the clonetarget>:<port>

Snap Creator has the capabilityto perform clone operations.Using the action clone_vol incombination with {PRE|POST}_CLONE_CREATE_CMDxx, you can handle thestorage objects on the remoteside. For example, mounting/unmounting file systems. Tospecify a clone target, enter itsname or IP address followed bya colon and the port the SnapCreator Agent is listening on.



SC_AGENT_ TIMEOUT Time (in seconds) Specifies the timeout inseconds. The implementedclient/server architecture uses atimeout mechanism. Thismeans that if the client does notrespond in the specifiedinterval, the server fails with atimeout message. However, thetask on the client is not abortedand requires furtherinvestigation. On a server withhigh load or known long-running tasks like own scriptsor complex SnapDriveoperations, it might benecessary to extend the timeoutand adapt this value to yourown requirements. By default, atimeout of 300 seconds is used.

SC_AGENT_WATCHDOG_ENABLE

(Y|N) Enables or disables the agentwatchdog process. When theagent receives a quiescerequest, the watchdog processstarts. The watchdog processwaits for theSC_AGENT_UNQUIESCE_TIMEOUT and unquiesces theapplication. If an unquiescerequest is received by the agent,the watchdog process isterminated.

Note: For all plug-ins thedefault setting is Y. ForVIBE plug-in the defaultsetting is N, and it shouldalways be N.



SC_AGENT_UNQUIESCE_TIMEOUT

Time (in seconds) This optional setting specifiesthe timeout in seconds. If thecommunication with the agentis not possible and anapplication is in the quiescestate, the agent automaticallyreturns the application into itsnormal mode of operationwithout communication fromthe server. If this setting is notset, then the unquiesce timeoutis set to whatever theSC_AGENT_TIMEOUT isplus 5 seconds.

SC_TMP_DIR (Y|N) Allows you to use a user-defined, alternate temporarydirectory to store the SnapCreator related files. The usercreates the directory andmanages the user access. Theplug-ins use temporary files tointeract with the database. Thetemp files are created in thehost's default temp directory,which has write access to allthe users. If the directory is full,Snap Creator displays an errorwhile creating the temp files.

SC_AGENT_LOG_ENABLE (Y|N) Setting which enables loggingon agent. The Snap CreatorServer sends operations to theagent. If something happensbefore agent sends callback toserver it is possible messagescould be lost. This allows agentmessages to be logged on agentso they are never lost.


Snap Creator Agent configuration

If Snap Creator Server uses a profile that has commands or scripts in PRE, POST or APP other thanthe built-in application plug-ins command to be executed on host where the agent resides, then thosecommands or scripts must be added to the /path/to/scAgent_v<#>/config/agent.conf.

* stands for any commands but regular expressions can be used to be more restrictive. Eachcommand or script should be added to the file as follows:

command: echo

command: /bin/mount

command: /path/to/myscript

In this example, the agent allows the Snap Creator Server to run echo ,/ bin/mount, or /path/to/myscript in addition to the application plug-ins. If the application plug-ins are not usedand the agent is required, run the application quiesce and unquiesce commands for applicationconsistency.

Additionally, the wildcard * can be used to allow all commands but it is not recommend it forsecurity reasons.

command: *

85

Snap Creator Backup process

The Snap Creator backup process is the same for all the applications and involves running optionalscripts, commands, or using the plug-in interfaces.

The scripts or commands are triggered by using PRE and POST command parameters in theconfiguration file. All the PRE and POST commands can be run remotely by using the Snap CreatorAgent. For the application quiesce and unquiesce, you must use the Snap Creator application plug-insor run commands and scripts.

The backup process involves the following steps:

1. Achieving application consistency

2. Achieving file system consistency (optional)

3. Creating a Snapshot copy

4. Returning the application to normal mode

5. Cloning the LUN or volume (optional)

6. Performing various SnapMirror or SnapVault functions (optional)

7. Deleting old Snapshot copies, thus managing retention policies on both primary and secondarystorage devices in the case of SnapVault or SnapMirror

List of commands

Application quiesce and unquiesce commands

The quiesce and unquiesce commands are used to achieve application consistency when not usingSnap Creator application plug-ins. Snapshot copies of volumes without application consistency areonly crash consistent.

Archive commands

Archive commands are user-defined commands or scripts that are run before the POST commands(last command that runs). The purpose of the archive commands is to provide the ability to interfacewith archiving tools after a backup is performed.

PRE commands

PRE commands are user-defined commands or scripts that are run before the following operations:

• The application quiesce commands or application integration plug-ins• The Data ONTAP API or SnapDrive calls• The application unquiesce command or application integration plug-ins• The volume or LUN clone delete commands are run

87

The following are the different types of PRE commands:

• PRE app quiesce

• PRE NetApp

• PRE app unquiesce

• PRE clone create

• PRE NetApp clone delete

• PRE exit

• PRE restore (in the case of interactive restore)

A PRE command can be used for a file system synchronization or consistency check before callsusing Data ONTAP API or SnapDrive are made. For example, run the file system command or scriptas a PRE NetApp command.

Note: PRE commands or scripts that do not exit with status 0 are handled as an error within SnapCreator.

POST commands

POST commands are user-defined commands or scripts that are run after the application quiescecommand, the Data ONTAP API calls, and the application unquiesce command.

The following are the different types of POST commands:

• POST application quiesce

• POST NetApp

• POST application unquiesce

• POST data transfer

• POST clone create

• POST restore (in the case of interactive restore)

A POST command can be used after the application unquiesce command is run to make sure thatthe database is running in normal mode. For example, run the database check command or script as aPOST application unquiesce command.

Note: POST commands or scripts that do not exit with status of 0 are handled as an error withinSnap Creator.


Running Snap Creator Server using CLI

You can perform actions such as creating a Snapshot copy, volume clone, LUN clone by runningSnap Creator Server and the associated parameters using CLI.

About this task

You should schedule the Snap Creator Server from either UNIX Cron, Windows task manager, or theSnap Creator built-in GUI scheduler. When scheduling through the Windows task manager, createa .bat file.

Step

1. Run Snap Creator Server by using the following command:

./snapcreator --profile Config --action Action --policy Policy OptionalArguments

The following table lists the Snap Creator Server parameters:


--profile <Profile> The name of the profile should be the nameyou gave to the directory/file withoutthe .conf suffix. To create alternate configfiles under the same profile, use the - configoption.

list Displays all configs known to Snap Creator.Do not use list as a profile name as it onlydisplays configs. For example:

./snapcreator --profile list

setup Runs the Snap Creator setup that configuresboth the GUI and Snap Creator itself. Forexample:

./snapcreator --profile setup

89


--action <Action> (snap|clone_vol|clone_lun|clone_del|arch|quiesce|unquiesce|discover|restore|delete|snaplist|clonelist|pmsetup|ossv|mount|umount)

There are currently ten possible actions: createa Snapshot copy (snap), perform an OpenSystems SnapVault backup, make a Snapshotcopy as well as a volume clone (clone_vol),make a Snapshot copy as well as a LUN clone(clone_lun), handle only archiving for anapplication (arch),perform an interactiverestore (restore), perform an interactive delete(delete), list Snapshot copies for a given policy(snaplist), list volume clones (clonelist),configure a Protection Manager data set(pmsetup).

snap Makes a Snapshot copy. For example:

./snapcreator --profile Profile --action snap --policy PolicyOptional Arguments

ossv Uses Open Systems SnapVault to perform thebackup; no Snapshot copy is created. Forexample:

./snapcreator --profile Profile --action ossv --policy PolicyOptional Arguments



clone_vol Makes a Snapshot copy plus whatever else isconfigured and then uses that Snapshot copy tomake a volume clone. This requires aFlexClone license. Once the volume is cloned,an IGROUP is mapped to all the LUNs thatreside in the cloned volume using theNTAP_CLONE_IGROUP_MAP option in theconfiguration file.

Note: The format of cloned volume in SnapCreator 3.5.0 is cl_configfile_volume_YYYYMMDDhhmmss as compared toSnap Creator 3.4.0 ( cl_<sourcevolume>_YYYYMMDDhhmmss)

Hence Snap Creator 3.5.0 does not list the oldformat cloned volumes. The user has to deletethe old cloned volumes and create a newcloned volume.

./snapcreator --profile Profileclone_vol --policy Policy OptionalArguments

If the SC_CLONE_TARGET parameter andthe options necessary for the database clonehandling are set after cloning the volume, thedatabase cloning is complete.

clone_lun Creates a Snapshot copy plus whatever else isconfigured and then uses that Snapshot copy tomake a LUN clone of all LUNs that reside inthe source volume. Once the LUNs are cloned,an IGROUP is mapped to all the cloned LUNsthat reside in the source volume using theNTAP_CLONE_IGROUP_MAP option in theconfiguration file. Note: Because there is apossibility that Snapshot copies can get lockedby cloned LUNs, this is not a recommendedmethod. However, this depends on whether thecustomer owns a FlexClone license. If thecustomer owns a FlexClone license, clone_vol,which uses FlexClone, should be used.

./snapcreator-profile Profile --action clone_lun --policy PolicyOptional Arguments

Running Snap Creator Server using CLI | 91


clone_del Deletes a volume clone(s) created by SnapCreator according to the volume clone settingsdefined in the configuration file. You can usethis option to separate the clone deleteworkflow from that of clone create. Some thirdparty integrations, such as BRTools by SAP,require separate clone create and deleteworkflows.

arch Provides archive log managementfunctionality as a separate workflow based onapplication plug-in settings as defined by theconfig file. Snap Creator performs archive logmanagement for a given application. Thepurpose of this action is to provide granularityallowing other tools to better integrate withSnap Creator. Additionally, this functionalityallows for multiple application backupworkflows that are required in certainvirtualized environments. For example:

./snapcreator-profile Profile --action arch Optional Arguments

quiesce Provides quiesce functionality as a separateworkflow based on application plug-in settingsas defined by the config file. Snap Creatorquiesces a given application. The purpose ofthis action is to provide granularity allowingother tools to better integrate with SnapCreator. Additionally, this functionality allowsfor multiple application backup workflows thatare required in certain virtualizedenvironments. For example:

./snapcreator-profile Profile --action quiesce Optional Arguments



unquiesce Provides unquiesce functionality as a separateworkflow based on application plug-in settingsas defined by the config file. Snap Creatorunquiesces a given application. The purpose ofthis action is to provide granularity allowingother tools to better integrate with SnapCreator. Additionally, this functionality allowsfor multiple application backup workflows thatare required in certain virtualizedenvironments. For example:

./snapcreator --profile Profile --action unquiesce Optional Arguments

discover Provides discover functionality as a separateworkflow based on application plug-in settingsas defined by the config file. Snap Creatorperforms discovery for a given application.The purpose of this action is to providegranularity allowing other tools to betterintegrate with Snap Creator. For example:

./snapcreator --profile Profile --action discover Optional Arguments

scdump Collects all support information for technicalsupport and places everything into a .zip filelocated under the root Snap Creator directory.Collected information consists of logs, configfiles, storage controller, OS, database (ifapplicable), and SnapDrive (if applicable)information. For example:

./snapcreator --profile Profile --action scdump Optional Arguments



restore Provides an interactive restore. You canperform a volume, file, or SnapVault restore.File restore is for LUNs. A volume restore isonly recommended in case of a disaster.Otherwise, you should always recover files.For NAS, you can recover files by simplycopying files out of the ~snapshot directory sothat there is no need to handle NAS file restorewith Snap Creator. A SnapVault restorerestores a qtree on secondary storage back toprimary storage either on its original oralternate location. For example:

./snapcreator --profile Profile --action restore --policy PolicyOptional Arguments

delete Guides you through an interactive Snapshotcopy delete menu for a given Snap Creatorpolicy. For example:

./snapcreator --profile Profile --action delete --policy PolicyOptional Arguments

snaplist Lists all Snapshot copies that are beingmanaged by Snap Creator. It displays Snapshotcopies on primary as well as secondarystorage. For example:

./snapcreator --profile Profile --action snaplist Optional Arguments

clonelist Lists all volume clones that are being managedby Snap Creator. It shows volume clones onprimary as well as secondary storage. Forexample:

./snapcreator --profile Profile --action clonelist Optional Arguments

Note: This action only lists the volumeclones created using Snap Creator 3.5.0 anddoes not list the volume clones fromprevious versions of Snap Creator.



dpstatus Shows detailed information about SnapVaultor SnapMirror relationships. For example:

./snapcreator --profile profile --action dpstatus

pmsetup Creates a Protection Manager Dataset forgiven config. For example:

./snapcreator --profile Profile --action pmsetup Optional Arguments

Note: After creating the Protection Managerdataset, you need to go into ProtectionManager to configure it. The configurationinvolves adding relationships and definingthe protection policy.

--policy <Policy> The name of the Snapshot policy defined inNTAP_SNAPSHOT_RETENTIONS andpossiblyNTAP_SNAPVAULT_RETENTIONS. Youcan name the Snapshot policy whatever youwant but it is important that the name you passSnap Creator as- policy be exactly the same asdefined inNTAP_SNAPSHOT_RETENTIONS as wellas possiblyNTAP_SNAPVAULT_RETENTIONS if youare using SnapVault. You can also have asmany of these as you want all with differentretentions.

Note: If you use SnapDrive to create theSnapshot copies, use lowercase. SnapDrive(at least Windows) cannot differentiatebetween uppercase and lowercase.

mount Mount a Snapshot copy using NFS orSnapDrive

umount Unmount a Snapshot copy using NFS orSnapDrive

The following table lists the optional parameters:



--config Allows you to specify an alternate config filelocated under the /path/to/scServer_v<#>/Config> directory. Forexample:

./snapcreator --profile Profile --action Action --policy Policy --config Alternate Config

Note: This option is required when theprofile / path/to/scServer_v<#>/configs/<profile> and the config doesnot match /path/to/scServer_v<#>/configs/<profile>/<config>.conf

--global Allows you to use a global config file. Thereare two possible global config files you canhave. Environment Global Config: configs/global.conf Profile Global Config: configs/<profile>/global.conf Parameters are loadedfirst from environment global, then the profileglobal, and finally your actual config file. Anyduplicate parameters are overwritten by youractual config file. For example:

./snapcreator --profile Profile --action Action --policy Policy --config Alternate Config --global

--verbose Displays all logging information to STDOUT.This is an optional setting and is used mostlyfor testing and running Snap Creator manually.For example:

./snapcreator --profile Profile --action Action --policy Policy --config Alternate Config --verbose

--debug Displays all logging information to STDOUTand the log file. This is an optional setting andis for debugging problems. For example:

./snapcreator --profile Profile --action Action --policy Policy --config Alternate Config --verbose-debug



--version Prints the Snap Creator version. For example:

./snapcreator -version

--cryptpasswd Encrypts a password for storing it in a configfile. For example: ./snapcreator --cryptpasswd

--config_dir Specifies an alternate path to the SnapCreator /configs directory. This is a CLI onlyoption and is not supported by the GUI.

--log_dir Specifies an alternate path to the SnapCreator /logs directory. This is a CLI onlyoption and is not supported by the GUI.

-- snap_name <snapshot> The name of the Snapshot copy which shouldbe used. Applies to action clone_vol, mount,and umount and restore operations

--clone_name <clone> The name of the clone which should be used.Applies to action clone_del and umount.

--volume_name <volume> The name of the primary volume which shouldbe used. Applies to action restore and delete

--file_names <files> A comma separated list of the full path to filesor LUNs which should be restored. Applies toaction restore when using non-interactivemode

--non_interactive Runs the operation in non-interactive mode.Applies to action restore and delete


Running Snap Creator Agent using CLI

You can run Snap Creator Agent and the associated parameters using CLI.

Step

1. Start the Snap Creator Agent by running the following command:

./snapcreator --start-agent <port> <Optional Arguments>

where:

• <port>: Starts the Snap Creator Agent on the specified port. If no port is specified, port 9090is used.

• <Optional arguments> are: - - debug : Displays all logging information to STDOUT and thelog file.

Note: You can start the agent automatically on UNIX by using the /path/to/scAgent_v<#>/bin/scAgent script.

You can start the agent in multithread mode by using the following command:

./snapcreator --start-multithreaded-agent <port>

99

Running Snap Creator using GUI

You can perform actions such as creating a Snapshot copy, volume clone, LUN clone using the SnapCreator GUI.

You can upload or download a configuration file through GUI by using Upload Configuration

and Download icons.

You can perform the following actions by using the Actions drop-down box in the ConfigurationContent pane.

•LUN clone

•Volume clone

•Snapshot

•Restore

•Scdump

•Discover

•Archive Log

•Quiesce

•Unquiesce

Note: Snap Creator 3.5.0 GUI supports performing the preceding actions with global optionsenabled.

Creating a scheduleYou can create a schedule and run the tasks using the GUI.

Steps

1. Click the Schedules tab on the left to load the Management Schedules screen.

2.Click Add new task

101

3.In the New Task window, enter the details and click Save.

Result

The new schedule is listed and you can view the details in the Configuration Details pane on theright.

To run the task, click Run task and to edit the task, click Edit task.

Note: If you create as hourly schedule with n minutes, the first job runs after n minutes andthereafter after every 1 hour.

Example: If you create a schedule on 12.56 PM with Hourly and 25 minutes. The job first runs at1.21 PM then it runs at 2.21 and so on.

For information about creating a schedule using cron refer the Cron Trigger tutorial.

Related information

http://www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger

Creating multiple usersYou can create multiple users and perform several actions like assigning profiles to the user,assigning user actions, editing password using the GUI.

Steps

1. Click the Users tab to load the Management Users screen.

2.Click Add new user and enter the details in New User window.

3.Select the user and click Assign profiles.

4. In the Assign profiles to the user window, select the profiles, drag and drop from the left pane to

the right pane and click Save.

5.Select the user and click Add User actions.

6. In the Assign Actions to user window, select the actions, drag and drop from the left pane to the

right pane and click Save.


http://www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger

Job monitoringYou can monitor the jobs using the GUI.

Steps

1. Click the Job Monitor tab to load the Management Job Monitor screen.

You can see list of jobs and details like Job ID, Job status, Start time, End time, and so on.

2.To start or stop job monitoring, select the job and click Start Job Monitor or Stop jobMonitor.

Note: To download the logs, click Download Logs on the right side of the screen and youcan set the Job Monitor size and the left bottom of the screen.

Viewing data and log detailsYou can view the volume, Snapshot copy, and volume clone details for each configuration under theData tab and log details under Reports tab.

Steps

1. Click the Volumes tab under Data to view the volume details like Total size, size available,state, and so on.

2. Click the Snapshots tab to view the Snapshot copy details like Snapshot copy name, access time,dependency, and so on.

The Snapshot copies can be renamed or deleted by clicking the rename and delete icons.

3. Click Volume Clones to view Volume clone details like Controller, clone, parent Snapshot, andso on.

4. Click Logs tab under Reports and select the Backup profile, configuration, log type, and log toview the Backup log details.

Running Snap Creator using GUI | 103

Performing restore using Snap Creator

You can perform Volume restore, Single File restore, VMware restore, and Domino restore usingSnap Creator.

Note: If you use SnapDrive for Windows you must use SnapDrive for restore and NOT SnapCreator. SnapDrive stores metadata inside Snapshot copies which is needed when it performs arestore.

Performing Volume restoreYou can perform a volume restore using CLI or GUI.

Step

1. Depending on whether you want to use CLI or GUI, perform the appropriate action:

If youwant touse

Do this

CLI Enter the following command:

./snapcreator --profile <Profile> --config <config> --actionrestore --policy <Policy>

Note: To perform a volume restore non interactively, use the following command:

./snapcreator --profile <Profile> --action restore --policy<Policy>--config <config> --volume_name <volume> --snap_name<snapshot> --non_interactive --debug --verbose

GUI a.Select the configuration file and in the configuration content pane, click Action and

select Restore.

b. Enter Restore details and in the Restore type drop-down list, select Volume Restore.

c. Proceed through the wizard.

105

Performing Single file restoreYou can perform a single file restore using CLI or GUI.

Step


If youwant touse

Do this


./snapcreator --profile <Profile> --config <config> --actionrestore --policy <Policy>.

Note: To perform a single file restore non-interactively, use the following command:

./snapcreator --profile <Profile> --config <config> --actionrestore --policy <Policy>--volume_name <volume>--snap_name<snapshot> --file_names <files> --non_interactive --verbose.

GUI a.Select the configuration file and in the configuration content pane, click Action and

select Restore

b. Enter Restore details and in the Restore type drop-down list, select Single file Restore.


Performing VMware restoreYou can perform VMware restore using CLI or GUI.

About this task

In certain VMware environments, restores can take a long time. In this case, you can either use theSnap Creator CLI or set up two agents - one for backup and one for restore.

Note: VMware restore using the GUI is supported only for Snap Creator Agent.

Step



If you want touse

Do this


./snapcreator --profile <Profile> --config <config> --actionrestore --policy <Policy> --snap_name <snap name>.

GUI a.Select the configuration file and in the configuration content pane, click Action

and select Restore.

b. Enter Restore details and in the Restore type drop-down list, select VMware Restore.


Performing restore with Domino plug-inWith Snap Creator 3.5.0 you can perform up to the minute restore and selectable point in time restorewith Domino plug-in.

The Domino plug-in has multiple restore options:

• Volume Restore (point-in-time only): This option restores a volume to the point-in-time of theselected Snapshot copy.

• Single File Restore - Point-in-time: This option restores a single file to the point-in-time of theselected Snapshot copy.

• Single File Restore - Up-to-the-minute: This option restores a single file and then plays forwardthe Domino transaction logs to the most recent copy.

• Single File Restore - Selectable Point-in-time: This option restore a single file then plays forwardthe Domino transaction logs to a specified point-in-time.

All these options are available in both the GUI and the CLI.

Note: Single File Restore operations work only with NFS. For Up-to-the-minute and Selectablepoint-in-time single file restore, Domino transaction logging must be enabled.

In all the options the changeinfo is written back to database(s) after a restore. TheDOMINO_RESTORE_DATA_PATH parameter in the config file must be set to the path where theDomino data is being restored. It is likely that this path changes depending on the type of restorebeing performed. Typical use cases for setting the DOMINO_RESTORE_DATA_PATH variableare:

• For a volume restore: DOMINO_RESTORE_DATA_PATH = DOMINO_DATA• For a single database restore: DOMINO_RESTORE_DATA_PATH= a subdirectory on the same

volume that the Domino Data volume exists on.

Performing restore using Snap Creator | 107

If the DOMINO_RESTORE_DATA_PATH is not set properly, the change info will not be applied tothe database which results in a post restore error. The file will still be restored, but the necessarychangeinfo will not be applied.

Note: While performing a single file restore, the replication of the database will be disabled.

Performing Volume restore for Domino using CLIYou can perform a full volume restore for Domino using the CLI.

Before you begin

You must have stopped the Domino server.

Steps

1. Initiate the CLI command for restore:

Example

snapcreator.exe --action restore --profile domino --policy daily --config lindom8

where

• --action restore: Indicates the action taken. In this case restore will be performed.• --profile domino: Indicates the name of the profile in this case domino.• --policy daily: Indicates the policy used. In this case daily.• --config lindom8: Indicates that the lindom8 config file is used. This parameter is required

when multiple config files are present within the profile or when the profile name is differentfrom the config name

2. Select the volume to be restored by typing the number next to the volume name.

3. Select the Snapshot copy to be restored by typing the number next to the volume name.

4. Select the type of restore.

5. Confirm the selected settings.

6. Select another volume to restore if desired.

Note: It is not recommended to use option q unless an error has occurred. Using q or quitoption causes Snap Creator to exit without performing any post restore activities.

7. The restore process is complete.

Example

INFO: Completing restore and running an post-restore commands that may be defined


Performing Volume restore for Domino using GUIYou can restore the entire volume for Domino using GUI.

Before you begin


Steps

1.Select the configuration file and in the configuration pane, click Action and select Restore.

2. An optional prompt appears asking if a global config file will be used. If yes, select the checkbox.If no, accept the default unselected status.

3. Enter Restore details and select Volume restore in the Restore type drop-down list.

4. Proceed through the wizard to complete the restore process.

After you finish

Start the Domino server.

Performing Single file restore for Domino using CLIYou can perform a single file restore for Domino using the CLI.

Before you begin


Steps

1. Initiate the CLI command for restore.

Example

snapcreator.exe --action restore --profile domino --policy daily --config lindom8

where

• --action restore: Indicates the action taken. In this case restore will be performed.• --profile domino: Indicates the name of the profile in this case domino.• --policy daily: Indicates the policy used. In this case daily.• --config lindom8: Indicates that the lindom8 config file is used. This parameter is required

when multiple config files are present within the profile or when the profile name is differentfrom the config name


2. Select the volume to be restored by typing the number next to the volume name.

3. Select the Snapshot copy to be restored by typing the number next to the volume name.

4. Select the type of restore. For single file restore, select option 02.

5. This step asks for the file to be selected.

For applications or file systems with a small number of files an automated menu can be displayedallowing for selected of a file. For Domino there can be hundreds or thousands of files, so it isrecommended to manually enter the name of the file to restore.

Example

Would you like to bypass file selection and manually enter a file for restore (y|n)?

6. Enter the file name and the path to be restored.

Note: This is asking for a path relative to the selected volume, so pay close attention to whatalready exists. Even though it is not displayed, the path ends with a "/".

7. Enter the local path on the storage system of the restored file.

8. Select the restore type:

Note: After this point the restore process is the same for all three restore types except forSelectable point-in-time restore you must enter the time and date to which the Dominotransaction logs will be played.

9. Select the replication option for this database.

10. Confirm the summary of the single file restore details.

11. Select if you want to restore to the file's original location.

12. Enter the alternate path to restore.

13. Confirm the settings and continue.

14. The restore process is complete at this stage but none of the post restore activities, such asapplying change info, have yet occurred. To restore files on other volumes enter

c

15. The post restore processes run in the background and typically will not be displayed on screen.

Example

INFO: Completing restore and running an post-restore commands that may be defined

16. The restore process is complete.


Performing Single file restore for Domino using GUIYou can perform the single file restore for Domino using the GUI.

Steps

1.Select the configuration file and in the configuration pane, click Action and select Restore .

2. An optional prompt appears asking if a global config file will be used. If yes, select the checkbox.If not, accept the default unselected status.

3. Enter Restore details and select Single File restore in the Restore type drop-down list.

4. Browse through the directory structure and select the file to restore. With Domino, only a singlefile can be restored at a time.

Note: The path is from the perspective of the storage system, not the server file system. This isbecause the file is restored at the storage system level.

5. Browse through the directory structure and select the location where the file will be restored.

Note: The path is from the perspective of the storage system, not the server file system. This isbecause the file is restored at the storage system level.

6. Select the restore type.

• Point-in-time• Up-to-the-minute• Selectable point-in-time

Note: You can disable Domino replication upon restore. This option zaps the replica IDkeeping changes to the database from replicating back to the database after a restore. Check oruncheck the box as desired to set this option.

7. Proceed through the wizard to complete the restore process.


Using the Plug-in Framework to create customplug-ins

The plug-in framework allows the users to create their own plug-ins for Snap Creator or reuseexisting plug-ins. The purpose of a plug-in is to provide Snap Creator with the steps for handlingbackup and recovery of a given application. The plug-in framework defines the following methods:

• quiesce - Method for handling quiesce for a given application plug-in• unquiesce - Method for handling unquiesce for a given application plug-in• discover - Method for handling discovery of storage objects for a given application plug-in• scdump - Method for handling collection of support information, database, Operating System,

and SnapDrive• restore - Method for handling restore for a given application plug-in• restore_pre - Method for handling pre-restore operations for a given application plug-in (can use

built-in restore CLI of Snap Creator)• restore_post - Method for handling post-restore operations for a given application plug-in (can

use built-in restore CLI of Snap Creator)• clone_pre - Method for handling pre-clone operations for a given application plug-in• clone_post - Method for handling post-clone operations for a given application plug-in• describe - Method for describing what a plug-in implements. This is optional for Perl plug-ins but

required for native plug-ins under plugins/native.• clone_all - Method for handling cloning for a given application plug-in (Cannot use built-in

cloning interface)• clone_cleanup - Method for handling cleanup if a clone operation fails• restore_clenaup - Method for handling cleanup if a restore operation fails• The plug-in framework supports Perl, PowerShell, Java, UNIX Shell, and Python for

programming.• The plug-in framework allows the user to implement objects and functions that exist within the

Snap Creator. For example, error handling is available, which means the plug-in can use thestandard implementation Snap Creator uses. This reduces the work required in order to create aplug-in.

• Perl plug-ins are installed under /plugins/<PLUGIN-nam>/<PLUGIN>.pm• Native plug-ins are installed under /plugins/native/

plugin.sh,plugin.java.plugin.bat, and so on.• The plug-in must be installed where it is supposed to run. This could be the Snap Creator Server

or Snap Creator Agent depending on the setup of Snap Creator.

For more information about the plug-in framework, plug-ins, and a plug-in user guides, see the SnapCreator Developer Community.

113

Related information

http://www.snapcreator.com


http://www.snapcreator.com

Troubleshooting Snap Creator issues

You can troubleshoot Snap Creator issues by using the information in the Snap Creator logs andError messages.

LogsYou can use Snap Creator logs to begin troubleshooting. The logs contain information abouteverything Snap Creator does.

Messages can be INFO, CMD, OUTPUT, DEBUG, WARN, or ERROR. Anything with INFO isconsidered to be a standard, normally occurring operation. Anything with CMD is an externalcommand or script that Snap Creator runs (according to configuration) and the return code from thecommand or script is logged. Typically, these are PRE, POST, or APP Quiesce/Unquiescecommands. Anything with OUTPUT is a Data ONTAP API call. Anything with DEBUG is debuginformation. Anything with WARN is considered to draw your attention, but, again under normalcircumstances, it is considered to be normal activity and should require no action (an example iswhen we delete Snapshot copies). Anything with ERROR is a problem and most likely requiresmanual action to fix the error. Snap Creator exits on any ERROR, so it is important to fix whateverproblem occurred before it runs again. Snap Creator does not automatically fix problems but you canspecify Snap Creator what to do before exiting by using the PRE_EXIT_CMD defined in theconfiguration file.

The logs contain the output from any external commands or scripts run by Snap Creator, forexample, SnapDrive. If you call other scripts through Snap Creator, it is important that you properlyset up exit codes and output for those scripts. You should never exit with status 0 if a problem occurs.

The out, debug, stderr, and agent logs are retained as defined by the LOG_NUM value in theconfiguration file while the error log is always appended. All logs are written to the /path/to/scServer_v<#>/logs/<profile> directory.

The four logs for every profile and configuration are as follows:

• Out• Debug• Error• Stderr

Out log

The out log contains only verbose logging information.

115

Debug log

The debug log contains verbose and debug logging information.

Trace messages are an extra level of debug logs which can be used by the plug-in to show tracemessages. LOG_TRACE_ENABLE - (Y|N) Setting enables or disables trace messages.

Error log

The error log contains a history of all the ERROR events for a given configuration. The error loghelps in viewing information about errors that occurred in the past so you can correlate things betterand get a historical perspective. You can also monitor this log file and use it as a means to integrateSnap Creator with your monitoring application.

Stderr log

This is usually empty but contains stderr if there are any issues. This usually shows bugs in code

Snap Creator Agent

The Snap Creator Agent optionally creates logs. This is enabled by default with the following option:

SC_AGENT_LOG_ENABLE=Y

The three logs for every profile and configuration created on agent are as follows:

• Out• Debug• Stderr

Additionally the agent console debug can be enabled by specifying the additional -- debug option:

/path/to/scAgent_v<#>/bin/scAgent --debug

SCDUMP

Snap Creator collects all support information using scdump and places it into a .zip file locatedunder the root Snap Creator directory. This information is useful for troubleshooting. The .zip fileconsists of the following items:

• Snap Creator version (build info, date, and so on)• Host OS and architecture• Database and version• SnapDrive version• Other environment variables

The syntax for SCDUMP is as follows:

.


/snapcreator.pl --profile profile [--config config] --action scdump -

verbose

Troubleshooting Snap Creator GUI error

Error starting the GUI

HTTP ERROR 503

Problem accessing /. Reason: SERVICE_UNAVAILABLE

You might receive this error message when there is no sufficient space for the temp file.

Please verify if you have sufficient space in the temp folder in the respective OS folders.

Example: For Linux, check /tmp

HTTPS errors when using Snap Creator on Linux

HTTPS might not work on Linux out-of-the-box. This appears mainly to be an issue with SuSe butreally could apply to any UNIX. Snap Creator does not include ssl libraries we are dependent on.

Install openssl and ensure symlinks are created correctly.

The requirements for HTTPS for Linux/Unix are as follows:

1. openssl package

2. SSL symlinks

Make sure the following symlinks are located under /usr/lib oder /usr/lib64 (depending onif OS is 64bit or not)

• libssl.so.6• libcrypto.so.6

If the symlinks do not exist please cd to /usr/lib or /usr/lib64 and run following command tolink them.

• ln -sf libssl.so.0.9.8 libssl.so.6• ln -sf libcrypto.so.0.9.8 libcrypto.so.6

Troubleshooting Snap Creator issues | 117

Troubleshooting Network issuesWhen authorization failures occur with Snap Creator, verify the configuration, firewall permissions,and network address translation (NAT).

IP/Hostname

Unless you use host equiv, the storage system name returned from the hostname command onthe controller should be the same as the one entered in the Snap Creator config file.

Do not use an FQDN when the hostname of a storage system is abbreviated.

Make sure that the IP resolution matches the name you specified. If there is a mismatch, correct it byusing host equiv on the storage system.

To enable host equiv, perform the following steps:

1. Enter the following command: options https.admin.hostsequiv.enable on

2. Edit the /etc/hostsequiv file and add the following: <IP/Name of host inSnapCreator config> <SnapCreator user>

Protection Manager

The storage controller name defined in the Snap Creator config parameter VOLUMES must match1:1 with the storage controller name in Protection Manager. If they do not match, you can use theoperating systems host file to force things to match 1:1.

Firewall

If there is a firewall between the host running Snap Creator and your storage system, make sure youhave ACLs (bidirectional) open for 80, 443, or both.

• 80: Used to communicate with storage system if http is selected.• 443: Used to communicate with storage system if https is selected.

If the agent is running, the port on which the agent is running must be open. Make sure the returntraffic from the storage system is allowed to go to the system running Snap Creator on at least non-privileged ports.

NAT

If you use NAT, make sure the source/destination IP addresses are not changed in the TCP packet.The host and storage systems need to know who they are talking to. Presenting a firewall IP insteadof the actual host or controller IP might cause problems.


HTTPS

To use HTTPS (443) for Linux, Solaris, or AIX, install the openssl-devel RPM. This RPM containsthe openssl libraries, which are required to use SSL.

Error messagesYou can review the error messages associated with different Snap Creator operations.

Each error message comprises of an area code and a five digit unique identifier. For example,ERROR: [<area code>-<unique area error identifier>] <error message>. The area code identifieswhere the error occurs. The following is the list of different area codes:

• scf - Snap Creator Framework• agt - Snap Creator Agent• ora - Oracle Plug-in• mys - MySQL Plug-in• db2 - DB2 Plug-in• syb - Sybase Plug-in• ltd - Lotus Domino Plug-in• psg - PostgreSQL Plug-in• vmw - VMware Plug-in• max - MaxDB Plug-in• sme - SnapManager for Microsoft Exchange Plug-in• sms - SnapManager for Microsoft SQL Server Plug-in• gui - Snap Creator GUI

Snap Creator Framework error messages

Error code Error message Description/resolution

scf-00001 Could not get serial number -<error message>

Make sure a serial number isset or blank. Serial numberwhen set can only be numeric.This probably means SnapCreator setup was not run. Run

snapcreator --profile

setup

command.



scf-00002 Couldn't Create directory <logdirectory>: <error message>

Log directory creation forprofile failed. Make sure theuser running Snap Creator hasread/write access to /snapcreator/logs

directory.

scf-00003 Application environment set forplugin <plugin name>encountered errors <errormessage> , proceeding withbackup!

This meansAPP_IGNORE_ERROR is setand we are not exiting due toapplication errors from plug-in.Check the logs to troubleshootproblem further.

scf-00004 Couldn't redirect STDERR to<debug log name>: <errormessage>

STDERR is redirected to*.debug logs. Make sure userrunning Snap Creator has read/write access to scServer/logs directory.

scf-00005 The action <action> is notsupported with OSSV, Exiting!

Open System SnapVault doesnot support all actions, use adifferent action.

scf-00006 Restore handling of plug-in<plugin name> failed with exitcode <exit code>, Exiting!

Restore failed due toapplication error. Check logsand application settings.

scf-00007 Pre restore handling of plugin<plugin name> failed with exitcode <exit code>, Exiting!

Pre restore handling failed dueto application error. Check thelogs and application settings.

scf-00008 This type of restore requiresSNAP_TIMESTAMP_ONLY=Y andNTAP_CONSISTENCY_GROUP_SNAPSHOT=Y, Exiting!

Set both options and retrycommand.

scf-00009 Clone handling of plugin<plugin name> failed with exitcode <exit code>, Exiting!

Cloning failed due toapplication error. Check logsand application settings.

scf-00010 Pre clone handling of plugin<plugin name> failed with exitcode <exit code>, Exiting!

Pre clone handling failed due toapplication error, totroubleshoot check logs andapplication settings.



scf-00011 Post clone handling of plugin<plugin name> failed with exitcode <exit code>, Exiting!

Pose clone handling failed dueto application error, totroubleshoot check logs andapplication settings.

scf-00012 NetApp Cloned Lun IgroupMap of <lun clone name> to<igroup> on <controller>failed! Exiting

The igroup map for LUN clonefailed. Check error you mostlikely have a Manage ONTAPSolution error which mayreveal the cause of the problem.

scf-00013 Indicates a ZAPI Error Snap Creator Framework error.Indicates error is coming fromManage ONTAP Solution, totroubleshoot check errormessage and logs on storagecontroller or Data FabricManger server.

scf-00014 NetApp PM backup list isundefined, no Backups fordataset <data set> exist! Exiting

Snap Creator started a backupin Protection Manager but noSnapshot copies exist. Makesure Snap Creator is registeringbackup and check configparametersNTAP_PM_UPDATE andNTAP_DFM_DATA_SET.

scf-00016 Protection Manager dataset Listfor dataset <data set> isundefined, check you dataset inProtection Manager! Exiting

Snap Creator determined thedataset does not exist or isempty and not setup correctly.

scf-00017 Protection Manager dataset<data set> was not created bysnapcreator, please createdataset from withinsnapcreator!

The dataset must be created bySnap Creator. Datasets notcreated by Snap Creator are notapplication datasets and willnot work. Please run


<profile> --action

pmsetup

to create dataset.



scf-00018 Protection Manager dataset<data set> is <conformantstatus>, Exiting!

Protection Manager dataset<data set> is <conformantstatus>, Exiting! In order to runa Protection Manager backupthe dataset must be conformant.This indicates a problem withthe dataset, please log intoprotection manager andconform the dataset.

scf-00019 No NetApp Volumes on<controller> found! Exiting

Volumes were not found.Please check VOLUMESparameter and if ProtectionManager is used ensureNTAP_DFM_DATA_SET andthe dataset itself were created/configured properly.

scf-00020 NetApp Snapmirror SourceVFiler <source vfiler> andvfiler specified in config<vfiler> don't match! Exiting

You have enabled vFilertunneling by using vFilerparameter in the config file. Ifthis is Data ONTAP 7.3.x youdon't need to do vFilertunneling. Configure sourcevFiler directly in VOLUMESand NTAP_USERS. If

snapmirror status

shows a secondary interface forvFiler then useSECODARY_INTERFACESparameter to tell Snap Creatorwhat maps to vFiler.

scf-00021 NetApp Snapmirror Sourcecontroller <source controller>and controller specified inconfig <controller> don'tmatch! Exiting

Check VOLUMES andSNAPMIRROR_VOLUMESparameter, controller nameshould be same in both andshould be the source controller.

scf-00022 Snapmirror for <controller> isnot enabled, please enablesnapmirror on <controller>!Exiting

Log into storage controller andsetup SnapMirror properly.



scf-00023 No Snapmirror Relationship for<controller>:<volume> exist!Exiting

Snap Creator was unable to findSnapMirror relationships forthe given controller/volumes.Logon to storage controller andrun a

snapmirror status

and ensure the relationships soup for given controller name. Ifa different name is used thenyou need to configureSECONDARY_INTERFACESparameter to tell Snap Creatorwhat maps to storage controller.

scf-00024 NetApp Snapvault Sourcecontroller <source controller>and controller specified inconfig <controller> don'tmatch! Exiting

Check VOLUMES andSNAPVAULT_VOLUMES thesame source controller nameand volumes should be used inboth parameters.

scf-00025 NetApp Snapvault SourceVFiler <source vfiler> andvfiler specified in config<vfiler> don't match! Exiting

You have enabled vFilertunneling by using vFilersparameter in the config file. Ifthis is Data ONTAP 7.3.x youdon't need to do vFilertunneling. Configure sourcevFiler directly in VOLUMESand NTAP_USERS. If

snapvault status

shows a secondary interface forvFiler then useSECONDARY_INTERFACESparameter to tell Snap Creatorwhat maps to vFiler.



scf-00026 No Snapvault Relationship for<controller>:<volume> exist!Exiting

Snap Creator was unable to findSnapVault relationships for thegiven controller/volumes.Logon to storage controller andrun a

snapvault status


scf-00027 NetApp Snapvault Status isundefined, check yourconfiguration for <controller>!Exiting

Snap Creator was unable todetermine SnapVault status.Please check config parametersVOLUMES andSNAPVAULT_VOLUMES.Check the storage controllerprimary and secondary andensure relationships exist onboth end for given controller/volumes.

scf-00028 NetApp Snapmirror Update onsource <controller>:<volume>failed to complete in<snapmirror wait time>minutes, Exiting!

The SnapMirror update tooklonger than configured waittime. You can adjust the waittime by increasing value forNTAP_SNAPMIRROR_WAITin the config file.

scf-00029 Snapmirror Transfer Errordetected - <transfer error>!Exiting

Check error and storagecontroller settings forSnapMirror.

scf-00030 NetApp Snapvault Update onsource <controller>:<volume>failed to complete in<snapvault wait time> minutes,Exiting!

The SnapVault update tooklonger than configured waittime. You can adjust the waittime by increasing value forNTAP_SNAPVAULT_WAITin the config file.



scf-00031 Snapvault Transfer Errordetected - <transfer error>!Exiting

Check error and storagecontroller settings forSnapVault.

scf-00032 Post restore handling of plugin$ENV{'APP_NAME'} failedwith exit code $result->{exit_code}, Exiting!

Post restore handling failed dueto application error. Check thelogs and application settings.

scf-00033 You have selected snapshot<snapshot name> for deletionbut it has a dependency<snapshot dependency>,Exiting!

You have selected a Snapshotcopy to delete which has aSnapshot dependency. This isnot allowed by default. Tooverride this setNTAP_SNAPSHOT_DEPENDENCY_IGNORE=Y.

scf-00034 OSSV snapvault statuscommand failed with returncode <exit code> and message<error message>

Open Systems SnapVaultcommand failed, check OpenSystems SnapVault logs onhost.

scf-00036 Couldn't open directory<directory>

Check permissions of userrunning Snap Creator againstdirectory.

scf-00037 Missing Required option --profile

The --profile argument isrequired. This is the name ofyour profile under scServer/configs.

scf-00038 Invalid option for --action use snap| ossv| clone_lun|clone_vol |clone_del |restore|delete |snaplist|clonelist |dpstatus|pmsetup |arch|quiesce |unquiesce|discover |mount|umount |scdump

scf-00039 Config File <config file> notfound

The config file was not found.Please check the arguments --profile and --config.



scf-00040 Couldn't open filehandle:<error message>

We could not open a file. Thisis usually a permissionsproblem, check the userrunning Snap Creator andensure the permissions arecorrect.

scf-00041 PORT is a required parameterand was not defined, pleasecheck your configuration file!

The PORT parameter is arequired setting, check configfile.

scf-00042 TRANSPORT is a requiredparameter and was not defined,please check your configurationfile!

The TRANSPORT parameter isa required setting, check configfile.

scf-00043 LOG_NUM is a requiredparameter and was not defined,please check your configurationfile!

The LOG_NUM parameter is arequired setting, check configfile.

scf-00044 NTAP_PWD_PROTECTIONis a required parameter and wasnot defined, please check yourconfiguration file!

TheNTAP_PWD_PROTECTIONparameter is a required setting,check config file.

scf-00045 NTAP_USERS is a requiredparameter and was not defined,please check your configurationfile!

The NTAP_USERS parameteris a required setting, checkconfig file.

scf-00046 VOLUMES is a requiredparameter and was not defined,please check your configurationfile!

The VOLUMES parameter is arequired setting, check configfile. For VMware plug-inswhich auto detects the volumeparameters, the user should setVOLUMES = auto: detect

scf-00047 SNAME is a requiredparameter and was not defined,please check your configurationfile!

The SNAME parameter is arequired setting, check configfile.

scf-00048 Invalid application plugin<plugin name>, supportedapplications are oracle

db2



scf-00049 Auto Discovery for plugin<plugin name> failed with exitcode <exit code>, Exiting!

Application discovery faileddue to application error. Checklogs and application settings. Inaddition auto discovery can bedisabled by settingAPP_AUTO_DISCOVERY=Nand commenting outVALIDATE_VOLUMES.

scf-00050 Auto Discovery for plugin<plugin name> failed becauseenv is empty, Exiting!

The application plug-in is notsupported for using autodiscovery. Disable autodiscovery by settingAPP_AUTO_DISCOVERY=N.

scf-00051 Discovering for <plugin name>failed with return code <exitcode>

Application discovery faileddue to application error. Checkconfig and application settings.You can disable auto discoveryby settingAPP_AUTO_DISCOVERY=Nand commenting outVALIDATE_VOLUMES.

scf-00052 Discovering discovered nostorage objects", <errormessage>

Application discovery usingVALIDATE_VOLUMES=DATA failed. Snap Creator wasunable to discover any datavolumes residing on storagesystem. To disable autodiscovery comment outVALIDATE_VOLUMES.

scf-00053 Application quiesce for plugin<plugin name> failed with exitcode <exit code>, Exiting!

Application quiesce failed dueto application error. Check logsand application settings. Toignore application errors andproceed with backup you canset APP_IGNORE_ERROR=Y.



scf-00054 Application unquiesce forplugin <plugin name> failedwith exit code <exit code>,Exiting!

Application unquiesce faileddue to application error. Checklogs and application settings.To ignore application errorsand proceed with backup youcan setAPP_IGNORE_ERROR=Y.

scf-00055 NetApp Snap CreatorFramework dump for plugin<plugin name> failed with exitcode <exit code>, Exiting!

The scdump action failed due toan application error. Check thelogs and application settings.

scf-00056 Couldn't write to file$scdumpFile: <error message>

The scdump action failedbecause Snap Creator could notcreate the zip archive. Checkpermissions on user runningSnap Creator.

scf-00057 Serial number must be numeric The serial number must benumeric. Enter numeric numberor press enter to leave blank.

scf-00058 Password does not match,Exiting!

The password entered does notmatch, please re-enter passwordcorrectly.

scf-00059 no application object specified Application plug-in notdefined. This probably meansyou are running a communityplug-in. If so check with plug-in developer or Snap Creatorcommunity.

scf-00060 unknown application object<application object>

Application plug-in is usingunknown object. This probablymeans you are running acommunity plug-in. If so checkwith plug-in developer or SnapCreator community.

scf-00061 SC_AGENT has to be specifiedas :n";

The syntax of the SC_AGENTparameter is not correct. Checkconfig file and set parameter tobe host:port.



scf-00062 SC_AGENT_TIMEOUT mustbe a positive, numeric value

The syntax of theSC_AGENT_TIMEOUT is notcorrect. Check config file andset parameter to be numericpositive value.

scf-00093 NetApp Snap CreatorFramework Agent could not bestarted: <error message>

The scAgent could not bestarted. The most likely cause isanother scAgent is alreadyrunning on port or somethingelse is using port.

scf-00094 Application environment set forplugin <plugin name> failed<error message>, Exiting!

Failed due to application error.Check the logs to troubleshootproblem further.

scf-00095 Discovery is only supported forapplication plugins

Discovery was run but is notimplemented in yourapplication plug-in. Make sureAPP_AUTO_DISCOVERY=Nso we don't try and do adiscover.

scf-00096 <policy> is not a definedsnapshot retention policy in theconfiguration! Exiting

The policy you are using --policy is not valid. Please checkconfig file and configureNTAP_SNAPSHOT_RESTENTIONS properly.

scf-00097 controller <controller> has nousername or password definedin config file <config file>,Exiting!

Check NTAP_USERS andmake sure user name/passwordis defined for storage controller.

scf-00098 Lun <lun> is either a CLONEor an actual lun, it is notsupported to perform LunClone(s) on luns that end with_CLONE, rename the lun oruse Volume Cloning!

You are trying to clone acloned LUN which isn'tsupported.

scf-00099 NetApp Protection Managerbackup for job-id <job id>completed with errors - <errormessage>

Check Protection Managererrors to find out why thebackup job completed witherrors.



scf-00100 No Snapmirror Relationshipsfound, check yourconfiguration for <controller>!Exiting

Snap Creator was unable to findSnapMirror relationships forthe given controller/volumes.Logon to storage controller andrun a

snapmirror status


scf-00101 No Snapvault Relationshipsfound, check yourconfiguration for <controller>!Exiting

Snap Creator was unable to findSnapVault relationships for thegiven controller/volumes. Logon to storage controller and runa

snapvault status


scf-00102 internal error, not all mandatoryoptions are set for executingcommands

Snap Creator is trying toexecute a command butsomething isn't being set. Findout what CMD is being run andtry using a different CMD.

scf-00104 Couldn't open plugin dir<plugin dir>, Exiting!

Check permissions of userrunning Snap Creator andensure read/write access toscServer/plugins directory.



scf-00105 Discovery is only supported forapplication plugins

Discovery is enabled but noapplication plug-in wasspecified. Check APP_NAMEand if no plug-in is to be useddisable discovery by settingAPP_AUTO_DISCOVERY=Nand commenting outVALIDATE_VOLUMES.

scf-00106 Volume <volume> on<controller> is not included inthe config file.

Check the VOLUMES settingin config file and ensure thecorrect controller:volumes areconfigured.

scf-00107 Validation failed, at least onevolume is not included in theconfig

Application discovery detectedthat some volumes are missing.Check which volumes aremissing and add them toVOLUMES parameter so theycan be included in backup.

scf-00108 Collection of OS informationfailed - <error message>

The scdump action failed due toerror collecting operatingsystem information. Check thelogs and try running thecommand manually by hand.

scf-00109 Collection of SnapDriveinformation failed - <errormessage>

The scdump action failed due toerror collecting SnapDriveinformation. Check the logs andtry running the commandmanually by hand.

scf-00110 Couldn't create scdump zip file- <error message>

The scdump action failedbecause Snap Creator could notcreate the zip archive. Checkpermissions on user runningSnap Creator.

scf-00111 NetApp Snap CreatorFramework dump completedwith errors

The scdump action waspartially successful. Check logsto determine error.



scf-00112 Archive Log Deletion failed,Exiting!

Snap Creator could not deletearchive logs for a givenapplication. Check permissionswhere on Snap Creator user,this could be the scServer orscAgent depending on theconfiguration.

scf-00113 No files found under $path forcontroller! Exiting

Verify that the file path existson the storage controller

scf-00114 Unknown file format for<controller> <file type> on<controller>:<volume>

A file exists which is anunknown format. This meansanything other than a directoryor a file. A LUN would be afile.

scf-00117 NetApp sis clone status of IDcloneID on controller failed!Exiting

Verify clone status on thestorage controller.

scf-00120 NetApp Single File Restore (sisclone) on $controller:$restorePath failed! Exiting

The sis clone restore failed.Make sure you are using DataONTAP 8.1 or greater. You canalso setNTAP_SNAPSHOT_RESTORE_AUTO_DETECT=N todefault to SFSR.

scf-00127 Action: mount requires the --snap_name option. To listavailable Snapshot copies for agive profile use the "snaplist"action

The mount option requiresadditional parameter --snap_name. Please addparameter and retry operation.

scf-00128 Invalid snapshot name<snapshot name> specified in --snap_name parameter, Exiting!

You didn't specify a validSnapshot name. Run


profile --action

snaplist

to see a valid list of Snapshotcopies.



scf-00130 End User License Agreementwas not accepted, please run "./snapcreator --profile setup" toaccept the End User LicenseAgreement

The Snap Creator Serverrequires acceptance of theEULA, please run


setup

and accept the EULA.

scf-00133 The <plugin name> plugin doesnot support restore from theNetApp Snap CreatorFramework. Restore must bedone through the SnapManager, Exiting!

Application plug-in does notsupport restore since this is anintegration with Snap Managerwhich is responsible for theapplication data.

scf-00134 OM_HOST is a requiredparameter and was not defined,please check your configurationfile!

The OM_HOST parameter is arequired setting, check configfile.

scf-00135 OM_USER is a requiredparameter and was not defined,please check your configurationfile!

The OM_USER parameter is arequired setting, check configfile.

scf-00136 OM_PWD is a requiredparameter and was not defined,please check your configurationfile!

The OM_PWD parameter is arequired setting, check configfile.

scf-00137 OM_PORT is a requiredparameter and was not defined,please check your configurationfile!

The OM_PORT parameter is arequired setting, check configfile.

scf-00138 Action scdump is not supportedwith CONFIG_TYPEPLUGIN, please check yourconfiguration file!

There are two types of configfiles STANDARD and PLUG-IN. The PLUG-IN configs onlysupport actions quiesce,unquiesce, discover, and arch.

scf-00139 Missing options for non-interactive restore

Make sure --snap_name and--volume_name are definedthey are both requiredparameters.



scf-00140 The volume specified did notmatch any controller or volumespecified in config

Check VOLUMES parameterin config file and ensure it isconfigured correctly

scf-00141 Data OnTap Cluster modedetected butCMODE_CLUSTER_MGMT_NAME is not configured,please check config parameter!Exiting

Check theCMODE_CLUSTER_MGMT_NAME setting in config. Thisis the name of the cluster mgmtLIF and is required for Cluster-Mode.

scf-00142 Discover cmode cluster nodesfailed

Check to make sureCMODE_CLUSTER_MGMT_NAME is configured correctly,it should be the cluster mgmtLIF. Also check the nodes andensure proper operation ofcluster.

scf-00143 Snapvault is not supported incmode, please setNTAP_SNAPVAULT_UPDATE to N in configuration

Check configuration andchange parameter. Cmode doesnot support snapvault.

scf-00144 Snapvault is not supported incmode, please setNTAP_SNAPVAULT_SNAPSHOT to N in configuration

Check configuration andchange parameter. Cmode doesnot support snapvault.

scf-00145 Plugin <plugin name> is notexecutable

The native or external pluginsmust have execute permissions,please check permissions onplugin under /plugins directory

scf-00146 The META_DATA_VOLUMEis defined but controller:volumespecified does not match whatis configured in VOLUMESparameter, please checkconfiguration!

This happens if theMETA_DATA_VOLUME isnot specified in VOLUMES.Please add to VOLUMES themeta data volume.



scf-00147 Data OnTap Cluster modedetected butCMODE_CLUSTER_NAMEis not configured correctly,please check config parameter!Exiting

The parameterCMODE_CLUSTER_NAMEis required and used for ASUPand SnapMirror, please definethis correctly in config file.

scf-00148 Consistency Group snapshot isnot supported with theMETA_DATA_VOLUMEoption

SetNTAP_CONSISTENCY_GROUP_SNAPSHOT=N in configwhen using theMETA_DATA_VOLUMEoption.

scf-00149 Protection Manager onlysupports timestamp snapshots,please setSNAP_TIMESTAMP_ONLY=Y

Update config file and set theSNAP_TIMESTAMP_ONLYoption to Y

scf-00150 A data protection option isenabled in configuration fileand IP address was detected.Please ensure no IPs are used inVOLUMES,SNAPMIRROR_VOLUMES,SNAPMIRROR_CASCADING_VOLUMES,SNAPVAULT_VOLUMES, orNTAP_DFM_DATA_SET

Check configuration file anduse names not IP. You can setALLOW_IP_ADDR=Y toallow IPs.

scf-00151 Mount handling of plugin<plugin name> failed with exitcode <exit code>, Exiting!

Mount is being handled byplugin, check for any pluginerrors or errors coming fromstorage system. As alternativeyou could setAPP_DEFINED_CLONE=Nand use standard SC interfacefor mounting Snapshot copies.



scf-00152 Umount handling of plugin<plugin name> failed with exitcode <exit code>, Exiting!

Umount is being handled byplug-in, check for any plug-inerrors or errors coming fromstorage system. As alternativeyou could setAPP_DEFINED_CLONE=Nand use standard SC interfacefor mounting Snapshot copies.

Snap Creator Agent error messages

Error code Error message Description/Resolution

agt-00001 Port <port> is being used The Snap Creator Agent orsome other process is runningon the port specified, tryanother port.

agt-00003 invalid parameters The parameters given were notcorrect for starting the SnapCreator Agent, check therequired parameters

agt-00004 Mandatory parameter'SC_AGENT' not yet defined,aborting!

The SC_AGENT configparameter must be definedwhen using a remote agent.

agt-00005 Another quiesce operation orwatchdog is already running onthis config

You are not allowed to do backto back quiesce operations andone is already running, pleasewait or run unquiesce.

agt-00006 cannot create watchdog,resources are not available

The watchdog process is unableto spawn, most likely thesystem has reached maximumnumber of processes, disablewatchdog in config or checkOS settings.



agt-00008 Either no quiesce operationperformed or forced unquiesceoperation already triggeredfrom watchdog, backup mightnot be useable

The quiesce and unquiesceoperation did not complete andbackup is only crash consistent,please check logs to see why.This can happen if quiescetakes too long and you areusing watchdog, the watchdogprocess will perform a forcedunquiesce after x seconds asdefined in config.

agt-00009 Agent configuration is empty,no commands are allowed to beexecuted remotely

PRE and POST CMDs must beallowed in the agent.conf on theagent side. Please update theagent.conf and allow necessarycommands.

agt-00010 Reloading configuration from<agent.conf> failed withmessage <message>

The agent could not read itsconfiguration file, please checkpermissions on the agent.conffile.

agt-00011 Command <command> is notallowed

A command was sent to theagent but is not allowed, pleaseupdate agent.conf to allowcommand.

agt-00012 <error message> This error has to do withloading a plug-in, please checkthe plug-in and APP_NAMEsetting.

agt-00013 <error message> This error has to do withrunning the setENV methodinside plug-in, please checkplug-in and ensure syntax.

GUI error messages


gui-00001 Unable to decrypt password -Failed to decrypt the controllerpassword.

Make sure encrypted passwordin the configuration file iscorrect.



gui-00002 Unable to encrypt password -Failed to encrypt the controllerpassword given.

Make sure you are using thecorrect Snap Creatorexecutable. Verify that /etc/snapcreatorgui.conf iscorrect.

gui-00003 Unable to get a list of log files -Failed to get the list of log files.Either log or correspondingprofile folder does not exist.

Ensure that logs andcorresponding profile folderexist.

gui-00004 Unable to find profiles path -Unable to find /logs/

Check if /logs/ exists.

gui-00005 Unable to load configurationfile - Configuration filecorresponds to a particularprofile does not exist.

Check if corresponding profileand configuration exists in theconfigs directory.

gui-00006 snapcreator.conf file not found- Failed to loadsnapcreatorgui.conf fileunder /gui/etc.

Try running

snapcreator profile

setup

, if thesnapcreatorgui.conf islost.

gui-00007 Unable to update configurationfile - Failed to write intoparticular profile config file.Same is deleted or renamed.

Check if your config isrenamed or deleted.

gui-00008 Invalid username or password -Failed to login to the system.Either because of wrongusername/password or not donethe --profile setup

Check your user name andpassword and verify if you ransnapcreator profile

setup.

gui-00009 Unable to delete file - Unableto delete profile folder or configfile. File does not exist or doesnot have the permission toperform the operation

Check if permissions on file/folder and if they exists.



gui-00010 Unable to rename file - Unableto rename profile folder orconfig file. File does not existor does not have the permissionto perform the operation.

Check if permissions on file/folder and if they exists.

gui-00011 Directory exists - Cannot createa new profile. Profile with samename already exist.

Choose a different profile ordelete the already existing one.

gui-00012 Unable to find configs directorycontaining the profiles - Unableto find /configs folder

Verify if configs directoryexists and if you ransnapcreator profile setup.

gui-00013 Unknown failure. Checkservice logs for more details -Unexpected error orRuntimeException happened.Needs to check the log for moredetails.

Check the logs for moreinformation.

gui-00014 Unable to update configurationproperty

Close the configuration andopen it again.

gui-00015 Configuration file not found. Check if permissions on fileand if they exists.

gui-00017 Unable to retrieve vCenterDatacenter information!

Check if your vCenter is correctand has a valid Datacenter.

gui-00019 Error while retrieving VM Listfor Datastore

Try again, as the datastoremight have been deleted duringretrieval.

gui-00020 Error while retrieving VMinformation for Datastore.

Try again, as the datastoremight have been deleted duringretrieval.

gui-00021 Error while retrieving DatastoreList!

Try again, Verify your vCenteris correct.

gui-00022 No Datastores found! Add Datastores to yourvCenter.

gui-00023 Error while retrieving DatastoreInformation!

Try again, verify your vCenter.



gui-00024 Unsupported vCloud APIversion

The version of vCloud Directoryou are using is unsupported.

gui-00025 Invalid vCloud Credentials! Enter correct credentials and tryagain.

gui-00026 Unable to find Organizations! Organizations not found forvCD. Create Organizations andretry.

gui-00027 Unable to Login to vCenter.Please check IP/Hostname andLogin details.

Check your vCentercredentials.

gui-00028 Verify controller details/NTAP_USERS configparameter.

Check the controller details/NTAP_USERS.

gui-00029 Invalid vCloud DirectorOrganization URL!

Verify the vCloud DirectorURL.

gui-00030 Unable to retrieve VDC List! Check if vDCs exist for theorganizations.

gui-00031 Unable to retrieve vApp List! Check if vApps exist for thevDCs.

gui-00032 Snapshot list operation failed. Check controller credentialsand volume parameters in theconfiguration file.

gui-00033 File list operation failed. Check controller credentialsand volume parameters in theconfiguration file.

gui-00034 License verification failed. Check controller credentialsand volume parameters in theconfiguration file.

gui-00035 Snapshot creation failed. Check controller credentialsand volume parameters in theconfiguration file.

gui-00036 Failed to create recoverySnapshot.

Check controller credentialsand volume parameters in theconfiguration file.



gui-00037 Post restore operation failed. Check controller credentialsand volume parameters in theconfiguration file.

gui-00038 Pre restore operation failed. Check controller credentialsand volume parameters in theconfiguration file.

gui-00039 File restore operation failed. Check controller credentialsand volume parameters in theconfiguration file.

gui-00040 SIS Clone start failed. Check controller credentialsand volume parameters in theconfiguration file.

gui-00041 SIS Clone clear failed. Check controller credentialsand volume parameters in theconfiguration file.

gui-00042 Failed to get API versioninformation.


gui-00043 Volume restore operationfailed.


gui-00044 Only admin user can performthis operation.

You need to log in as an adminuser to perform this operation,

gui-00045 User already exists. Use a different username.

gui-00046 Admin user has access to allprofiles, invalid operation!

No need to assign profiles toadmin user. Admin user alreadyhas access.

gui-00047 A user can only be assignedAll(Administrator) orNone(ReadOnly) or a set ofOther actions!

Either select just Administratoror just Read-only or acombination of other actions.

gui-00048 Admin user has access to allactions, invalid operation!

No need to assign actions toadmin user. Admin user alreadyhas access.

gui-00049 Action is not allowed for thisuser.

Check with your administratorand request for permissions.



gui-00050 Verify Cluster details/CMODE_CLUSTER_USERSconfig parameter.

Check and correct Clusterdetails/CMODE_CLUSTER_USERSparameter.

gui-00051 Cluster details are not valid,please verify.

Check cluster details inconfiguration as they seem tobe invalid.

gui-00052 Controller already exists! Youcan update the username/password, just by a doubleclick.

You are adding the samecontroller again to theconfiguration, please add a newcontroller or update the existingone.

gui-00053. Cluster already exists! You canupdate the username/password,just by a double click

You are adding the same clusteragain to the configuration,please add a new controller orupdate the existing one.

gui-00054 No host systems found at theVCenter.

vCenter doesn't have any ESXhosts. Please add and try again.

gui-00055 ZAPI Execution IO Error! IO error thrown by thecontroller.

gui-00056 ZAPI Execution protocol Error! Protocol error was thrown bythe controller.

gui-00057 ZAPI Execution API FailureError!

API failed, check the errordescription in logs.

gui-00058 ZAPI Execution AuthenticationError!

Invalid controller/clustercredentials

gui-00059 Error setting job monitor size,verifySNAPCREATOR_JOB_MONITOR_SIZE entry insnapcreatorgui.conf

Correct value ofSNAPCREATOR_JOB_MONITOR_SIZE insnapcreatorgui.conf.

gui-00060 Error stopping job monitor,verifySNAPCREATOR_JOB_MONITOR entry insnapcreatorgui.conf

Correct value ofSNAPCREATOR_JOB_MONITOR insnapcreatorgui.conf.



gui-00061 Error starting job monitor,verifySNAPCREATOR_JOB_MONITOR entry insnapcreatorgui.conf

Correct value ofSNAPCREATOR_JOB_MONITOR insnapcreatorgui.conf.

gui-00062 Log file not found. Log file you are looking todownload is not available onthe server.

gui-00063 User session expired, pleaselogin again.

Log in again.

gui-00064 This task is already running. You cannot run the same taskagain while it is alreadyrunning.

gui-00065 Maximum size for Job Monitoris 1000 and minimum is 1

Set the job monitor size onlybetween 1-1000.

Oracle Plug-in error messages


ora-00001 Verifying correct version ofdatabase <db> failed

Verification failed, check ORAerror and re-run sqlplusmanually.

ora-00002 Database <db> is runningOracle <ver>, only 10g orhigher are supported!

Oracle 8 and 9 are notsupported by Snap Creator.

ora-00003 Verifying RAC status fordatabase <db> failed

RAC check failed, check ORAerror and re-run sqlplusmanually.

ora-00004 Verifying archive log mode ofdatabase <db> failed

Archive log mode check failed,check ORA error and re-runsqlplus manually.

ora-00005 Database <db> is notconfigured in Archive LogMode

Archive log mode must be set.Please configure db in archivelog mode and restart backup.

ora-00006 Creating a backup controlfilefor <db> to <control file>failed

Check permissions of directorywhere backup control file isbeing created.



ora-00007 Archive Log only backup fordatabase <db> failed

The archive log only mode wasselected and failed. The oracleplug-in will do an archive logcurrent, look at ORA error andtry running manually.

ora-00008 Starting hot backup mode fordatabase <db> failed

The hot backup mode beginsqlplus command failed, checkORA error and re-run sqlplusmanually.

ora-00009 Quiescing databases finishedwith errors

Quiesce completed but witherrors, check logs.

ora-00010 Ending hot backup mode fordatabase <db> failed

The hot backup mode endsqlplus command failed, checkORA error and re-run sqlplusmanually.

ora-00012 Unquiescing databases finishedwith errors

Unquiesce completed but witherrors, check logs.

ora-00013 Retrieving database objects ofdatabase <db> failed

Discovery is enabled but cannotlocate data files and archivelogs, check ORA error and re-run sqlplus manually.

ora-00014 Discovering databases failed Database discovery failed,check log.

ora-00015 Collection of OS informationfailed - <error message>

SCDUMP failed and we wereunable to collect OSinformation, check commandthat was run and try runningmanually.

ora-00017 Collection of SnapDriveinformation failed - <errormessage>

SCDUMP failed and we wereunable to collect SnapDriveinformation, check path toSnapDrive command andpermissions.

ora-00018 Collecting Oracle informationfor database <db> failed

SCDUMP failed and we wereunable to collect Oracleinformation, check ORA errorand re-run sqlplus manually.



ora-00019 No SQLPLUS_CMD defined The SQLPLUS_CMD is arequired oracle plug-in configparameter.

ora-00020 Oracle SQL*Plus command<sqlplus cmd> failed withreturn code <exit code/> andmessage <error message>

The sqlplus command failedcheck error.

MySQL plug-in error messages


mys-00001 Database connection does notexist

A connection to databasecannot be established, try telnetto port usually 3306, this couldbe local firewall or networkissue.

mys-00002 Database connection problemfor <db> detected


mys-00003 Quiescing databases finishedwith errors

Quiesce failed, please checklog.

mys-00004 Database connection does notexist


mys-00006 Unquiescing databases finishedwith errors

Unquiesce failed, please checklog.

mys-00007 SQL command <sql query> didnot return any lines

The sql query didn't returnoutput, please check foradditional errors.

mys-00008 Discovering databases finishedwith errors

Discovery failed, please checklog.



mys-00009 Collection of OS informationfailed - <error message>

SCDUMP failed, couldn'tcollect OS information, pleasecheck error and ensure OScommand is specified in path.

mys-00010 Collection of SnapDriveinformation failed - <errormessage>

SCDUMP failed, couldn'tcollect SnapDrive information,please check error and ensureSnapDrive command isspecified in path.

DB2 plug-in error messages


db2-00001 Quiescing database <db> failedwith message <error message>

Quiesce failed for db, checkerror message and try runningcommand manually.

db2-00002 Quiescing databases failed Quiesce of databases failed,check log.

db2-00003 Unuiescing database <db>failed with message <errormessage>

Unquiesce failed for db, checkerror message and try runningcommand manually.

db2-00004 Unquiescing databases failed Unquiesce of databases failed,check log.

db2-00005 Retrieving database path usedfor database <db> failed

Discovery of database failedcould not find path, checkPATH settings.

db2-00007 Retrieving tablespaces fordatabase <db> failed

Discovery could not retrievetable spaces, check databaseerror and try running manually.

db2-00008 Retrieving tablespacecontainers for database <db>failed

Discovery could not retrievetable space containers, checkdatabase error and try runningmanually.

db2-00009 Retrieving databaseconfiguration for database<db> failed

Discovery could not retrievedatabase configuration, checkdatabase error and try runningmanually.



db2-00010 Discovering databases failed Discovery failed, please checklog.

db2-00011 Collection of OS informationfailed - <error message>

SCDUMP failed, could notcollect OS information, checkcommand and ensure it is inPATH.

db2-00013 Collection of SnapDriveinformation failed - <errormessage>

SCDUMP failed, couldn'tcollect SnapDrive information,check command and ensure it isin PATH.

db2-00014 Collecting DB2 information fordatabase <db> failed withmessage <error message>

SCDUMP failed, couldn'tcollect DB information, checkdatabase error and try runningmanually.

Lotus Domino plug-in error messages


ltd-00001 Domino plugin cannot workwithSNAP_TIMESTAMP_ONLY= N.SNAP_TIMESTAMP_ONLYshould be set to Y.

For Domino plug-in to workSNAP_TIMESTAMP_ONLYshould always be set to Y in theconfig file. This error isdisplayed ifSNAP_TIMESTAMP_ONLYis set to N.

ltd-00002 Quiescing databases finishedwith errors

Domino plug-in was unable toquiesce all the databasessuccessfully. Check the logs tofind the exact reason for theerror or run snapcreator indebug mode to find the error.

ltd-00003 Unquiescing databases finishedwith errors

Domino plug-in was unable tounquiesce all the databasessuccessfully. Check the logs tofind the exact reason for theerror or run snapcreator indebug mode to find the error.



ldt-00004 Discovering databases failed Application discovery faileddue to application error. Checkconfig and application settings.You can disable auto discoveryby settingAPP_AUTO_DISCOVERY=Nand commenting outVALIDATE_VOLUMES.

ldt-00005 Collection of OS informationfailed

The scdump action failed due toerror collecting OSinformation. Check the logs andtry running the commandmanually by hand.

ldt-00006 Collection of SnapDriveinformation failed

The scdump action failed due toerror collecting SnapDriveinformation. Check the logs andtry running the commandmanually by hand.

ldt-00008 Restoring databases finishedwith errors

Domino plug-in was unable torestore all the databasessuccessfully. Check the logs tofind the exact reason for theerror or run snapcreator indebug mode to find the error.

ldt-00009 Domino plugin could'nt beloaded.

Reasons could be 1) Dominoplug-in is not supported on thisplatform.2)Prerequisites fordomino plug-in to run are notsatisfied. Please checkdocumentation(domino plug-insetup).

SnapManager for Microsoft Exchange plug-in error messages


sme-00001 SME is only supported onwindows operating systems

SnapManager for MicrosoftExchange is only supported onWindows.

sme-00002 Quiescing databases failed Quiesce failed, check othererror messages and log.



sme-00003 Collection of OS informationfailed - <error message>

SCDUMP failed, could notcollect operating systeminformation, ensure operatingsystem command is in path andcheck log.

sme-00004 Collection of SnapDriveinformation failed - <errormessage>

SCDUMP failed, could notcollect SnapDrive information,ensure SnapDrive command isin path and check log.

sme-00005 Command <command> failedwith return code <exit code>and message <error message>

The Powershell commandfailed, please check errormessage and try runningmanually.

SnapManager for Microsoft SQL Server plug-in error messages


sms-00001 SMSQL is only supported onwindows operating systems

SnapManager for MicrosoftSQL Server is only supportedon Windows.

sms-00002 Quiescing databases failed Quiesce failed, check othererror messages and log.

sms-00003 Collection of OS informationfailed - <error message>

SCDUMP failed, could notcollect operating systeminformation, ensure operatingsystem command is in path andcheck log.

sms-00004 Collection of SnapDriveinformation failed - <errormessage>

SCDUMP failed, could notcollect SnapDrive information,ensure SnapDrive command isin path and check log.

sms-00005 Command <command> failedwith return code <exit code>and message <error message>

The Powershell commandfailed, please check errormessage and try runningmanually.

Sybase ASE plug-in error messages



syb-00001 SYBASE:QUIESCE:Quiescing database <db>failed, it is already quiesced!

Wait for unquiesce to completeor run a unquiesce manually.

syb-00002 SYBASE:QUIESCE: Could notget Database <db> status,ensure database is running!

Couldn't verify database, checkto make sure it is running andtry running commandmanually.

syb-00004 SYBASE:QUIESCE:Quiescing databases failed

Quiesce failed, please checklog.

syb-00005 SYBVASE:UNQUIESCE:Unquiescing databases failed

Unquiesce failed, please checklog.

syb-00006 SYBASE:DISCOVER: Error inrunning isql. Exiting

Error running isql command,check additional errorinformation and try runningcommand manually.

syb-00007 SYBASE:DISCOVER: Error inrunning isql. Exiting

Error running isql command,check additional errorinformation and try runningcommand manually.

syb-00008 SYBASE:DISCOVER: Error inthrowing back the paths toSC_Framework

Discovery failed, couldn't sendthe necessary information backto framework. Check foradditional errors and info inlog.

syb-00009 Collection of OS informationfailed - <error message>

SCDUMP failed, couldn'tcollect OS info. Please ensureOS command is in path andcheck log.

syb-00010 Collection of SnapDriveinformation failed - <errormessage>

SCDUMP failed, couldn'tcollect SnapDrive info. Pleaseensure SnapDrive command isin path and check log.

syb-00012 SYBASE:RUN_CMD:Command xxxxx failed withreturn code <exit code> andmessage <error message>

A Sybase command failed,check error and try runningmanually.



syb-00013 SYBASE:RUN_CMD: <errormessage>

Generic error message, checkerror and log.

VMware plug-in error messages


vmw-00001 Could not remove (leftover)snapshot for VM <vm_name>:<msg>>!

A SOAP error (web access)occurred while trying to callRemoveSnapshot() in VMwarefor a Snapshot taken as part ofthe backup or restore operation.Use Snapshot Manager in thevSphere Infrastructure Client toremove any Snapshot copiescreated that is unwanted.

vmw-00002 Could not create snapshot forVM <vm_name>!

Calling the CreateSnapshot()function in VMware did notwork as expected -- either theVM cannot make a Snapshot ora vSphere error occurred. Usethe vSphere InfrastructureClient to evaluate the Snapshoterror condition.

vmw-00003 No IP address found for NFSDatastore <ds_name>!

The IP address associated to theNFS datastore could not betranslated, meaning based onthe storage controllersspecified, there is no IP addresson any storage controllerassociated to an NFS export.Verify all the appropriatestorage controllers are listed inthe NTAP_USERS field of theSnap Creator configuration file.



vmw-00004 <remote_host> not found instorage appliance list!

The hostname and IP addressassociated to the NFS datastorecould not be translated,meaning based on the storagecontrollers specified, there is noIP address on any storagecontroller associated to an NFSexport. Verify all theappropriate storage controllersare listed in the NTAP_USERSfield of the Snap Creatorconfiguration file.

vmw-00005 No disk name found forDatastore <ds_name>!

The VIBE module could notfind a disk extend associated tothe VMFS datastore, whichmeans a matching datastore todisk translation did not appearbased on VMware query of theVMFS disk extent list. Verifythe VMFS datastore listed inthe backup has disk extentsassociated to it.

vmw-00006 Could not find identifying LUNon any storage appliance forVMFS datastore!

Based on a translation of LUNto VMware UUID, a matchingLUN was not found. Thismeans the LUNs on the storagecontrollers associated to theNTAP_USERS field do notmap to this VMFS datastore.Verify all the appropriatestorage controllers are listed inthe NTAP_USERS field of theSnap Creator configuration file.



vmw-00007 ONTAP API call lun-list-infofailed: <msg>

The reported Data ONTAP APIcall was unsuccessful. Read theerror message and contacttechnical support for anynecessary assistance intranslating the error message.The condition can normallyoccur in situations whereRBAC is in use and the SnapCreator user on the storagecontrollers do not havesufficient access for the APIcall.

vmw-00008 ONTAP API call lun-get-serial-number failed: <msg>


vmw-00009 Query of Datacenter failed:<msg>!

A SOAP error (web access)occurred while trying to querythe list of DataCenter objects inVMware. Review the eventlogs in the vSphereInfrastructure Client to removeany Snapshot copies createdthat is unwanted.



vmw-00010 Query of Datacenter failed! A general vSphere API erroroccurred while trying to querythe list of DataCenter objects inVMware. Review the eventlogs in the vSphereInfrastructure Client to removeany Snapshot copies createdthat is unwanted.

vmw-00011 Could not find entity views forDatacenter!

A general vSphere API erroroccurred while trying to querythe Managed Object referenceto a given DataCenter object inVMware. Review the eventlogs in the vSphereInfrastructure Client to removeany Snapshot copies createdthat is unwanted.

vmw-00012 Datastore <msg> not found inany Datacenter!

The datastore specified forbackup is not associated to theDataCenter in the vCenterserver. The VIBE modulecurrently supports oneDatacenter per vCenter server.In addition, verify the Datastorename is properly listed in theSnap Creator configuration file.

vmw-00013 <controller_name> not found instorage appliance list (privatesubnets for NFS Datastores?)!

The set of Snapshot locationsqueried through the process ofcollecting VMFS and NFSdatastore information found adatastore that does not have anassociated Snapshot location.Verify that all storagecontrollers are listed in theNTAP_USERS field in theSnap Creator configuration file.

vmw-00014 VIBE_TRIM_VSPHERE_NAMES format is wrong (no extracolons, semi-colons or commasallowed per entry)!

The format of theVIBE_TRIM_VSPHERE_NAMES field is incorrect. Reviewthe format in the Snap Creatorconfiguration file for accuracy.



vmw-00015 Query of VirtualMachine objectfailed: <msg>!

A SOAP error (web access)occurred while trying to query aspecific Virtual Machine objectin VMware. Review the eventlogs in the vSphereInfrastructure Client to removeany Snapshot copies createdthat is unwanted.

vmw-00016 Query of Virtual Machineobject failed!

A general vSphere API erroroccurred while trying to query aspecific Virtual Machine objectin VMware. Review the eventlogs in the vSphereInfrastructure Client to removeany Snapshot copies createdthat is unwanted.

vmw-00017 Could not get API versionsfrom vCD: (<code>: <msg>)!

The REST API call /api/versions to the vCloud Directorfailed. This call should alwayssucceed, which may mean thevCD server specified in theSnap Creator configuration fileis not correct. Verify the SnapCreator configuration file orcheck the vCD logs for moreinformation.

vmw-00018 Could not get login URL inAPI versions results from vCD:(<code>: <msg>)!

The REST API call /api/versions to the vCloud Directordid not return a properauthentication cookie. This callshould always succeed, whichmay mean the vCD serverspecified in the Snap Creatorconfiguration file is not correct.Verify the Snap Creatorconfiguration file or check thevCD logs for more information.



vmw-00019 Could not login to vCD:(<code>: <msg>)!

The REST API call /login tothe vCloud Director failed.Verify the proper user name,password and URL for the vCDand review the vCD logs forany RBAC or other errorconditions.

vmw-00020 Could not get Organizations:(<code>: <msg>)!

The REST API call to list allOrganizations within vCloudDirector failed. Verify theproper user name, passwordand URL for the vCD andreview the vCD logs for anyRBAC or other errorconditions.

vmw-00021 Could not get vDCs forOrganization<organization_name>:(<code>: <msg>)!

The REST API call to query aspecific Organization withinvCloud Director failed. Verifythe proper user name, passwordand URL for the vCD andreview the vCD logs for anyRBAC or other errorconditions.

vmw-00022 Could not get vCD vApps:(<code>: <msg>)!

The REST API call to query thelist of vApps associated to avDC within vCloud Directorfailed. Verify the proper username, password and URL forthe vCD and review the vCDlogs for any RBAC or othererror conditions.

vmw-00023 Could not get vCenter data:(<code>: <msg>)!

The REST API call to collectthe vCenter server associated toa given vApp within vCloudDirector failed. Verify theproper user name, passwordand URL for the vCD andreview the vCD logs for anyRBAC or other errorconditions.



vmw-00024 Could not get vCD VMs:(<code>: <msg>)!

The REST API call to get thespecific VMs associated to avApp within vCloud Directorfailed. Verify the proper username, password and URL forthe vCD and review the vCDlogs for any RBAC or othererror conditions.

vmw-00025 No IP address for host<hostname>!

The gethostbyname() call forthe specified vCenter server inthe Snap Creator configurationfile could not be translated.Verify the specified vCentername can be translated to an IPaddress, or specify an IPaddress instead.

vmw-00026 Cannot ping <vcenter_name>! The IP address associated to thevCenter server cannot bepinged via ICMP. Verify the IPaddress is correct, or use theVIBE_NOPING=Y field in theSnap Creator configuration file.

vmw-00027 vCenter server login failed --invalid login!

The permissions associated tothe vCenter user name orpassword is invalid. VerifyvCenter server access with thevCenter user name andpassword specified in the SnapCreator configuration file.

vmw-00028 vCenter server login failed --internal error!

A general login error occurredusing the vCenter user nameand password in the SnapCreator configuration file.Review event and access logsin the vSphere InfrastructureClient for more details.



vmw-00029 vCenter server login failed --check authentication andfirewall settings (<msg>)!

An authentication erroroccurred using the vCenter username and password in the SnapCreator configuration file. Theeither user name or passwordare likely incorrect. Reviewevent and access logs in thevSphere Infrastructure Clientfor more details.

vmw-00030 Cannot ping storage appliancenamed <controller_name>:<msg>!

The IP address associated to thestorage controller cannot bepinged via ICMP. Verify the IPaddress is correct, or use theVIBE_NOPING=Y field in theSnap Creator configuration file.

vmw-00031 ONTAP API connection to<controller_name> failed:<msg>!

The Data ONTAP API callsystem-get-info failed. IfRBAC is in use, verify the userhas access to the system-get-info API call. In addition,verify API access is available tothe default HTTPS port forData ONTAP API access.

vmw-00032 Storage appliance did not havenetwork configurationinformation!

Execution of the Data ONTAPAPI call system-cli wasunsuccessful, and the 'ifconfig -a' output could not be pulledfrom the controller. Verifynetwork interface and DataONTAP API networkconfiguration information isavailable and correct.



vmw-00033 ONTAP API inquiry snapshot-list-info on <volume_name>failed: <msg>


vmw-00034 ONTAP API inquiry snapshot-list-info on <volume_name>failed: <msg>


vmw-00035 Power off of virtual machine<vm_name> failed: <msg>!

A general SOAP error occurredwhen executing thePowerOffVM() operation invSphere. Review the vSphereInfrastructure Client logs fordetails on why the operationcould not be completed.

vmw-00036 Power off of virtual machine<vm_name> failed!

The vSphere PowerOffVM()call was unsuccessful. Reviewthe vSphere InfrastructureClient logs for details on whythe operation could not becompleted.



vmw-00037 Problem powering on VM<vm_name>: <msg>!

A general SOAP error occurredwhen executing thePowerOnVM() operation invSphere. Review the vSphereInfrastructure Client logs fordetails on why the operationcould not be completed.

vmw-00038 Problem powering on VM<vm_name>!

The vSphere PowerOnVM()call was unsuccessful. Reviewthe vSphere InfrastructureClient logs for details on whythe operation could not becompleted.

vmw-00039 Could not power off vApp<vapp_name> (<code>:<msg>)!

The vCloud power off RESTAPI operation failed. Reviewthe vCD logs for specificreasons why the operationcould not be completed.

vmw-00040 Could not power on vApp<vapp_name> (<code>:<msg>)!

The vCloud power on RESTAPI operation failed. Reviewthe vCD logs for specificreasons why the operationcould not be completed.

vmw-00041 Failure in parsing volume pathformat of "<volume_path>"!

The volume path does notconsist of<controller_name>:<volume_name>. Review the logs and seewhere the volume or storagecontrollers are not beingtranslated properly.



vmw-00042 ONTAP API file-list-directory-iter-next failed: <msg>


vmw-00043 ONTAP API call snapshot-restore-file failed: <msg>


vmw-00044 ONTAP API file-list-directory-iter-start failed: <msg>




vmw-00045 Timer expired on busy single-file snap restore, still running(increaseVIBE_RESTORE_TIME)!

There are situations where therestore operation on the storagecontroller takes a very longtime, either due to a busyFilesystem or a large amount ofdata requiring to be restored. Inthis case, theVIBE_RESTORE_TIME valuein the Snap Creatorconfiguration file must beincreased to allow for a longerrestoration period.

vmw-00046 ONTAP API call license-list-info failed: <msg>


vmw-00047 ONTAP API call volume-clone-create failed: <msg>




vmw-00048 ONTAP API call lun-create-clone failed: <msg>


vmw-00049 ONTAP API call volume-offline failed: <msg>


vmw-00050 ONTAP API call volume-destroy failed: <msg>




vmw-00051 ONTAP API call lun-destroyfailed: <msg>


vmw-00052 ONTAP API call lun-onlinefailed: <msg>


vmw-00053 ONTAP API call lun-map-list-info failed: <msg>




vmw-00054 Initiators for LUN <lun_name>do not exist!

The LUN with the appropriateUUID mapped to an vSpherehost does not have any initiatorgroups associated to the LUN,which means the Datastore mayhave either been unmapped orremoved in the middle of arestore operation. Verify theLUN IDs on the storagecontroller are unique and thatthere are no forced mounts ofduplicate datastores in thevSphere environment.

vmw-00055 ONTAP API call lun-mapfailed: <msg>


vmw-00056 Storage query of host system<esx_host_name> failed:<msg>!

Execution of theRefreshStorageSystem()vSphere API call failed due to ageneral SOAP error (webservices). Verify connectivityto the vCenter server andproper vSphere host and clusterconfiguration within thevSphere environment where theVM restore is taking place.



vmw-00057 Storage query of host system<esx_host_name> failed!

Execution of theRefreshStorageSystem()vSphere API call failed to thevCenter server. Verifyconnectivity to the vCenterserver and proper vSphere hostand cluster configuration withinthe vSphere environment wherethe VM restore is taking place.

vmw-00058 Rescan of VMFS file systemson host system<esx_host_name> failed:<msg>!

Execution of the RescanVmfs()vSphere API call failed due to ageneral SOAP error (webservices). Verify connectivityto the vCenter server andproper vSphere host and clusterconfiguration within thevSphere environment where theVM restore is taking place.

vmw-00059 Rescan of VMFS file systemson host system<esx_host_name> failed!

Execution of the RescanVmfs()vSphere API call failed to thevCenter server. Verifyconnectivity to the vCenterserver and proper vSphere hostand cluster configuration withinthe vSphere environment wherethe VM restore is taking place.

vmw-00060 ONTAP API call snapshot-create failed: <msg>




vmw-00061 ONTAP API call snapshot-delete failed: <msg>


vmw-00062 vCenter validation of sessionfailed: <msg>!

A SOAP error occurred whenrefreshing the vSphere sessionto the vCenter server. This iscalled after a restore operation,primarily for situations where along restore operation is takingplace and the connection to thevCenter server times out.Verify the timeout values in thevCenter server or ensure propernetwork connectivity to thevCenter server.

vmw-00063 vCenter validation of sessionfailed!

A general error occurred whenrefreshing the vSphere sessionto the vCenter server. This iscalled after a restore operation,primarily for situations where along restore operation is takingplace and the connection to thevCenter server times out.Verify the timeout values in thevCenter server or ensure propernetwork connectivity to thevCenter server.



vmw-00064 vCenter view validation ofsession failed: <msg>!

A SOAP error occurred whenrefreshing the session managerManaged Object view of thevSphere session to the vCenterserver. This is called after arestore operation, primarily forsituations where a long restoreoperation is taking place andthe connection to the vCenterserver times out. Verify thetimeout values in the vCenterserver or ensure proper networkconnectivity to the vCenterserver.

vmw-00065 vCenter view validation ofsession failed!

A general error occurred whenrefreshing the session managerManaged Object view of thevSphere session to the vCenterserver. This is called after arestore operation, primarily forsituations where a long restoreoperation is taking place andthe connection to the vCenterserver times out. Verify thetimeout values in the vCenterserver or ensure proper networkconnectivity to the vCenterserver.

vmw-00066 vCenter new login failed --invalid login!

Creation of a new vCentersession after a long restoreoperation has failed. Verify thetimeout values in the vCenterserver or ensure proper networkconnectivity to the vCenterserver. This should normallynot occur unless someone ischanging the vCenterconfiguration andauthentication during an activerestore operation.



vmw-00067 vCenter new login failed --internal error!

Creation of a new vCentersession after a long restoreoperation has failed. Verify thetimeout values in the vCenterserver or ensure proper networkconnectivity to the vCenterserver. This should normallynot occur unless someone ischanging the vCenterconfiguration andauthentication during an activerestore operation and is evenmore unique in that the vSphereAPI call has come back with anundefined error condition.

vmw-00068 vCenter new login failed --check authentication andfirewall settings!

The permissions associated tothe vCenter user name andpassword is invalid. VerifyvCenter server access with thevCenter user name andpassword specified in the SnapCreator configuration file. Thiswould only happen if there isan active restore, a timeout hasoccurred to the vCenter serverand the authenticationparameters to the vCenterserver for the user havechanged.

vmw-00069 Query of host systems failed:<msg>!

A SOAP error (web access)occurred while trying to query aspecific Host System object invSphere during a restoreoperation on an NFS datastore.Review the event logs in thevSphere Infrastructure Client toremove any Snapshot copiescreated that is unwanted.



vmw-00070 Query of host systems failed! A general occurred while tryingto query a specific Host Systemobject in vSphere during arestore operation on an NFSdatastore. Review the eventlogs in the vSphereInfrastructure Client to removeany Snapshot copies createdthat is unwanted.

vmw-00071 Could not find entity views forHostSystem!

When querying for hostsystems associated to thevCenter server, no hosts cameback as connected to thevCenter server. This is a highlyimprobable error -- verifyconnectivity to the vCenterserver and proper configurationof host systems through thevSphere Infrastructure Client.

vmw-00072 No host system with Datastorenamed <datastore_name>found!

The datastore specified forrestore does not show up onany host system in vSphere.This is highly unlikely to occurunless the Datastore isdisconnected in the middle of arestore operation. Verifyconnectivity to the vCenterserver and proper configurationof host systems through thevSphere Infrastructure Client.



vmw-00073 Query of host system viewfailed: <msg>!

Collection of the entity view ofthe Host System specified forrestore where the originalVMFS datastore is found couldnot be executed to the vCenterserver. Given the restore hostsystem has already beenuncovered, this query shouldalways be successful unlessthere is a connectivity problemor an vSphere host is put intomaintenance mode during arestore operation. Verifyconnectivity to the vCenterserver and proper configurationof host systems through thevSphere Infrastructure Client.

vmw-00075 Could not find entity views forhost system!

Query of the entity view on therestore host could not beexecuted to the vCenter server.Given the restore host systemhas already been uncovered,this query should always besuccessful unless there is aconnectivity problem or anvSphere host is put intomaintenance mode during arestore operation. Verifyconnectivity to the vCenterserver and proper configurationof host systems through thevSphere Infrastructure Client.



vmw-00076 Could not find new Datastore tocopy VMs from!

Discovery of the new VMFSdatastore that has been cloned,mapped and rescanned to therestore host has failed. Thismeans that despite multipleHBA and VMFS rescans,mapping of the cloned LUNassociated to the VMFSdatastore and refreshing of therestore host, the new Datastorewas still not shown. Verifyadvanced options settings withthe vSphere host, make sureresignatured VMFS volumescan be discovered, verifyconnectivity to the vCenterserver and validate properconfiguration of host systemsthrough the vSphereInfrastructure Client.

vmw-00077 vCenter validation of sessionfailed: <msg>!

A query of the session managerin the vCenter server objectfailed due to a SOAP error(web services). Verify theconnection to the vCenterserver has not timed out.

vmw-00078 vCenter validation of sessionfailed!

A query of the session managerin the vCenter server objectfailed. Verify the connection tothe vCenter server has nottimed out.

vmw-00079 CopyDatastoreFile() onDatastore <datastore_name>failed: <msg>!

Data cannot be copied from theVMFS datastore Snapshot intothe original Datastore for theVM. The <msg> output willoutline why the VMware APIcall failed. Verify properconfiguration and permissionsto the Datastore folder throughthe vSphere InfrastructureClient.



vmw-00080 Problem reverting to VMsnapshot for <vm_name>:<msg>!

A SOAP error (web access)occurred while trying toexecute theRevertToCurrentSnapshot() ona VM in vSphere during arestore operation on a VMFSdatastore. Review the eventlogs in the vSphereInfrastructure Client to removeany Snapshot copies createdthat is unwanted.

vmw-00081 Problem reverting VM snapshotfor <vm_name>!

A general error occurred whiletrying to execute theRevertToCurrentSnapshot() ona VM in vSphere during arestore operation on a VMFSdatastore. Review the eventlogs in the vSphereInfrastructure Client to removeany Snapshot copies createdthat is unwanted.

vmw-00082 Could not clear LUN -- LUN/volume clone must be clearedmanually!

The LUN or volume cloneassociated to the restore of aVM on a VMFS Datastorecould not be taken offline ordestroyed. If FlexClonelicensing exists on the storagecontroller, it is the volumeclone that cannot be takenoffline or destroyed. If a LUNclone was created, the clonedLUN cannot be taken offline ordestroyed. Review the storagecontroller event messages forerrors related to the ONTAPAPI calls.



vmw-00083 Could not destroy temporarysnapshot -- may need manualcleanup!

The VIBE restore Snapshotcopies created as part of therestore process cannot beremoved. The storage controllerSnapshot on the volume wherethe Datastore was created mustbe removed manually.

vmw-00084 Restore operation of VM filesfailed -- reverting to originalcontents!

The single-file snap restore(SFSR) operation on thestorage controller failed. Therewill generally be another errormessage in the Snap Creatorlog displaying exactly why theSFSR operation did notcomplete. Look for timeoutconditions, space availability orvSphere refresh times for moreclues as to why the SFSRoperation did not complete.

vmw-00085 Restore operation of VM filesfailed -- confirm contents ofVM directory!

If the first SFSR restoreoperation on the NFS Datastoredid not complete, and thesecond SFSR restoring back tothe VIBE restore Snapshot alsofails, this message appears.Review storage controller andSnap Creator logs for moredetailed messages as to why theSFSR operations are notcompleting.

vmw-00086 Problem reverting to VMsnapshot for <vm_name>:<msg>!

A SOAP error (web access)occurred while trying toexecute theRevertToCurrentSnapshot() ona VM in vSphere during arestore operation on an NFSdatastore. Review the eventlogs in the vSphereInfrastructure Client to removeany Snapshot copies createdthat is unwanted.



vmw-00087 Problem reverting VM snapshotfor <vm_name>!

A general error occurred whiletrying to execute theRevertToCurrentSnapshot() ona VM in vSphere during arestore operation on an NFSdatastore. Review the eventlogs in the vSphereInfrastructure Client to removeany Snapshot copies createdthat is unwanted.

vmw-00088 Could not destroy temporarysnapshot -- may need manualcleanup!

The VIBE restore Snapshotcreated as part of the restoreprocess cannot be removed.The storage controller Snapshoton the volume where theDatastore was created must beremoved manually.

vmw-00089 Could not find matchingstorage appliance for vCenter/Datastore pair!

If the storage does not appear inan internal list based on avCenter and Datastore pairinternally to VIBE, then the listwas improperly configuredbased on data collection ofexisting vSphere and vCloudobjects. Review the logs andSnap Creator configuration filesand ensure all parameters areproperly defined and no othererrors appear in the SnapCreator log files.

vmw-00090 Restore snapshot<restore_snapshot_name> doesnot exist on storage appliance<controller_name>, volume<volume_name>!

The Snapshot copy specifiedwith the --snap_name optiondoes not exist for the volumeand storage controller listed.Confirm the spelling andexistence of the Snapshot copybeing restored.



vmw-00091 Could not query stateinformation on restore snapshot<restore_snapshot_name>!

The Data ONTAP API callsnaphost-list-info failed -- lookin the Snap Creator log forother error messages indicatingwhy the Data ONTAP API callfailed.

vmw-00092 Restore snapshot<restore_snapshot_name> is ina busy state -- select a differentsnapshot!

VIBE requires that theSnapshot copy being used forrestore purposes on the storagecontroller not be busy -- itcannot be part of a clone or bebusy according to the status onthe storage controller. Runningsnap list on the storagecontroller and looking at thestate of the Snapshot copy inthe volume where the Datastoreis located will indicate whetherthe Snapshot copy is busy, andwhy.

vmw-00093 Restoring of VM(s) onDatastore <datastore_name>failed!

This is a general failuremessage - look for other errormessages for specific failureconditions.

vmw-00094 VIBE_VCENTER_USER notdefined!

The VIBE_VCENTER_USERfield in the Snap Creatorconfiguration file must alwaysbe defined. Check the SnapCreator configuration file andmake sure the value is definedand not commented out.

vmw-00095 VIBE_VCENTER_PASSWDnot defined!

TheVIBE_VCENTER_PASSWDfield in the Snap Creatorconfiguration file must alwaysbe defined. Check the SnapCreator configuration file andmake sure the value is definedand not commented out.



vmw-00096 VIBE_VCLOUD_USER notdefined!

The VIBE_VCLOUD_USERfield in the Snap Creatorconfiguration file must alwaysbe defined when theVIBE_VCLOUD_NAMESconfiguration option is beingused. Check the Snap Creatorconfiguration file and makesure the value is defined andnot commented out.

vmw-00097 VIBE_VCLOUD_PASSWDnot defined!

TheVIBE_VCLOUD_PASSWDfield in the Snap Creatorconfiguration file must alwaysbe defined when theVIBE_VCLOUD_NAMESconfiguration option is beingused. Check the Snap Creatorconfiguration file and makesure the value is defined andnot commented out.

vmw-00098 ACTION not defined! The action field must bedefined. This generally happensthrough use of the --actionoption when executing SnapCreator. Verify propercommand line use of SnapCreator.

vmw-00100 USER_SNAP_NAME notdefined (use --snap_name<snapshot name>)!

When performing a restoreoperation, the Snapshot namemust be specified on thecommand line or throughexecution in the GUI in order toknow which Snapshot toperform the restore from.Verify the Snap Creatorcommand line for propersyntax.



vmw-00101 VIBE_VCLOUD_NAMESformat is wrong (no extracolons, semi-colons or commasallowed per Org entry)!

The format ofVIBE_VCLOUD_NAMESmust be defined based on theformat specified in thecomments of the Snap Creatorconfiguration file. If anyOrganizations, vDCs or vAppshave colons in the names, orany objects within vSphere usecolons, please use differentnaming conventions so thatparsing ofVIBE_VCLOUD_NAMES willwork properly.

vmw-00102 Organization field must bedefined for eachVIBE_VCLOUD_NAMESentry!

When defining a new backupset within a Snap Creatorconfiguration file, theOrganization field must alwaysbe specified. Verify theVIBE_VCLOUD_NAMESsyntax in the Snap Creatorconfiguration file.

vmw-00103 VIBE_VSPHERE_NAMESformat is wrong (no extracolons, semi-colons or commasallowed per vCenter entry)!

The format ofVIBE_VSPHERE_NAMESmust be defined based on theformat specified in thecomments of the Snap Creatorconfiguration file. If anyvCenters, Datastores or VMshave colons in the names,please use different namingconventions so that parsing ofVIBE_VCLOUD_NAMES willwork properly.



vmw-00104 vCenter field must be definedfor eachVIBE_VSPHERE_NAMESentry!

When defining a new backupset within a Snap Creatorconfiguration file, the vCenterfield must always be specified.Verify theVIBE_VSPHERE_NAMESsyntax in the Snap Creatorconfiguration file.

vmw-00105 VIBE_VMWARE_SNAPSHOT must be set to Y or N!

This value must be either Y (thedefault) or 'N' to specify not totake VMware Snapshot copies.

vmw-00106 NTAP_USERS value must be<ip>:<user>/<passwd> pairs(separated by semi-colons)!

Check the NTAP_USERSvalue in the Snap Creatorconfiguration file for propersyntax and format.

vmw-00107 NTAP_USERS value must be<ip>:<user>/<passwd> pairs(separated by semi-colons)!

Check the NTAP_USERSvalue in the Snap Creatorconfiguration file for propersyntax and format.

vmw-00108 Could not create snapshot forVM <vm_name>!

The VM Snapshot creationprocess failed. There will beanother error message in the logindicating the failure. Reviewthe vSphere InfrastructureClient logs for VMware errormessages.

vmw-00109 Snapshot creation process wasNOT completed successfully!

At least one of the VMs whereSnapshot copies were beingcreated did not executeproperly. Review the SnapCreator and vSphereInfrastructure Client logs forerror messages.

vmw-00110 Could not remove snapshot forVM <vm_name>!

The VM snapshot removalprocess failed. There will beanother error message in the logindicating the failure. Reviewthe vSphere InfrastructureClient logs for VMware errormessages.



vmw-00111 Snapshot removal process wasNOT completed successfully!

At least one of the VMs whereSnapshot copies were beingremoved did not executeproperly. Review the SnapCreator and vSphereInfrastructure Client logs forerror messages.

vmw-00112 Collection of OS informationfailed: <msg>!

The scdump() function used forsupport debugging requirescollection of OS information.The internal request to checkthe operating system versiondid not succeed. Review theSnap Creator logs forinformation as to why the erroroccurred.

vmw-00113 Collection of OS informationfailed: <msg>!

The scdump() function used forsupport debugging requirescollection of OS information.The internal request to checkthe operating system versiondid not succeed. Review theSnap Creator logs forinformation as to why the erroroccurred.

vmw-00114 NTAP_PM_UPDATE value setfrom VOLUMES environmentvariable has an invalid numberof array items!

Check theNTAP_PM_UPDATE value inthe Snap Creator configurationfile for proper syntax andformat.

vmw-00115 No datastore systems availableon vSphere host<esx_host_name>!

The datastore system associatedto the vSphere session contextis invalid. Check that thevSphere host used for restoresis operational and not inmaintenance mode. Review thevSphere Infrastructure Clientlogs for more information aboutthe vSphere host status.



vmw-00116 No storage systems availableon vSphere host<esx_host_name>!

The storage system associatedto the vSphere session contextis invalid. Check that thevSphere host used for restoresis operational and not inmaintenance mode. Review thevSphere Infrastructure Clientlogs for more information aboutthe vSphere host status.

vmw-00117 Collection of datastore systemsfor vSphere host failed: <msg>!

The datastore system associatedto the vSphere session contextdoes not have any managedobject reference. Check that thevSphere host used for restoresis operational and not inmaintenance mode. Review thevSphere Infrastructure Clientlogs for more information aboutthe vSphere host status.

vmw-00118 Collection of storage systemsfor vSphere host failed: <msg>!

The storage system associatedto the vSphere session contextdoes not have any managedobject reference. Check that thevSphere host used for restoresis operational and not inmaintenance mode. Review thevSphere Infrastructure Clientlogs for more information aboutthe vSphere host status.

vmw-00119 Scan of unresolved VMFSvolumes for vSphere host<esx_host_name> failed!

TheQueryUnresolvedVmfsVolumes() vSphere API call on the hostsystem failed. Review thevSphere Infrastructure Clientlogs for more information aboutthe vSphere host status.



vmw-00120 Resignature of unresolvedVMFS volumes on vSpherehost failed: <msg>!

TheResolveMultipleUnresolvedVmfsVolumes() vSphere API callon the host system failed.Review the vSphereInfrastructure Client logs formore information about thevSphere host status.

vmw-00121 Failure in file-list-directory-iter-start: <msg>!


vmw-00122 Could not remove (leftover)snapshot for VM <vm_name>!

A SOAP error (web access)occurred while trying to callRemoveSnapshot() in VMwarefor a snapshot taken as part ofthe backup or restore operation.Use Snapshot Manager in thevSphere Infrastructure Client toremove any snapshot createdthat is unwanted.

vmw-00123 Storage query of host system<esx_host_name> failed:<msg>!

Execution of theRescanAllHba() vSphere APIcall failed due to a generalSOAP error (web services).Verify connectivity to thevCenter server and propervSphere host and clusterconfiguration within thevSphere environment where theVM restore is taking place.



vmw-00124 Storage query of host system<esx_host_name> failed!

Execution of theRescanAllHba() vSphere APIcall failed to the vCenter server.Verify connectivity to thevCenter server and propervSphere host and clusterconfiguration within thevSphere environment where theVM restore is taking place.

vmw-00125 vCenter view validation ofsession failed: <msg>!

A query of the file manager inthe vCenter server object faileddue to a SOAP error (webservices). Verify the connectionto the vCenter server has nottimed out.

vmw-00126 vCenter view validation ofsession failed!

A query of the file manager inthe vCenter server object failed.Verify the connection to thevCenter server has not timedout.

vmw-00127 Query of VirtualMachine objectfailed: <msg>!

Collection of the entity view ofthe VirtualMachine during theVM iteration process could notbe executed to the vCenterserver. This is specifically forwhen vCloud objects are re-translated to VM objects invSphere. Verify connectivity tothe vCenter server and properconfiguration of host systemsthrough the vSphereInfrastructure Client and thatthe vCenter IP address iscorrect.



vmw-00128 Query of VirtualMachine objectfailed!

Collection of the entity view ofthe VirtualMachine during theVM iteration process could notbe executed to the vCenterserver. This is specifically forwhen vCloud objects are re-translated to VM objects invSphere. Verify connectivity tothe vCenter server and properconfiguration of host systemsthrough the vSphereInfrastructure Client and thatthe vCenter IP address iscorrect.

vmw-00129 Power off condition of vApp<vm_name> unknown:(<num>: <msg>)!

When the vApp powerOffREST API is executed, theREST return status indicates anunknown condition. ThepowerOff call should alwaysreturn a Task or Error, so itmeans a third condition ofunknown type was returned.Check with VMware on thepossible return codes forvCloud powerOff APIoperations.

vmw-00130 Power on condition of vApp<vm_name> unknown:(<num>: <msg>)!

When the vApp powerOnREST API is executed, theREST return status indicates anunknown condition. ThepowerOn call should alwaysreturn a Task or Error, so itmeans a third condition ofunknown type was returned.Check with VMware on thepossible return codes forvCloud powerOn APIoperations.



vmw-00131 Could not power off vApp<vm_name> unknown:(<num>: <msg>)!

When the vApp powerOffREST API is executed, theREST return status indicates anerror condition. Review theerror code for informationabout the failure, and checkwith VMware on the possiblereturn codes for vCloudpowerOff API operations.

vmw-00132 Could not power on vApp<vm_name> unknown:(<num>: <msg>)!

When the vApp powerOnREST API is executed, theREST return status indicates anerror condition. Review theerror code for informationabout the failure, and checkwith VMware on the possiblereturn codes for vCloudpowerOn API operations.



vmw-00133 Scan for unresolved VMFSvolumes did not find anyentries!

This condition occurs whenVMware is unable to see newDatastores listed in the vSphereenvironment during restoreoperations. The sequence ofevents is to clone, map andonline the new LUN associatedto the VMFS datastore beingrestored on the identified ESXhost. Once this is done, thevSphere API callQueryUnresolvedVmfsVolumes() is called to find unresolvedVMFS volumes not currentlymapped to a datastore orresigned on the ESX host.Essentially, the API callreturned no new entries, whichmeans VMware does not seethe new LUN. Check theexisting vSphere configurationto determine if new Datastorescan be provisioned on therestore ESX host, as well ascheck with VMware on thecondition of the ESX host whennew Datastores are connected.

vmw-00134 Collection of storage systemsfor vSphere host failed: <msg>!

This condition occurs when thevSphere API callQueryUnresolvedVmfsVolumes() fails on the ESX hostidentified for restore. Check theexisting vSphere configurationto determine if new Datastorescan be provisioned on therestore ESX host, as well ascheck with VMware on thecondition of the ESX host whennew Datastores are connected.



vmw-00135 Could not remove snapshot(s)for VM <vm_name>!

Snap Creator deletes VMSnapshot copies on VMs aboutto be restored before startingthe restore process. It is calledto remove leftover Snapshotcopies if any exist. If thisoperation fails, it means SnapCreator has found leftover VMSnapshot copies (created bySnap Creator) that it cannotdelete. Delete these VMSnapshot copies manuallybefore attempting the restoreoperation.

vmw-00136 No snapshot named<snapshot_name> found forVM <vm_name>!

When attempting to removeVM Snapshot copies, theremove function could not finda Snap Creator created VMsnapshot. Verify the existingVMware Snapshot copies andalso ensure two Snap Creatorbackup jobs of the same VMobjects are not taking place atthe same time.

vmw-00137 Restore process had errors anddid not complete successfully!

The restore operation failed.Look for additional vmw-<num> errors in the log outputfor more details as to whatfailed during the restoreprocess.



vmw-00138 No root snapshot list found forVM <vm_name>!

When attempting to removeVM Snapshot copies, theremove function could not finda Snap Creator created VMsnapshot. In addition, therewere no Snapshot copies(period) for the VM .There isno root Snapshot list when thiserror occurs. Verify the existingVMware Snapshot copies andalso ensure two Snap Creatorbackup jobs of the same VMobjects are not taking place atthe same time.


Snap Creator examples

Snap Creator offers the flexibility to perform simple procedures such as creating a Snapshot copy aswell as complex procedures such as SnapMirror destination volume.

Snapshot copy

This example uses Snap Creator to create a consistent Snapshot copy. As a Snapshot copy is the basisfor all operations, all examples require the following settings:

Configuration option Setting

SNAME Snapshot copy name

VOLUMES controller1:vol1,vol2,vol3

NTAP_USERS controller1:snapadm/mypassword

TRANSPORT HTTP

PORT 80

LOG_NUM 10

NTAP_PWD_PROTECTION N

NTAP_SNAPSHOT_RETENTIONS daily:7

Run Snap Creator with the following options:

./snapcreator --profile Profile Name --action snap --policy daily Optional

Arguments

These settings are always required. In this example, we have only created one retention policy set todaily, which retains seven Snapshot copies.

Application-consistent backup

This example combines an application quiesce and unquiesce with a Snapshot copy.


APP_NAME oracle|db2|mysql|<plug-in>

APP_IGNORE_ERROR N

APP_DEFINED_RESTORE N

APP_AUTO_DISCOVERY N

189


APP_CONF_PERSISTENCE Y


./snapcreator --profile Profile Name --action snap --policy Policy Name

Optional Arguments

Snapshot copy and backup to tape

This example uses Snap Creator to create and clone a Snapshot copy, mount this clone, and then backup the mount point to tape using third-party backup software.


NTAP_CLONE_FOR_BACKUP Y

NTAP_CLONE_SECONDARY N

NTAP_CLONE_IGROUP_MAP controller1:src_volume1/igroup1

NTAP_VOL_CLONE_RESERVE none

NTAP_NUM_VOL_CLONES 1

NTAP_LUN_CLONE_RESERVATION false

PRE_NTAP_CLONE_DELETE_CMD1 Mount script or SnapDrive command

PRE_NTAP_CLONE_DELETE_CMD2 CLI command to start backup of mountpoint

To clone a volume, run Snap Creator with the following options:

./snapcreator --profile Profile Name --action clone_vol --policy Policy

Name Optional Arguments

To clone a LUN, run Snap Creator with the following options:

./snapcreator --profile Profile Name --action clone_lun --policy Policy

NameOptional Arguments

Backup to disk (Open Systems SnapVault)

This example uses the Open Systems SnapVault client to perform a SnapVault update or create aSnapshot copy on the secondary storage.


NTAP_OSSV_ENABLE Y

NTAP_OSSV_HOMEDIR /usr/snapvault



NTAP_OSSV_FS_SNAPSHOT N


./snapcreator --profile Profile Name --action ossv --policy Policy Name

Optional Arguments

Snapshot copy and backup to disk (SnapVault)

This example uses Snap Creator to create a Snapshot copy, perform a SnapVault update, and create aSnapshot copy of the SnapVault secondary.


SNAPVAULT_VOLUMES controller1:vol1,vol2,vol3

NTAP_SNAPVAULT_RETENTIONS Daily:30

NTAP_SNAPVAULT_RETENTION_AGE 30

NTAP_SNAPVAULT_MAX_TRANSFER kbps or blank

NTAP_SNAPVAULT_UPDATE Y

NTAP_SNAPVAULT_WAIT minutes

NTAP_SNAPVAULT_NODELETE N



Optional Arguments

Snapshot copy and backup to disk (SnapMirror)

This example uses Snap Creator to create a Snapshot copy and perform a SnapMirror update.


SNAPMIROR_VOLUMES controller1:vol1,vol2,vol3

NTAP_SNAPMIRROR_USE_SNAPSHOT Y

NTAP_SNAPMIRROR_MAX_TRANSFER kbps or blank

NTAP_SNAPMIRROR_UPDATE Y


Snap Creator examples | 191


Optional Arguments

Snapshot copy and database refresh (primary)

This example uses Snap Creator to create and clone a Snapshot copy.



NTAP_CLONE_IGROUP_MAP controller1:src_volume1/igroup1


NTAP_LUN_CLONE_RESERVATION false

NTAP_NFS_EXPORT_HOST hostname

NTAP_NFS_EXPORT_ACCESS root

NTAP_NFS_EXPORT_PERSISTENT True

MOUNT_CMD01 Mount Script or SnapDrive command to mountclone

MOUNT_CMD02 CLI command or script to start cloned database

UMOUNT_CMD01 Mount script or SnapDrive command to umountclone

To clone a volume, run Snap Creator with the following options:

./snapcreator --profile Profile Name --action clone_vol --snap_name

snapshot name --policy Policy Name Optional Arguments

To clone a LUN, call Snap Creator with the following options:

./snapcreator --profile Profile Name --action clone_lun --policy Policy


Snapshot copy and database refresh (secondary)

This example uses Snap Creator to create a Snapshot copy, perform a SnapMirror update, and clonethe SnapMirror destination volume.


SNAPMIROR_VOLUMES controller1:vol1,vol2,vol3

NTAP_SNAPMIRROR_USE_SNAPSHOT Y

NTAP_SNAPMIRROR_MAX_TRANSFER kbps or blank



NTAP_SNAPMIRROR_UPDATE Y

NTAP_CLONE_SECONDARY_VOLUMES controller1:controller1-sec/vol1,vol2,vol3

NTAP_CLONE_SECONDARY Y



NTAP_NUM_VOL_CLONES 1

NTAP_NFS_EXPORT_HOST hostname

NTAP_NFS_EXPORT_ACCESS root

NTAP_NFS_EXPORT_PERSISTENT true

MOUNT_CMD01 Mount script or SnapDrive command to mountclone

MOUNT_CMD02 CLI command or script to start cloned database

UMOUNT_CMD01 Mount script or SnapDrive command to umountclone

For volume clone, run Snap Creator with the following options:

./snapcreator --profile Profile Name --action clone_vol --policy Policy


Snapshot copy and Protection Manager update

When using Snap Creator to create a Snapshot copy, register the Snapshot copy with ProtectionManager and then use Protection Manager to manage SnapVault or SnapMirror.


NTAP_PM_UPDATE Y

NTAP_DFM_DATA_SET controller1:dataset1/vol1,vol2;controller1:dataset2/vol3

NTAP_SNAPSHOT_NODELETE Y

NTAP_PM_RUN_BACKUP Y

NTAP_DFM_SNAPSHOT_FORMAT mysnap_%T


Snap Creator examples | 193


Optional Arguments

Note: Both Operations Manager and Protection Manager are required. Additionally, you mustconfigure a dataset created by Snap Creator within Protection Manager and create a schedule forthat dataset (secondary). Snap Creator or Protection Manager can delete primary Snapshot copies.Protection Manager manages all secondary Snapshot copies and their retentions.


Copyright information

Copyright © 1994–2012 NetApp, Inc. All rights reserved. Printed in the U.S.A.

No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in anelectronic retrieval system—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to the following license anddisclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time, and without notice.NetApp assumes no responsibility or liability arising from the use of products described herein,except as expressly agreed to in writing by NetApp. The use or purchase of this product does notconvey a license under any patent rights, trademark rights, or any other intellectual property rights ofNetApp.

The product described in this manual may be protected by one or more U.S.A. patents, foreignpatents, or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject torestrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

195

Trademark information

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri,ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, CampaignExpress, ComplianceClock, Cryptainer, CryptoShred, Data ONTAP, DataFabric, DataFort, Decru,Decru DataFort, DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView,FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful,gFiler, Go further, faster, Imagine Virtually Anything, Lifetime Key Management, LockVault,Manage ONTAP, MetroCluster, MultiStore, NearStore, NetCache, NOW (NetApp on the Web),Onaro, OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX, SANscreen,SANshare, SANtricity, SecureAdmin, SecureShare, Select, Service Builder, Shadow Tape,Simplicity, Simulate ONTAP, SnapCopy, SnapDirector, SnapDrive, SnapFilter, SnapLock,SnapManager, SnapMigrator, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot,SnapSuite, SnapValidator, SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror,Tech OnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager, VPolicy, WAFL,Web Filer, and XBB are trademarks or registered trademarks of NetApp, Inc. in the United States,other countries, or both.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. A complete and current list ofother IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.

Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the U.S.A. and/orother countries. Microsoft is a registered trademark and Windows Media is a trademark of MicrosoftCorporation in the U.S.A. and/or other countries. RealAudio, RealNetworks, RealPlayer,RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, andSureStream are trademarks of RealNetworks, Inc. in the U.S.A. and/or other countries.

All other brands or products are trademarks or registered trademarks of their respective holders andshould be treated as such.

NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.

NetApp, Inc. NetCache is certified RealSystem compatible.

197

http://www.ibm.com/legal/copytrade.shtml

How to send your comments

You can help us to improve the quality of our documentation by sending us your feedback.

Your feedback is important in helping us to provide the most accurate and high-quality information.If you have suggestions for improving this document, send us your comments by e-mail to [email protected]. To help us direct your comments to the correct division, include in thesubject line the product name, version, and operating system.

You can also contact us in the following ways:

• NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089• Telephone: +1 (408) 822-6000• Fax: +1 (408) 822-4501• Support Telephone: +1 (888) 4-NETAPP

199

mailto:[email protected]