Virtual TapeServer 6.03.42 Operations and Administration Guide

Managing Pools and Virtual Tapes | 69
#LOAD /LOADED evt_x/ $system.zspidef.ztactacl
#LOAD /LOADED evt_x/ $system.zspidef.ztaptacl
#DEF evt_buf STRUCT BEGIN BYTE b(1:3000); END;
#SET collector $0
#SET action_id 0
#SET evt_error [#REQUESTER /WAIT/ READ [collector] req_error req_read
req_prompt]
#PUSH evt_num action emphasis evt_text text_len
#SET evt_num number
#SET action -1
#SET emphasis -1
#SET evt_text VTSPolicy Erase|Delete - virt_tape...
#SET text_len
#SET evt_error [#EMSINIT evt_buf [ZEMS^VAL^EXTERNAL^SSID] [evt_num]
ZEMS^TKN^TEXT [#charcount evt_text] [evt_text]]
#SET evt_error [#SSPUT evt_buf ZEMS^TKN^EMPHASIS [ZSPI^VAL^TRUE]]
#SET evt_error [#SSPUT evt_buf ZEMS^TKN^ACTION^NEEDED [ZSPI^VAL^TRUE]]
#APPENDV req_prompt evt_buf
Exporting and importing virtual tapes or pools
VTS enables you to export a virtual tape to physical tape, or import a physical tape to a
virtual tape. The import and export features were designed for occasional low-volume use and
require that a standalone tape drive or simple cartridge autoloader is connected to VTS. You
must ensure that the tape drive is available and that appropriate tape media is installed
before beginning an import or export operation.
You can import or export a single virtual tape or an entire pool. If you export a single virtual
tape, you can use that tape outside of the VTS environment, just as you would any other
physical tape. When you export a virtual tape, VTS transfers the data to the attached drive or
autoloader as if the data was being transferred by the host server. All metadata, files, and file
marks are transferred to physical tape. The format of the physical tape is that of the host that
originally transferred the data to VTS, where it was stored as a virtual tape. If you export a
pool, you can only import the tape(s) back into VTS. Also, when exporting a pool, only those
virtual tapes that contain data are exported.