Migrating Existing Packages to a new location using Repository Migration Tool
Overview:
The Repository migration tool is used to move packages from one repository / machine to another repository / machine. The tool used in this process updates the necessary database information, copies the packages, and then verifies the package data.
To change the repository location for existing packages, use the repository migration tool. This tool will be useful when the available space is less in the repository machine after we upload the packages.
Basic Information about the Tool:
- All the packages can be migrated using MigrateData.cmd file placed under <Installdir>/StreamletEngine/bin folder
- Type the file name on command prompt at <InstallDir>/StreamletEngine/bin path to view syntax / usage
- Provide appropriate arguments to this command to migrate the existing packages
Note: Corrupted Packages cannot be migrated using this tool
Syntax:
MigrateData.cmd <Options> [Note: options must be in order]
Options:
| Options |
Descriptions |
| Host |
Specify Streamlet Engine hostname or IP. |
| Port |
Specify Streamlet Engine/DA port. By default 9832.
If this port is non-default, you must specify IP and port explicitly. |
| Source |
Specify the source location in double quotes |
| Target |
Specify the target location in double quotes |
| Pkg.Count | All |
Specify All or count of pkgs to be moved |
| Force to Move |
Yes | No . If Yes means system process will be down |
| -a |
Move Packages manually & update its location in database. (If migration is failed. Use this option) |
Command Format:
MigrateData <source> <target> <pkg count | All>
Where "target" machine should be accessible from the "source" machine.
Note: Use "Net Use" command to connect to the "target" machine before trying to migrate the packages.
Syntax: net use [\\computername] /user:username password
Example: net use \\192.168.1.1/user:username password
Sample Repository Migration:
Let us take this migration tool to migrate the existing packages from the default repository location to another local drive in the Repository machine.
Execute the following command:
MigrateData.cmd "C:\Symantec\Workspace Streaming\Server\packageRepo" "D:\Repo" ALL
After migration is completed, it will display detailed report to show no. of packages moved / failed.
Sample migration screen is shown in the Fig 1.
Fig 1: Sample Migration Screen
Refer log file: 'PackageMigrationTool.log' placed under <InstallDir>\Workspace streaming\Server folder for trouble shooting.
Note:
Repository migration tool supports local file paths as well as UNC paths.
While migrating the existing packages to UNC path make sure that new path is accessible by SWS server. After the packages got migrated to UNC path open service manager window and change the access right of "Awe StreamletEngine" from 'Local account' to 'This Account' in Logon Tab window. Make sure, the given username/password has read/write privileges to the new repository path.
Repository Information after using the Migration Tool:
Repository Information in the streaming console before using this tool is shown in the Fig 2.
Fig 2: Repository Information in the streaming console.
After we migrate the existing packages to new repository location, a new entry will be added in the Repository Information tab.
Repository Information in the streaming console after using this tool is shown in the Fig 3.
Fig 3: Repository Information in the streaming console after migrating the packages.
Note:
Repository migration tool is used to change the repository location for existing packages only. But the new packages which are uploaded will be stored in the default path as specified in the console.
If you want to change this default path, click Repository Location tab in the Preferences link and update the default location.