Replace Minidisks in CRR File Pool

If you are interested in recovery procedures for SFS file pools, see Recovery Procedures. IBM recommends you do control data backup and restore (use the BACKUP and RESTORE startup parameters) for SFS file pools, see Backing Up a File Pool - Overview.

IBM recommends you do not do control data backup and restore (use the NOBACKUP and NORESTORE startup parameters) for CRR file pools. In CRR file pools, there is no user-created file pool catalog data (storage group 1) and user data (storage group 2) to protect. The file pool catalog and user minidisks are minimal size and are only required for server startup and shutdown. In the unlikely event of a error, the minidisks can easily be recreated by using the FILESERV GENERATE command, which is an easy administrative task. You would only have to recreate a minidisk if the error is with the control or catalog minidisks. If you did control data back up, you would have to periodically process a control data back up and save them just in case you ever got the error. Therefore, not doing a control data backup and restore is administratively simpler and cheaper.

CRR file pools, are mainly interested in maintaining the integrity of the CRR log minidisks, not the other minidisks. The CRR logs contain extremely important sync point data necessary for resynchronization processing. The integrity of the CRR logs is maintained by having two copies of the CRR logs on different DASD volumes, not by doing a backup and restore.