Backup/Restore a bad practice for deployment ?

  1. Import export allow us to export a site or web and move it to another server or another location with in the same server

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.

dump of (a part of) your content database.

It keeps every GUIDs except one (and the most important): when you restore the file, it generates a new GUID for the site collections.

This was done on purpose because Sites table of configuration database uses SiteID as 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 all others GUIDs remain unchanged.

Stsadm –o export/import

This is the only standard operation that allows you to store a sub site (a SPWeb), but it can also export a site collection or an entire web application. It exports the data using object model, and generates a new GUID for every objects such as sites, sub sites, lists and items.

Another difference is that an import does not involve losing existing data. You can restore a site 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 copy any information related to workflows. If import creates new lists and a workflow was associated to them, you must recreate it manually. Additionally, it does not copy workflow history and tasks lists.

Contrary to the backup operation, it does not matter in which content database you run import operation, and you can restore a top site as a subsite, and reciprocally.

This operation is probably more designed for people that want to merge content of sites, and finely choose how to handle identical data between source and target. Very important, do not forget to use includeusersecurity parameter in both export and import if you wish to preserve information relative to permissions and other properties such as documents authors.

It will restore everything for web application

Another feature of import export is reprint a web. Backup and restore allows you to move the physical files to another server this doesn’t need any trust, you could copy using a USB drive etc.

Content deployment moves a site collection from one farm to another (you can also move to a location on the same server if its using a different database). There must be some trust between the source farm and the destination farm. Think of this as a staging process.

I would use content deployment to move content from a staging server to a production server as long as the two environments have a trust

There must be some trust between the source farm and the destination farm

Backup and restore allows you to move the physical files to another server this doesn’t need any trust, we can use USB drive to take it.

Content Deployment keeps the same GUIDs for the objects so you cannot deploy to the same web application (due to the uniqueness of the objects in the same database) unless the site has its own content database. For more information please see

The deployment destination must have a site collection created using the blank template.

Export allows you to backup a copy of a site to the file system. This will generate one or more .CMP files (based on the size of the site, this will distribute the contents over many .CMP files).

Import allows you to take the files generated by an export and import over a blank SharePoint Site.

STSADM -o export -url http://localhost/KKPOCSite -filename c:\export\ProjectSite1 -includeusersecurity
STSADM -o createweb -url http://localhost/KKArchive/KKProjectSite1

STSADM -o import -url http://localhost/KKArchive/KKProjectSite1 -filename c:\export\KKProjectSite1.cmp –

The createweb operation creates a blank site for the import to write the contents of the export over. You shouldn’t specify a sitetemplate as you just need a blank container (the template is defined in the export .CMP files).

Can back up top-level websites (Site Collections), an individual database, a Web application, or an entire farm.

Like Smigrate.exe utility in SPS 2003, you can migrate sites, subsites and Site Collection.

There is no Default File Extension for back up files

Default file Extension (if not mentioned) “.cmp

Supports “Full” and “Differential” back up. If “overwrite” option is selected while

Provides “versions” option to control migrate/overwrite files in siteS

Import / Export allows you to move a web (sub site).

How we can take Backup / Restore —

For site collection backup

stsadm -o backup

-url <URL name>

-filename <file name>

[-overwrite]

stsadm -o backup

-directory <UNC path or local drive>

-backupmethod <full or differential>

[-item] <created path from tree>

[-percentage] <integer between 1 and 100>

[-backupthreads] <integer between 1 and 10>

[-showtree]

[-quiet]

For Import and Export :

stsadm -o export

-url <URL name>

-filename <export file name>

[-overwrite]

[-includeusersecurity]

[-haltonwarning]

[-haltonfatalerror]

[-nologfile]

[-versions] <1-4>

[-cabsize] <integer value>

[-nofilecompression]

[-quiet]

stsadm -o import

-url <URL name>

-filename <import file name>

[-includeusersecurity]

[-haltonwarning]

[-haltonfatalerror]

[-nologfile]

[-updateversions] <1-3>

[-nofilecompression]

[-quiet]

14. For catastrophic restore
stsadm -o restore

-directory <UNC path>

-restoremethod <overwrite or new>

[-backupid] <GUID from backuphistory, see stsadm -help backuphistory>

[-item] <created path from tree>

[-percentage] <integer between 1 and 100>

[-showtree]

[-suppressprompt]

[-username] <user name>

[-password] <password>

[-newdatabaseserver] <new database server name>

[-preservechangelog]

[-quiet]

About Krishana Kumar

Krishana Kumar is SharePoint Architect/Trainer having Architecture experience with high volumes at Enterprise level and global scale - creation of highly scalable solutions with global user base and geographically distributed architectural components. Good knowledge of SharePoint best practices and governance models. I hold Two Master degree in Computer Science with over 11 years of experience working on Microsoft Technologies specially SharePoint, Project, .NET and other Information Worker Technologies. Having good exposer in Client side scripting Angular.js, backbone and Node. I am currently responsible for SharePoint Infrastructure set up and leading teams in various medium and large scale projects, architecting, designing & installing SharePoint farms, developing custom components,, and providing advanced SharePoint administration and development training to teams and customers. I regularly speaks in various SharePoint User Groups and other Events. I have MCSA Windows Azure, MCSA Office 365, MCSE & MCSD SharePoint 2013, Microsoft Certified Developer (MCD) and holds MCPD, MCTIP and MCTS for SharePoint 2010, MCTS MOSS 2007 & WSS 3.0, MCPD, MCITP (EPM 2010 & 2007) and MCSD .NET.
This entry was posted in General Interest. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *