Pre-upgrade checklist
To make upgrade experience smoother a pre-update validation checklist is added as part of prepare-for-update to check and find any discrepancy before starting the upgrade process. This checklist is applicable to Resiliency Manager only.
Following checks are done in pre-upgrade checklist:
Verify pre-upgrade configuration:
If the configuration consists of duplicate objects, the post upgrade operations might fail. It checks the database and fetches if any duplicate objects are found. If duplicate objects are found, a warning is displayed.
If the duplicate objects persist, the post-upgrade operations fail. It checks the database and fetches if any duplicate objects are found. If duplicate objects are found, this check will fail and you need to clean the duplicate object with help of Veritas Support and retry.
These objects might be present in the environment due to any of the following reasons:
If any stale Consistency Groups present.
If there is any failed rehearsal operation present.
If you have performed "force cleanup" which might have left residue.
Stale objects block the replace Replication Gateway as part of upgrade activity. To reduce this downtime, these are validated as part of pre-upgrade checks. These stale objects do not block the upgrade process, but it is recommended to clean these duplicate objects with help of Veritas Support. This can be done either before upgrade process or just after upgrading the Resiliency Manager.
Check for on-going activities: While upgrade is in progress, number of on-going activities is displayed. These activities might get terminated if you confirm to proceed with the upgrade.
Check for on-going reports: While upgrade is in progress, number of on-going reports is displayed. These activities might get terminated if you confirm to proceed with the upgrade.
Check pending process: While upgrade is in progress, multiple number of process are pending for execution. You need to make sure these processes are completed or the upgrade operation may exit. While upgrade is in progress, make sure all the processes are complete. If multiple number of process are pending for execution, prepare-for-update will exit after 30 minutes.