"There is no FIB [summary.xml]" error with Veeam Cloud Connect v12.2

Service Providers operating Veeam Cloud Connect v12.2 (build 12.2.0.334) that have tenants reporting that their jobs have failed are advised to perform the following steps to remediate their situation.

1. Download the Hotfix and Remediation Scripts.
2. Extract the hotfix package to a folder on the SP Veeam Backup Server.
3. Switch the SP Veeam Backup Server to the Maintenance mode.
4. Once all tenant jobs have stopped or been completed, disable all tenant accounts.
5. On the machine where Veeam Cloud Connect is installed, run veeam_backup_12.2.0.334_PrivateFix_TF787128.exe.
   
   Note: The hotfix installer may require a reboot after installation is complete. Please plan accordingly.
6. Create a backup of the configuration database.
7. Extract the Remediation Scripts package and identify the SQL script applicable to the database engine hosting the configuration database.
   
   • For Microsoft SQL Server 2012 or 2014, use DeletingStorageswithoutFIB_MSSQL2012-2014.txt
   • For Microsoft SQL Server 2016 or higher, use DeletingStorageswithoutFIB_MSSQL2016+.txt
   • For PostgreSQL, use DeletingStorageswithoutFIB_PG.txt
8. Open the appropriate database management software and connect the SQL server hosting the Veeam Cloud Connect configuration database.
   ^{For information about identifying the location of the VCC configuration database, review the Identify Veeam Database Location section of Veeam KB1471.}
   
   • For Microsoft SQL Server, use Microsoft SQL Server Management Studio (SSMS).
   • For PostgreSQL, use pgAdmin.
     ^{If you encounter the error "SSPI authentication failed for user," review Veeam KB4542.}
9. Use the SQL script to repair the Configuration Database.
   1. Paste the contents of the appropriate DeletingStorageswithoutFIB script into a new SQL query.
      • For SSMS, right-click on the database, select “New query,” then paste the text from the script file.
      • For pgAdmin, right-click on the database, select “Query Tool,” then paste the text from the script file.
   2. Execute the script against the Veeam Cloud Connect Configuration Database
   3. Review the message output and collect the list of deleted storage for later use.
   4. Repeat the previous two steps (9b and 9c) until the script output reports no storages were deleted (0 rows affected).
10. Using the list of deleted storages you collected in Step 9c, locate and remove those storages from the cloud repositories.
    ^{You may proceed without completing this step right away. Please remember to perform this cleanup step at a later time.
    Those storages will remain in the repository until they are manually cleaned up.}
11. Enable the tenant accounts that were disabled in Step 4.
12. Switch the SP Veeam Backup Server to normal operational mode.
13. Notify all active tenants to first rescan the Service Provider and then start their jobs.
    
    Failure to rescan first will not directly affect the jobs; the rescan simply ensures that tenants will not have latent restore point entries for partial restore points that were cleaned up as part of Step 9.

Service Providers operating Veeam Cloud Connect v12.2 (build 12.2.0.334) that have no tenants reporting that there jobs have failed are advised to download and install the hotfix as soon as possible to prevent any occurrences of this issue.

1. Download the Hotfix.
2. Extract the hotfix package to a folder on the SP Veeam Backup Server.
3. Switch the SP Veeam Backup Server to the Maintenance mode.
4. On the machine where Veeam Cloud Connect is installed, run veeam_backup_12.2.0.334_PrivateFix_TF787128.exe.
   
   Note: The hotfix installer may require a reboot after installation is complete. Please plan accordingly.
5. Switch the SP Veeam Backup Server to normal operational mode.

This hotfix will ensure that should network connection drops occur, they will not impact tenants’ jobs.