VMware Cloud Community
MarcoLITP
Enthusiast
Enthusiast

VCSA Backup failure after upgrade to 7.0U3g

After updating from 7.0U3e to U3g, backups stopped working.

Both manual and scheduled, the typical error:
"BackupManager encountered an exception. See logs for details. https://vcenter.domain.com/appliance/support-bundle"

 

The link isn't working but I managed to find the cause in backup.log;

 

2022-09-06T10:11:16.234 [20220906-101110-20150588] [MainProcess:PID-34012] [integrity_checker::log_and_print:integrity_checker.py:74] ERROR: [FILE_INTEGRITY_CHECK] Overall status : FAILED. RESULTS: TOTAL: 68910 VERIFIED: 68914 [ADDED: 4 DELETED: 0 MODIFIED: 138]
2022-09-06T10:11:16.242 [20220906-101110-20150588] [MainProcess:PID-34012] [BackupManager::CheckFileIntegrity:BackupManager.py:454] ERROR: Fileintegrity [FILE_INTEGRITY_CHECK] Overall status: Failed. Check /var/log/vmware/cloudvm/fileintegrity.log for more details.

 

The lines preceeding are a lot of these:

 

WARNING: [FILE_INTEGRITY_CHECK_FAILED] Reason : REGULAR FILE MODIFIED, Name : "/usr/lib/vmware-wcp/py-modules/vapi-bindings/com/vmware/vcenter/__pycache__/__init__.cpython-37.pyc"

 

 

Every integrity check failure seems to be in a "__pycache__" folder.

How can I fix this ? I don't have a valid backup anymore as the many failures has overwritten the successful ones.

Tags (2)
Reply
0 Kudos
1 Reply
MarcoLITP
Enthusiast
Enthusiast

I requested support that fixed a problem in the database, also an issue with the SMB server it tries to connect to. Apparently they recently switched from CIFS to Samba causing various issues. I wasn't able to fix the issue on the SMB server so it's using a different location that does work.

Reply
0 Kudos