The backup-to-disk feature lets CA VM:Backup send backup and MPC data to DASDtape instead of to physical tape. Each DASDtape is a CMS file with a filename that corresponds to the volser of the tape and a filetype of TAPE. These files, which contain images of CA VM:Backup physical tapes, reside on DASDtape minidisks.
CA VM:Backup manages DASDtapes in the same way that it manages real tapes, and it does not rewrite a DASDtape if it is not expired. However, CA VM:Backup also automatically erases expired DASDtape files that no catalog references to make room for new DASDtapes whenever the DASDtape disk becomes full.
Important! Never modify a DASDtape file. Under some circumstances, such as when a resource pool is modified or discarded, erase DASDtape files manually.
DASDtape minidisks can reside at any virtual address in the range 0100 to 01EF or 1000 to 1FFF. CA VM:Backup does not initialize unless it has read/write links to these minidisks. For specific DASDtape minidisk requirements, see TAPEDISK Record.
Each DASDtape minidisk must correspond to a resource pool definition that a TAPEPOOL Record defines. All DASDtapes that are defined to the resource pool are created on the associated DASDtape minidisk as they are used in backup and MPC jobs.
Every DASDtape resource pool that a TAPEPOOL Record defines has a one-to-one correspondence to a DASDtape minidisk that a TAPEDISK Record defines.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|