CommCell Migration - Advanced

Table of Contents

Performing Temporary Migration

The following section describes the process of performing a temporary migration of a CommCell. Temporary migration can be useful in the following scenarios:

  • To free some space on a source CommCell.
  • When a copy of the Client(s) Metadata on one (source) CommCell is maintained on another CommCell. In this case, the Client continues to remain in the original CommServe, but the metadata records associated with the Client are restored to another CommCell.
  • To perform maintenance operation on a source server.

The clients and configuration settings that are temporarily migrated exist in the source CommCell and destination CommCell. The properties and associations of clients and configurations in the destination CommCell exist as in the source CommCell.

Follow steps described in Export Metadata from the Source CommCell and Import Metadata on the Destination CommCell to perform temporary migration.

Managing Global Migration Options

The CommCell Import/Export settings for client migration and configuration of default locations can be configured globally from the CommCell Console. When you set the migration settings from CommCell console, the configuration can be used globally for all the future migration jobs. The default export and import folder locations will automatically appear in the export options and import wizard.

Configure Default Export Location

Use the following steps to configure default export location on the CommCell:

  1. From the ribbon in the CommCell Console, click the Tools tab.
  2. Click CommCell Import/Export icon.
  3. In the Default Export Folder box, type the path of the folder or Browse to the folder in which the exported metadata must be located.
  4. By default, Use Local is selected to export location in local path.

    Click Use Network to use a network share as the export location. If you select a UNC path, provide the access credentials to access the export location.

    Click User Name/Password to provide the user details.

  5. Click OK.

Specify Maximum Number of Dumpsets

Use the following steps to specify maximum number of dumpsets to be retained in a dump location on the CommCell:

  1. From the ribbon in the CommCell Console, click the Tools tab.
  2. Click CommCell Import/Export icon.
  3. In the Maximum Number of Dumpsets to be retained in a dump location box, type or select the maximum number of dumpsets that can be retained in a dump location

    By default, this value is set to 10.

  4. Click OK.

Specify Number of Subclients in a Dump

Use the following steps to specify maximum number of subclients that can be stored in a dump location on the CommCell:

  1. From the ribbon in the CommCell Console, click the Tools tab.
  2. Click CommCell Import/Export icon.
  3. In the Number of Subclients to be stored in a single dump file box, type or select the maximum number of subclients that can be stored in a dump file.

    By default, this value is set to 50.

  4. Click OK.

Configure Default Import Location

Use the following steps to configure default import location on the CommCell:

  1. From the ribbon in the CommCell Console, click the Tools tab.
  2. Click CommCell Import/Export icon.
  3. In the Default Import Folder box, type the path of the folder or Browse to the folder from which the metadata must be imported.
  4. By default, Use Local is selected to export location in local path.

    Click Use Network to use a network share as the export location. If you select a UNC path, provide the access credentials to access the export location.

    Click User Name/Password to provide the user details.

  5. Click OK.

Exporting Metadata to a Remote CommCell

You can perform CommCell migration by exporting metadata of source (current) CommCell directly on to the destination CommCell.

Use the following steps to export metadata from current (source) CommCell to a remote (destination) CommCell:

  1. Log on to source CommCell Console.
  2. From the CommCell Browser, right-click the <Source CommServe>, point to All Tasks | CommCell Migration and then click Export To Folder.
  3. Click Use Other CommServe to export metadata from current CommCell and save it into another CommCell which can be used as a host for migration.
  4. Click Host Details.
    1. From the CommCell list, click already registered CommCell or click Next to register a new CommCell.
    2. In the User Name and Password box, type the CommCell user name and password of the host CommServe to be registered.
    3. In the CommCell Host Name box, type the fully qualified domain name of the CommCell to be used as a host.
    4. If there is a firewall configured between the source and the remote CommCell, click Select CommServe client located across a firewall check box and then select the Proxy clients from the list.
    5. Click OK.

      The destination CommServe name will be displayed in the Write files to CommServe field.

  1. In the Export Folder box, type the path of the folder or Browse to the folder in which the exported metadata must be located.
  2. Under Select Associations, select the components for migration.
  3. Click OK.

Exporting Metadata from a Remote CommCell

To perform CommCell migration of a remote CommCell from current CommCell, you can export metadata of a  remote CommCell.

Use the following steps to export metadata from a remote CommCell.

  1. From the CommCell Browser, right-click the <Source CommServe>, point to All Tasks | CommCell Migration and then click Export To Folder.
  2. From the Export Options dialog box, specify the following:
    1. By default, Use Local is selected to export location in local path.

      Click Use Network to use a network share as the export location. If you select a UNC path, provide the access credentials to access the export location.

      Click User Name/Password to provide the user details.

    2. In the Export Folder box, type the path of the folder or Browse to the folder in which the exported metadata must be located.
  3. Select the Export From Other SQL Instance check box to export metadata from remote CommCell across different database instances.
  4. Click SQL Server Details.
  5. In the SQL Server Name box, type the SQL server name.
    1. In the User Name box, type the user name to access the SQL server.
    2. In the Password box, type the password for the specified user account.
    3. Click OK.
  6. Under Select Associations, select the components for migration.
  7. Click OK.

Exporting Associations

You can export Client(s) and Client Computer Groups from one CommCell  to another. You can select the individual components such as Agents, BackupSets, and/or, Subclients to be exported for a client. Client Computer Groups can be selected to export a client group definition.

Exporting Client Computers

Use the following steps to export client(s) and client computer groups from source CommCell:

  1. From the CommCell Browser, right-click the <Source CommServe>, point to All Tasks | CommCell Migration and then click Export To Folder.
  2. From the Export Options dialog box, specify the following:
    1. By default, Use Local is selected to export location in local path.

      Click Use Network to use a network share as the export location. If you select a UNC path, provide the access credentials to access the export location.

      Click User Name/Password to provide the user details.

    2. In the Export Folder box, type the path of the folder or Browse to the folder in which the exported metadata must be located.
  3. Under Select Associations, select the Client Computers and Client Computer Groups to be exported.

    For a client, you can select the individual components such as Agents, BackupSets, and/or, Subclients to be exported.

    Client Computer Groups can be selected to export a client group definition.

  4. Click OK.

Exporting Configurations

Migrating configuration is useful when you want to use the same set of configurations across multiple CommCells. You can migrate specific configurations such as Subclient Policies, Schedule Policies, Users and User Groups, Alerts and Media Locations across different CommCells. Any associations related to the configurations i.e., non-data bearing entities associated with a client are migrated as configuration templates.

The CommCell Migration license will not be consumed for migrating the configuration i.e., non-data bearing entities associated with a client from a source CommCell.

Use the following steps to export CommCell configurations from source CommCell:

  1. From the CommCell Browser, right-click the <Source CommServe>, point to  All Tasks | CommCell Migration and then click Export To Folder.
  2. From the Export Options dialog box, specify the following:
    1. By default, Use Local is selected to export location in local path.

      Click Use Network to use a network share as the export location. If you select a UNC path, provide the access credentials to access the export location.

      Click User Name/Password to provide the user details.

    2. In the Export Folder box, type the path of the folder or Browse to the folder in which the exported metadata must be located.
  3. Under Select Associations, select the Configuration to be exported.

    Subclient policies, Users and User groups, Alerts and Media Locations can be migrated as a group and not as individual components. However, the individual components of schedule policies can be migrated.

  4. Click OK.

Exclude Exporting MediaAgents

You can exclude exporting the MediaAgents of the selected source clients from the migration process.

Use the following steps to prevent export of MediaAgents from source CommCell:

  1. From the CommCell Browser, right-click the <Source CommServe>, point to  All Tasks | CommCell Migration and then click Export To Folder.
  2. From the Export Options dialog box, specify the following:
    1. By default, Use Local is selected to export location in local path.

      Click Use Network to use a network share as the export location. If you select a UNC path, provide the access credentials to access the export location.

      Click User Name/Password to provide the user details.

    2. In the Export Folder box, type the path of the folder or Browse to the folder in which the exported metadata must be located.
  3. Under Select Associations, select the Do not export MediaAgents check box, to exclude MediaAgents export from the migration process.
  4. Select the components to be migrated.
  5. Click OK.

Export Complete Cluster

You can export all the physical and the virtual nodes of the selected source cluster during CommCell Migration.

Use the following steps to export complete cluster from source CommCell:

  1. From the CommCell Browser, right-click the <Source CommServe>, point to  All Tasks | CommCell Migration and then click Export To Folder.
  2. From the Export Options dialog box, specify the following:
    1. By default, Use Local is selected to export location in local path.

      Click Use Network to use a network share as the export location. If you select a UNC path, provide the access credentials to access the export location.

      Click User Name/Password to provide the user details.

    2. In the Export Folder box, type the path of the folder or Browse to the folder in which the exported metadata must be located.
  3. Based on the type of cluster that you want to export, do the following:
    Cluster Type Action
    Windows Under Select Associations, select the Automatically Select Complete Cluster check box, to export all the physical and the virtual nodes of the selected source cluster.
    Linux Under Select Associations, select the Automatically Select Complete Cluster check box, to export all the physical and the virtual nodes of the selected source cluster.
    Exchange DAG Under Select Associations, manually select the physical and the virtual nodes of the selected source cluster.
    SQL AlwaysOn Under Select Associations, manually select the physical and the virtual nodes of the selected source cluster.
    Oracle RAC If you want to export the complete cluster, then select only RAC clients.

     If you manually select some physical clients in the cluster, then the complete cluster selection will be ignored and only selected clients will be exported.

  4. Click OK.

Exporting Client Capture Options

You can choose to capture and export Holiday schedules, Operation Window rules, Activity Control settings and Schedules of a Client from one CommCell  to another.

Use the following steps to export client configuration settings from source CommCell:

  1. From the CommCell Browser, right-click the <Source CommServe>, point to All Tasks | CommCell Migration and then click Export To Folder.
  2. From the Export Options dialog box, specify the following:
    1. By default, Use Local is selected to export location in local path.

      Click Use Network to use a network share as the export location. If you select a UNC path, provide the access credentials to access the export location.

      Click User Name/Password to provide the user details.

    2. In the Export Folder box, type the path of the folder or Browse to the folder in which the exported metadata must be located.
  3. Under Select Associations, select the components for migration.
  4. Click Advanced.
  5. In the Select Export Options dialog box, click the Export Options tab.
  6. By default, all the Client Capture Options are selected to be exported.
    1. Click to clear the Capture Holidays check box to prevent exporting holiday schedules of the client
    2. Click to clear the Capture Operation Window check box to prevent exporting Operation Window rules of the client.
    3. Click to clear the Capture Activity Control check box to prevent exporting Activity Control settings of the client.
    4. Click to clear the Capture Schedules check box to prevent exporting Schedules of the client.
  7. Click OK.

Exporting Metadata to a Staging Location

You can export metadata to a staging location on the source CommCell during CommCell migration. The exported metadata can be imported from the same staging location during the import process.

Use the following steps to export metadata to a staging location on the source CommCell.

  1. From the CommCell Browser, right-click the <Source CommServe>, point to All Tasks | CommCell Migration and then click Export To Folder.
  2. From the Export Options dialog box, specify the following:
    1. By default, Use Local is selected to export location in local path.

      Click Use Network to use a network share as the export location. If you select a UNC path, provide the access credentials to access the export location.

      Click User Name/Password to provide the user details.

    2. In the Export Folder box, type the path of the folder or Browse to the folder in which the exported metadata must be located.
  3. Under Select Associations, select the components for migration.
  4. Click Advanced.
  5. In the Select Export Options dialog box, click the Export Options tab.
  6. Select the Specify Staging Path check box
  7. In the Staging Path box, type the staging path or Browse to the folder in which the exported metadata must be staged.
  8. Click OK to close the Select Export Options dialog box.
  9. Click OK.

Exporting Metadata to a Staging Location for a Remote CommCell Database

CommCell migration can be performed even if the CommServe and its database resides in two different computers. This can be achieved by exporting the metadata and staging it on the remote SQL Server hosting the CommServe database.

Use the following steps to export metadata to a staging location for a remote CommServe Database instance:

  1. From the CommCell Browser, right-click the <Source CommServe>, point to All Tasks | CommCell Migration and then click Export To Folder.
  2. From the Export Options dialog box, specify the following:
    1. By default, Use Local is selected to export location in local path.

      Click Use Network to use a network share as the export location. If you select a UNC path, provide the access credentials to access the export location.

      Click User Name/Password to provide the user details.

    2. In the Export Folder box, type the path of the folder or Browse to the folder in which the exported metadata must be located.
  3. Under Select Associations, select the components for migration.
  4. Click Advanced.
  5. In the Select Export Options dialog box, click the Export Options tab.
  6. Select Please specify the location of a shared folder on the SQL server.
  7. In the Local path on SQL Server box, enter the local path to export and stage the metadata on the SQL Server.
  8. In the UNC path of above path box, enter the machine name and the location of the local path of the SQL server to stage the metadata.

    Click  User Name/Password to provide the user credentials.

    The Local path on SQL Server and UNC path of above path should point to same physical storage location.

  9. Click OK.

Configuring MediaAgent on the Destination CommCell

In CommCell Migration, when a library is migrated from source CommCell to destination CommCell, by default, it is not associated to any MediaAgent. However , if required you can associate a MediaAgent to the source library migrated on the destination CommCell from Destination MediaAgent list.

Use the following steps to associate a MediaAgent to the source library migrated on the destination CommCell:

  1. From the CommCell Browser, right-click the <Destination CommServe>, point to  All Tasks | CommCell Migration and then click Import From Folder.
  2. Enter the import location in the Import Folder box where the exported metadata is located.
    1. By default, Use local is selected to access imported files from local path.

      Click Use Network for a network location. If you select a UNC path, provide the access credentials to access the import location. Click User Name/Password to provide the user details.

    2. Click Next.
  3. Under Select CommCell, select the destination CommServe to import and click Next.
  4. Select the Source Library, Mount Path and Mount Path location on the destination CommCell for importing data.
  5. By default, Destination MediaAgent for the migrated Library is selected as Not Accessible.
    1. Select a MediaAgent to associate with the migrated Library from the Destination MediaAgent list.
    2. Click Next.
  6. Enter a new name for the client if required. If nothing is specified the old name will be used. Click Next.
  7. Review the selected import options and click Next.
  8. Click Finish to complete the import operation.

Data Aging of Migrated Mount Paths

By default, data aging is disabled on the migrated mount paths. However in case of permanent CommCell Migration, you can configure pruning on migrated mount paths by enabling read/write access on them and then enable data aging on the migrated storage policy copy.

It is recommended to enable pruning on a migrated mount path only after all the clients having data on that mount path have been permanently migrated over to the destination CommCell and the source CommCell is no longer using that mount path for any backups.

Note: When a DDB is migrated, all the backup jobs that went to that DDB must meet the retention rules (defined in their associated storage policy copy) for the DDB to become aged. Once all of the jobs have met their retention criteria, the entire DDB is considered ageable, and the backup jobs are then aged.

Use the following steps on Destination CommCell to enable read/write access on the migrated mount paths after permanent CommCell Migration:

  1. From the CommCell Browser, navigate to Storage Resources | Libraries | <Library>.
  2. Select and right-click the <Mount Path>, and then click Properties.
  3. Click the Sharing tab.
  4. Select the mount path and click Edit button.
  5. In the MediaAgent list, by default Read access type is selected.

    Select the Read/Write access type.

  6. Click OK.

    After enabling pruning on a mount path, it is recommended to use that mount path for read operations only on the source CommCell.

Use the following steps to enable Data Aging for migrated storage policy copies:

  1. From the CommCell Browser, navigate to Policies | Storage Policies | <Storage_Policy>.
  2. Right-click the <Storage Policy Copy> and click Properties.
  3. Click the Retention tab.
  4.  Select the Enable Data Aging check box to enable Data Aging.

    Do not change the retention rule of a copy while a backup, restore, or auxiliary copy operation is running.

  5. Click OK.

Configuring New Location for Mount Path

You can change the mount path location for importing metadata on the destination CommCell. The existing data is pruned based on the data aging settings of the data contained in the mount path. Once all the data in the mount path is completely pruned, the mount path can be deleted.

Use the following steps to change the mount path location on the destination CommCell:

  1. From the CommCell Browser, right-click the <Destination CommServe>, point to  All Tasks | CommCell Migration and then click Import From Folder.
  2. Enter the import location in the Import Folder box where the exported metadata is located.
    1. By default, Use local is selected to access imported files from local path.

      Click Use Network for a network location. If you select a UNC path, provide the access credentials to access the import location. Click User Name/Password to provide the user details.

    2. Click Next.
  3. Under Select CommCell, select the destination CommServe to import and click Next.
  4. Select the Source Library, Mount Path and Mount Path location on the destination CommCell for importing data.
  5. By default, Destination MediaAgent for the migrated Library is selected as Not Accessible.

    Select a MediaAgent to associate with the migrated Library from the Destination MediaAgent list.

  6. Click Edit Location to change the Mount Path location.
  7. From the Edit Location dialog box, specify the following:
    1. Select the MediaAgent from the MediaAgent list on the source CommCell for importing data.
    2. In the Unix Sharing Folder, type the access path or Browse to the Mount Path of the shared library for Unix based machine
    3. In the Windows Sharing Folder, specify the following:

      By default, Local Path is selected if the shared library is in local machine.

      Click Network Path if the shared library is in network location.

      In the Connect As box, provide the access credentials to access the shared library.

      In the Password box, enter the password to access the network shared library.

      In the Verify Password box, re-type the key for verification.

      In the Folder box, type the access path or Browse to the Mount Path of the shared network library

      Click OK to close the Edit Location dialog box.

  8. Click Next.
  9. Enter a new name for the client if required. If nothing is specified the old name will be used. Click Next.
  10. Review the selected import options and click Next.
  11. Click Finish to complete the import operation.

Configuring Multiple MediaAgents for a Shared Device

In order to share a library among MediaAgents, either directly or via a Storage Area Network (SAN), it is required to configure and map the resident drives. You can detect and configure the shared disk devices in the CommCell. The associated MediaAgents collect the information necessary to configure a device. All the configured devices and the MediaAgents that share a shared library will be displayed in the Library and Drive Configuration window.

Before you Begin

  • For Windows, configure multiple MediaAgents if the mount path of the device is UNC path.
  • For Unix, the mount path should be unique

Use the following steps to configure multiple MediaAgents for a Shared Disk Device:

  1. From the CommCell Console, click the Tools menu and then click Control Panel.
  2. From the Control Panel, double-click the Library & Drive Configuration.
  3. Select the MediaAgent(s) whose devices you want to detect or display from the Available MediaAgents list box.

    Click Add >> to move the MediaAgent(s) to the Selected MediaAgents list box and then click OK.

  4. From the Library and Drive Configuration window, click the Shared Disk Device tab.
  5. Expand the Device to which you want to configure multiple MediaAgents.
  6. Right-click the <Mount Path> and then click Configure for All Selected MediaAgents.

    • For Windows, configure all MediaAgents when the mount path is configured as UNC path and all selected MediaAgents have access to this UNC path.
    • For Unix, ensure that the directory path to be mounted in the unconfigured MediaAgents has the same directory path as that of the configured MediaAgent.

  7. Click Yes.

The device is configured with the list of selected MediaAgents.

Managing Import Operations

You can configure the import process to complete successfully and choose to avoid any conflicts when performing multiple CommCell Migration jobs. You can import Client(s), Client Groups and Configurations from source CommCell to destination CommCell. This aids in using the same set of configurations across multiple CommCells.

Prevent Import of Data from Conflicting Media

For multiple CommCell Migration jobs, if the data on media has already been imported on destination CommCell and the media has been reused, then for subsequent import process there may arise a conflict of the media on the destination CommCell. This is because the data on media as per exported metadata will be different  from the current data on media. This may fail the import process.

Use the following steps to exclude importing data from a conflicting media on the destination CommCell:

  1. From the CommCell Browser, right-click the <Destination CommServe>, point to  All Tasks | CommCell Migration and then click Import From Folder.
  2. Enter the import location in the Import Folder box where the exported metadata is located.
    1. By default, Use local is selected to access imported files from local path.

      Click Use Network for a network location. If you select a UNC path, provide the access credentials to access the import location. Click User Name/Password to provide the user details.

    2. Click Next.
  3. Under Select CommCell, select the destination CommServe to import and click Next.
  4. Select the Source Library, Mount Path and Mount Path location on the destination CommCell for importing data and click Next.
  5. Enter a new name for the client if required. If nothing is specified the old name will be used. Click Next.
  6. From the Import Options window, select the Skip Import of Data From Conflict Media check box and click Next.
  7. Review the selected import options for client import and data path and click Next.
  8. Click Finish to complete the import operation.

Reuse Imported Media on Destination CommCell

In CommCell Migration, when a library is migrated from source CommCell to destination CommCell, by default, it is not associated to any MediaAgent. Hence the associated media will not move to the scratch set even after the data is aged.

Use the following steps to reuse imported media on the destination CommCell:

  1. From the CommCell Browser, right-click the <Destination CommServe>, point to  All Tasks | CommCell Migration and then click Import From Folder.
  2. Enter the import location in the Import Folder box where the exported metadata is located.
    1. By default, Use local is selected to access imported files from local path.

      Click Use Network for a network location. If you select a UNC path, provide the access credentials to access the import location. Click User Name/Password to provide the user details.

    2. Click Next.
  3. Under Select CommCell, select the destination CommServe to import and click Next.
  4. Select the Source Library, Mount Path and Mount Path location on the destination CommCell for importing data and click Next.
  5. Enter a new name for the client if required. If nothing is specified the old name will be used. Click Next.
  6. From the Import Options window, select the Allow imported media to be reused on this CommCell check box and click Next.
  7. Review the selected import options for client import and data path and click Next.
  8. Click Finish to complete the import operation.

Delete Entities on Destination CommCell

In CommCell Migration, while migrating configurations, you can choose to delete the migration elements that are available in destination CommCell and not present in the source CommCell.

For example : During CommCell Migration, while importing data, if Alert1, Alert2 and Alert3 are defined on source CommCell and Alert 2 (added from previous migration), Aert4 and Alert5 exist on destination CommCell and you select the Delete Entities Not Present (does not apply to clients and MediaAgents) option then after migration process you will have Alert1, Alert2 and Alert3 on the destination CommCell. Alert4 and Alert5 will be deleted from the destination CommCell. However system created alerts are not affected by this option.

Use the following steps to delete the entities on the destination CommCell which are not present in the source CommCell:

  1. From the CommCell Browser, right-click the <Destination CommServe>, point to  All Tasks | CommCell Migration and then click Import From Folder.
  2. Enter the import location in the Import Folder box where the exported metadata is located.
    1. By default, Use local is selected to access imported files from local path.

      Click Use Network for a network location. If you select a UNC path, provide the access credentials to access the import location. Click User Name/Password to provide the user details.

    2. Click Next.
  3. Under Select CommCell, select the destination CommServe to import and click Next.
  4. Select the Source Library, Mount Path and Mount Path location on the destination CommCell for importing data and click Next.
  5. Enter a new name for the client if required. If nothing is specified the old name will be used. Click Next.
  6. From the Import Options window, select the Delete Entities Not Present (does not apply to clients and MediaAgents) check box to delete the migration elements that are available in destination CommCell and not present in the source CommCell.
  7. Select the Delete entities If only from Source check box to delete entities that have been migrated from the same source CommCell earlier. Entities created locally in the destination CommCell will not be affected.

    For example: During first CommCell Migration, alerts (Alert1 and Alert2) are migrated from source to destination CommCell and later deleted from the source. Few alerts (Alert3 and Alert4) are then created locally on destination CommCell. During next CommCell Migration if new alerts (Alert5 and Alert6) are being migrated from same source and the Delete entities If only from Source option is selected then the alerts that were merged during the previous CommCell Migration will be deleted. So the destination CommCell will have Alert3, Alert4, Alert5 and Alert6.

  8. Review the selected import options for client import and data path and click Next.
  9. Click Finish to complete the import operation.

Configure Overwrite for Existing Entities on Destination CommCell

If you have the same configuration in the destination CommCell as that of the source CommCell the import fails as the same entity exists in the destination CommCell. You can choose to retain the same entity that already exist on the destination CommCell.

Use the following steps to retain the same entity that already exist on the destination CommCell:

  1. From the CommCell Browser, right-click the <Destination CommServe>, point to  All Tasks | CommCell Migration and then click Import From Folder.
  2. Enter the import location in the Import Folder box where the exported metadata is located.
    1. By default, Use local is selected to access imported files from local path.

      Click Use Network for a network location. If you select a UNC path, provide the access credentials to access the import location. Click User Name/Password to provide the user details.

    2. Click Next.
  3. Under Select CommCell, select the destination CommServe to import and click Next.
  4. Select the Source Library, Mount Path and Mount Path location on the destination CommCell for importing data and click Next.
  5. Enter a new name for the client if required. If nothing is specified the old name will be used. Click Next.
  6. From the Import Options window, under On Conflict, click Force Overwrite to overwrite existing entities on the destination CommCell.

    By default, Fail if Entity Already Exists is selected to fail the import if an entity already exist on the destination CommCell.

  7. Review the selected import options for client import and data path and click Next.
  8. Click Finish to complete the import operation.

Configure Overwrite Options for Non-Client Entities on Destination CommCell

You can retain the Holiday schedules, Operation Window rules, Activity Control settings and Schedules of the destination CommCell.

Use the following steps to retain non-client entities on the destination CommCell:

  1. From the CommCell Browser, right-click the <Destination CommServe>, point to  All Tasks | CommCell Migration and then click Import From Folder.
  2. Enter the import location in the Import Folder box where the exported metadata is located.
    1. By default, Use local is selected to access imported files from local path.

      Click Use Network for a network location. If you select a UNC path, provide the access credentials to access the import location. Click User Name/Password to provide the user details.

    2. Click Next.
  3. Under Select CommCell, select the destination CommServe to import and click Next.
  4. Select the Source Library, Mount Path and Mount Path location on the destination CommCell for importing data and click Next.
  5. Enter a new name for the client if required. If nothing is specified the old name will be used. Click Next.
  6. From the Import Options window, under On Conflict, click Force Overwrite to overwrite existing entities on the destination CommCell.
  7. Under Force Overwrite Options for non-client entities specify the following:

    Select the Force Overwrite Holiday check box to overwrite Holidays details.

    Select the Force Overwrite Operation Window check box to overwrite Operation Window rules.

    Select the Force Overwrite Schedules check box to overwrite Schedule details.

  8. Review the selected import options for client import and data path and click Next.
  9. Click Finish to complete the import operation.

Import Configurations

You can import the CommCell configurations such as Holiday schedules, Operation Window rules, Activity Control settings and Schedules of a Client from source CommCell to destination CommCell.

Use the following steps to import configuration details on the destination CommCell:

  1. From the CommCell Browser, right-click the <Destination CommServe>, point to  All Tasks | CommCell Migration and then click Import From Folder.
  2. Enter the import location in the Import Folder box where the exported metadata is located.
    1. By default, Use local is selected to access imported files from local path.

      Click Use Network for a network location. If you select a UNC path, provide the access credentials to access the import location. Click User Name/Password to provide the user details.

    2. Click Next.
  3. Under Select CommCell, select the destination CommServe to import and click Next.
  4. Select the Source Library, Mount Path and Mount Path location on the destination CommCell for importing data and click Next.
  5. Enter a new name for the client if required. If nothing is specified the old name will be used. Click Next.
  6. Review the selected import options and click Next.
  1. In the Import Options window, by default, all the Client Import Options are selected to be imported.
    1. Click to clear the Import Holidays check box to prevent importing holiday schedules of the clients.
    2. Click to clear the Import Operation Window check box to prevent importing Operation Window rules of the clients.
    3. Click to clear the Import Activity Control check box to prevent importing Activity Control settings of the clients.
    4. Click to clear the Import Schedules check box to prevent importing Schedules of the clients.
  2. Click Next.
  3. Click Finish to complete the import operation.

Importing Metadata from a Staging Location

You can import the exported metadata from a staging location on the destination CommCell during CommCell migration.

Use the following steps to import metadata from a staging location on the destination CommCell

  1. From the CommCell Browser, right-click the <Destination CommServe>, point to  All Tasks | CommCell Migration and then click Import From Folder.
  2. Enter the import location in the Import Folder box where the exported metadata is located.
    1. By default, Use local is selected to access imported files from local path.

      Click Use Network for a network location. If you select a UNC path, provide the access credentials to access the import location. Click User Name/Password to provide the user details.

    2. Click Next.
  3. Under Select CommCell, select the destination CommServe to import and click Next.
  4. Select the Source Library, Mount Path and Mount Path location on the destination CommCell for importing data and click Next.
  5. Enter a new name for the client if required. If nothing is specified the old name will be used. Click Next.
  6. Review the selected import options and click Next.
  7. Select the Specify Staging Path check box
  8. In the Staging Path box, type the staging path or Browse to the location from where the staged metadata needs to be imported. Click Next.
  9. Click Finish to complete the import operation.

Importing Metadata from a Staging Location for a Remote CommCell Database

CommCell migration can be performed even if the CommServe and its database resides in two different computers. This can be achieved by exporting the metadata and staging it on the remote SQL Server hosting the CommServe database and importing it from the staged location on the remote SQL Server.

Use the following steps to import metadata from a staging location for a remote CommServe Database instance:

  1. From the CommCell Browser, right-click the <Destination CommServe>, point to  All Tasks | CommCell Migration and then click Import From Folder.
  2. Enter the import location in the Import Folder box where the exported metadata is located.
    1. By default, Use local is selected to access imported files from local path.

      Click Use Network for a network location. If you select a UNC path, provide the access credentials to access the import location. Click User Name/Password to provide the user details.

    2. Click Next.
  3. Under Select CommCell, select the destination CommServe to import and click Next.
  4. Select the Source Library, Mount Path and Mount Path location on the destination CommCell for importing data and click Next.
  5. Enter a new name for the client if required. If nothing is specified the old name will be used. Click Next.
  6. Review the selected import options and click Next.
  7. Select the Please specify the location of a shared folder on the SQL Server check box.
    1. In the Local path on SQL Server box, enter the local path to import the staged metadata from the SQL Server.
    2. In the UNC path of above path box, enter the machine name and the location of the local path of the SQL server where the metadata is staged.
    3. Click User Name/Password to provide the user credentials.
    4. Click OK.
  8. Click Next.
  9. Click Finish to complete the import operation.

Creating Autonomous Backups Using CommCell Migration

You can create autonomous sets of backups that can be saved to external disks and can be restored without access or availability of the CommCell with which the data was backed up.

This is achieved by creating a selective copy which will write data to a dedicated mount path. You can then perform an auxiliary copy operation to replicate the data from primary copy to the selective copy followed by an export of the backup jobs using a relative or absolute time range. Both the mount path data and the exported data are then written to the external disk which can be restored by any CommCell.

The following procedure provides step-by-step instructions on how to perform  autonomous backups which can be restored without using the source CommCell used for the backups.

  1. Create a Disk library and add a mount path. The mount path will act as a staging area for the data to be exported. Hence it is recommended that this should not be an external disk as another copy to the external media will happen.

    See Create a Disk Library for step-by-step instructions.

    See Add Additional Mount Path for step-by-step instructions.

  2. Create a selective copy and Disable data aging for the copy.

    See Creating a Selective Copy for step-by-step instructions.

    See Enable / Disable Data Aging Jobs for information on disabling Data Aging for the copy

  3. Perform an auxiliary copy operation to replicate the Client data from primary copy to a secondary copy.

    See Running an Auxiliary Copy for instructions.

  4. Run CommCell Migration export by selecting the required clients and Specifying the time range.

    Use the following steps to export metadata of the required client by specifying a relative or absolute time range:

    1. From the CommCell Browser, right-click the <Source CommServe>, point to All Tasks | CommCell Migration and then click Export To Folder.
    2. From the Export Options dialog box, specify the following:
      1. By default, Use Local is selected to export location in local path.

        Click Use Network to use a network share as the export location. If you select a UNC path, provide the access credentials to access the export location.

        Click User Name/Password to provide the user details.

      2. In the Export Folder box, type the path of the folder or Browse to the folder in which the exported metadata must be located.
    3. Under Select Associations, select the components for migration.
    4. Click Advanced.
    5. In the Select Export Options dialog box, click the Job Selection tab.
      1. By default, All Jobs is selected.
      2. Click Absolute Time to specify the Start Time and/or End Time of the backup operations which need to be included in the export.
      3. Click Relative Time to specify relative time in terms of number of Days and Hours.
    6. Click OK to close the Select Export Options dialog box.
    7. Click OK.
  5. Copy all the data of the mount path to the external disk.
  6. Copy the exported data to the external disk.
  7. Delete all the jobs from the secondary copy (used as staging area).

  8. Install the CommServe and MediaAgent software in the new computer with evaluation license.

    See Install the CommServe for information on installing the CommServe software.

    See Install the MediaAgent for information on installing the MediaAgent software.

  9. Create a magnetic library and specify any path for the mount path. No backups will ever be written to it.

    See Create a Disk Library for step-by-step instructions.

  10. Import the exported dump.

    See Import Metadata on the Destination CommCell for step-by-step instructions.

    In the Specify MediaAgents that have read access to the mount paths and edit access paths if needed wizard, select the MediaAgent from destination CommCell to access the migrating library for restore operation. Identify the mount path acting as staging area which was created on source and map it to the copied mount path folder on the external disk in the Location list.

  11. Enable the option to change the copy precedence automatically to ensure that browse (which will require index restores) and restores do not fail because of the inability to access the data on the primary copy.

    Use the following steps to change the copy precedence automatically if the primary copy is unreachable:

    1. From the CommCell Browser, right-click the <CommServe> and then select Control Panel.
    2. Double-click Browse/Search/Recovery.
    3. Select the Automatically switch copy to read data from any copy check box.
    4. Click OK.
  12. Perform a restore of any desired job.

    See Perform a Restore for step-by-step instructions.

Managing Jobs

Jobs can be managed in a number of ways. See Job Management for a comprehensive information on managing jobs.

The following sections provide information on the different job management options available:

Resubmitting Jobs

You can resubmit a job from the job history windows. This is useful if a job has failed, and you want to run it again. This removes the need to reconfigure a job with the same options. You can resubmit the same job directly from the job history windows.

Right-click the <Source CommServe> node and point to View | Admin Job History and select the CommCell Export as job type.

  1. From the CommCell Browser, right-click the CommCell node and click View | Admin Job History.
  2. Select CommCell Export as job type for <Source CommServe> from the Admin Job History Filter window.

    Alternatively, select CommCell Import as job type for <Destination CommServe> from the Admin Job History Filter window,

  3. Select the desired filter options such as time range, job status, number of jobs and click OK.
  4. The Admin Job History window displays the history for selected filter options.
  5. From the Admin Job History window, right-click the job and then click Resubmit Job...
  6. Select the job options.
  7. Click OK.

Controlling Jobs

The following controls are available for running jobs in the Job Controller window:

Suspend

Temporarily stops a job. A suspended job is not terminated; it can be restarted at a later time.

Resume

Resumes a job and returns the status to Waiting, Pending, Queued, or Running. The status depends on the availability of resources, the state of the Operation Windows, or the Activity Control setting.

Kill

Terminates a job.

Suspending a Job

  1. From the Job Controller of the CommCell Console, right-click the job and select Suspend.
  2. The job status may change to Suspend Pending for a few moments while the operation completes. The job status then changes to Suspended.

Resuming a Job

  1. From the Job Controller of the CommCell Console, right-click the job and select Resume.
  2. As the Job Manager attempts to restart the job, the job status changes to Waiting, Pending, or Running.

Killing a Job

  1. From the Job Controller of the CommCell Console, right-click the job and select Kill.
  2. Click Yes when the confirmation prompt appears if you are sure you want to kill the job. The job status may change to Kill Pending for a few moments while the operation completes. Once completed, the job status will change to Killed and it will be removed from the Job Controller window after five minutes.

Related Reports

CommCell Export Job Summary and CommCell Import Job Summary reports provide job summary details of export and import jobs when performing CommCell Migration.

CommCell Export Job Summary Report

The CommCell Export Job Summary Report displays information about export jobs that run in the CommCell during the specified time period. It provides a summary of CommCell Migration/Export jobs, export job status, the destination folder where CommCell data was migrated, and the path type.

The following procedure provides the steps necessary to run CommCell Export Job Summary report:

  1. From the CommCell Browser, click the Reports tab and then click Summary icon.
  2. From the Reports pane, navigate to Jobs and click Job Summary.
  3. Click Administrative Jobs and then click CommCell Export.
  4. Click Run.

CommCell Import Job Summary Report

The CommCell Import Job Summary Report displays information about import jobs that run in the CommCell during the specified time period. It provides a summary of CommCell Migration/Import jobs, import job status, the source folder from which the CommCell data was imported, and the path type.

The following procedure provides the steps necessary to run CommCell Export Job Summary report:

  1. From the CommCell Browser, click the Reports tab and then click Summary icon.
  2. From the Reports pane, navigate to Jobs and click Job Summary.
  3. Click Administrative Jobs and then click CommCell Import.
  4. Click Run.