# Moving a Backup Location to a New Location

You can move a backup location from one location to a new location on the same MediaAgent or another MediaAgent. The destination path can be a local path or a network path.

When you move a backup location, deduplicated and non-deduplicated data that resides on the source backup location is moved to the destination backup location.

You can move a backup location to a new location in the following cases:

- You want to move to another location that has more storage capacity.

- You want to move to a faster disk media.

A move backup location operation involves the following steps:

- Disables the pruning of data present on the source backup location.

- During phase 1, the software copies the full volumes from the source backup location folder to the destination device. The software allows the operations like backup, restore, auxiliary copy, data verification, synthetic full and deduplication database (DDB) reconstruction.

- During phase 2, the software suspends backup and other operations for the source backup location and copies the active volumes from the source backup location folder to the destination device.

- Enables the pruning of data.

- Resumes backup and other operations that are pending.

Notes

- If the source backup location is a consolidated backup location, the software initiates multiple move backup location operations to move each backup location in the consolidated backup location.

- When you move a backup location between two Linux MediaAgents, the move backup location operation does not support drill hole capability. If you move a backup location with drill hole capability, the backup location will consume more space after the move.

- Any backup locations that failed to move will remain on the source backup location.

- Do NOT add MediaAgent to the backup location while the move backup location operation is in progress. Otherwise, you will end up with duplicate MediaAgent on the backup location.

## Before You Begin

- Review the Move Backup Location - Support page.

- Ensure that the destination backup location is not a sub folder under the source backup location.

- Do not move the backup location to the software installation directory.

- The move backup location operation overwrites the destination backup location. Therefore, ensure that the destination backup location is an empty folder.

- Ensure that the destination backup location folder has at least 5% more free space than the space consumed by the source backup location.

- Ensure that the source backup location has backup data.

- Ensure that the source MediaAgent and the destination MediaAgent are online and accessible.

- The user must have the Library Management permission or Library Administration permission on the library that hosts the backup location.

- Verify that the backup location is not shared with the destination MediaAgent.

## Procedure

1. From the Command Center navigation pane, go to Manage > Storage > Disk.

   The Disk page appears.

2. Click the disk storage.

   The disk storage page appears.

3. Under the Backup Locations section, for the backup location that you want to move, click the Actions button , and then click Move backup location.

   The Move backup location dialog box appears.

4. Under Source, from MediaAgent list, select the source MediaAgent.

   In the MediaAgent list, more than one MediaAgent appears if the backup location is shared between MediaAgents.

5. Under Destination, select Move to new location option.

6. From MediaAgent list, select the MediaAgent to which you want to move the backup location.

   For help with the entering information in the fields that appear, review the additional information and notes below.

7. Click Save.

## Result

- After the completion of a move backup location job, the space on the source backup location is freed up after 24 hours (one day).

- If the backup location move job fails or is killed, you must manually clean the data that was copied to the destination backup location.

## What to Do Next

- Verify that the destination device is online and accessible after the move.

- Perform a disaster recovery backup. For instructions, see Performing a Disaster Recovery Backup.

- If the source backup location or the destination backup location is a network path, the software automatically updates the credentials for the shared MediaAgents with the credentials from the new location. For other MediaAgents (with local or UNIX paths) that share the source backup location, you must modify the path to the new location. For instructions, see Modifying a Disk Access Path.

## Additional Information

When you try to move to a new backup location, you need to enter the shared paths if the backup location need to be shared with other MediaAgents after the creation.

### Scenario 1: Single Windows MediaAgent

When only one Windows MediaAgent is associated with the disk storage:

#### Local Backup Location

The following field is displayed:

- Backup Location

  For example: `E:\Backups`

#### Network Backup Location

The following fields are displayed:

- Credential

- Backup Location

  For example: `\\WinMA1\Backups`

Shared path fields are not displayed.

### Scenario 2: Multiple Windows MediaAgents

When multiple Windows MediaAgents are associated with the disk storage and a Windows MediaAgent is selected as the host:

#### Local Backup Location

The following fields are displayed:

- Backup Location

  For example: `E:\Backups`

- Windows Shared Path

  - Credential

  - Path

    Format: `\\<hostMediaAgent>\Backups`

    For example: `\\WinMA1\Backups`

#### Network

- Credential

- Backup Location

  Format: `\\StorageMachineName\Backups`

  For example: `\\WinMA2\Backups`

All Windows MediaAgents except the selected host MediaAgent use the Windows shared path to access the backup location.

### Scenario 3: Unix-Only MediaAgents (one or multiple)

When only Unix MediaAgents are associated with the disk storage and a Unix MediaAgent is selected as the host:

#### Local Backup Location

The following field is displayed:

- Backup Location

  For example: `/MountedLibrary/folder1`

No additional shared path configuration is required because the backup location path is entered from the perspective of the selected Unix host.

### Scenario 4: Mixed Windows and Unix MediaAgents (Windows Host)

When both Windows and Unix MediaAgents are associated with the disk storage and a Windows MediaAgent is selected as the host:

#### Local Backup Location

The following fields are displayed:

- Backup Location

  For example: `E:\Backups`

- Windows Shared Path (appears when there is more than one Windows MediaAgent)

  - Credential

  - Path

    For example: `\\WinMA1\Backups`

- Unix Shared Path

  - Path: This is the path where Windows shared path is mounted that allows access to Unix MediaAgents.

    For example: `/MountedLibrary/folder1`

The Windows shared path is used by the additional Windows MediaAgents.

#### Network

- Credential

- Backup Location

  Format: `\\StorageMachineName\Backups`

  For example: `\\WinMA2\Backups`

- Unix Shared Path

  - Path: This is the path where Windows shared path is mounted that allows access to Unix MediaAgents.

    For example: `/MountedLibrary/folder1`

### Scenario 5: Mixed Windows and Unix MediaAgents (Unix Host)

When both Windows and Unix MediaAgents are associated with the disk storage and a Unix MediaAgent is selected as the host:

The following fields are displayed:

- Backup Location

  For example: `E:\Backups`

- Windows Shared Path

  - Credential

  - Path

    For example: `\\WinMA1\Backups`

- Unix Shared Path (appears when there is more than one Windows MediaAgent)

  - Path: This is the path where Windows shared path is mounted that allows access to Unix MediaAgents.

    For example: `/MountedLibrary/folder1`

The Windows shared path is used by the Windows MediaAgents.

Notes

- Ensure that all associated MediaAgents can access the backup location.
- All shared paths must point to the same physical storage location.
- Validate access to the backup location from each MediaAgent.

×

Loading...