The most important item to address when backing up RBS enabled SharePoint content is backing up the BLOBs. To do this, define a Backup endpoint in StoragePoint and use the settings within StoragePoint to manage the schedule and retention of these items. The backup is a mirror of the active BLOB store with the addition of SharePoint items that have been deleted or changed over time.
Creating a backup endpoint is done in the same fashion as creating a normal endpoint. Simply ensure that the type is set to backup.
Once the backup endpoint is created, you can then specify that endpoint in the backup settings portion of the StoragePoint profile. You then need to set a schedule for the timer job to move any new or modified BLOBs into this endpoint. Running the BLOB backup job on a very frequent basis is preferred as there is no impact on SharePoint users and less content is required to be moved with each job. The intent is to continually update the backup location to ensure BLOBs are in a safe location should a disaster occur. The retention date for BLOBs in the backup endpoint should be set to a period of time that includes all content database backup sets that might be used for recovery. Note that BLOBs are immutable and are thus never updated. As new BLOBs are created a continuous copy is made. This concept is key to creating faster and smaller backups.
Alternatively, you may use your own methods for mirroring the BLOBs, but this eliminates the ability of the StoragePoint Health Analyzer job to automatically restore BLOB if they are missing. In a recovery scenario, where BLOB backup was accomplished using tools other than the StoragePoint BLOB backup, the BLOBs must be restored to the endpoint manually.