The BRMS recovery report is enhanced to provide instructions to assist in a full system recovery using an NFS host server.
Recovering a system using the NFS install procedure is an intensive process that requires special attention to the details. This page highlights some of these details and addresses some main areas to be mindful of for a successful NFS recovery.
Review the Recovery Report
It is important to review your recovery report for accuracy and check for Attention blocks which identify areas of concern.
New Sections
The new NFS specific instructions are being included in 7.2 and later releases and have the following characteristics:
The new information is printed in UPPER CASE English only.
The new steps are printed when the backup uses the DSI VTL iSCSI support implementation with control group QNFSIPLFUL.
The new steps are printed when the backup uses cloud control groups prefixed with QCLDBIPL or QCLDUIPL after they have been enabled for NFS support with one of the following commands:
In 7.3 and 7.4 run one of the following commands:
CALL QBRM/Q1AOLD PARM('SETUPFUN ' '*SET ' 'Q1ACLDNFS' '*JOB') - set up to for current job only
CALL QBRM/Q1AOLD PARM('SETUPFUN ' '*SET ' 'Q1ACLDNFS' '*SYS') - set up to affect all jobs
In 7.5 run the following command:
SETFCNBRM ACTION(*ADD) FUNCTION(CLDNFS) SCOPE(*SYS)
NOTE: The SCOPE parameter also supports *JOB to only affect the current signed on job.
Avoid Library Spanning
When reviewing your recovery report, it is critical to check if libraries QSYS2, QUSRSYS, or QGPL span optical volumes. Depending on where the span occurs, it may be an object that is needed by the operating system to process the volume switch which may make the library unrecoverable. If any of these libraries span, you should adjust your volume sizes and backup strategy to make every effort to avoid a volume span to ensure a successful recovery.
Incremental Strategy
When your backup strategy implements the 4 BRMS control group strategy for cloud or DSI VTL iSCSI backups to NFS, this will result in multiple optical image catalogs being used during the recovery.
Virtual Optical Device Recommendation
The recovery report will provide instructions to create 2 virtual optical devices. This is suggested to prevent the overhead of having to switch image catalog directories on a single device. It is helpful to name these devices appropriately to easily identify which one has the full images and which has the incremental. Example device names: OPTNFSFUL and OPTNFSINC
User Profiles and Configuration Data
When processing the steps to 'Recover User Profiles' and 'Recover Configuration Data' pay special attention to the control group name and volume on the report. User profile and configuration data will always be listed as a full save, meaning this information could be on the optical images from the incremental backup control group.
Order is Critical
When processing the steps to 'Recover Required System Libraries' it is critical to follow the recovery report. Libraries QSYS2, QGPL, and QUSRSYS need to be processed in the order they are listed. You cannot process all the *FULL backups first and then the *CUML backups, you have toggle between the *FULL and *CUML to restore the entire libraries as they are listed on the recovery report.