The next three recipes showcase SharePoint 2010's integrated granular backup and restore capability.
One content database can contain several site collections. As the amount of data grows in an organization, the content database grows quickly, along with the value of the information in a site collection. It is the administrator's job to monitor this growth and ensure the data is backed up at regular intervals.
There is a chance that the database either grows too large or someone needs something restored from a particular site collection.
To reduce the size of the content database, the administrator can split off the information by site collection. Splitting off the information by site collection, and parsing it out to another physical content database, reduces the size of the existing content database.
The other condition entails restoring the whole content database from a backup. However, this is quite painful for every site collection in that content database...
