Windows Workstation or Server
AutoVAULT runs on a Windows 32 bit or 64 bit platform. It can be run on the TSM for Windows Server (x32 or x64) or from a remote Windows workstation or server. AutoVAULT has been tested with 2003/2008/2008R2/2012/2012R2 Server, or Windows 7/8/10. VMware is also supported.
TSM Server for Windows, AIX, HP-UX, Solaris, or Linux
AutoVAULT will manage Tivoli Storage Manager (TSM) versions v7.1, v8.1 or newer. TSM Server must be running on a Windows (x32 or x64), AIX, HP-UX, Linux, or Solaris platform. To manage a TSM server, AutoVAULT must run on an Windows server or workstation with TCP/IP access to the remote TSM server or can run directly on a TSM for Windows server. The TSM administrative command line client, the TSM ODBC interface (for TSM 5 only), and FTP (remote only) are used by AutoVAULT to manage the Storage Manager Server and you must have at least one volume history file and device configuration file defined at the same location as the DSMSERV.OPT file.
Tape Libraries Supported by AutoVAULT
AutoVAULT interfaces with tape libraries using TSM commands. Therefore, AutoVAULT supports the same tape libraries that TSM supports with the same restrictions. Note that AutoVAULT ejects media individually, one tape per MOVE or CHECKOUT command. Your tape library must be configured to allow for ejects of individual media.
Use AutoVAULT with OR without IBM Tivoli Disaster Recovery Manager (DRM)
If you have a TSM server running DRM, you can now add AutoVAULT to DRM to fully automate your vaulting functions and provide all the vaulting reports you need. AutoVAULT still supports the traditional vaulting method using CHECKOUT LIBV and UPDATE VOLUME commands, but now also supports all DRM functions including MOVE DRMEDIA, MOVE MEDIA, and PREPARE. You can choose which method works best for each of your TSM server instances. If you want to use DRM with AutoVAULT, you must have a DRM license. If you don't wish to use DRM, AutoVAULT will provide all the tape vaulting and disaster recovery features you need on its own without the need for DRM or a DRM license.
TSM administrative command line client
A TSM administrative command line client is required for the operation of AutoVAULT. You should install a version that matches the version of your TSM Server. The TSM administrative client must be installed on the same Windows server or workstation running AutoVAULT. The TSM administrative client is bundled with the TSM backup/archive client and must be installed using a custom install.
TSM Administrator access
AutoVAULT requires a TSM administrator with system privilege so that it can communicate with the Storage Manager server. After the userid and password are supplied and verified during the AutoVAULT installation, they are encrypted for AutoVAULT to use when it runs. If the userid and/or password need to be changed at a later date, run AutoVAULT configuration by selecting 'Configure' from the AutoVAULT management console.
FTP access for Remote Management
If AutoVAULT is managing a TSM server remotely, a userid is required with ftp access (active or passive) to the Storage Manager server's configuration files. After the userid and password are supplied and verified during the AutoVAULT installation, they are encrypted for AutoVAULT to use when it runs. If the userid and/or password need to be changed at a later date, run AutoVAULT configuration by selecting 'Configure' from the AutoVAULT management console. On TSM for Windows, you must enable the FTP server and create a virtual ftp directory to the location containing your dsmserv.opt file.
TCP/IP connectivity to TSM server
The ODBC interface, TSM administrative client, and FTP require TCP/IP access to the Storage Manager server. If your TSM server runs remotely, the server or workstation running AutoVAULT must have TCP/IP communications to the TSM Server.
To use AutoVAULT with TSM Library Clients you must use the DRM vaulting method. IBM only supports Library clients using the DRM commands. AutoVAULT supports TSM Library Clients using MOVE DRMEDIA and MOVE MEDIA commands. Backupset media management has limited support for a Library Client. For backupset media, AutoVAULT uses TSM command routing to send CHECKOUT LIBV commands to the Library Manager server. Only one tape library can be specified for all backupset media. Error checking is also limited.
Once AutoVAULT has been installed and configured, it should be scheduled to run using whatever mechanism you are comfortable with using. This might be manually by an operator or you might choose a method that is somewhat more automated. AutoVAULT can be scheduled using any scheduling method. We recommend running AutoVAULT as a scheduled command from the Storage Manager Central Scheduler. By doing this, the operation of AutoVAULT is accessible through the same interface you already use to schedule your database and onsite storage pool backups. details.
Phone: (1) 888-402-6937, email@example.com