When combining several application profiles with differenct priorities into an application group, these should be taken into account when a recovery plan is executed so that the objects in the highest prioritised profile are reovered first.
Today the objects from different profiles are spread across the recover jobs instead of keeping the highest prioritised in one job.
Today all recover jobs are are run as a serial group and only when that has completed are jobs for rebuild index and check data executed. So all objects wait.
One of the first actions in the "introjob" is to set status of all objects to UT. Not until all objects have been recovered and rebuilt/checked are the objects started in RW.
The end result is that it is not possible to recover critical data first using application groups.
|Who would benefit from this IDEA?||Any client with critical applications that need to be recovered faster than others.|
How should it work?
The application profiles with highest priority should be recovered first. This could be done by creating several batches of recover jobs, each batch corresponding to a priority, and ensuring that higher prioritised batches do not wait for lower prioritised batches.
The only current workaround is to avoid using application groups, but instead create the different application profiles and submit them individually and keeping manually track of the execution.
|Priority Justification||One of the reasons we are looking to get a recovery tool is to avoid having to do manual housekeeping in a recover situation.|
|Customer Name||JN Data|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions