How can we avoid device/media availability becoming an issue for restores of massive historic data from decades ago?
Cybersecurity
DevOps Cloud
IT Operations Cloud
How can we avoid device/media availability becoming an issue for restores of massive historic data from decades ago?
Hi,
To avoid the device availability issues, (pre-)select the devices you preferer to use for the restore.
In the device configuration, set the devices you prefer for restore with the "Device may be used for restore" flag in the Policies tag.
Then, select the "Automatic device selection" in the restore GUI to allow filesystem backups to replace the devices which are in use with the one of the marked devices.
For the application integration backups, please use the "restoredev" file to re-assign the original backup devices into the preferred restore devices.
Please check for more details on the "restoredev" file in the appropriate application integration section if it applies for the given application integration.
To avoid media availability issues, you shall use the DP GUI or DP CLI to list media for every session you are going to restore.
For restore of (Unix, Linux, Windows ...) filesystem sessions, this list shall be accurate to select the exact media needed for the restore.
If the restore is required from the "incremental" type of session, media for whole restore chain are needed.
This includes all the related "incremental" sessions between the selected session and the previous "full" session, plus the media for full session.
Situation with application integration backups is more complicated, as the restore requests may be sent from the application itself.
The applications may restore of data from previous session(s), or next session(s) for the same database instance.
As many of the applications require *log data, include also media for related *log sessions in the media selection.
Best Regards,
Alex