The CommCell Migration feature enables you to move Client(s) or MediaAgent(s)
from one CommCell to another. This eliminates the need to uninstall/reinstalling
and recreate all the associated components for a Client/MediaAgent. You can also
move 8.0 version clients from 9.0 version CommServe to 8.0 Version
CommServe.
You can select individual content associated with a Client (for e.g., Agents, Backupsets, Subclients etc.) that you wish to move form one CommCell to another.
The existing backup information will also be moved from the source CommCell to
the destination CommCell.
You can select the configuration (for e.g., Subclient Policies, Schedule
Policies) associated with a CommCell for migration.
You can migrate previous version clients from an upgraded/current version CommServe to
previous Version CommServe. Ensure that the same version of SQL database is used in both
the CommServes while performing a cross version migration.
what is Migrated
what is not Migrated
Client computers from the previous version and the Agents installed on these Clients.
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.
Client entities such as holidays, operation window, activity
control etc.
The data and binaries that are associated with metadata.
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.
Use the following steps to perform cross version migration:
From the CommCell Browser, right-click the <Source CommServe> in which you want to add
the registry key, and then click Properties.
In the Location list, type
HKEY_LOCAL_MACHINE/SOFTWARE/CommVaultSystems/Galaxy/<Instance>/CCM
In the Type list, select REG_DWORD.
In the Value field, type 1
to enable crossversion migration.
Click OK.
From the CommCell Browser, right-click the <Source CommServe>,
point to All Tasks, click CommCell Migration and then click Export To
Folder.
Type the path or click Browse to select the location of an export folder.
You can select any of the following options for accessing an export
location:
Use local for a local path
Use Network for a network location
Use Other CommServe to specify other CommServe along with its local
path as a host for migration
In the Export entities from database list, click a database if
the clients to be migrated are from other database than the one selected by default.
Under Select Associations, select Automatically Select Complete Cluster option to
export all the physical and the virtual nodes of the source cluster.
Select previous version client(s) that you wish to export from Client
Computers list. If you select a current version client, the export job will skip
this client and continue with the cross version capture/export.
Click OK. The following files are created in the specified export folder:
answerfile.xml
capture.dmp
CCM_MediaInfo_XXX.txt
CommcellMigration.xsl
In the specified export folder,
edit the following details in answer.xml file:
Under the DataPath Information for tape/optical libraries,
type the Library Alias Name and MediaAgent Name for each
Storage_Policy Name and Copy Name in the destination
CommServe.
Under the Mount Path Information for magnetic libraries, type
the Destination Mount Path and the magnetic Library Alias Name
in the destination CommServe.
Optionally, you can also type the New Client Name and New
Client Host Name to change the name of the client and the Host Name
in the destination CommServe.
Migrated clients can be deconfigured from
source CommServe before renaming the client in the answer file.
Click Save.
From the Command Prompt in the destination CommServe, type the following
qoperation merge command to perform a
merge operation:
This command reads the answer file for the merge configuration and
performs merge operation in the destination CommServe. You can specify
whether or not to consume a license during this merge. On successful
completion of merge operation, qoperation merge
displays the following message:
Merge Successful
In case of an error, an error code and the error description are
displayed in the following format:
merge: Error errorcode:
errordescription
After a successful merge operation, the merged clients must be configured to use the destination CommServe. From the
destination CommCell browser, click the Control Panel button in the
toolbar.
Double-click the Name Management icon.
Select the Update CommServe for Clients post Migration or Split
check box.
Click Next.
Select the source CommServe name from the Old CommServe Host Name
list.
Click Next.
Select the clients that are migrated to the destination CommServe from the Available list. Use the arrow button to move
them to the Selected list.
The CommCell merge settings for performing migration of clients and
configuration from source CommCell to destination CommCell can be configured
globally from the CommCell Console. When you set the merge settings from
CommCell console, the configuration can be used globally for all the future
migration jobs. For example, if you specify the export and import folders,
configure the media, mount path, client answers, Dedupe and Device access paths in the merge settings, they will automatically appear in
the export options and import wizard.
Follow the steps given below to configure merge settings::
From the CommCell Browser, right-click the CommServe,
click Control Panel, and select Commcell Merge Settings.
From the General tab on the CommCell Merge Settings dialog box, provide the export location in
the Default 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. 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.
From the Media tab, provide the Media Type, Library, Media Agent,
Drive Pool and Spare Group for a destination CommCell.
From the Mount Path tab, click Edit to provide the
destination mount path details for importing data.
From the Client Answers tab, specify a new
name(s) for source client(s). If you do not specify a new name, the
destination CommCell imports the metadata with the source client and
client host name(s).
From the Dedupe path tab, specify the target
MediaAgent and target SIDB/SILO access path on the
destination CommCell for importing data.
From the Device path tab, specify the target
MediaAgent and target device path on the
destination CommCell for importing data.
Click OK to set the configuration for all the
migration jobs.
The following section describes the process of migrating the configurations i.e., non-data bearing entities associated with a client from a source CommCell
to destination CommCell(s).
This migration of configuration is useful
when you want to use the same set of configurations across multiple
CommCells. For example, you have created a Schedule Policy and want to use it
for all the CommCells, you can migrate configuration alone across the other
CommCells.
The configuration includes the following entities:
Subclient Policies
Schedule Policies
Users and User groups
Alerts
Media Locations
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.
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.
Follow the steps given below to migrate configurations:
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 components for migration from Select
Associations.
From Configuration, select the CommCell
configurations such as Subclient Policies, Schedule Policies, Users
and User Groups, Alerts, and Location.
4.
Click Advanced to display the Select Export Options dialog
box to view the selected client export options.
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.
6.
Click OK to export the metadata. After the
successful export operation, you can specify corresponding entities for the
destination CommCell for the entities associated with the source
CommCell in Import Wizard.
7.
From the CommCell Browser, right-click the CommServe, click
All Tasks, click CommCell Migration and select Import
From Folder.
8.
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.
9.
From Select CommCell to Import window, select a
CommCell to import and click Next.
10.
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.
11.
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.
12.
From the Specify Target Device Path and MediaAgent
for Imported Devices 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.
13.
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.
14.
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.
15.
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.
If you have the same configuration in the destination CommCell as that
of the source CommCell, you can opt for any of the following options from
Import Options page of Import Wizard:
Fail if entity already exists: Select this option to fail the import if
the same entity exists in the destination CommCell.
Force Overwrite: Select this option to overwrite if you need to retain
the same entity that already exist on the destination CommCell.
For example, if you have the same alert in source CommCell and
destination CommCell, you may want to fail the migration or overwrite the
existing alert.
If you have entities in destination CommCell which are not present in
source CommCell, you can opt for any of the following options from Import
Options page of Import Wizard:
Delete Entities not present : Select this option if you wish to delete
the migration elements that are available in destination CommCell and not
present in the source CommCell.
Delete Entities If Only from Source: Select this option to delete
entities if available only on source. If the destination CommCell may
consist of the entities that may have merged from other CommCell. The same
entities may also be present in the source CommCell. In such cases, this
option will be helpful.
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.
16.
From the Import Options window, review the selected
import options and click Next.
17.
From the Job Initiation window, select Immediate
to start the import process. Alternatively, you can schedule the import
job for a later time.
In order to share a library among MediaAgents, either directly or via a
Storage Area Network (SAN), you must properly configure and map the resident
drives. If you want to modify the configuration of a shared library, use the
Library and Drive
Configuration window. The Shared Disk Device tab in Library and Drive
Configuration window allows you to 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.
After CommCell migration, the deduplication store operates in the read-only
mode on the destination CommCell. The migrated (deduplication enabled) storage
policies on the destination CommCell can be used to restore the deduplicated
data migrated from the source CommCell and perform auxiliary copy jobs with the
migrated data as the source. However, the migrated storage policies on the
destination CommCell cannot be used to perform new deduplication backup jobs.
After CommCell Migration, you may no longer require the configured mount
paths for deduplicated data on destination CommCell. When a mount path is no
longer required, disable write operations on the mount path. This prevents the
mount path from being used for subsequent write operations. 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. You can create a new SIDB mount path for migrated magnetic libraries on
the destination CommCell.
To ensure that a mount path with sufficient space is available in the library
at all times, you can have a dedicated mount path that is reserved for Silo
restore operations only. When reserved for Silo restores, the number of data
writers to the mount path is set to zero and this prevents the mount path from
being used for regular backup operations.
Make sure to use the same barcode while restoring silo storage on destination
CommCell.
When using global deduplication, by default all deduplication store
operations are performed on the Primary copy of the Global Deduplication Policy.
You can seal the store, mark the active media full, and reconstruct the
deduplication store if configured.
Once you initiate the migration, a job is generated in the Job Controller.
Jobs can be managed in a number of ways. The following sections provide
information on the different job management options available:
If necessary, 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. Once you resubmit the job, you will also
have the ability to edit the schedule pattern (e.g., daily, weekly, monthly,
etc.) and the job options, (e.g., if it is a schedule for a backup job, then the
job options would be the the type of backup, full, differential, etc.).
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. Click OK.
The specified jobs are displayed in the Admin Job History window.
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. Only preemptible jobs can be suspended.
Resume
Resumes a job and returns the status
to Waiting, Pending, Queued, or Running depending on the availability of
resources or the state of the operation windows and activity control settings.
Backup jobs for this Agent are resumed from the point-of-failure.
Kill
Terminates a job.
To control a job:
From the Job Controller of the CommCell Console, right-click the job and
select Kill, Suspend, or Resume as desired.
When killing a job:
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.
When suspending a job:
The job status may change to Suspend Pending
for a few moments while the operation completes. The job status then changes
to Suspended.
When resuming a job:
As the Job Manager attempts to restart the job,
the job status changes to Waiting, Pending, or Running.
