Data Protector has not been installed, the uma command is fully functional and behave
as documented, but it is probably not able to locate and use Data Protector NLS
message catalog.
On HP-UX and Solaris systems, uma is located in /opt/omni/lbin/ directory,
and the Data Protector NLS message catalog is located in the
/opt/omni/lib/nls/C/ directory.
On other UNIX systems, uma is located in /usr/omni/bin/ directory, and the
Data Protector NLS message catalog is located in the /usr/omni/lib/nls/C/
directory.
On Windows systems, uma is located in Data_Protector_home\bin directory,
and the Data Protector NLS message catalog is located in the
Data_Protector_home\bin directory.
Uma can be started both interactively or in batch mode. The only obligatory option
is the pathname of the device file (UNIX systems) or the SCSI address (Windows
systems) that controls the robotics of the target autochanger (the -ioclt option).
For backup devices with library robotics connected to an NDMP Server (to a supported
NAS device), the -interface and the -ddt options must also be specified.
For your convenience, the uma command allows you to specify symbolic instead of
physical element addresses (slot IDs). Whenever you need to refer to the 1st drive of
the autochanger, you can specify either the physical address '128' or the more
convenient, symbolic 'D1'. The output of the addr command reflects this addressing
convention.
OPTIONS
-version
Displays the version of the uma command.
-help
Displays the usage synopsis for the uma command.
-policy LogicalDevicePolicy
Specifies the backup device policy ID. Policy can be defined as 6 (external
control), 8 (Grau DAS exchanger library), 9 (STK Silo medium library), 10 (SCSI
Library), or 13 (VLS).
The default value for the -policy option is 10.
-ioctl deviceFile
Specifies the pathname of the device file (UNIX systems) or the robotics SCSI
address (Windows systems) that controls the robotics of the target autochanger.
404
To Next Page
Loading...
Need help?
General