in

SharePoint Blogs

The Best Place for SharePoint-related Blogs

akila's blog

July 2006 - Posts

  • Reply : I have a Sharepoint set up on one server and want to transfer it to another server on a seperate host. Do you have any idea of how to accomplish this?

    Someone had asked me how to migrate Sharepoint data from one server to another. Here's what needs to be done:

    1. Take a backup of the Content database.
    2. Install Windows Sharepoint Services on the new server and extend the virtual server.
    3. Now create a database in the new server, and restore the backup of the old content database.
    4. Go to central Administration -> Configure Virtual Server Settings -> Select the Virtual Server -> Under Virtual Server Management -> Manage Content Databases.
    5. In the manage content database page, enter the database server, name, username and password and click OK.
    6. Now the restored Content Database is added to the Virtual Server.
    7. If requierd, you can delete the content database created at the time of extending the virtual server.
    8. All the sites will be restored back as it was in the old WSS server.

    Now the sites are restored and you can use the new WSS as it was previously.

    //Akila

  • No content databases are available for restoring this site collection. Create a new content database and then try the restore operation again.

    When you try to restore the backup of a site collection multiple times to the same content database using stsadm, you may get the error:

    "No content databases are available for restoring this site collection. Create a new content database and then try the restore operation again."

    In the Microsoft Site its has been mentioned that to restore the same site collection multiple times, new content databases have to be created. This is because, the globally-unique identifiers (GUID) for lists are preserved in the backup file and reused during restore, but the content database requires list GUIDs to be unique. Therefore, you cannot restore a site collection twice to the same content database, and must instead use a different content database.

    There are two workarounds for this issue:

    1. Make the site you want to restore multiple times, as a template and apply the template to new sites, so that all the data in the template is also carried over to the new site.

    2. If you don't want to make the site as a template, then follow the steps to restore into the same content database.
       (i). Create the site (destination site, into which you want to restore the source site collection) using the Central Administration Page -> Create Top Level Website. Do not apply any template to this site.
       (ii). Backup the source site as a FWP (Frontpage Web Package) using the SMigrate Tool.
       (iii). Now restore this backedup site to the new site (created without applying template) using SMigrate Tool. The site collection is restored on to the same content database.

       One thing to be noted here is that the Site Settings are not restored and you have to add the users to the site manaully (whom you want to access the site), whereas with stsadm restoration, the users are also restored. Still, instead of creating new content database each time you want to restore the same site, adding users sounds much better. Doesn't it?

    //Akila.


Need SharePoint Training? Attend a SharePoint Bootcamp!

Posts (c) their respective authors. Everything else (c) 2007 SharePoint Experts