When upgrading NSX-T in a VMware Cloud Foundation (VCF) environment (observed in SDDC 5.2.4.0), upgrade prechecks fail with a "Backup Operation Check" error despite no active backups.
A stale lock file from a previous backup remains on the NSX Manager filesystem. The Upgrade Coordinator detects this file and incorrectly determines a backup is in progress, blocking the upgrade.
Manually remove the stale lock file from the affected NSX Manager node(s).
/opt/vmware/upgrade-coordinator-tomcat/bin/.backup_restore_in_progress /image/backup/.backup_restore_in_progressrm /opt/vmware/upgrade-coordinator-tomcat/bin/.backup_restore_in_progress rm /image/backup/.backup_restore_in_progressrestart service install-upgrade/etc/init.d/upgrade-coordinator restartIf the precheck still reports the same alert, perform a rolling reboot of the NSX manager cluster by rebooting one manager VM at a time. Wait for all services to be online and the VM to be stable before moving onto the next VM. It is recommended to reboot the NSX manager that is the master of the VIP for the last reboot.
If the above steps do not resolve the issue, please open a case with Broadcom support Creating and managing Broadcom cases and provide the NSX log bundle for review. Collect Support Bundles