Moving a Mount Path

Supported Mount Paths

A disk library with multiple disk devices. For example, a disk library Lib1 with disk devices Device_1 and Device_2.
Multiple disk devices pointing to the same path on the same disk library or on multiple libraries. For example:
- Disk devices Device_1 and Device_2 pointing to path D:\MP1 on disk library Lib1.
- Disk devices Device_1 and Device_2 pointing to path D:\MP1 on disk library Lib1 and Lib2.

Mount paths on HyperScale nodes cannot be moved.
Mount paths cannot be moved across 2 different libraries. For example, from Magnetic_Lib1 to Magnetic_Lib2.
A disk device configured as multiple mount paths on the same library or on multiple libraries cannot be moved. For example:
- Path D:\MP1 and D:\MP1 on a disk library Lib1 associated with disk device Device_1
- Path D:\MP1 on disk library Lib1 and path D:\MP1 on disk library Lib2 associated with disk device Device_1

Refer the following support matrix to verify MediaAgent version, platform, paths that support moving mount path:

Cross-platform move mount path operation is not supported. You cannot move a mount path from Windows to Linux or from Linux to Windows.
Cross-version move mount path operation is not supported. You cannot move a mount path from V10 MediaAgent to a V11 MediaAgent or from V11 MediaAgent to V10 MediaAgent.
You cannot run move mount path operations on V9 MediaAgents.
To avoid slow data transfer, do not move mount paths between UNC paths.
You can move a mount path across V10 MediaAgents that are pointing to V11 CommServe.
You cannot move a mount path shared using the Data Server-IP, SAN or iSCSI to a UNC destination path.
If you move from a local mount path to a UNC mount path, and the UNC mount path does not support sparse files, then the data will grow in size.
On Linux, sparse files are not supported.