The upgrade prechecks failed for both of these components:
Source and target systems use different datastores: Source=ds:///vmfs/volumes/###############/, Target=ds:///vmfs/volumes/###############/. Please configure and retry the operation or contact support if the issue persists. [VCFMS-PRECHECK-IMPORT-###]
For this upgrade to proceed, the source and target datastores must be the same. Make necessary adjustments and retry. If the issue persists, please contact support.
Import Configuration Validation Precheck
Failed
Import precheck completed with errors. [VCFMS-PRECHECK-IMPORT-###]
VCF 9.1 uses a blue-green upgrade model for VCF Identity Broker and VCF Automation. In this model a new VCF services runtime cluster is provisioned and the component's persistent disks are re-attached from the 9.0 cluster to the 9.1 cluster. This re-attachment requires both the source and destination clusters to reside on the same datastore.
If the VIDB or VCF-A 9.0 cluster was originally deployed on a non-default datastore (for example iSCSI, FCoE, or local storage) and the 9.1 target runtime was provisioned on a different datastore (for example vSAN), the precheck detects the mismatch and blocks the upgrade to prevent data loss or an unrecoverable state.
The issue can be resolved by migrating the 9.0 component to use the same datastore that the 9.1 VCF services runtime will use, and then update its storage configuration to reflect the new datastore.
Please engage Broadcom Support for assistance with this process.
https://support.broadcom.com/web/ecx/software-contact-support