Optional parameters follow the query exchange command.
- /CONFIGfile=filename
- Use the /CONFIGfile parameter
to specify the name (filename) of the Data Protection for Microsoft Exchange configuration
file that contains the values to use for a query exchange operation.
The filename variable
can include a fully qualified path. If the filename variable
does not include a path, the Data Protection for Microsoft Exchange installation
directory is used. If the /CONFIGfile parameter
is not specified, or if the filename variable
is not specified, the default value is tdpexc.cfg.
If
the
filename variable includes spaces, enclose
the entire
/CONFIGfile parameter entry in double
quotation marks. For example:
/CONFIGfile="c:\Program Files\file.cfg"
- /LOGFile=logfilename
- Use
the /LOGFile parameter to specify the name of
the activity log file that is generated by Data Protection for Microsoft Exchange.
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 Data Protection for Microsoft Exchange installation
directory. If the logfilename variable includes
spaces, enclose the entire /LOGFile parameter
entry in double quotation marks. For example:
/LOGFile="c:\Program Files\mytdpexchange.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.When you use multiple
simultaneous instances of Data Protection for Microsoft Exchange to
perform operations, use the /LOGFile parameter
to specify a different log file for each instance used. This function
directs logging for each instance to a different log file and prevents
interspersed log file records. Failure to specify a different log
file for each instance can result in unreadable log files.
- /LOGPrune=numdays|No
- Use
the /LOGPrune parameter to disable log pruning
or to explicitly request that the log be pruned for one command run.
By default, log pruning is enabled and done once per day. The numdays variable
represents the number of days to save log entries. By default, 60 days
of log entries are saved in the pruning process. You can use the Data Protection for Microsoft Exchange graphical
user interface or the set command to change the
defaults so that log pruning is disabled, or so that more or less
days of log entries are saved. If you use the command line, you can
use the /LOGPrune parameter to override these
defaults. When the value of the /LOGPrune variable numdays is
a number in the range 0 to 9999,
the log is pruned even if log pruning is already done for the day.
Changes
to the value of the
timeformat or
dateformat parameter
can result in prunning the log file unintentionally. If the value
of the
timeformat or
dateformat parameter
is changed, before issuing a
Data Protection for Microsoft Exchange command
that might prune the log file, perform one of the following actions
to prevent the log file from being pruned:
- Make a copy of the existing log file.
- Specify a new log file with the /LOGFile parameter
or logfile setting.