Change Between VCF 9.1.0 and 9.1.1 for NSX Backup Locations

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

When using Invoke-NSXManagerRestore there is a change between VCF 9.1.0 and 9.1.1 when it comes to the backup folder configuration.

• VCF 9.1.0 uses /media/backups/ when configured by SDDC Manager within NSX Manager
• VCF 9.1.1 uses /media/backups/<vip_fqdn>/ by SDDC Manager with NSX Manager

As a result you must use the following between versions:

• VCF 9.1.0 = -sftpServerBackupPath /media/backups/
• VCF 9.1.1 = -sftpServerBackupPath /media/backups/<vip_fqdn>/

Otherwise in VCF 9.1.1 you will not find any previous backups.

Use Case(s)

Changes between VCF versions

Potential Configuration

The Invoke-NSXManagerRestore should be enhanced to handle this difference automatically. Using the ``\extracted-sddc-data.json" file which is read you can certain the version of SDDC Manager and then automatically add the VIP cluster FQDN to the sftpServerBackupPath variable used to configure the SFTP backup in NSX.

$extractedSddcData.sddcManager.version would provide the SDDC Manager Version
$workloadDomainDetails.nsxClusterDetails.clusterFqdn would provide the NSX Manager cluster VIP

References

No response

Start at the Invoke-NSXManagerRestore entry point and inspect how extracted-sddc-data.json, $extractedSddcData.sddcManager.version, and $workloadDomainDetails.nsxClusterDetails.clusterFqdn are read. Trace the sftpServerBackupPath configuration and verify the restore handles the VCF 9.1.0 and 9.1.1 backup locations correctly, including locating previous backups.