Adding RBS to the SharePoint architecture splits the backup and recovery tasks into two parts: databases and BLOBs. This document will discuss how StoragePoint can automatically backup your BLOB data and how you can ensure BLOBs are protected and retained for as long as your database backups.
If you have different time periods that backups must be retained for each database, it is recommended that the granularity of StoragePoint profiles be created to match the granularity of the SharePoint content databases. This allows a backup to be created for each profile which correlates to a specific content database.
Having RBS in places makes no difference to the Backup-SPSite method of backing up SharePoint content. It should be faster than OOTB since the files are pulled from the storage endpoints rather than from SQL Server, but not to a significant degree. However, you do not attain the drastic improvement in backup speed that is discussed throughout this paper. This is because as the backup job crawls content, BLOBs are included and stored with the backup content. If you are using this method to recover SharePoint you will not need to make any changes in the procedures currently in place for the backup process. There are additional considerations that must be addressed when developing a recovery plan. These will be addressed later in the Recovering SharePoint Using PowerShell section of this document.
With Native SQL Server backups there are architectural changes that need to be addressed with both backup and recovery. The database backup itself will not change, but the remote BLOB store now needs to be backed up as well. StoragePoint will automatically backup BLOBs via the continuous BLOB backup discussed in the Backing up BLOBs section. The steps that must be addressed when developing a recovery plan with StoragePoint in place is noted in the Recovering SharePoint from a Native SQL Server Backup section of this document.
Metalogix SharePoint Backup is RBS aware and integrates with the BLOB backup functions within StoragePoint. Other than ensuring a backup endpoint is defined and setting the BLOB backup schedule, there are no additional requirements.