Previous Topic: Considerations for Restoring SFS AliasesNext Topic: Restoring From Physical Backups


Restoring From CMSALLOC Backups

Minidisks backed up in CMSALLOC format must be restored in their entirety and must be restored to disk. Minidisks restored from a CMSALLOC backup are always formatted before any data is restored. Each CMS block backed up from the original minidisk is restored to the same location on the target minidisk.

To a limited extent, this means that CMSALLOC backups are device-dependent; for example, you cannot restore a minidisk backed up in CMSALLOC format from a CKD DASD to a minidisk on a different type of CKD DASD. However, all FBA devices are interchangeable; a minidisk backed up in CMSALLOC format from a CKD DASD can always be restored to an FBA device because the appropriately-sized minidisk can always be constructed out of 512-byte blocks.

The minidisk to which you restore (the target minidisk) must contain the same number of CMS blocks as the backed-up minidisk (the source minidisk) when formatted at the same blocksize.

CA VM:Backup determines whether there are enough CMS blocks on the target minidisk before restoring the data. If there are not enough CMS blocks, CA VM:Backup enters a message in the job output listing and does not change the target minidisk.

On the CA VM:Backup file selection screens, the descriptor ** CMS Alloc ** appears instead of a filename and filetype when you are restoring from a CMSALLOC backup. You can neither select nor view the individual files. Although the backup data contains all the files on the minidisk, the data is backed up and cataloged as CMS blocks, rather than as CMS files.