feedburner

Subscribe

View Venkat Varkala's profile on LinkedIn

STSADMIN : Backup/Restore vs. Import/Export

Labels:

I have been asked by many about the differences between Backup/Restore vs. Import/Export operations, they both really serve very different purpose.


Backup/Restore Import/Export

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

  2. There is no Default File Extension for back up files

  3. Supports "Full" and "Differential" back up. If "overwrite" option is selected while restoring it overwrites entire SiteCollection

  4. Supports UNC path to save/restore backup files.

  5. Backup of Site Collection can be tracked by stsadm -o backuphistory operation

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

  2. Default file Extension (if not mentioned) ".cmp"

  3. Provides "versions" option to control migrate/overwrite files in site

  4. Backup files should be copied to server

  5. Sites/SiteCollections would not track export/Import history

Syntax

For site collection backup

stsadm -o backup

   -url <URL name>

   -filename <file name>

   [-overwrite]

 

For catastrophic backup

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 site collection restore
stsadm -o restore

   -url <URL name>

   -filename <file name>

   [-hostheaderwebapplicationurl] <Web application URL>

   [-overwrite]

 

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]



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]


Useful Links

http://technet2.microsoft.com/Office/f/?en-us/library/16a7e571-3531-4a4e-baa7-f348a9f9d1d11033.mspx

http://blogs.msdn.com/joelo/archive/2006/10/16/what-happened-to-smigrate-exe-what-if-i-only-want-to-upgrade-one-site-what-can-i-do-now-with-stsadm-exe.aspx

http://blah.winsmarts.com/2007-10-Backup_and_Restore_Strategies_in_MOSS_2007.aspx

http://blogs.msdn.com/joelo/archive/2007/03/09/sharepoint-backup-restore-high-availability-and-disaster-recovery.aspx

3 comments:
gravatar
Anonymous said...
December 14, 2009 at 10:43 PM  

stsadm import always duplicate my data.. there is no database overwrite option available with Import.. can you please guide me the any other possible solution to deploy my subsite to production server...

gravatar
Ashish said...
March 31, 2011 at 3:05 PM  

Great post. It was very crisp and clear, thank u :)

gravatar
Ganesh said...
August 31, 2011 at 1:18 AM  

Still it does not explain what is the major difference. Since I am new to shrepoint, it is confusing why there are so many options to do the same job.

Post a Comment