You are here: Replication > Upgrading from legacy vaulting to replication

Upgrading from legacy vaulting to replication

A high-level overview of the steps required to upgrade from legacy vaulting to replication is given here. Proceed to the sections that follow for detailed instructions.

These procedures assume the source (backup system) and target (legacy vault) you wish to upgrade are currently vaulting. Vaulting must be running and configured correctly to use these upgrade procedures.

Run these procedures on the target for each source system you wish to upgrade. For a target receiving vaulted data from multiple sources, you must complete these procedures for each source.

Migration limitations

The following vaulted data does not migrate during the upgrade process:

• Source system data vaulted with the legacy Vault Local Directory option.
• Vaulted CIFS/NFS NAS client backups.
• Vaulted legacy Exchange backups (backups run with the Windows legacy Exchange agent).

Before migrating, be sure to archive this data.

Run these procedures to upgrade from legacy vaulting to replication

Step 1: Prepare source and target systems
ClosedPrepare source and target systems
1 Log in to the target and suspend vaulting on all source systems in preparation for installing updates.
• Select a source system in the Navigation pane, then select Settings > Replication > Replication Attributes. Select Connection Options and Process Control, and click Suspend Vaulting.
• Repeat for each source that is vaulting to this target.
2 Update the target to version 7.1 or higher.

With the target (brown vault icon) selected in the Navigation pane, select Settings > System Updates, and Licensing > Updates > Install.

3 Update the source to version 7.1 or higher.

With the source (blue server icon) selected in the Navigation pane, select Settings > System Updates, and Licensing > Updates > Install.

4 Restart vaulting on all sources other than the one you are upgrading to replication.
• Select the source system in the Navigation pane, then select Replication > Replication Attributes. Select Connection Options and Process Control, and click Resume Vaulting.
• Be sure that vaulting remains suspended on the source you are upgrading.
• The upgrade only impacts the selected source system. Restarting vaulting on the other sources enables legacy vaulting to resume and continue throughout the upgrade procedure.
5 Configure the target as a cross-vault. (If the target is already configured as both a backup system and replication target, skip this step.)

With the target selected in the Navigation pane, select Replication > System Management > Add System, check Create Cross-Vault, and click Confirm.

Note:  This configuration is required for replication even if the target will not be used as a backup system.

6 With the target selected in the Navigation pane, select Settings > Storage and Retention > Storage Allocation.
7 Adjust storage to add replication space, either by dragging a border in the circle or entering a value in the Backup/Replication field below.
• To increase replication storage, you must decrease Vaulting and/or Instant Recovery storage.
• Vaulted data is stored on the target in the Vaulting storage area. Replicated data is stored in the Backup/Replication storage area. Increase this storage area to accommodate replicated data. When you complete the Upgrade to replication procedure, data will begin replicating. If there is no space in the Backup/Replication area, replication jobs fail.
• If you are also using the target as a local backup system, regular backups are stored in the Backup/Replication area. Be sure to allocate enough space for both replicated and backup data.
• If the target is receiving vault data from multiple sources, be sure to leave enough space in the Vaulting area. If you run out of space in the Vaulting area, legacy vault jobs fail.
• When you complete the Upgrade to replication procedure, vaulted data for this source is removed from the target. This frees space. For targets with multiple sources, freeing space as you upgrade one source at a time works well for tight systems.
Step 2: Migrate legacy vaulted data
ClosedMigrate legacy vaulted data

Note:   We strongly recommend migrating legacy vault data to avoid transferring the initial replication data set over the network. If you skip this migration procedure, the initial transfer requires a tremendous amount of time and bandwidth. After the legacy vaulted data is migrated, only changed blocks are transferred over the network.

1 Verify the following prerequisites have been met:
• All steps in the Prepare source and target systems procedure have been completed.
• The backups device on the target has as much or more free space as the total size of the backups to be migrated. To check free space, select Settings > Storage and Retention > Storage.
• If any encrypted backups on the source will be replicated, encryption must be enabled on the target. See To configure encryption for details.
• If any encrypted backups on the source will be replicated, the source encryption passphrase must be available. You will be prompted for this passphrase when migrating data.
2 Using a terminal emulator, such as PuTTY, connect to the target with the following:
• target system IP address
• port 22
• SSH connection type
3 Log in as a user with root privileges.

login as: root

root@192.168.220.56's password:

4 Enter this command to launch the migration utility:

[root]# /usr/bp/bin/vaultMigration-scripts/mr71VaultMigration.php

5 Preliminary checks are run and messages display. Check the last paragraph on the screen and do one of the following:
• If you see Select the system to migrate..., continue to the next step in this procedure.
• If you see Found some problems..., check for Failed results above in the Preliminary Check list, correct any issues, then rerun the migration utility.
6 In the System(s) list, find the source whose vaulted data you wish to migrate, type its number and press Enter. For example:

Selection (‘q’ to quit): 0

7 Information for the selected system displays. Check the last paragraph on the screen and do one of the following:
• If you see Insufficient space..., note the available space and amount needed. Allocate more space to the Backup/Retention area (Settings > Storage and Retention > Storage Allocation), then rerun the migration procedure.
• If you see Enter to start migration process..., press Enter to begin migration (or type q to quit).
8 If you are migrating encrypted backups, you are prompted for the source’s encryption passphrase. Type in the passphrase and press Enter.
9 While migration is in progress, status messages display.

Note:   You can run up to 5 migration sessions to migrate multiple source systems concurrently. Use caution when running multiple sessions as each consumes system resources, which may adversely impact performance. To run another session, start with step in Prepare source and target systems above to prepare your next source.

10 When migration is complete, you see the message Done, Exiting... and the Linux command prompt returns. For example,

Done, Exiting...

[root]#

If you see any errors, simply rerun the utility to migrate any remaining data. Once the script completes without errors, continue to Upgrade to replication.

Step 3: Upgrade to replication
ClosedUpgrade to replication

Warning!     Upgrading a source system from legacy vaulting to replication deletes all vaulted data for this source on the target system. If you have multiple sources vaulting to the target, legacy vaulting for other sources continues and vaulted data for these systems is preserved.

1 Verify the following prerequisites have been met:
• All steps in Prepare source and target systems have been completed.
• All steps in Migrate legacy vaulted data have been completed.
2 Log in to the target system interface (not the command line).
3 Select the source system in the Navigation pane, then select Replication > System Management.
4 Verify that the desired source system displays in the System Username field.

Warning!     Be sure the desired system displays in the System Username field. Any vaulted data associated with this system on the target will be deleted upon upgrading to replication.

5 Check the Configured For Replication box and click Confirm.
6 When the warning message displays, click Yes to continue.
7 When the upgrade is complete, restart replication.

With the source system selected in the Navigation pane, select Replication > Replication Attributes > Resume Replication.

8 Verify that replication is running by selecting Replication > Dashboard. You should see system metadata replicating within minutes. For details, see Working with the replication dashboard.

All clients and applications that were configured for legacy vaulting begin replicating. No further configuration is required.

9 To upgrade another source on this target, suspend vaulting on the source and repeat this procedure starting with step in Prepare source and target systems