Update Mounts
The system starts using the content in the target system after the mounts are updated. Perform the following steps to update the mounts:
1. Prepare the input file.
2. Update the mounts.
Prerequisite:
• Azure storage account is configured with Windchill.
• Windchill Server is up and running.
Prepare the Input File
Use the command line utility, PrepareInputDataForMountMigrationTool, to generate a report in the CSV format. You can then use this CSV report as an input to the MountMigrationTool for updating the mounts. The report is stored in <Windchill>/logs/MountMigration/ directory. This report contains the following information:
• Root Folders — A list of all the available root folders.
• Source Host
• Source Mount Path
• Source Mount Type
• Target Mount Path
• Target Mount Type — By default, the target mount type is azureBlob.
To list all possible command line options, run the following command from the windchill shell::
windchill wt.fv.tools.datamigration.PrepareInputDataForMountMigrationTool mount -h
Following is the list of valid arguments:
• -h = <help> — Help
• -u = <username> — Administrator user name
• -p = <password> — Administrator password
• -v = <verbose> — Runs the utility in debug mode
• -c = <container> — Target container name
• -a = <storageAccount> — Target storage account name
• -t = <mountType> — Target mount type (default mount type is azureBlob)
To generate the report, run the following command from the windchill shell:
windchill wt.fv.tools.datamigration.PrepareInputDataForMountMigrationTool mount -u <userName> -p <password> -t <mountType>
The target storage account name and target container name are optional arguments. To migrate mounts from one Azure Storage to another Azure Storage, provide the target storage account name and target container name using the -a and -c arguments. If the source mount type is azureBlob, the tool automatically generates the target mount path based on the target storage account name, target container name, and with the same directory structure as that of the source mount path.
If you are migrating mounts from file-based vaults or Amazon S3 storage to Azure Storage, enter the target mount path manually in the CSV report. In this case, the tool does not generate the target mount path automatically.
 |
• The vault directory structure in source Azure Storage and target Azure Storage should be the same to generate the correct target mount paths using -a and -c arguments. If the directory structure in not same, the target mount path must be entered manually.
• If a root folder is found with property AutoFolderCreation=false, an error is displayed on the windchill shell. To resolve this error, execute wt.fv.tools.FolderToRootFolderConverter tool.
• If you are migrating mounts from file-based vaults to other file-based vaults, enter the target mount path manually in the CSV report. In this case, the tool does not generate the target mount path automatically.
|
Update the Mounts
You can use the CSV report generated in the previous step as an input file to update mounts using the MountMigrationTool.
To list all possible command line options, run the following command:
windchill wt.fv.tools.datamigration.MountMigrationTool migrate -u <username> -p <password> -h
Following is the list of valid arguments:
• -h = <help> — Help
• -u = <username> — Administrator user name
• -p = <password> — Administrator password
• -v = <verbose> — Runs the utility in debug mode
• -r = <rootFolderName> — Name of the root folder.
• -t = <newMountType> — Mount type. Valid values are amazonS3 and azureBlob.
• -m = <newMountPath> — Mount path on Amazon S3 or Blob Storage.
• -i = <inputFile> — Input CSV file path.
Run the following command from the windchill shell to change the mount type and mount path for all root folders simultaneously:
windchill wt.fv.tools.datamigration.MountMigrationTool migrate -u <username> -p <password> -i <inputFile>
Run the following command from the windchill shell to change the mount type and mount path for one root folder at a time:
windchill wt.fv.tools.datamigration.MountMigrationTool migrate -u <username> -p <password> -r <RootFolder name> -m <mount path on Azure Blob Storage Container> -t azureBlob
For example:
windchill wt.fv.tools.datamigration.MountMigrationTool migrate -u <username> -p <password> -r defaultuploadfolder1 -m storageaccountname/testcontainer/defaultup -t azureBlob
After running the utility with -i argument, the summary displays the following status:
• Successful — Name of the root folders successfully migrated.
• Failed — Name of the root folders failed to migrate.
• Skipped — Name of the root folders skipped, as they were successfully migrated in the previous run.
You can also view the mount migration status in the input CSV file after the utility is run. You can run the MountMigrationTool multiple times with same input CSV file.
|
|
During migration, if an existing root folder has a mirror root mount path in the input file, only the primary path is processed, and the secondary paths are discarded.
|
As an alternative to the command line tool, you can unmount the root folder and mount it for Azure Blob from the Vault Configuration user interface. Note that while performing these operations from user interface, users must not access content in the root folder. If you are migrating a single mount using -r, -t, and -m arguments, remove the migrated root folder’s Read Only flag from vault configuration user interface. The newly created root folder in the Prepare system for migration section may contain files that are not required to be moved out of the root folder as part of this vault migration process.
After the vault migration process is complete, reestablish the revaulting and content replication schedules, and configure the property wt.fv.faultTolerantVaultsAutoRestore.