Import vs Backup for site collection. RRS feed

  • Question

  • Hi All,

    As per my understanding, fort web application we can only take backup. for site/sub site we can ony take import.

    for site collection both are possible, we can take the backup and import as well. it is not clear to me what is the difference between the backup and import for site collection?

    Regards Amit

    Tuesday, September 18, 2012 2:33 AM


  • Hi,

    SharePoint offers two approaches to generating a site collection copy. The first approach, a site collection backup, is commonly carried out using either STSADM.exe –o backup –url <urL> or through the Backup-SPSite cmdlet in SharePoint 2010. The other approach, a site collection export, is invoked through either STSADM.exe –o export or the Export-SPWeb cmdlet in SharePoint 2010.

    Stsadm –o backup/restore
    With the URL and filename parameters, it allows you to backup either a site collection or web application. You can basically consider the file generated more or less as a SQL dump of (a part of) your content database.
    It preserves the GUID of every object except the GUID of the Site: when you restore the backup, SharePoint generates a new GUID for the site collection.
    This was done on purpose, among others things because Sites table in configuration database uses SiteID as the primary key.
    This is very important because it allows you to restore the backup in the same farm in which you did the backup. You can even restore the same backup several times in the same farm, but you must always restore in a different content database, because the GUID of every other object remains unchanged.

    This operation is designed to take an exact copy of a site collection, no data will be changed, transformed or lost.

    Stsadm –o export/import
    This is the only standard operation (not talking about possibilities with custom code) that allows you to backup data of a sub site (SPWeb object), but it can also export a site collection, an entire web application, or a single list. It generates a new GUID for every objects such as sites, sub sites, lists and items.

    Another difference is that you can restore the content in an existing site, the behavior with existing data is defined with the parameter updateversions in import operation.

    A major drawback of this operation is that it does not preserves workflows instances, associations, history and tasks. Every workflow association must be recreated and there is no way to restore the running instances from original site.
    Contrary to the backup operation, it does not matter on which content database you run import operation, and you can restore a top site as a subsite, and reciprocally (except for sites with publishing feature where it is not supported:


    Tuesday, September 18, 2012 4:43 AM