Help Center>Foundation Help

Applies to:

  • Winshuttle Foundation

Migrating Winshuttle Workflow Data using SVMigrate

Back to

The SVMigrate tool helps you migrate Workflow data from one system to another. The tool can also be used to restore SharePoint backups.

Migrating data consists of 4 distinct phases:

  1. Create an XML file
  2. Backup SharePoint Data
  3. Clear the cache
  4. Update the Root Site

The following set of short procedures requires the use of two command line tools:

  • STSadm (Windows SharePoint Services 3)
  • SVMigrate (a Winshuttle Workflow tool)

    Note: The SVMigrate tool must be run within the context of the Workflow Administrator. (See Account Requirements for more information about the Workflow Administrator account.)

Create an XML file

Back to top
  1. If you are migrating your data to a different path, create an XML file similar to the following. Open NotePad or any text editor and copy the following lines. Substituting your old and new site locations as appropriate. The old and new are indicated in bold in the example.

    If you are not changing the path, continue to step 2.

    <?xml version="1.0" encoding="utf-16"?>

    <MapPack xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" (see http://www.w3.org/2001/xmlschema-instance - http://www.w3.org/2001/xmlschema-instance) xmlns:xsd="http://www.w3.org/2001/XMLSchema" (see http://www.w3.org/2001/xmlschema - http://www.w3.org/2001/xmlschema)>

    <SiteToSites>

    <anyType xsi:type="SiteToSite">

    <OriginalSite>/Departments/HR</OriginalSite>

    <NewSite>/sites/sharevis/HR</NewSite>

    </anyType>

    </SiteToSites>

    </MapPack>

  2. On the source site, Back up the ShareVis database using the SQL Server backup. Right-click on the ShareVis database. Under the Tasks vategory, click Backup.

Backup SharePoint Data

Back to top
  1. Run the following command to backup the SharePoint data:

    stsadm -o export -url http://server/site -filename svbackup.back
  2. Run the following command to create the Workflow mapping data:

    svmigrate -w http://server/site -f svbackup.svb

  3. On the destination server, restore the ShareVis database.
  4. Create the site http://newserver/site without a template applied. (Use either stsadm or the Web Interface to create the site without picking a template when prompted.)
  5. Run the following command:

    stsadm -o import -url http://server/site -filename svbackup.back
  6. Run one of the following commands, depending on whether or not you are moving the path.
    • If you are moving the path, run the following command. Replace <filename> with the name of the XML file you created in step 1 .

      svmigrate -r -w http://newserver/site -f svbackup.svb -m <Filename>

      Note: If you are using Foundation 11.1.1, the -m parameter in the command above is mandatory.


    • If you are not moving the path, run the following command:

      svmigrate -r -w http://newserver/site -f svbackup.svb

  7. Run the IISRESET command on the destination server.

Clear the cache

Back to top
  1. On each Web Front End server, open a command prompt (with Administrative privileges). Or, if you are running Workflow 10.6 or higher, open the Workflow Command Prompt located in All Programs under Winshuttle.
  2. Run the following SVAdm command:

    svadm.exe -o clearcache

If process strings aren't being replaced as expected during the svmigrate procedure, then do the following:

  1. On each Web Front End server, navigate to c:\program files\sharevis\temp
  2. Delete all contents of the temp folder

Update the Root Site

Back to top

If you are having trouble creating logs, it is possible that no root site was created when the installation Wizard configured Workflow. If this happens, then the wizard automatically configures Workflow to the default root site collection.

Updating the URL to the proper root site:

  1. Open the SVConfigurator.

    See Changing Workflow Settings and the SVConfigurator Options Table for more information about SVConfigurator.

  2. Load the desired root site.
  3. In the Add section, enter the key LocalURL and set the value to the working site collection.
  4. Click Save to update.
  5. Perform an IISRESET.
  6. Test the logging capability again.