The Following strategies are available in Sharepoint (Moss 2007) to migrate the Content.
I. Using SQL
II. Using STSADM BACKUP/RESTORE
III. Using STSADM EXPORT and IMPORT
IV. Using Content Migration API (SPIMPORT or SPEXPORT Classes )
V. Using Sharepoint Central Admin
VI. Using Sharepoint Designer
Please find the Explanation for each of these strategies.
USING SQL
Using SQL, Backup the SQL Content Databases which are required and Restore them to a new databases in the SQL and attach these databases to the new application.
(Briefly we can say that take your content db ‘Offline’ using the Central admin. Take the content database offline in SQL Studio (Take Offline context menu item). Copy your database mdf and ldf files to the new machine (the destination machine). Attach the copies on the new SQL server using SQL Studio. Add the copied content DB to the Web Application on the new machine using the Central Admin on the new web server.)
STEPS:
1) Find the content Database
These are listed under Central Admin->Application Management->Site Collection List
2) Backup the content database
You could alternatively detach it, and copy it. Just doing a backup in SQL Server 2005 Management studio is easier.
3) Restore content database to new server
Copy the BAK file to new server. Create an empty DB in Management Studio, restore from backup, you may need to change an option in the “options” tab
of the restore dialog to get it to work. (Overwrite db).
4) Create Web App on new Server
Central Admin->Application Management->Create or extend Web App->Create New Web App.
5) Associate restored DB with new Web App
Central Admin->Application Management->
SharePoint Web Application Management->Content Databases->
Remove Content Database from your new web app.
Now use STSADM to add restored DB to this web app
c:\program files\common files\microsoft shared\web server extentions\12\bin on new server is where you can find the STSADM.
run this command from there.
stsadm -o addcontentdb -url http://yourwebapp:port -databasename yourcontentdb -databaseserver yoursqlserver
6) Run ISSRESET from command prompt.
MORE INFO on ATTACHING a Database and Detaching a Database
http://blogs.technet.com/corybu/archive/2007/06/01/detaching-databases-in-moss-2007-environments.aspx
http://blogs.msdn.com/sharepoint/archive/2007/04/13/stsadm-operations-published.aspx
http://blogs.technet.com/corybu/archive/2007/06/21/sharepoint-site-migration-and-balancing-growth.aspx
- External SQL Server Database Move Example
Database shipping
To migrate your content database from 1 SQL Server to another there are a few choices, your choice will depend on how much downtime you are willing to take.
First option being you can setup SQL Log shipping,
Stsadm –o preparetomove –contentdb SQLServerA:demo_content_1
Stsadm –o deletecontentdb –url http://demo –databasename demo_content_1 –databaseserver SQLServerA
At this point you would perform the final cutover on your shipped database to SQLServerB
Then finish with
Stsadm –o addcontentdb –url http://demo –databasename demo_content_1 –databaseserver SQLServerB
Copy Method(high impact)
Your other option would be to simply detach the database from SQL and copy the .mdf and .ldf to the new SQL server. While in transit your users will get a
generic “Cannot connect to content database” error when visiting their site. Following the copy you would perform the following on your web front end.
Stsadm –o preparetomove –contentdb SQLServerA:demo_content_1
Stsadm –o deletecontentdb –url http://demo –databasename demo_content_1 –databaseserver SQLServerA
Stsadm –o addcontentdb –url http://demo –databasename demo_content_1 –databaseserver SQLServerB
USING STSADM Backup/ Restore
Using STSADM BACKUP and RESTORE backup the complete WEB application and RESTORE it in the new Farm
When you back up by using the Stsadm command-line tool, you can back up individual aspects of your SharePoint Products and Technologies deployment. For example, you can back up an individual site collection or you can back up the entire farm.
To export sites from your SharePoint Products and Technologies deployment, you use the following Stsadm command.
Backup
Stsadm –o export –url <URL> -filename <FileName>.cmp
To back up a site collection, you must use the following stsadm command.
stsadm –o backup –url <URL of the site collection> -filename <Name of the backup file>
To back up an individual database, Web application, or the entire farm, you can use the following Stsadm command.
stsadm –o backup –directory <UNC path or local drive> -backupmethod <Full or Differential>
Restore
To import sites to your SharePoint Products and Technologies deployment, you use the following Stsadm command.
Stsadm –o import –url <URL> -filename <FileName>.cmp
To restore a site collection, you must use the following Stsadm command.
stsadm –o restore –url <URL of the site collection> -filename <Name of the backup file>
To restore an entire farm you can use the following Stsadm command.
stsadm –o restore –directory <UNC path or local drive> -restoremethod <overwrite or new>
So what are the types of backups we can perform. There are two types:
Full backup
Differential backup
Before you create a differential backup however, you need to at least perform a full backup for the first time.
USING STSADM EXPORT / IMPORT
Using STSADM EXPORT and IMPORT we can Export the complete web application and Import it in the Other Farm.
The command-line tool STSADM.exe supports only basic import and export operations and is only useful when importing or exporting entire SharePoint Web
sites or when reparenting a Web site. Content migrated using this tool will not retain object GUIDs. Note that you cannot use this utility to import or export individual items or lists.
stsadm.exe -o export
-url <URL to be exported>
-filename <export file name>
[-overwrite]
[-includeusersecurity]
[-haltonwarning]
[-haltonfatalerror]
[-nologfile]
[-versions <1-4>
1 - Last major version for files and list items (default)
2 - The current version, either the last major or the last minor
3 - Last major and last minor version for files and list items
4 - All versions for files and list items]
[-cabsize <integer from 1-1024 megabytes>]
[-quiet]
You must use the -includeusersecurity parameter in order to preserve time stamps, security information, and user data.
stsadm.exe -o import
-url <URL to import to>
-filename <import file name>
[-includeusersecurity]
[-haltonwarning]
[-haltonfatalerror]
[-nologfile]
[-updateversions <1-4>
1 - Add new versions to the current file (default)
2 - Overwrite the file and all its versions (delete then insert)
3 - Ignore the file
4 - Terminate with conflicts]
[-quiet]
More info
http://farhanfaiz.wordpress.com/2008/02/07/mossback-up-and-restore-site-collection-sites-using-stsadm-utility-export-import/
http://msdn.microsoft.com/en-us/library/aa979099.aspx
Using Content Migration Sharepoint API ( SPEXPORT / SPIMPORT)
Create a New Webapplication and
- Move all the Document Libraries from source to destination Using Content Deployment Migration ( SPEXPORT and SPIMPORT)\
The content import/export feature of the deployment object model allows you to export not only Web site content but also existing dependencies, like security features, user roles, versioning data, workflows, and other metadata.
The Microsoft.SharePoint.Deployment object model is designed to work with data ranging from an entire Web site to a single item in a list or library. The import/export features of the Microsoft.SharePoint.Deployment object model uses two key objects: Microsoft.SharePoint.Deployment.SPImport and Microsoft.SharePoint.Deployment.SPExport.
However, before you run the import or export operations using these objects, you must first specify your import or export settings using Microsoft.SharePoint.Deployment.SPImportSettings and Microsoft.SharePoint.Deployment.SPExportSettings objects. Then you simply call the Run() method on the SPImport or SPExport object, as appropriate.
You can get more info here
http://msdn.microsoft.com/en-us/library/aa979099.aspx
USING Sharepoint Central Administration ( Backup / Restore)
Using Central ADMIN Backup the Complete Farm and Restore the Complete Farm in the New Farm
More info
http://www.sharepointbeagle.com/channels/administration/Pages/MOSS2007BackupandRestoreOperations.aspx
Using Sharepoint Designer
We can find more info about this here
http://office.microsoft.com/en-us/sharepointdesigner/HA100699391033.aspx
I. Using SQL
II. Using STSADM BACKUP/RESTORE
III. Using STSADM EXPORT and IMPORT
IV. Using Content Migration API (SPIMPORT or SPEXPORT Classes )
V. Using Sharepoint Central Admin
VI. Using Sharepoint Designer
Please find the Explanation for each of these strategies.
USING SQL
Using SQL, Backup the SQL Content Databases which are required and Restore them to a new databases in the SQL and attach these databases to the new application.
(Briefly we can say that take your content db ‘Offline’ using the Central admin. Take the content database offline in SQL Studio (Take Offline context menu item). Copy your database mdf and ldf files to the new machine (the destination machine). Attach the copies on the new SQL server using SQL Studio. Add the copied content DB to the Web Application on the new machine using the Central Admin on the new web server.)
STEPS:
1) Find the content Database
These are listed under Central Admin->Application Management->Site Collection List
2) Backup the content database
You could alternatively detach it, and copy it. Just doing a backup in SQL Server 2005 Management studio is easier.
3) Restore content database to new server
Copy the BAK file to new server. Create an empty DB in Management Studio, restore from backup, you may need to change an option in the “options” tab
of the restore dialog to get it to work. (Overwrite db).
4) Create Web App on new Server
Central Admin->Application Management->Create or extend Web App->Create New Web App.
5) Associate restored DB with new Web App
Central Admin->Application Management->
SharePoint Web Application Management->Content Databases->
Remove Content Database from your new web app.
Now use STSADM to add restored DB to this web app
c:\program files\common files\microsoft shared\web server extentions\12\bin on new server is where you can find the STSADM.
run this command from there.
stsadm -o addcontentdb -url http://yourwebapp:port -databasename yourcontentdb -databaseserver yoursqlserver
6) Run ISSRESET from command prompt.
MORE INFO on ATTACHING a Database and Detaching a Database
http://blogs.technet.com/corybu/archive/2007/06/01/detaching-databases-in-moss-2007-environments.aspx
http://blogs.msdn.com/sharepoint/archive/2007/04/13/stsadm-operations-published.aspx
http://blogs.technet.com/corybu/archive/2007/06/21/sharepoint-site-migration-and-balancing-growth.aspx
- External SQL Server Database Move Example
Database shipping
To migrate your content database from 1 SQL Server to another there are a few choices, your choice will depend on how much downtime you are willing to take.
First option being you can setup SQL Log shipping,
Stsadm –o preparetomove –contentdb SQLServerA:demo_content_1
Stsadm –o deletecontentdb –url http://demo –databasename demo_content_1 –databaseserver SQLServerA
At this point you would perform the final cutover on your shipped database to SQLServerB
Then finish with
Stsadm –o addcontentdb –url http://demo –databasename demo_content_1 –databaseserver SQLServerB
Copy Method(high impact)
Your other option would be to simply detach the database from SQL and copy the .mdf and .ldf to the new SQL server. While in transit your users will get a
generic “Cannot connect to content database” error when visiting their site. Following the copy you would perform the following on your web front end.
Stsadm –o preparetomove –contentdb SQLServerA:demo_content_1
Stsadm –o deletecontentdb –url http://demo –databasename demo_content_1 –databaseserver SQLServerA
Stsadm –o addcontentdb –url http://demo –databasename demo_content_1 –databaseserver SQLServerB
USING STSADM Backup/ Restore
Using STSADM BACKUP and RESTORE backup the complete WEB application and RESTORE it in the new Farm
When you back up by using the Stsadm command-line tool, you can back up individual aspects of your SharePoint Products and Technologies deployment. For example, you can back up an individual site collection or you can back up the entire farm.
To export sites from your SharePoint Products and Technologies deployment, you use the following Stsadm command.
Backup
Stsadm –o export –url <URL> -filename <FileName>.cmp
To back up a site collection, you must use the following stsadm command.
stsadm –o backup –url <URL of the site collection> -filename <Name of the backup file>
To back up an individual database, Web application, or the entire farm, you can use the following Stsadm command.
stsadm –o backup –directory <UNC path or local drive> -backupmethod <Full or Differential>
Restore
To import sites to your SharePoint Products and Technologies deployment, you use the following Stsadm command.
Stsadm –o import –url <URL> -filename <FileName>.cmp
To restore a site collection, you must use the following Stsadm command.
stsadm –o restore –url <URL of the site collection> -filename <Name of the backup file>
To restore an entire farm you can use the following Stsadm command.
stsadm –o restore –directory <UNC path or local drive> -restoremethod <overwrite or new>
So what are the types of backups we can perform. There are two types:
Full backup
Differential backup
Before you create a differential backup however, you need to at least perform a full backup for the first time.
USING STSADM EXPORT / IMPORT
Using STSADM EXPORT and IMPORT we can Export the complete web application and Import it in the Other Farm.
The command-line tool STSADM.exe supports only basic import and export operations and is only useful when importing or exporting entire SharePoint Web
sites or when reparenting a Web site. Content migrated using this tool will not retain object GUIDs. Note that you cannot use this utility to import or export individual items or lists.
stsadm.exe -o export
-url <URL to be exported>
-filename <export file name>
[-overwrite]
[-includeusersecurity]
[-haltonwarning]
[-haltonfatalerror]
[-nologfile]
[-versions <1-4>
1 - Last major version for files and list items (default)
2 - The current version, either the last major or the last minor
3 - Last major and last minor version for files and list items
4 - All versions for files and list items]
[-cabsize <integer from 1-1024 megabytes>]
[-quiet]
You must use the -includeusersecurity parameter in order to preserve time stamps, security information, and user data.
stsadm.exe -o import
-url <URL to import to>
-filename <import file name>
[-includeusersecurity]
[-haltonwarning]
[-haltonfatalerror]
[-nologfile]
[-updateversions <1-4>
1 - Add new versions to the current file (default)
2 - Overwrite the file and all its versions (delete then insert)
3 - Ignore the file
4 - Terminate with conflicts]
[-quiet]
More info
http://farhanfaiz.wordpress.com/2008/02/07/mossback-up-and-restore-site-collection-sites-using-stsadm-utility-export-import/
http://msdn.microsoft.com/en-us/library/aa979099.aspx
Using Content Migration Sharepoint API ( SPEXPORT / SPIMPORT)
Create a New Webapplication and
- Move all the Document Libraries from source to destination Using Content Deployment Migration ( SPEXPORT and SPIMPORT)\
The content import/export feature of the deployment object model allows you to export not only Web site content but also existing dependencies, like security features, user roles, versioning data, workflows, and other metadata.
The Microsoft.SharePoint.Deployment object model is designed to work with data ranging from an entire Web site to a single item in a list or library. The import/export features of the Microsoft.SharePoint.Deployment object model uses two key objects: Microsoft.SharePoint.Deployment.SPImport and Microsoft.SharePoint.Deployment.SPExport.
However, before you run the import or export operations using these objects, you must first specify your import or export settings using Microsoft.SharePoint.Deployment.SPImportSettings and Microsoft.SharePoint.Deployment.SPExportSettings objects. Then you simply call the Run() method on the SPImport or SPExport object, as appropriate.
You can get more info here
http://msdn.microsoft.com/en-us/library/aa979099.aspx
USING Sharepoint Central Administration ( Backup / Restore)
Using Central ADMIN Backup the Complete Farm and Restore the Complete Farm in the New Farm
More info
http://www.sharepointbeagle.com/channels/administration/Pages/MOSS2007BackupandRestoreOperations.aspx
Using Sharepoint Designer
We can find more info about this here
http://office.microsoft.com/en-us/sharepointdesigner/HA100699391033.aspx
