Overview
The pre-backup validations step will perform two types of checks:
- Checks on the source gateway that is about to be backed-up
- Only if the target gateway is available at this stage - compatibility checks on the target gateway
It is not mandatory, but highly recommended to have the target gateway up and running at this stage, so DPOD can check if the hardware, firmware and features are compatible between the source and target gateways.
If the target gateway is not available at this stage - DPOD will run those checks later on, just before the Secure-Restore.
Validations
- Application edition - checks that DPOD is not running on Docker or Developer Edition
- Secure Backup mount point - the path where DPOD will download the backup to (and upload the backup from) is determined in the System Parameters page (the "Backups - Destination Path" parameter), this path should be a dedicated mounted filesystem.
- Source is in Secure Backup mode - checks whether the source gateway's Backup Mode is "Secure backup", if the gateway is in "Normal" mode - no Secure Backups or Secure Restores can be issued against it.
If the target gateway is available, more validations can be done at this stage:
4. Target is in Secure Backup mode - checks whether the target gateway's Backup Mode is "Secure backup", if the gateway is in "Normal" mode - no Secure Backups or Secure Restores can be issued against it.
5. Identical firmware level - the source and target gateways must be on the same firmware level, if you need to upgrade the target gateway, consider using DPOD's Firmware Upgrade feature
6. Gateway features compatibility - checks whether the source and target have the same license and features (such as ORA-DCO) - this is an informational check,the user can choose to mark it as "ignored" if it fails.
7. Hardware compatibility - checks whether the gateways device type is compatible (for example, and IDG gateway cannot be migrated to XG45) - this is an informational check, the user can choose to mark it as "ignored" if it fails.