CA VM:Backup can use one of five formats when backing up minidisks:
CA VM:Backup uses the CMS file directory to determine which files to back up, then backs up the minidisk by file. If the minidisk contains non-CMS files, CA VM:Backup does not back up the minidisk.
CA VM:Backup reads the block allocation map on CMS minidisks to identify which blocks are in use. CA VM:Backup backs up only the blocks that are in use.
For minidisks, CA VM:Backup identifies the type of minidisk being processed, then determines the appropriate backup format. CA VM:Backup tries a CMS-formatted backup first. If it is not successful, CA VM:Backup performs a physical backup according to the minidisk device type. For SFS data, CA VM:Backup uses SFS format.
CA VM:Backup determines the disk type of the minidisk, then performs the appropriate physical backup. CA VM:Backup backs up count key data (CKD) minidisks by track and fixed block architecture (FBA) minidisks in groups of 32 blocks of 512 bytes.
When backing up SFS data, CA VM:Backup backs up enrollment information, directory structure, and directory authorizations. If a job specifies backing up file spaces, CA VM:Backup backs up aliases, files, file authorizations, and directory authorizations for all directories in those file spaces. If a job specifies backing up only specific directories in a file space, CA VM:Backup backs up the following data for those directories only:
All other directories in the file space appear empty.
CA VM:Backup uses this format for backing up BFS data. CA VM:Backup backs up BFS data at the file space level only. When backing up BFS data, CA VM:Backup backs up the following data:
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|