# Running the HyperScale Migration

You can migrate a HyperScale 1.5 Appliance storage pool to a Commvault Grid storage pool.

## Before You Begin

Disable all backup jobs in the CommCell. For more information, see Controlling Activities. Backups can be enabled once the initial configuration phase is completed, which may take about 30 minutes approximately.

Note

Recommended: Do not edit or modify the Storage Pool and the Storage Policy settings during the migration.

## Procedure

1. From the Command Center navigation pane, go to Manage > Integration > Developer tools.

2. Click CV apps.

   The CV apps list page appears.

3. Click the Replace HyperScale StoragePool app.

   The HyperScale Pre-Migration Report appears.

4. Click the Run Migration button displayed at the top of the report.

   The Replace HyperScale Storage Pool dialog box is displayed.

5. Click OK.

   The Storage Pool dialog box is displayed

6. Select the following:

   1. From the Source list, select the storage pool that must be migrated.

   2. From the Destination list, select the destination storage pool.

   3. Click Confirm.

   The Data Copy dialog box is displayed.

7. Choose/select the following:

   1. Under Do you want to copy data from old storage to new storage, choose one of the following options:

      - No, to migrate only the storage pool and the associated entities.

      - Yes, migrate all data, to migrate the storage pool and the data.

      - Yes, migrate only data retained for more than X days, to migrate data with a specified retention.

   2. Select Force next backup to full (applicable to primary copies only) option to convert all the first Incremental and Differential backup jobs to a Full backup job, after the migration.

      The retention settings are displayed for information purposes in the Min Basic Retention, Max Basic Retention, Min Extended Retention, and Max Extended Retention boxes.

   3. Click Next.

8. The Retain Data for (Extended backup will always be copied) dialog box will be displayed if you selected the option to migrate data with a specified retention.

   1. Specify the number of retention days that must be used to migrate data in the Copy data which have rete... box.

   2. Click Next.

   The Data Need to be Copied dialog box will be displayed.

9. Verify the information and then click Confirm.

## Result

- A Migration job will be started and you can view the job in the Active jobs page. For more information about viewing jobs, see Viewing Jobs.

  If the option to migrate data was chosen, an Auxiliary Copy operation will be started and hence the job may take some time to complete, depending on the amount of data.

- A HyperScale Migration Configuration: Completed email will be sent to the email account associated with the user performing the migration as follows:

  - In the case of migration with data, the email will be sent twice, once at the completion of the configuration tasks, and another at the completion of the data migration.

  - In the case of migration without data, an email will be sent at the completion of the migration.

## Troubleshooting

- If the workflow is restarted after a failure, re-submit the workflow using the same data copy option (step 7) and the same number of retention days settings (step 8) as input. If you change these options, you may encounter unexpected behavior as some of the copies may have already been created during the first attempt.

- When the complete or partial migration option is selected, in some situations, the workflow may go into the Waiting for data migration state, even if the corresponding Auxiliary Copy job initiated by the workflow is completed.

  This is because there may still be some more data to be copied. The workflow will wait for additional Auxiliary copy jobs to copy the remaining data.

  If this situation occurs, perform one of the following actions:

  - If a primary copy is being migrated:

    - Ensure that at least one Auxiliary Copy schedule is associated with the copy HSReplace_<PrimaryCopyName>. Also ensure that this schedule is enabled, and running.

      Or

    - Manually initiate an Auxiliary Copy job on the Storage Policy, with HSReplace_<PrimaryCopyName> selected as the destination copy.

  - If a secondary copy is being migrated:

    - Ensure that at least one Auxiliary Copy schedule is associated with the copy <SecondaryCopyName>. Also ensure that this schedule is enabled, and running.

      Or

    - Manually initiate an Auxiliary Copy job on the Storage Policy with the <SecondaryCopyName> selected as the destination copy.

×

Loading...