Environment variables supported by ONTAP
Environment variables are used to communicate information about a backup or restore operation between an NDMP-enabled backup application and a storage system. ONTAP supports environment variables, which have an associated default value. However, you can manually modify these default values.
If you manually modify the values set by the backup application, the application might behave unpredictably. This is because the backup or restore operations might not be doing what the backup application expected them to do. But in some cases, judicious modification might help in identifying or working around problems.
The following tables list the environment variables whose behavior is common to dump and SMTape and those variables that are supported only for dump and SMTape. These tables also contain descriptions of how the environment variables that are supported by ONTAP work if they are used:
In most cases, variables that have the value, |
Environment variables supported for dump and SMTape
Environment variable | Valid values | Default | Description |
---|---|---|---|
DEBUG |
|
|
Specifies that debugging information is printed. |
FILESYSTEM |
|
|
Specifies the path name of the root of the data that is being backed up. |
NDMP_VERSION |
|
|
You should not modify the NDMP_VERSION variable. Created by the backup operation, the NDMP_VERSION variable returns the NDMP version. ONTAP sets the NDMP_VERSION variable during a backup for internal use and to pass to a backup application for informational purposes. The NDMP version of an NDMP session is not set with this variable. |
PATHNAME_SEPARATOR |
|
|
Specifies the path name separator character. This character depends on the file system being backed up. For ONTAP, the character “/” is assigned to this variable. The NDMP server sets this variable before starting a tape backup operation. |
TYPE |
|
|
Specifies the type of backup supported to perform tape backup and restore operations. |
VERBOSE |
|
|
Increases the log messages while performing a tape backup or restore operation. |
Environment variables supported for dump
Environment variable | Valid values | Default | Description | ||
---|---|---|---|---|---|
ACL_START |
|
|
Created by the backup operation, the ACL_START variable is an offset value used by a direct access restore or restartable NDMP backup operation. The offset value is the byte offset in the dump file where the ACL data (Pass V) begins and is returned at the end of a backup. For a direct access restore operation to correctly restore backed-up data, the ACL_START value must be passed to the restore operation when it begins. An NDMP restartable backup operation uses the ACL_START value to communicate to the backup application where the nonrestartable portion of the backup stream begins. |
||
BASE_DATE |
|
|
Specifies the start date for incremental backups. When set to These variables are an alternative to the LEVEL/UPDATE based incremental backups. |
||
DIRECT |
|
|
Specifies that a restore should fast-forward directly to the location on the tape where the file data resides instead of scanning the entire tape. For direct access recovery to work, the backup application must provide positioning information. If this variable is set to |
||
DMP_NAME |
|
|
Specifies the name for a multiple subtree backup. This variable is mandatory for multiple subtree backups. |
||
DUMP_DATE |
|
|
You do not change this variable directly. It is created by the backup if the BASE_DATE variable is set to a value other than The DUMP_DATE variable is derived by prepending the 32-bit level value to a 32-bit time value computed by the dump software. The level is incremented from the last level value passed into the BASE_DATE variable. The resulting value is used as the BASE_DATE value on a subsequent incremental backup. |
||
ENHANCED_DAR_ENABLED |
|
|
Specifies whether enhanced DAR functionality is enabled. Enhanced DAR functionality supports directory DAR and DAR of files with NT Streams. It provides performance improvements. Enhanced DAR during restore is possible only if the following conditions are met:
|
||
EXCLUDE |
|
|
Specifies files or directories that are excluded when backing up data. The exclude list is a comma-separated list of file or directory names. If the name of a file or directory matches one of the names in the list, it is excluded from the backup. The following rules apply while specifying names in the exclude list:
|
||
EXTRACT |
|
|
Specifies that subtrees of a backed-up data set are to be restored. The backup application specifies the names of the subtrees to be extracted. If a file specified matches a directory whose contents were backed up, the directory is recursively extracted. To rename a file, directory, or qtree during restore without using DAR, you must set the EXTRACT environment variable to |
||
EXTRACT_ACL |
|
|
Specifies that ACLs from the backed up file are restored on a restore operation. The default is to restore ACLs when restoring data, except for DARs (DIRECT=Y). |
||
FORCE |
|
|
Determines if the restore operation must check for volume space and inode availability on the destination volume. Setting this variable to If enough volume space or inodes are not available on the destination volume, the restore operation recovers as much data allowed by the destination volume space and inode availability. The restore operation stops when volume space or inodes are not available. |
||
HIST |
|
|
Specifies that file history information is sent to the backup application. Most commercial backup applications set the HIST variable to
|
||
IGNORE_CTIME |
|
|
Specifies that a file is not incrementally backed up if only its ctime value has changed since the previous incremental backup. Some applications, such as virus scanning software, change the ctime value of a file within the inode, even though the file or its attributes have not changed. As a result, an incremental backup might back up files that have not changed. The
|
||
IGNORE_QTREES |
|
|
Specifies that the restore operation does not restore qtree information from backed-up qtrees. |
||
LEVEL |
|
|
Specifies the backup level. Level 0 copies the entire data set. Incremental backup levels, specified by values above 0, copy all files (new or modified) since the last incremental backup. For example, a level 1 backs up new or modified files since the level 0 backup, a level 2 backs up new or modified files since the level 1 backup, and so on. |
||
LIST |
|
|
Lists the backed-up file names and inode numbers without actually restoring the data. |
||
LIST_QTREES |
|
|
Lists the backed-up qtrees without actually restoring the data. |
||
MULTI_SUBTREE_ NAMES |
|
|
Specifies that the backup is a multiple subtree backup. Multiple subtrees are specified in the string, which is a newline-separated, null-terminated list of subtree names. Subtrees are specified by path names relative to their common root directory, which must be specified as the last element of the list. If you use this variable, you must also use the DMP_NAME variable. |
||
NDMP_UNICODE_ FH |
|
|
Specifies that a Unicode name is included in addition to the NFS name of the file in the file history information. This option is not used by most backup applications and should not be set unless the backup application is designed to receive these additional file names. The HIST variable must also be set. |
||
NO_ACLS |
|
|
Specifies that ACLs must not be copied when backing up data. |
||
NON_QUOTA_TREE |
|
|
Specifies that files and directories in qtrees must be ignored when backing up data. When set to
|
||
NOWRITE |
|
|
Specifies that the restore operation must not write data to the disk. This variable is used for debugging. |
||
RECURSIVE |
|
|
Specifies that directory entries during a DAR restore be expanded. The DIRECT and ENHANCED_DAR_ENABLED environment variables must be enabled (set to
For example, the following are valid recovery paths because all of the recovery paths are within
The following are invalid recovery paths:
|
||
RECOVER_FULL_PATHS |
|
|
Specifies that the full recovery path will have their permissions and ACLs restored after the DAR. DIRECT and ENHANCED_DAR_ENABLED must be enabled (set to |
||
UPDATE |
|
|
Updates the metadata information to enable LEVEL based incremental backup. |
Environment variables supported for SMTape
Environment variable | Valid values | Default | Description |
---|---|---|---|
BASE_DATE |
|
|
Specifies the start date for incremental backups.
The backup application assigns the |
DUMP_DATE |
|
|
At the end of an SMTape backup, DUMP_DATE contains a string identifier that identifies the Snapshot copy used for that backup. This Snapshot copy could be used as the reference Snapshot copy for a subsequent incremental backup. The resulting value of DUMP_DATE is used as the BASE_DATE value for subsequent incremental backups. |
SMTAPE_BACKUP_SET_ID |
|
|
Identifies the sequence of incremental backups associated with the baseline backup. Backup set ID is a 128-bit unique ID that is generated during a baseline backup. The backup application assigns this ID as the input to the |
SMTAPE_SNAPSHOT_NAME |
Any valid Snapshot copy that is available in the volume |
|
When the SMTAPE_SNAPSHOT_NAME variable is set to a Snapshot copy, that Snapshot copy and its older Snapshot copies are backed up to tape. For incremental backup, this variable specifies incremental Snapshot copy. The BASE_DATE variable provides the baseline Snapshot copy. |
SMTAPE_DELETE_SNAPSHOT |
|
|
For a Snapshot copy created automatically by SMTape, when the SMTAPE_DELETE_SNAPSHOT variable is set to |
SMTAPE_BREAK_MIRROR |
|
|
When the SMTAPE_BREAK_MIRROR variable is set to |