Mount Backup optional parameters
Optional parameters follow the mount backup command and positional parameters.
- /CONFIGfile=configfilename
- Use
the /configfile parameter to specify the name
(configfilename) of the IBM Storage Protect™
SnapshotData Protection for Exchange Server configuration file that contains the
values to use for a mount backup operation.
The configfilename variable can include a fully qualified path. If the configfilename variable does not include a path, the IBM Storage Protect SnapshotData Protection for Exchange Server installation directory is used. If the /configfile parameter is not specified, or if the configfilename variable is not specified, the default value is tdpexc.cfg.
If the configfilename variable includes spaces, enclose the entire /configfile parameter entry in double quotation marks. For example:/CONFIGfile="c:\Program Files\tdpexc.cfg" - /LOGFile=logfilename
- Use
the /logfile parameter to specify the name of
the activity log file that is generated by IBM Storage Protect
SnapshotData Protection for Exchange Server. The logfilename variable
identifies the name of the activity log file.
If the specified log file does not exist, a new log file is created. If the specified log file exists, new log entries are appended to the file. The logfilename variable can include a fully qualified path. However, if no path is specified, the log file is written to the IBM Storage Protect SnapshotData Protection for Exchange Server installation directory.
If the logfilename variable includes spaces, enclose the entire /logfile parameter entry in double quotation marks. For example:/LOGFile="c:\Program Files\tdpexc.log"If the /logfile parameter is not specified, log records are written to the default log file, tdpexc.log.
The /logfile parameter cannot be turned off, logging always occurs.
- /LOGPrune=numdays|No
When you prune log data, you can discard some of the generated logs according to detailed filtering criteria that you set. Depending on the option that you set for the /LOGPrune parameter, a certain number of days of data are saved. By default, 60 days of log entries are saved. The option No can be entered to disable log pruning.
Regardless of the option that you set for this parameter, you can explicitly request log pruning at any time.
Considerations:- For numdays, the range is 0 to 9999. A value of 0 deletes all entries in the activity log file except for the current command entries.
- If you specify no, the log file is not pruned.
- If you do not specify /LOGPrune, the default value is that specified by the logprune configurable option in the configuration file. The default value is 60.
- If you specify /LOGPrune, its value is used instead of the value that is stored in the configuration file. Specifying this parameter does not change the value in the configuration file.
- You can specify /LOGPrune without specifying numdays or no; in this case, the default value, 60, is used.
- Changes to the value of the TIMEformat or DATEformat parameter
can result in an unwanted pruning of the log file. If you are running
a command that might prune the log file, and the value of the TIMEformat or DATEformat parameter
is changed, complete one of the following to prevent unintentional
pruning of the log file:
- Make a copy of the existing log file.
- Specify a new log file with the /LOGFile parameter or logfile setting.
- /MOUNTRW=Yes|No
You can mount a read/write copy of your IBM Storage Protect backup so that you can modify the copy without invalidating the backup. You use this option to indicate whether a snapshot backup is mounted as read/write. The default value is as specified in the configuration file with the /MOUNTRW parameter. If a default value is not specified in the configuration file, the default value is No. By specifying the /MOUNTRW option, you override the default value.
The following values are available:- No
- Perform a read-only mount operation.
- Yes
- Perform a read/write mount operation. The behavior of the read/write mount is controlled by the
USESNAPOFASNAPTOMount parameter in the configuration file.
- If USESNAPOFASNAPTOMount is set to No, you can mount only COPY backups as read/write. After mounting, the original backup is modified and can no longer be used as a restore point in future database restore operations (on the VSS Options properties page, the Mount read/write (modifies backup, applies to COPY backups only) check box is selected).
- If USESNAPOFASNAPTOMount is set to Yes, you can mount both
FULL and COPY backup types as read/write (on the VSS Options properties page,
the Mount read/write (without modifying backup) check box is selected). In
this instance, the backups are not modified and can be used in future restore operations.Important:This mount option is only available for the following devices:
- SAN Volume Controller (SVC) devices, which require IBM® System Storage® Support for Microsoft™ Virtual Disk and Volume Shadow Copy Services version 4.12 or later. Dynamic target allocation is not supported.
-
XIV system devices, which require IBM Storage® Accelerate Family Provider for Microsoft Windows Volume Shadow Copy Service version 2.9 or later.
- /REMOTECOMPUTER=computername
- Enter the computer name or IP address of the remote system where the backup was created.
- /REMOTECOMPUTERUser=user
- Enter the user name that is used to log on to the server specified with the REMOTECOMPUTER parameter. If a domain is required to log on with the domain account, enter Domain\User. To log on to the local account, the domain is not required. There is no default value.
- /REMOTECOMPUTERPassword=passwd
- Enter the password for the user name that is specified with the REMOTECOMPUTERUser parameter. There is no default value.
- /TSMNODe=tsmnodename
- Use
the tsmnodename variable to refer to the IBM Storage
Protect node name
that IBM Storage Protect
SnapshotData Protection for Exchange Server uses to log on to the IBM Storage
Protect server.
You can store the node name in the IBM Storage Protect options file (dsm.opt). This parameter overrides the value in the IBM Storage Protect options file if PASSWORDACCESS is set to PROMPT. This parameter is not valid when PASSWORDACCESS is set to GENERATE in the options file.
- /TSMOPTFile=tsmoptfilename
- Use
the tsmoptfilename variable to identify the IBM Storage
Protect options
file.
The file name can include a fully qualified path name. If no path is specified, the directory where IBM Storage Protect SnapshotData Protection for Exchange Server is installed is searched.
If the tsmoptfilename variable includes spaces, enclose the entire /tsmoptfile parameter entry in double quotation marks. For example:/TSMOPTFile="c:\Program Files\dsm.opt"The default is dsm.opt.
- /TSMPassword=tsmpassword
- Use
the tsmpassword variable to refer to the IBM Storage
Protect password
that IBM Storage Protect
SnapshotData Protection for Exchange Server uses to log on to the IBM Storage
Protect server.
If you specified PASSWORDACCESS GENERATE in the IBM Storage Protect SnapshotData Protection for Exchange Server options file (dsm.opt), supplying the password is not necessary here because the one that is stored in the registry is used. However, to store the password in the registry, you must specify the IBM Storage Protect password the first time IBM Storage Protect SnapshotData Protection for Exchange Server connects to the IBM Storage Protect server.
If you do specify a password with this parameter when PASSWORDACCESS GENERATE is in effect, the command-line value is ignored unless the password for this node is not yet stored in the registry. In that case, the specified password is stored in the registry and used when you run this command.
If PASSWORDACCESS PROMPT is in effect, and you do not specify a password value on the command line, then you are prompted for a password.
The IBM Storage Protect password that IBM Storage Protect SnapshotData Protection for Exchange Server uses to log on to the IBM Storage Protect server can be up to 63 characters in length.