...
The BRMS Cloud Solution was not designed to handle Parallel Backup and Restores. Therefore, it is not recommended.
How does the BRMS Cloud control group with a SAVSYS manage cloud transfers with restricted state processing?
When using the BRMS supplied cloud control groups named QCLDIPLxx the backup always goes to virtual optical and the transfers are not initiated until after the control group is finished. This is because BRMS uses leave processing during the backup and appends to the optical volume set. Optical does not have an exit program available to call to initiate a transfer when a volume is full. By default, the QCLDIPLxx control group attributes for option 9 'Subsystems to process' value is set to Restart *YES which will start the subsystems and allow automatic transfers to happen after the control group completes. If the Restart value is changed to *NO, BRMS does not do any special processing to start any subsystems and the automatic transfer request will fail. The volumes will stay in *TRF state until the problem is resolved. When the subsystem is started again, running STRMNTBRM will find and transfer any volumes left in *TRF state.
How does the BRMS Cloud control group with a SAVSYS manage transfers when the control group is set to IPL after the backup?
If the control group is set to IPL after the backup, the volumes are not automatically transferred. The user needs to run media movement to transfer the volumes after the system is back online. There could be a small timing window where the transfer might be initiated while the system is coming down, but the transfer would fail and leave the volume in *TRF state. Like any other failed transfer, once the system is back online and cloud communication is reestablished, running STRMNTBRM will find and transfer any volumes stuck in *TRF state.