You can migrate the Transfer Server repository to a new location if your current disk drive is running out of space.
All View Transfer Server instances that are associated with a View Connection Server must be in maintenance mode before you can migrate the Transfer Server repository.
If you have multiple View Transfer Server instances, migrate the Transfer Server repository to a network-shared drive. Other View Transfer Server instances cannot access a Transfer Server repository that is configured on a local drive on one View Transfer Server instance.
■
|
Verify that View Transfer Server is installed and configured. See Add View Transfer Server to View Manager. |
■
|
Do not publish packages in the Transfer Server repository while you migrate the repository. If a package is published in the current repository after you start copying the repository files to the new location, the package might not be copied to the new location. To enforce this prerequisite, you could put View Transfer Server in maintenance mode before you manually copy the repository, but that approach would extend the downtime for data transfers while the repository files are copied. Instead, this procedure directs you to copy the repository files before you put View Transfer Server in maintenance mode. This approach minimizes the time that View Transfer Server is unavailable. |