HP BB118BV - StorageWorks Data Protector Express Package User's Manual & Technical Reference page 112

Data protector express user's guide and technical reference (bb116-90089, september 2008)
Hide thumbs Also See for BB118BV - StorageWorks Data Protector Express Package:
Table of Contents

Advertisement

pathScripts: Path to scripts directory
pathVirtualDevices: Path to virtual device directory
pathInstallFrom: Only used during installation, specifies the installation source directory
pathInstallTo: Only used during installation, specifies the destination installation directory
pathOsProfiles: Directory where the operating system user home folders reside (c:\documents and
settings)
time: Current time
date: Current date
buildnumber: Build number of application
option_smartstreams: Name of smartstream licensable option
nodename: Node name where current application resides on
quickaccess: Name of quick access application (Quick access)
sessionInstance: Secondary, or primary, depending on the context where the macro is expanded
masterPort: TCP port number used by the application
threadId: Current operating system specific thread id of current thread
pathSep: OS specific path separator (\ or /)
executeScript: Used to call the script engine, usage: $executeScript$=script.scr
Logs
The pre/post commands add detailed logs to the jobs which executed them. A new execution section
was added to the job log, where all commands executed by the job are logged.
Command type: Indicates what kind of command this was, whether a pre job/post job/fail job,
or pre object/post object/fail object command.
Command path: The fully macro expanded command path sent to the operating system for
execution.
Host attempted on: The host name where the command was attempted on.
Time executed: The start time when the command was attempted.
Time completed: The end time when the command either timed out and was killed, or when it
completed on its own accord.
Execution result: The result of the execution, either the execution failed, or the execution
succeeded. If the execution succeeded, then the return code of the command will be logged here.
If no return code is logged, then success is logged here.
Command Execution Example
This example shows a command which does not exist in the operating system. The error code returned is
an OS-specified reason why the command could not be executed. In this case, it is "File not found".
1 12
Backup Jobs

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Data protector express

Table of Contents