The Backup Exec Sharepoint Agent and Remote Blob Storage (RBLOB or RBS)

Article:TECH210234  |  Created: 2013-09-04  |  Updated: 2013-09-04  |  Article URL http://www.symantec.com/docs/TECH210234
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Issue



Does Backup Exec support backing up Sharepoint content databases where Remote Blob Storage has been implemented?


Cause



With Sharepoint 2010 and 2013 it is possible to store file data external to the Sharepoint content database.  In these cases, the location within the content database where the file data would normally reside is replaced by pointers to externally stored file data. This can be accomplished in a couple of ways:  

The first is with SQL FILESTREAM.  This is an option implemented in SQL server where BLOB data like files and documents are stored in the file system instead of inside the database.   The Backup Exec Sharepoint agent backs up this database and filestream data fully and all data is restorable at the database level.  Granular Restore Technology restores of this data are not possible because the Sharepoint agent can only restore granular content that is stored within the content database. 

The second is called Remote Blob Store or RBS.  While SQL FILESTREAM can be considered a form of Remote BLOB Storage, RBS as included here refers to third party providers that perform external storage of BLOB data to dedicated storage locations.  Backup and restore of Sharepoint databases configured in this way is not supported with Backup Exec. 


 


Solution



Workaround: For RBS enabled content databases, the internal Sharepoint 2010 or 2013 backup and restore utility should be used along with the supported RBS provider.  See http://technet.microsoft.com/en-us/library/ee748649.aspx for more information.




Article URL http://www.symantec.com/docs/TECH210234


Terms of use for this information are found in Legal Notices