topic Re: SnapCreator 3.4p2 vmware restore error (vmw-00133) in Data Protection

SnapCreator 3.4p2 vmware restore error (vmw-00133)

jntballard — Thu, 05 Jun 2025 06:41:23 GMT

I recently created a snapcreator configuration to backup a datastore containing 3 VMs. Backup worked fine (had to cycle the agent on the vSphere server before it would work - not sure why I had to do that), but I receive the following error during the restore process:

Scan for unresolved VMFS volumes did not find any entries!

On the VC Client I see the following:

Copy file: Invalid datastore path '[snap-0eda0c1a-zESX_SCTST1] SCTST2'.

Here is the configuration:

- SnapCreator Server LINUX

- vSphere 4.1

- SC Agent installed on VC server (W2K8)

- FC LUNs (VMFS datastores)

- NetApp FAS3240 DOT 8.0.2P3

While watching the process run I see the following:

- Use GUI for restore process

- On VC Client, see VMs are powered off

- See Volume clone created on NetApp and mapped to iGROUP

- VC rescans HBAs

- See datastore 'snap...' show up in inventory

- Get 'Invalid datastore path' error during copy operation

Perhaps I have something configured incorrectly... Reading the documentation it indicates this is a VMware issue, but now sure where to go from here.

Here is my config file:

cat SCTST.conf

########################################################

### NetApp Snap Creator Framework Configuration File ###

########################################################

##############################

### Referencing a Variable ###

##############################

#########################################################################################

# Reference previously assigned variables or variables #

# assigned within Snap Creator itself by prepending #

# the variable name with "%". #

# #

# For example) If you want to reference a VARIABLE: #

# BLAH=/usr/local/bin/foo %USER_DEFINED #

# Below is a list of all the built in referenceable variables: #

# %SNAP_TYPE - The Snapshot Schedule: daily, monthly, etc #

# %SNAP_TIME - An epoch time stamp associated with the snapshot #

# %ACTION - Could be -snap,-clone_vol, or -clone_lun, -arch, -list depending on which #

# Action you used #

# %MSG - Used to send the error message to other monitoring tools or email. Can only #

# be used with SENDTRAP function #

# %USER_DEFINED - Pass a user defined argument to the script, a good example would be #

# in order to integrate with a backup application like netbackup, #

# you may need to pass into configuration file the netbackup schedule #

# desired in the case where you have multiple schedules #

#########################################################################################

#############################

### Snap Creator Settings ###

#############################

#################################################################################################################

# CONFIG_TYPE (required) - (PLUGIN|STANDARD) We can have two types of configuration in SC 3.4.0 app or #

# standard. We can use multiple app configs to build up complex quiesce and unquiesce workflows. #

# SNAME - (required) Your snapshot naming convention, should be unique, snapshots on netapp will be deleted #

# according to this naming convention #

# SNAP_TIMESTAMP_ONLY - (Y|N) Setting to set snapshot naming convention "Y" will create _recent, "N" will #

# use a human readable time stamp #

# VOLUMES - (required) List of primary filers and volumes you want to snapshot #

# ie: filer1:vol1,vol2,vol3;filer2:vol1;filer3:vol2,vol3 #

# VFILERS - List of primary vfilers and their hosting filer/volumes #

# ie: vfiler1@filer1:vol1,vol2,vol3;vfiler2@filer2:vol1,vol2,vol3 #

# SNAPMIROR_VOLUMES - List of primary filers and volumes you want to perform a snapmirror update on #

# ie: filer1:vol1,vol2,vol3;filer2:vol1;filer3:vol2,vol3 #

# SNAPVAULT_VOLUMES - List of primary filers and volumes you want to perform a snapvault update on #

# ie: filer1:vol1,vol2,vol3;filer2:vol1;filer3:vol2,vol3 #

# SNAPVAULT_QTREE_INCLUDE - List of primary filers and qtree paths which should be included in snapvault #

# update. Without this option all qtrees under a volume will be backed up #

# qtrees listed here will be backed up, the rest will be ignored. #

# ie: filer1:/vol/qtree/qtree1,/vol/volume/qtree2;filer2:/vol/volume/qtree1 #

# SNAPMIRROR_CASCADING_VOLUMES List of secondary filers and volumes where you want to perform a snapmirror #

# update from snapvault source volume (snapshot->snapvault->snapmirror) #

# ie: sec-filer1:vol1-sec,vol2-sec #

# NTAP_USERS - (required) List of primary/secondary filers and their corresponding usernames/passowrds #

# ie: filer1:joe/password1;filer2:bob/password2;filer3:ken/password3 #

# SECONDARY_INTERFACES - List of primary filers or vfilers and there secondary interfaces source/destination #

# for snapvault and snapmirror relationships #

# ie: filer1:filer1-source/filer2-destination #

# USE_PROXY - (Y|N) Setting which allows API calls to go through DFM proxy instead of storage controller #

# directly. If this option is used NTAP_USERS is no longer required. #

# MANAGEMENT_INTERFACES - List of primary filers and their management interfaces used for communications #

# ie: filer1:filer1-mgmt;filer2:filer2-mgmt #

# NTAP_PWD_PROTECTION - (Y|N) Setting for enabling password protection, you must first create a scambled #

# password and then save that password in config file #

# TRANSPORT - (HTTP|HTTPS) Setting to use either HTTP or HTTPS to connect to NetApp filer #

# PORT - (80|443) Setting which configures which port number on the NetApp filer to use #

# LOG_NUM - The number of logs .debug and .out for Snap Creator to keep #

# SC_TMP_DIR - The directory used for storing temporary created files #

# The directory must exists and must be writable. #

# If not specified, the system default will be used. #

# SNAPDRIVE - (Y|N) Setting which allows you to use snapdrive instead of ZAPI for snapshot creation #

# SNAPDRIVE_DISCOVERY - (Y|N) Setting which enables use of snapdrive for storage discovery, required in SAN #

# or iSAN environment when using VOLUME_VALIDATION #

# NTAP_SNAPSHOT_DISABLE - (Y|N) Setting which tells Snap Creator to not take a snapshot. The idea of the option #

# is that Snap Creator can handle SnapVault or SnapMirror for SnapManager. In order for #

# that to work the SnapManager snapshots need to follow this naming convention #

# <snapshot name>-<policy>_recent #

# NTAP_SNAPSHOT_CREATE_CMD<#> - SnapDrive command to create a snapshot and flush the file system buffers #

# where "#" is a number 01-xx #

# NTAP_SNAPSHOT_RETENTIONS - (required) Setting which determines the number of netapp snapshots you want to #

# retain for a given policy ie: daily:7,weekly:4,monthly:1 #

# NTAP_SNAPVAULT_RETENTIONS - Setting which determines the number of netapp snapshots on the snapvault #

# secondary you want to retain for a given policy #

# ie: daily:21,weekly:12,monthly:3 #

# NTAP_SNAPVAULT_SNAPSHOT - (Y|N) Setting which enables creation of snapvault snapshot. A snapshot compatible #

# with the storage controller snapvault scheduler. Snapshots are named #

# sv_<policy>.<#> and deletion is handled by the storage controller #

# NTAP_SNAPSHOT_RETENTION_AGE - Setting in (days) which allows you to define a retention age for snapshots. If #

# configured snapshots will only be deleted if there are more than defined in #

# SNAPSHOT Retentions and if they are older than retention age (days) #

# NTAP_SNAPVAULT_RETENTION_AGE - Setting in (days) which allows you to define a retention age for snapvault #

# snapshots. If configured snapvault snapshots will only be deleted if #

# there are more than defined in SNAPVAULT Retentions and if they are older #

# than retention age (days) #

# NTAP_SNAPSHOT_NODELETE - Setting which will override NTAP_SNAPSHOT_RETENTIONS and ensure no snapshots are #

# deleted, leaving this on can cause your netapp volume to fill up #

# NTAP_SNAPVAULT_NODELETE - Setting which will override NTAP_SNAPVAULT_RETENTIONS and ensure no snapshots are #

# deleted, leaving this on can cause your netapp volume to fill up #

# NTAP_SNAPVAULT_RESTORE_WAIT - (Y|N) Setting which waits for snapvault restore to complete. This is #

# recommended since after restore is complete user will be prompted to delete the #

# baseline snapshot which gets created on the primary volume #

# NTAP_SNAPMIRROR_UPDATE - (Y|N) Setting which allows you to turn off and on the snapmirror update function #

# NTAP_SNAPMIRROR_CASCADING_UPDATE - (Y|N) Setting which allows you to turn off and on the cascading snapmirror #

# function (snapshot->snapvault->snapmirror) #

# NTAP_SNAPVAULT_UPDATE - (Y|N) Setting which allows you to turn off and on the snapvault update function #

# NTAP_PM_UPDATE - (Y|N) Setting which allows you to turn off and on the protection manager update function #

# NTAP_SNAPVAULT_WAIT - Time in minutes where we will wait for snapvault update process to complete before #

# taking a snapshot on the snapvault secondary #

# NTAP_SNAPMIRROR_WAIT - Time in minutes where we will wait for snapmirror update process to complete #

# NTAP_SNAPMIRROR_USE_SNAPSHOT - (Y|N) Setting which determines if the snapshot will be sent with the #

# snapmirror update #

# NTAP_SNAPVAULT_MAX_TRANSFER - Maximum bandwidth for snapvault to consume in kbps, if left blank snapvault #

# will consume as much bandwidth as possible #

# NTAP_SNAPMIRROR_MAX_TRANSFER - Maximum bandwidth for snapmirror to consume in kbps, if left blank snapmirror #

# will consume as much bandwidth as possible #

# NTAP_VOL_CLONE_RESERVE - (none|file|volume) Space Guarantee for cloned volume #

# NTAP_LUN_CLONE_RESERVATION - (true|false) If true will reserve space for cloned luns if false will not #

# NTAP_CLONE_IGROUP_MAP - List of filer(s), source volume(s), and the Igroups used to map cloned volumes and #

# luns. IE: filer1:src_volume1/igroup1;filer2:src_volume2/igroup2 #

# NTAP_CLONE_FOR_BACKUP - (Y|N) Setting which determines when the clone is deleted. "Y" will delete clone #

# after it is created, "N" will delete clone before snapshot occurs so during #

# the next run of Snap Creator for the given policy and config. #

# NTAP_CLONE_SECONDARY - (Y|N) Setting which determines where to perform a clone. If "Y" is selected #

# the snapmirror destination will be cloned. This only works with snapmirror #

# and you must set NTAP_SNAPMIRROR_USE_SNAPSHOT=Y #

# NTAP_CLONE_SECONDARY_VOLUMES - Mapping of primary filers and their secondary Filer/volume #

# ie: filer1:secondaryFiler1/vol1;filer2:secondaryFiler2/vol2 #

# NTAP_NUM_VOL_CLONES - Setting which configures how many volume clones Snap Creator will keep #

# NTAP_NFS_EXPORT_HOST - (honstname|ip) The hostname or IP address of the server where cloned volume should be #

# exported #

# NTAP_NFS_EXPORT_ACCESS - (root|read-write|read-only) Setting which controls access permission to cloned vol #

# NTAP_NFS_EXPORT_PERSISTENT -(true|false) Setting which allows for export permissions of cloned vol to be #

# saved in the /etc/exports file on the storage controller. #

# NTAP_DFM_DATA_SET - List of filers and their protection manager to volume correlations #

# ie: filer1:dataset1/vol1,vol2;filer1:dataset2/vol3 #

# NTAP_PM_RUN_BACKUP - (Y|N) Setting which enables starting the Protection Manager backup as soon as the #

# snapshot registration process is complete. Eliminates need to schedule secondary #

# backup in Protection Manager. #

# NTAP_CONSISTENCY_GROUP_SNAPSHOT - (Y|N) Setting which enables use of consistency groups for creating #

# consistent snapshot across multiple volumes ie: IO Fencing #

# NTAP_CONSISTENCY_GROUP_TIMEOUT - (urgent|medium|relaxed) Setting which defines how long filer will wait for #

# consistently group snapshot (urgent=2sec,medium=7sec,relaxed=20sec) #

# NTAP_CONSISTENCY_GROUP_WAFL_SYNC - (Y|N) Setting which can improve performance of the CG snapshot by forcing #

# a CP through a wafl-sync before the cg-start #

# NTAP_SNAPSHOT_DELETE_BY_AGE_ONLY - {PRIMARY|SECONDARY|BOTH|N} Setting which allows the deletion of outdated #

# snapshots, regardless of the retention count #

# NTAP_SNAPSHOT_DEPENDENCY_IGNORE - (Y|N) Setting which allows for ignoring snapshot dependencies when #

# prompted for deletion using the "--action delete" option #

# NTAP_SNAPSHOT_RESTORE_AUTO_DETECT - (Y|N) Setting which if disabled will always force a SFSR when doing a #

# single file restore #

# NTAP_OSSV_ENABLE - (Y|N) Setting which enables the Open Systems Snapvault (OSSV) integration. This option #

# must be used in combination with the NTAP_OSSV_HOMEDIR parameter. OSSV is also #

# required on the host running Snap Creator #

# NTAP_OSSV_HOMEDIR - The path to the OSSV home directory IE: /usr/snapvault #

# NTAP_OSSV_FS_SNAPSHOT - (Y|N) Setting which enables ability to create file system snapshot. The file system #

# snapshot command must be provided using the NTAP_OSSV_FS_SNAPSHOT_CREATE_CMD<#> #

# parameter #

# NTAP_OSSV_FS_SNAPSHOT_CREATE_CMD<#> - Script or command that takes a file system snapshot in use with ossv #

# backup, where "#" is a number between 01-xx #

# OM_HOST - Name or IP Address of your Operations Manager system #

# OM_USER - User name of an Operations Manager user which has privilages to create events #

# OM_PWD - Password of the above Operations Manager User #

# OM_EVENT_GENERATE - (Y|N) Setting which will enable event creation in Operations Manager #

# APP_QUIESCE_CMD<#> - Script or command that puts your application into backup mode, where "#" is a #

# number between 01-xx #

# APP_UNQUIESCE_CMD<#> - Script or command that takes your application out of backup mode, where "#" is a #

# number between 01-xx #

# ARCHIVE_CMD<#> - The archive command command where "#" is a number 01-xx #

# MOUNT_CMD<##> - Mount commands to be used to mount file system for cloning or mount actions where "#" is a #

# number 01-xx #

# UMOUNT_CMD<##> - Umount commands to be used to mount file system for cloning or mount actions where "#" is a #

# number 01-xx #

# PRE_APP_QUIESCE_CMD<#> - The pre application quiesce command where "#" is a number 01-xx #

# PRE_NTAP_CMD<#> - The pre netapp command where "#" is a number 01-xx #

# PRE_APP_UNQUIESCE_CMD<#> - The pre application unquiesce command where "#" is a number 01-xx #

# PRE_NTAP_CLONE_DELETE_CMD<#> - The pre netapp clone delete command where "#" is a number 01-xx #

# PRE_RESTORE_CMD<#> - The pre restore command where "#" is a number 01-xx #

# PRE_EXIT_CMD<#> - Command which will run before Snap Creator exists due to an error #

# ie: you want to return application or backup into normal mode before Snap Creator exist #

# due to an error. Where "#" is a number between 01-xx #

# PRE_CLONE_CREATE_CMD<#> - The pre clone create command, where "#" is a number 01-xx #

# POST_APP_QUIESCE_CMD<#> - The post application quiesce command where "#" is a number 01-xx #

# POST_NTAP_CMD<#> - The post netapp command where "#" is a number 01-xx #

# POST_APP_UNQUIESCE_CMD<#> - The post application unquiesce command where "#" is a number 01-xx #

# POST_NTAP_DATA_TRANSFER_CMD<#> - The post data transfer command runs after SnapVault or SnapMirror transfer #

# Where "#" is a number 01-xx. #

# POST_RESTORE_CMD<#> - The post restore command where 2#" is a number 01-xx #

# POST_CLONE_CREATE_CMD<#> - The post clone create command, where "#" is a number 01-xx #

# NTAP_ASUP_ERROR_ENABLE - (Y|N) Setting which enables Snap Creator error messages to also log an auto support #

# message on the NetApp storage controller. Snap Creator will always create an info #

# auto support message when the backup has started and completed #

# SENDTRAP - Command which interfaces with your monitoring software or email, allows you to pass alerts #

# generated from Snap Creator into your own monitoring infrastructure. The %MSG variable is the #

# message sent from Snap Creator #

# SUCCESS_TRAP - Command which interfaces with your monitoring software or email, allows you to pass the #

# success message generated from Snap Creator into your own monitoring infrastructure #

# The %SUCCESS_MSG variable is the success message for Snap Creator #

# SUCCESS_MSG - Upon Snap Creator success will log the message you define and also send it to SENDTRAP, if #

# SENDTRAP is defined #

#################################################################################################################

########################

### Required Options ###

########################

CONFIG_TYPE=STANDARD

SNAME=SCTST

SNAP_TIMESTAMP_ONLY=N

VOLUMES=netapp-spo-c1a:zESX_SCTST1

NTAP_SNAPSHOT_RETENTIONS=hourly:4

NTAP_USERS=netapp-spo-c1a:root/53616c7465645f5f652285019faf8f9c28037a9d587c6ccc79f1f56d3c41b67b

NTAP_PWD_PROTECTION=Y

TRANSPORT=HTTP

PORT=80

LOG_NUM=10

SC_TMP_DIR=

##########################

### Connection Options ###

##########################

VFILERS=

MANAGEMENT_INTERFACES=

SECONDARY_INTERFACES=

USE_PROXY=N

########################

### Snapshot Options ###

########################

NTAP_SNAPSHOT_RETENTION_AGE=

SNAPDRIVE=N

SNAPDRIVE_DISCOVERY=N

NTAP_SNAPSHOT_DISABLE=N

NTAP_SNAPSHOT_NODELETE=N

NTAP_CONSISTENCY_GROUP_SNAPSHOT=N

NTAP_CONSISTENCY_GROUP_TIMEOUT=medium

NTAP_CONSISTENCY_GROUP_WAFL_SYNC=N

NTAP_SNAPSHOT_DELETE_BY_AGE_ONLY=N

NTAP_SNAPSHOT_DEPENDENCY_IGNORE=N

NTAP_SNAPSHOT_RESTORE_AUTO_DETECT=Y

#########################

### SnapVault Options ###

#########################

NTAP_SNAPVAULT_UPDATE=N

SNAPVAULT_VOLUMES=

SNAPVAULT_QTREE_INCLUDE=

NTAP_SNAPVAULT_RETENTIONS=

NTAP_SNAPVAULT_RETENTION_AGE=

NTAP_SNAPVAULT_SNAPSHOT=N

NTAP_SNAPVAULT_NODELETE=N

NTAP_SNAPVAULT_RESTORE_WAIT=N

NTAP_SNAPVAULT_WAIT=60

NTAP_SNAPVAULT_MAX_TRANSFER=

##########################

### SnapMirror Options ###

##########################

NTAP_SNAPMIRROR_UPDATE=N

NTAP_SNAPMIRROR_CASCADING_UPDATE=N

SNAPMIRROR_VOLUMES=

SNAPMIRROR_CASCADING_VOLUMES=

NTAP_SNAPMIRROR_WAIT=60

NTAP_SNAPMIRROR_USE_SNAPSHOT=N

NTAP_SNAPMIRROR_MAX_TRANSFER=

#######################

### Cloning Options ###

#######################

NTAP_VOL_CLONE_RESERVE=none

NTAP_LUN_CLONE_RESERVATION=false

NTAP_CLONE_IGROUP_MAP=

NTAP_CLONE_FOR_BACKUP=Y

NTAP_CLONE_SECONDARY=N

NTAP_CLONE_SECONDARY_VOLUMES=

NTAP_NUM_VOL_CLONES=1

NTAP_NFS_EXPORT_HOST=

NTAP_NFS_EXPORT_ACCESS=

NTAP_NFS_EXPORT_PERSISTENT=

##################################

### Protection Manager Options ###

##################################

NTAP_PM_UPDATE=N

NTAP_DFM_DATA_SET=

NTAP_PM_RUN_BACKUP=N

####################

### OSSV Options ###

####################

NTAP_OSSV_ENABLE=N

NTAP_OSSV_HOMEDIR=

NTAP_OSSV_FS_SNAPSHOT=N

NTAP_OSSV_FS_SNAPSHOT_CREATE_CMD01=

###################################

### Operations Manager Settings ###

###################################

OM_HOST=

OM_USER=

OM_PWD=

OM_PORT=

OM_EVENT_GENERATE=N

####################

### APP Commands ###

####################

ARCHIVE_CMD01=

MOUNT_CMD01=

UMOUNT_CMD01=

####################

### Pre Commands ###

####################

PRE_APP_QUIESCE_CMD01=

PRE_NTAP_CMD01=

PRE_NTAP_CLONE_DELETE_CMD01=

PRE_APP_UNQUIESCE_CMD01=

PRE_RESTORE_CMD01=

PRE_CLONE_CREATE_CMD01=

#####################

### Post Commands ###

#####################

POST_APP_QUIESCE_CMD01=

POST_NTAP_CMD01=

POST_NTAP_DATA_TRANSFER_CMD01=

POST_APP_UNQUIESCE_CMD01=

POST_RESTORE_CMD01=

POST_CLONE_CREATE_CMD01=

###########################

### Event Configuration ###

###########################

NTAP_ASUP_ERROR_ENABLE=N

SENDTRAP=

SUCCESS_TRAP=

SUCCESS_MSG=INFO: NetApp Snap Creator Framework finished successfully ( Action: %ACTION )

###################################

### Client/Server Configuration ###

###################################

##################################################################################################################

# SC_AGENT - <hostname or ip>:<port> #

# Snap Creator has the capability to perform tasks on remote hosts. A task is either a defined module #

# (parameter APP_NAME) or a command specified with the parameters *_CMD*, e. g. NTAP_SNAPSHOT_CREATE_CMD01 #

# #

# To specify a remote host, enter it's name or ip address followed by a colon and the port, the Snap Creator #

# Agent listening on. #

# On the remote host, start the Snap Creator Agent #

# <path to Snap Creator>/snapcreator --start-agent <port> #

# #

# If running in local mode, the parameter must be left blank. #

# #

# SC_CLONE_TARGET - <hostname or ip of the clone target>:<port> #

# Snap Creator has the capability to perform clone operations. Using the action 'clone_vol' in combination #

# with {PRE|POST}_CLONE_CREATE_CMDxx to handle the storage objects on the remote side #

# (e. g. mounting/unmounting filesytems), either the module is enabled to perform all the necessary #

# activities to #

# #

# To specify a clone target, enter it's name or ip address followed by a colon and the port, the Snap Creator #

# Agent listening on. #

# #

# SC_AGENT_TIMEOUT - Number, timeout in seconds #

# The implemented client/server architecture uses a timeout mechanism. This means, if the client does not #

# respond in the specified interval, the server fails with a timeout message. However, the task on the client #

# is left untouched (will not be aborted) and needs further investigation. #

# #

# On server with high load or known, long running tasks like own scripts or complex SnapDrive operations #

# it might be necessary to extend the timeout and adapt this value on your own needs. #

# #

# Per default, a timeout of 300 seconds is used. #

# #

# SC_AGENT_WATCHDOG_ENABLE - (Y|N) #

# Snap Creator starts a watchdog process while quiescing the database. After the period specified with #

# SC_AGENT_UNQUIESCE_TIMEOUT, the database will be brought into normal operation automatically. #

# #

# SC_AGENT_UNQUIESCE_TIMEOUT - Number, timeout in seconds #

# Time to wait after a database quiesce operation to bring back the database into normal operation mode again. #

# This is only available in combination with SC_AGENT_WATCHDOG_ENABLE=Y #

# #

# Per default, SC_AGENT_TIMEOUT + 5 is used. #

##################################################################################################################

SC_AGENT=nessus:9090

SC_AGENT_TIMEOUT=300

SC_AGENT_UNQUIESCE_TIMEOUT=

SC_CLONE_TARGET=

SC_AGENT_WATCHDOG_ENABLE=

#############################

### Plugin Module Options ###

#############################

##################################################################################################################################

# Snap Creator has built-in support for the listed applications. A community plug-in can be used or you can configure #

# APP_QUIESCE_CMD01, APP_UNQUIESCE_CMD01, and PRE_EXIT_CMD01 #

# #

# APP_IGNORE_ERROR - (Y|N) Will cause Snap Creator to not exit when encountering an application error. An error #

# message will be sent if SENDTRAP is configured but Snap Creator will not exit. This may be useful if you #

# are backing up multiple databases and dont want a single database failure to stop the backup #

# #

# VALIDATE_VOLUMES - (DATA) Snap Creator validates that all volumes where the database resides are in fact part of the backup. #

# Currently, there are some limitations. Only NFS is supported and only for db2, maxdb, mysql, and Oracle. #

# Currently, this option only checks data files only for the above databases. Going forward, support for more data #

# types like LOG will be added. #

# #

# APP_DEFINED_RESTORE - (Y|N) The normal cli restore insterface will not be shown. Instead the plug-in is responsible for #

# handling all restore activities including the restore of the snapshot. The built-in plug-ins do not support #

# this type of a restore #

# #

# APP_DEFINED_CLONE - (Y|N) The built-in cloning abilities of Snap Creator will be ignored. Instead the plug-in is responsible #

# for handling all clone activities including vol or lun clone creation and deletion. The built-in plug-ins do not #

# support this type of clone. #

# APP_AUTO_DISCOVERY - (Y|N) Similar to APP_DEFINED _RESTORE this parameter allows the plug-in to handle application discovery. #

# As with restore the plug-in must handle this operation itself #

# #

# APP_CONF_PERSISTENCY - (Y|N) If APP_AUTO_DISCOVERY is used configuration parameters can be changed dynamically. This setting #

# allows any changes to be saved, meaning the configuration file updated dynamically. #

##################################################################################################################################

APP_NAME=vibe

APP_IGNORE_ERROR=N

VALIDATE_VOLUMES=

APP_DEFINED_RESTORE=Y

APP_DEFINED_CLONE=N

APP_AUTO_DISCOVERY=Y

APP_CONF_PERSISTENCE=Y

############################

### Archive Log Settings ###

############################

##########################################################################################

# ARCHIVE_LOG_ENABLE - (Y|N) Setting which Enables Archive Log Management #

# (deletion of old archive logs) #

# ARCHIVE_LOG_RETENTION - Retention in Days for how long archive logs should be kept #

# ARCHIVE_LOG_DIR - Path to where the archive logs are stored #

# ARCHIVE_LOG_EXT - File Extension for the archive logs, must be <something>.<extension> #

# ie: 109209011.log in which case you would enter "log" #

##########################################################################################

ARCHIVE_LOG_ENABLE=N

ARCHIVE_LOG_RETENTION=1

ARCHIVE_LOG_DIR=/tmp/log

ARCHIVE_LOG_EXT=log

###############################

### General Plugin Settings ###

###############################

####################

### DB2 Settings ###

####################

#################################################################################################################

# DB2_DATABASES - List of database(s) and their username separated by a comma #

# #

# DB2_DATABASES=db1:user1;db2:user2 #

# #

# DB2_CMD - Path to the db2 command, for connecting to the database(s). #

# If not specified, sqllib/db2 will be used. #

# #

#################################################################################################################

DB2_DATABASES=

DB2_CMD=/path/to/db2

#######################

### MYSQL Settings ###

#######################

#################################################################################################################

# MYSQL_DATABASES - List of database(s) and their username/password separated by a comma of which you #

# #

# MYSQL_DATABASES=db1:user1/password;db2:user2/password #

# #

# HOST - Name of Host where the database(s) are running, ie: localhost #

# PORTS - List of Database(s) and the ports they are listening on #

# #

# PORTS=db1:3307;db2:3308 #

# #

# MASTER_SLAVE - (Y|N)If the Database(s) are part of a MASTER or SLAVE Environment #

#################################################################################################################

MYSQL_DATABASES=

HOST=

PORTS=

MASTER_SLAVE=N

#######################

### Oracle Settings ###

#######################

#################################################################################################################

# ORACLE_DATABASES - A list of Database(s) and the username ie: db1:user1;db2:user2 #

# #

# ORACLE_DATABASES=db1:user1;db2:user2 #

# #

# SQLPLUS_CMD - PATH to the sqlplus command #

# CNTL_FILE_BACKUP_DIR - Path to the directory where we should store backup cntl files #

# (must be owned by oracle user) #

# ORA_TEMP - Path to a directoy for storing temp files ie: /tmp (oracle user must have permissions) #

# ARCHIVE_LOG_ONLY - (Y|N) Tells Oracle Module to only do a switch log, useful if you are handling #

# archive logs separate from data backup #

# ORACLE_HOME - PATH to the Oracle home directory #

# ORACLE_HOME_<SID> - PATH to Oracle home directory for a given SID. When backing up multiple databases it #

# may be important to specfiy more than one Oracle home #

# ORACLE_EXPORT_PARAMETERS - (Y|N) The ORACLE_HOME and ORACLE_SID environment parameres will be exported using #

# the export command. This only applies to Unix systems #

#################################################################################################################

ORACLE_DATABASES=

SQLPLUS_CMD=/path/to/sqlplus

CNTL_FILE_BACKUP_DIR=/path/to/cntl_files

ORA_TEMP=/path/to/oratemp

ARCHIVE_LOG_ONLY=N

ORACLE_HOME=/path/to/orahome

ORACLE_EXPORT_PARAMETERS=Y

#####################################

### SnapManager Exchange Settings ###

#####################################

#################################################################################################################

# SME_PS_CONF - Path to the powershell configuration file for SME #

# #

# SME_PS_CONF="C:\Program Files\NetApp\SnapManager for Exchange\smeShell.psc1" #

# #

# SME_BACKUP_OPTIONS - SME backup options, Snap Creator uses a powershell new-backup cmdlet #

# #

# SME_BACKUP_OPTIONS=-Server 'EX2K10-DAG01' -GenericNaming -ManagementGroup 'Standard' -NoTruncateLogs $False #

# -RetainBackups 8 -StorageGroup 'dag01_db01' -BackupCopyRemoteCCRNode $False #

# #

# SME_SERVER_NAME - SME server name #

# SME_32bit - (Y|N) Setting to enable use of 32bit version of powershell #

#################################################################################################################

SME_PS_CONF=

SME_BACKUP_OPTIONS=

SME_SERVER_NAME=servername

SME_32bit=N

###################################

### Sybase Settings (unix only) ###

###################################

#################################################################################################################

# #

# GLOBAL (CORE) SNAP CREATOR CONFIGURATION (external to the SYBABE module) #

# #

# - Set 'APP_NAME=SYBASE' #

# - If you want to validate configutation then set 'VALIDATE_VOLUMES=DATA,OFFLINE_LOG,EXTERNAL_FILES' #

# - DATA - logs and data as resported by sp_helpdb #

# - OFFLINE_LOG - Dump location, extracted from SYBASE_TRAN_DUMP #

# - EXTENAL_FILE - Manifest files, extracted from SYBASE_MANIFEST #

# - If you want to auto discovery storage then set "APP_AUTO_DISCOVERY=Y" as NFS based filer volumes #

# which will override the "VOLUMES" option #

# - If you want to permanantly update the configuration file with the results of the storage auto #

# discovery then set "APP_CONF_PERSISTENCE=Y" #

# - If you want to use encrypted password then set "NTAP_PWD_PROTECTION=Y". NOTE this also sets #

# encryption on filer passwords. #

# #

# LOCAL (SYBASE module) SNAP CREATOR CONFIGURATION (internal to the SYBASE module) #

# #

# - SYBASE_SERVER the sybase dataserver name (-S option on isql) #

# example: SYBASE_SERVER=p_test #

# - SYBASE_DATABASES the list of databses within the instance to backup. Format is #

# "DB1:USER:PASSWD;DB2:USER:PASSWD" The master database is added as a matter of course. If a datbase #

# called "+ALL" is used then database autodiscovery will be used and excludes the sybsyntax, #

# sybsystemdb, sybsystemprocs and tempdb databases. The password are used are passwd to isql as -P. #

# excrypted passwords are supported if NTAP_PWD_PROTECTION is set. #

# example: SYBASE_DATABASES=DBAtest2:sa/53616c7465645f5f76881b465ca8ce3745c239b60e04351e #

# example: SYBASE_DATABASES=+ALL:sa/53616c7465645f5f76881b465ca8ce3745c239b60e04351e #

# - SYBASE_DATABASES_EXCLUDE allows databases to be excluded if the +ALL construct is used use ';' #

# to allow multiple databases to be used. #

# example: SYBASE_DATABASES_EXCLUDE=pubs2;test_db1. #

# - SYBASE_TRAN_DUMP allows post snapshot sybase transaction dump to be performed. Each database #

# requiring a txn dump needs to be specified. Format is "DB1:PATH;DB2:PATH" where path is a #

# diectory. #

# example: SYBASE_TRAN_DUMP=pubs2:/sybasedumps/pubs2 #

# - SYBASE_TRAN_DUMP_FORMAT Allows the dump naming convention to use sepecified to match site #

# specific formats. Three "keys" can be sepecified, %S = Instance name from SYBASE_SERVER #

# %D is datbase from SYBASE_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 sybase transaction dump compression to be enabled. #

# example: SYBASE_TRAN_DUMP_COMPRESS=Y #

# - SYBASE_ISQL_CMD defines the path to the "isql" command to use. #

# example: SYBASE_ISQL_CMD=/opt/sybase/OCS-15_0/bin/isql #

# - SYBASE the location of the sybase install #

# example: SYBASE=/sybase #

# - SYBASE_LOGDIR defines the directory where snap creator logs will be placed #

# example: SYBASE_LOGDIR=/usr/local/ntap/scServer3.3.0/logs #

# - SYBASE_MANIFEST allows those databases where a manifest file should be created and the location #

# where they should be placed. Needed for database mount to be supported. #

# example: SYBASE_MANIFEST=DBAtest2:/t_inf_nzl_devs/ #

# - SYBASE_MANIFEST_FORMAT Allows the manifest naming convention to use sepecified to match site #

# specific formats. Three "keys" can be sepecified, %S = Instance name from SYBASE_SERVER #

# %D is datbase from SYBASE_DATABASES and %T is a unique timestamp which is the same as used for #

# snapshot naming. Default format is %S_%D_%T.manifest #

# example: SYBASE_MANIFEST_FORMAT=%S_%D_%T.manifest #

# - SYBASE_MANIFEST_DELETE allows the manifest to be deleted once the snapshot has been performed. The #

# manifest file should be captured within the snapshot so it is always available with the backup. #

# example: SYBASE_MANIFEST_DELETE=Y #

# #

#################################################################################################################

SYBASE_SERVER=

SYBASE_DATABASES=

SYBASE_DATABASES_EXCLUDE=

SYBASE_TRAN_DUMP=

SYBASE_TRAN_DUMP_FORMAT=

SYBASE_TRAN_DUMP_COMPRESS=Y

SYBASE_ISQL_CMD=/path/to/isql

SYBASE=/path/to/sybase

SYBASE_LOGDIR=/path/to/logs

SYBASE_MANIFEST=

SYBASE_MANIFEST_FORMAT=

SYBASE_MANIFEST_DELETE=Y

############################

### VIBE Custom Settings ###

############################

#####################################################################################################

# AUTHENTICATION PARAMETERS #

# ------------------------- #

# VIBE_VCLOUD_IPADDR - IP address(es) of the vCloud Director to log into (vCloud ONLY) #

# VIBE_VCLOUD_USER - Username to use when logging into the vCloud Director (vCloud ONLY), #

# and you must set @<org> or @system (top level vCloud database) #

# #

# Example: #

# #

# VIBE_VCLOUD_USER=administrator@system #

# #

# VIBE_VCLOUD_PASSWD - Password associated to the VCLOUD_USER specified (vCloud ONLY) #

# VIBE_VCENTER_USER - Username to use when logging into vCenter #

# VIBE_VCENTER_PASSWD - Password associated to the VCENTER_USER specified #

# #

# OBJECT PARAMETERS #

# ----------------- #

# VIBE_VCLOUD_NAMES - list of Organization, vDC and vApp object names 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 per vCenter (vSphere ONLY) #

# VIBE_TRIM_VSPHERE_NAMES - list of VMs to remove from backup per vCenter (vSphere ONLY) #

# #

# Example: #

# #

# VIBE_VSPHERE_NAMES=VCENTER1:DS1:VM1;VCENTER2;DS2,DS3:;VCENTER3::VM4 #

# VIBE_TRIM_VSPHERE_NAMES=VCENTER1:VM99;VCENTER2:VM5,VM12 #

# #

# RESTORE PARAMETERS #

# ------------------ #

# VIBE_RESTORE_INTERVAL - time between each restore check (default: 30 seconds) #

# VIBE_RESTORE_TIME - total time to wait for complete restore (default: 3600 seconds) #

# VIBE_VMWARE_SNAPSHOT - take a VMware snapshot during backup (default: Y) #

# #

# ALTERNATE PARAMETERS #

# -------------------- #

# VIBE_NOPING - do not ICMP ping VMware or storage controllers (default: N) #

# VIBE_DYNAMIC_VOLUMES_UPDATE - if set to 'N', does not perform dynamic volume update, which means #

# you have to set VOLUMES, SNAPVAULT_VOLUMES, SNAPMIRROR_VOLUMES and #

# NTAP_DFM_DATA_SET manually (default: not set) #

#####################################################################################################

VIBE_VCLOUD_IPADDR=

VIBE_VCLOUD_USER=

VIBE_VCLOUD_PASSWD=

VIBE_VCENTER_USER=vcadmin

VIBE_VCENTER_PASSWD=53616c7465645f5ff7f6bfd4debc07d7bf4f95a6c091e0a4286231c0ce4910e7

VIBE_VCLOUD_NAMES=

VIBE_VSPHERE_NAMES=nessus::SCTST2,SCTST3

# VIBE_TRIM_VSPHERE_NAMES=

# VIBE_RESTORE_INTERVAL=30

# VIBE_RESTORE_TIME=3600

# VIBE_VMWARE_SNAPSHOT=Y

# VIBE_NOPING=Y

################################

### SnapManager SQL Settings ###

################################

##################################################################################################

# SMSQL_PS_CONF - Path to the powershell configuration file for SMSQL #

# #

# SMSQL_PS_CONF="C:\Program Files\NetApp\SnapManager for SQL Server\smsqlShell.psc1" #

# #

# SMSQL_BACKUP_OPTIONS - SMSQL backup options, Snap Creator uses a powershell new-backup cmdlet #

# #

# SMSQL_BACKUP_OPTIONS=-svr 'SQL' -d 'SQL\SHAREPOINT', '1', 'WSS_Content' -RetainBackups 7 #

# -lb -bksif -RetainSnapofSnapInfo 8 -trlog -gen -mgmt standard #

# #

# SMSQL_SERVER_NAME - SMSQL server name #

# SMSQL_32bit - (Y|N) Setting to enable use of 32bit version of powershell #

##################################################################################################

SMSQL_PS_CONF=

SMSQL_BACKUP_OPTIONS=

SMSQL_SERVER_NAME=servername

SMSQL_32bit=N

#############################

### Lotus Domino Settings ###

#############################

###################################################################################

# #

# DOMINO_DATA_PATH - Path to Domino Data directory #

# eg:/notes/notesdata #

# DOMINO_INI_PATH - Path to notes.ini file (include notes.ini in path) #

# eg:/notes/notesdata/notes.ini #

# DOMINO_CHANGE_INFO_PATH - Path where change info files should be saved. #

# Use a different volume than Domino Data or Log paths #

# eg:/notes/changeinfo #

# DOMINO_DATABASE_TYPE - Can be any of the following values #

# 0 = Backup everything ( 1+2+3 below) #

# 1 = Backup only for *.BOX files. #

# 2 = Backup only for *.NSF, *.NSG and *.NSH files. #

# 3 = Backup only for *.NTF files. #

# LOTUS - Path where Domino is installed #

# eg:/opt/ibm/lotus #

# Notes_ExecDirectory - Path that contains Domino shared object(.so or .dll) #

# files eg:/opt/ibm/lotus/notes/latest/linux/ #

# DOMINO_RESTORE_DATA_PATH - Path to restored lotus data directory #

# Use the same volume as the Domino Data path #

# Use the same path as DOMINO_DATA_PATH if restoring to #

# the same location eg:/notes/notesdata #

# #

###################################################################################

DOMINO_DATA_PATH=

DOMINO_INI_PATH=

DOMINO_CHANGE_INFO_PATH=

DOMINO_DATABASE_TYPE=0

LOTUS=

Notes_ExecDirectory=

DOMINO_RESTORE_DATA_PATH=

############################

### PostgresSQL Settings ###

############################

#################################################################################################################

# POSTGRES_DATABASES - A list of Database(s) and the username ie: db1:user1;db2:user2 #

# #

# POSTGRES_DATABASES=db1:user1;db2:user2 #

# #

# PSQL_CMD - PATH to the psql command #

# NO_PASSWORD_OPTION - (Y|N)Option supported by PostGresSQL 8.4 and higher which doesn't require #

# PGPASSWORD to be set #

#################################################################################################################

POSTGRES_DATABASES=

PSQL_CMD=/path/to/psql

NO_PASSWORD_OPTION=Y

#######################

### MAXDB Settings ###

#######################

#################################################################################################################

# XUSER_ENABLE - (Y|N) Enables the use of an xuser for maxdb so password is not required for db user #

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

# DBMCLICMD - The path to the MaxDB dbmcli command, if not set dbmcli on the search path is used #

# SQLCLICMD - The path to the MaxDB sqlcli command, if not set sqlcli on the search path is used #

# MAXDB_UPDATE_HIST_LOG - (Y|N) Tells the maxdbbackup program if it should update maxdb hostory log #

# MAXDB_DATABASES - List of database(s) and their username/password separated by a comma of which you #

# want to backup #

# #

# MAXDB_DATABASES=db1:user1/password;db2:user2/password #

# #

# MAXDB_CLONE_META - #

# source_sid - Database SID used on the source side #

# target_sid - Database SID used on the target side #

# target_db_path - top level directory of the MaxDB installation #

# dbm_user - Target Database Management User #

# dbm_passwd - Password or authentication key of dbm_user #

# dbadmin_user - Target SQL User with DBA privileges #

# dbadmin_passwd - Password or authentication key of dbadmin_user #

# os_user - Target operating system user #

# os_group - Primary group of os_user #

# #

# MAXDB_CLONE_META=PRD:QAS,/sapdb/QAS,dbm/secret,dbadmin/secret,sdb/sdba #

# #

# MAXDB_CLONE_ADAPT_FS - #

# target_sid - Database SID used on the target side #

# path - full qualified path, file access permissions will be changed recursively #

# wildcards are allowed #

# multiple pathes can be specified, separated by a comma #

# #

# MAXDB_CLONE_ADAPT_FS=QAS:/sapdb/QAS/sapdata* #

# #

# MAXDB_CLONE_RENAME_USER - #

# target_sid - Database SID used on the target side #

# source_username- Schema/Table owner on the source side #

# target_username- Schema/Table owner on the target side #

# Multiple source/target user can be specified, separated by a comma #

# #

# MAXDB_CLONE_RENAME_USER=QAS:sapprd/sapqas,sapprddb/sapqasdb #

# #

# MAXDB_CLONE_RESIZE_LOG - #

# target_sid - Database SID used on the target side #

# new log size - log size in pages #

# #

# MAXDB_CLONE_RESIZE_LOG=QAS:2000 #

# #

# MAXDB_SOURCE_PRESERVE_PARAM - #

# source_sid - Database SID used on the source side #

# parameter - Parameter on the source that should be enabled on the target #

# Multiple Parameters can be specified, separated by a comma #

# #

# MAXDB_SOURCE_PRESERVE_PARAM=PRD:MaxLogVolumes,MaxDataVolumes #

# #

# MAXDB_BACKUP_TEMPLATES - specifies for each database a backup template #

# template - must be an existing backup template of type external #

# #

# MAXDB_BG_SERVER_PREFIX - prefix for naming the background server #

# <prefix> - the prefix will be suffixed with the database id, if not specified, na_bg is being used #

# #

# MAXDB_CHECK_SNAPSHOT_DIR - setting to check, if a SC snapshot operation was successful and the snapshot #

# has been taken. #

# NFS only. directory must point to the directory which contains the .snapshot #

# directory. #

# Multiple directories can be specified as a comma separated list. #

# Multiple databases can be specified as a semicolon separated list. #

# #

# In case of MaxDB 7.8 and newer, the database backup request will be marked as #

# failed in the backup history. The shown error code identifies the number of #

# missing snapshots. #

# #

# MAXDB_CHECK_SNAPSHOT_DIR=SID:directory[,directory...][SID2:directory[,directory...] #

# #

#################################################################################################################

XUSER_ENABLE=N

HANDLE_LOGWRITER=Y

DBMCLICMD=/path/to/dbmcli

SQLCLICMD=/path/to/sqlcli

MAXDB_UPDATE_HIST_LOG=N

MAXDB_DATABASES=

Re: SnapCreator 3.4p2 vmware restore error (vmw-00133)

jntballard — Thu, 17 Nov 2011 04:43:52 GMT

To further validate, I created a datastore using the VSC and cloned VMs using the RCU.

I have no issues creating snapshots of the VMs/Volumes, I consistantly get the following error during the restore:

[Wed Nov 16 19:44:19 2011] [nessus:9090(3.4.0.1)] ERROR: [vmw-00079] CopyDatastoreFile() on Datastore zESX_SCTST1 failed: InvalidDatastorePath!

The guide indicates it may be an issue with permissions. Since this is FCP, and I can easily clone and create additional VMs on this datastore, not sure where to look from here.

Thanks,

Jerry

Re: SnapCreator 3.4p2 vmware restore error (vmw-00133)

jntballard — Thu, 17 Nov 2011 23:58:30 GMT

I have done further testing in this environment. They have multiple clusters. I created a new datastore on another cluster, cloned VMs, and used SnapCreator to create a VM consistent backup.

Using SnapCreator, I was able to use the 'Restore' feature via the GUI without getting the 'VMW-00079' error.

Any ideas as to why it would work on one cluster/ESX servers, then not the other? I am assuming this must be an issue with the vSphere config/permissions, but not sure where the descrpancy is. These systems are all managed by the same VIC.

Any ideas definitely appreciated.

Thanks,

Jerry

Re: SnapCreator 3.4p2 vmware restore error (vmw-00133)

patro — Thu, 24 Nov 2011 18:50:16 GMT

Hi jerry,

In the config details you have mentioned - "SnapCreator Server LINUX " as SC server.

In SC 3.4p2 vmware plugin is not supported on Linux.It is supported only on Windows.

But it supported(Linux and Windows) in current community release i.e 3.5.0c

Thanks

Hari

Re: SnapCreator 3.4p2 vmware restore error (vmw-00133)

jntballard — Mon, 28 Nov 2011 16:18:08 GMT

Thanks Hari,

Unfortunately the 3.5.0c release does not appear to have all the same fixes that are in 3.4p2 (tested both on Linux and Windows). The bugs that are addressed in 3.4p2 for VMware do not appear to be rolled into the 3.5.0c release. Since this is a production environment at this time I am more inclined to stay with 3.4p2. Several of the enhancements in 3.5 are really good, and can't wait for the final release.

Will there be another interim release prior to the final?

Thanks,

Jerry

Re: SnapCreator 3.4p2 vmware restore error (vmw-00133)

ANDREW_GALLANT — Mon, 28 Nov 2011 18:07:51 GMT

I have found that many of the NetApp point and click tools for vmware can be finicky when you get in to really large deployments. You can always do it via the CLI.

vol clone create new_vol_name -s none -b vol_with_snapshot snap_name

Example: vol clone create test_volume_restore -s none -b test_volume hourly.1

assuming NFS modify the exports if ISCSI or FCP add to initiator group

Mount it to the ESX host

remove your old vm from the volume

import your vm in to inventory from your mounted snapshot

storage v motion your vm back to the proper volume

unmount the snap restore volume from esx host

off line the volume on the filer

destroy the volume.

Re: SnapCreator 3.4p2 vmware restore error (vmw-00133)

ktenzer — Tue, 29 Nov 2011 18:35:12 GMT

The 3.4p2 fixes will be in 3.5.0 (netapp release) which releases on Jan 12 2012.

Regards,

Keith

Re: SnapCreator 3.4p2 vmware restore error (vmw-00133)

jntballard — Fri, 02 Dec 2011 03:01:43 GMT

Thanks for the input -

Since we will be working with several systems/datastores the admins prefer the method above leveraging flexclone to import the devices on their DR vCenter systems and validate the VMs prior to full recovery (i.e. S-VM to production datastore). Since some of these instances have Oracle and they are also applying archive logs this provides the flexibility to ensure the DB is fully recovered to an appropriate recovery point before they S-VM to the production datastore.

Jerry