Loading...
Loading...
A backup job's task is completed with the warning: Failed to publish guest file system index to the catalog
This warning occurs when either the Veeam Guest Catalog Service service is unable to complete the file interaction task or the service is not operating correctly. Common causes observed from cases: There was insufficient disk space where VBRCatalog was stored. The disk where VBRCatalog is located was failing. The disk where the VBRCatalog is located had a failing iSCSI connection. Security software (antivirus) was locking files within the VBRCatalog. The Veeam Guest Catalog service was not started. The Veeam Guest Catalog was running but was unable to initialize fully... Because one of the configuration XML files it reads as part of the service startup was corrupted by a recent unexpected power loss that caused the Veeam Backup Server to turn off. Because it could not connect to the Configuration Database.
Review the Job-Level Warning Read the job-level warning (starts with "Failed to commit catalog transaction"); it will provide a lead for which issue to investigate.
If the advice in this article does not resolve the issue, please collect logs and create a support case.
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.