How to backup blobs after EBS was configured on server? I've tried "Backup and Restore" from Central Administration and it works, but my blobs aren't saved nor restored, blobs are intacked, but Content DB is always refreshed. Is this the right way or is there some other way of doing backup of blobs on ebs?

It's working as expected. Remember the point of EBS is to EXTERNALISE the BLOBS, so that they're no longer within the Content Databases. EBS will keep the metadata and the reference to where they're stored but not the BLOBS themselves. Where did you move them? If they're sitting on a file server, or a shared drive somewhere, than the BLOBS will be covered by the back-up and restore plans for those disks and NOT SharePoint. Hope that helpsSteven Andrews | SharePoint Professional | http://www.twitter.com/backpackerd00d | https://baron72.wordpress.com/

Thanks for the answer. So, if I have 1 GB of data in SP and I want to store it (backup) from SP to External Storage (shared drive) and possibly restore it later how do I do that?

Hi SPManiac, when you install and enable the EBS Provider for the first time, you must manually move existing BLOBs that are currently stored in the content database to your external BLOB store. You can do this in two ways. 1.You can use site-level backup and restore methods on the SPSiteCollection object to backup and restore your entire data store. After first backing up all of your data, and then installing and enabling the EBS Provider, when you Then when you invoke the restore operation, the EBS Provider routes BLOB streams to the external BLOB store, while routing structured data to the appropriate tables in the content database. 2.A second, passive method relies on the issue discussed earlier in this section. Because new BLOB data streams are saved to the external BLOB store whenever a file is updated, you can simply install and enable the EBS Provider and then allow the natural process of file updates to gradually populate the external BLOB store with binary files that were previously held in the content database. When an updated file is routed to the external BLOB store, the previous version of the file is automatically deleted from the content database. Thanks, Jack