The process of building custom solutions for SharePoint Server.
Hi kippie cale
Based on current observations, from my perspective view, the suggested approach to address this issue is to avoid or pause RBS-related migrations while the farm is running the March 2026 Cumulative Update, as this update does not document any RBS-related fixes and has been observed to introduce regressions in some environments.
If orphaned BLOBs have already been created, it is recommended to use the supported SQL Server RBS Maintainer tool to perform consistency checks and garbage collection, which is designed to safely identify and remove unreferenced or orphaned BLOBs from the external store.
Additionally, if migration must continue, consider temporarily migrating content out of RBS (back into SQL inline storage) prior to database movement, and re-enabling RBS only after the migration is complete and the environment is stable.
You can read here for more information: https://learn.microsoft.com/en-us/sharepoint/administration/rbs-overview
Hope this help
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.