CommCell Migration provides the facility to move Clients or MediaAgents from
one CommCell to another for performing cross server restores or on a permanent
basis to allow backups to continue in a new CommCell.
The following components are available for migration:
Client computers and the Agents installed on the Client can be migrated
to another CommCell. You can select the individual Agents, Backupsets, and Subclients
for migration.
Client Group definitions are migrated but not the associations and the clients
associated to the Client group.
Note that the client group definition is migrated.
The actual clients within the group are not migrated unless they are
selected for migration.
Subclient policies, schedule policies, users and user groups, media location
and alerts associated with the CommCell.
Client configurations such as holidays, operation window, activity control,
and schedules can be migrated.
Metadata records associated with the backup data secured by Data Protection
operations from the Agents. This includes the following:
History information.
Information about media.
Storage Policy and Storage Policy Copies associated with the subclients
configured in the Client, including storage policies and storage policy
copies used in the past, that contain valid data from the Client.
MediaAgent details, excluding the library configurations can be
migrated to another CommCell. After the migration you will have to manually
configure the libraries on the destination CommCell.
The following components associated with a source CommCell are not migrated:
The data and binaries that are associated with metadata are not migrated.
Information associated with MediaAgents such as, configured libraries, master
drive pools, drive pools and drives.
History information associated with Data Recovery operations and administration
jobs.
Firewall related configuration information.
Events associated with jobs generated by Clients that are migrated.
Audit trail information associated with the client
Subclient-based Storage Policy Copy associations.
Any associations related to the configurations i.e., non-data bearing
entities associated with a client such as schedule policies, subclient
policies etc. They are migrated as configuration templates.
Verify that no jobs are in progress or scheduled to occur in the Clients
that you wish to migrate. If jobs are scheduled, either perform the export at
another time or disable all jobs for the client using the Activity Control
tab from the Client Properties dialog box in the CommCell Console.
Perform an Auxiliary Copy operation before exporting the metadata records
for migration. This will ensure that all the copies associated with all storage
policies are synchronized.
It is recommended that you perform a disaster recovery backup operation
prior to a migration operation.
Ensure that compatible drives are available in the destination CommCell
to restore the migrated backup data.
The source and destination CommCells should be accessing the same version
of CommServe(s).
Make sure that you have the same SQL Server version in the source and destination
CommServe. For example, if you have SQL 2008 R2 version in the source, you need
to have the same version in the destination as well.
If the SRM Server is installed in Source CommServe, make sure to install
the SRM Server on destination CommServe too while performing CommCell
Migration. This is because an SRM Analytics Policy is required to be
associated with the migrated SRM components and there is one SRM Analytics
Policy per CommCell.
When computers are relocated or for load balancing, some clients may have to
be attached to another CommCell. This process requires permanent migration of the
metadata records associated with these clients. The following steps describe the
process involved in migrating the metadata of an entire CommCell to another CommCell:
When performing CommCell Migration you will first need to export the metadata
associated with the source CommCell. The export operation is performed on the source
CommCell, allowing you to select entities that you wish to export from a source
CommCell to the specified export location.
Follow the steps given below to export an entire CommCell:
1.
From the CommCell Browser, right-click the CommServe, click
All Tasks, click CommCell Migration and select Export To
Folder.
2.
From the General tab on the Export Options
dialog box, provide the export location in the Export Folder field.
Select Use local for a local path. Select Use Network for
a network 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. Select Use Other CS Host to specify other CommServe
along with its local path as a host for migration. Select a database from
Export entities from list to export metadata.
3.
Select the following components for migration from Select
Associations.
Client(s) that you wish to export. For a client, you can select
the individual components such as Agents, Backupsets, and/or, Subclients.
Client Computer Groups to select a client group definition for export.
MediaAgent that you wish to export. If you select Do Not Select
MediaAgents option, the MediaAgents of the selected source clients
will not be migrated.
Desired CommCell configurations such as Subclient Policies, Schedule
Policies, Users and User Groups, Alerts, and Location.
If you select Automatically Select Complete Cluster option, all
the physical and the virtual nodes of the selected source cluster will be
exported.
4.
Click Advanced to view and select the advanced exportoptions from Select Export Options dialog box.
5.
From the Job Initiation tab on the Export Options
dialog box, select Immediate run the export immediately. Alternatively,
you can schedule the export job for a later time.
The metadata associated with the source CommCell can now be imported into the
destination CommCell. The import will use the import entries that you have defined
for the destination CommCell.
Follow the steps given below to import metadata of a source CommCell to the destination
CommCell:
1.
From the CommCell Browser, right-click the CommServe, click
All Tasks, click CommCell Migration and select Import
From Folder.
2.
From the Import Wizard, provide the import location
in the Import Folder field. Select Use local for a local path.
Select 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. Click Next.
3.
From Select CommCell to Import window, select a
CommCell to import and click Next.
4.
From the Specify Target Libraries for Imported Media
and Future Backups window, provide
the media mapping options to import data from the source CommCell. Select
the library, MediaAgent, drive pool, and spare group on the destination
CommCell for importing data and click Next.
You need to map the MediaAgent in order to associate the media.
The MediaAgent should have a compatible media library to map and import
the metadata from source on to the destination CommCell.
Ensure that you copy the disk libraries to the appropriate computer
specified during the import operation.
The CV_MAGNETIC folder must have read-write access in the destination
CommCell. For example, if you make copies of the CV_MAGNETIC folder
using a disc, ensure that the contents are copied to a computer, so
that it can be accessed during a restore operation.
5.
From the Specify Target Libraries and Mount Path
Details for Imported Disk Data window, you can
view the default MediaAgent, Device Name and Mount
Path on the Source CommCell for importing metadata.
The Mount Path and Library on the destination CommCell are displayed by default
in this window. If you wish to change the destination mount path, click
Edit to provide the destination Library Name and MediaAgent Name for importing
metadata. Verify the mount path mapping on the Source Mount Path Mapping
window and click Next.
If you are mapping the Source Mount path for the first time, the MediaAgent, Device Name,
destination library and Mount Paths will appear in Blue.
6.
From the Specify new Locations for Dedupe Database window, specify
the target MediaAgent and target SIDB access path on the destination CommCell
for importing data and click Next. The SIDB needs be copied on to
the destination CommCell. Otherwise, it cannot be pruned.
If you use
the Global Dedup Policy as the storage policy, then the mapping path in
the Specify new Locations for Dedupe Database window will appear in Italics.
For more information on SIDB/SILO configuration and mapping on the
destination CommCell, see
SIDB/SILO
configuration.
7.
From the Client Name Mapping window, specify a new
name for the client if required. If nothing is specified the old name will
be used. Click Next.
Migrated clients can be deconfigured from original CommServe module,
before renaming the client in the migrated setup.
If a firewall is configured for the migrated client, then you need
to uninstall and reinstall the client on the destination CommCell after
the migration.
8.
From the Import Options window, select the Consume
license(s) option to consume the license on the destination CommCell
after the import is completed click Next.
Ensure that you have a license available on the destination CommCell.
The destination client will be enabled once all data has been migrated.
If you choose not to consume a license during this operation, the client
data will be migrated, but the destination client will not be enabled.
9.
From the Import Options window, review the selected
import options and click Next.
10.
From the Job Initiation window, select Immediate
to start the import process. Alternatively, you can schedule the import
job for a later time.
11.
Click Finish to complete the import operation.
12.
From the Control Panel, Click Name Management Wizard
to change the CommServe Name.
You can also right click the client in the destination CommCell. From
the Client Computer Properties dialog box, click Name Change
to change the CommServe host name.
13.
From the Name Management Wizard, select Update CommServe
for clients. Click Next to Proceed.
14.
Select the old CommServe hostname from which you wish to
migrate the clients to the current CommServe and click Next to proceed.
15.
Select the clients that you wish to update with this change
from the list and click Finish to complete the migration process.
The following section describes the process of performing a temporary migration
of a CommCell. You may be need to perform a temporary migration in any of the following
cases:
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.
When performing CommCell Migration you will first need to export the metadata
associated with the source CommCell. The export operation is performed on the source
CommCell, allowing you to select entities that you wish to export from a source
CommCell to the specified export location.
Follow the steps given below to temporarily export the metadata from a source
CommCell on to a destination CommCell:
1.
From the CommCell Browser, right-click the CommServe, click
All Tasks, click CommCell Migration and select Export
To Folder.
Make sure to specify only the names of clients that you wish to
temporarily migrate during the Export process.
2.
From the General tab on the Export Options
dialog box, provide the export location in the Export Folder field.
Select Use local for a local path. Select Use Network for
a network 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. Select Use Other CS Host to specify other CommServe
along with its local path as a host for migration. Select a database from
Export entities from list to export metadata.
3.
Select the following components for migration from Select
Associations.
Client(s) that you wish to export. For a client, you can select
the individual components such as Agents, Backupsets, and/or, Subclients.
Client Computer Groups to select a client group definition for export.
MediaAgent that you wish to export. If you select Do Not Select
MediaAgents option, the MediaAgents of the selected source clients
will not be migrated.
Desired CommCell configurations such as Subclient Policies, Schedule
Policies, Users and User Groups, Alerts, and Location.
If you select Automatically Select Complete Cluster option, all
the physical and the virtual nodes of the selected source cluster will be
exported.
4.
Click Advanced to view and select the advanced exportoptions from Select Export Options dialog box.
5.
From the Job Initiation tab on the Export Options
dialog box, select Immediate run the export immediately. Alternatively,
you can schedule the export job for a later time.
The metadata associated with the client in a source CommCell can now be temporarily
imported on to the destination CommCell. The import will use the import entries
that you have defined for the destination CommCell.
Follow the steps given below to temporarily import metadata of a source CommCell
on to the destination CommCell:
1.
From the CommCell Browser, right-click the CommServe, click
All Tasks, click CommCell Migration and select Import
From Folder.
2.
From the Import Wizard, provide the import location
in the Import Folder field. Select Use local for a local path.
Select 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. Click Next.
3.
From Select CommCell to Import window, select a
CommCell to import and click Next.
4.
From the Source Mediatype Mapping window, provide
the media mapping options to import data from the source CommCell. Select
the library, MediaAgent, drive pool, and spare group on the destination
CommCell for importing data and click Next.
You need to map the MediaAgent in order to associate the media.
The MediaAgent should have a compatible media library to map and import
the metadata from source on to the destination CommCell.
Ensure that you copy the disk libraries to the appropriate computer
specified during the import operation.
The CV_MAGNETIC folder must have read-write access in the destination
CommCell. For example, if you make copies of the CV_MAGNETIC folder
using a disc, ensure that the contents are copied to a computer, so
that it can be accessed during a restore operation.
5.
From the Source MountPath Mapping window, you can
view the default MediaAgent, Device Name and Mount
Path on the Source CommCell for importing metadata.
The Mount Path and Library on the destination CommCell are displayed by default
in this window. If you wish to change the destination mount path, click
Edit to provide the destination Library Name and MediaAgent Name for importing
metadata. Verify the mount path mapping on the Source Mount Path Mapping
window and click Next.
If you are mapping the Source Mount path for the first time, the MediaAgent, Device Name,
destination library and Mount Paths will appear in Blue.
6.
From the Shared Library Device Mapping window, click
Edit to provide the Target MediaAgent and Device Path for importing
metadata.
Verify the device mapping on the Shared Library Device Mapping
window and click Next.
7.
From the Dedupe Database Mapping window, specify
the target MediaAgent and target single instance (SIDB) access path on the
destination CommCell for importing data and click Next.
8.
From the Client Name Mapping window, specify a new
name for the client if required. If nothing is specified the old name will
be used. Click Next.
In the case of temporary migration, it is recommended to use the
old names and mapping for continuous replication from source CommCell.
9.
From the Import Options window, review the selected
import options and click Next.
10.
From the Import Options window for client import
and datapath options, review the selected import options and click Next.
11.
From the Job Initiation window, select Immediate
to start the import process. Alternatively, you can schedule the import
job for a later time.
12.
Click Finish to complete the import operation.
13.
From the Control Panel, Click Name Management Wizard
to change the CommServe Name.
You can also right click the client in the destination CommCell. From
the Client Computer Properties dialog box, click Name Change
to change the CommServe host name.
14.
From the Name Management Wizard, select Update CommServe
for clients. Click Next to Proceed.
15.
Select the old CommServe hostname from which you wish to
migrate the clients to the current CommServe and click Next to proceed.
16.
Select the clients that you wish to update with this change
from the list and click Finish to complete the migration process.
You can view the CommCell Migration job history from the Admin Job History window.
Once a migration job is completed, it may be useful to view specific historical
information about the job, such as the following:
Details of the job
Events of the job
Log files of the job
From the CommCell Browser, right-click the CommCell whose migration history
you want to view, click View, and then click View Admin Job History.
For the source CommCell, select the CommCell Export as job type from
the Admin Job History filter window to view the export history.
For the destination CommCell, select the CommCell Import as job type
from the Admin Job History filter window to view the Import history.
Select the desired filter options such as time range, job status, number
of jobs etc.
Ensure that you check the barcodes associated with the tapes in the CommCell
to make sure that there are no duplicate barcodes across all CommCells being
migrated. If you find two tapes that have the same bar code, one of them needs to be changed.
When you migrate a mount path that contains deduplicated data, the
Interval (Minutes) between disk space updates
parameter is created with a default value in minutes. This value will ascertain
the time taken by MediaManager to automatically detect and update the new mount
paths for deduplicated data. This in turn will determine the time to restore
the data on the new target MediaAgent.
The migrated mount paths and their corresponding migrated device
controllers will be marked read only to ensure data is not corrupted. This
means that no new backups can be written to the migrated mount paths and also
no data can be pruned from the migrated mount paths. The migrated data is
read-only and used for restore purposes. To write new backups,
you need to create new local libraries with local mount paths (using a local
read/write device), or add a new read/write device, device controllers and mount paths to an existing library after the migration.
To enable pruning on the mount path after a
MediaAgent is permanently migrated to a new CommCell, enable
read/write on the device controller pointing to the mount path. See
Modify the Access Type for Shared Disk Device for step-by-step
instructions.
After a client is permanently migrated to a new CommCell, the
backup for each of its subclients will automatically be converted to a full
backup. This is to make sure that the metadata is disassociated from the old CommCell and recreated
in the new CommCell.
All the migrated Dedupe stores will be sealed on destination CommServe
after migration.
