InfoScale™ Operations Manager 9.0 Add-ons User's Guide
- Section I. Storage Provisioning and Enclosure Migration Add-on 9.0
- Provisioning storage
- About storage provisioning
- About creating a storage template
- Creating a storage template using VxFS file systems
- Creating a storage template using NTFS file systems
- Creating a storage template using volumes
- Updating a storage template
- Provisioning storage
- Uploading storage templates
- Downloading storage templates
- Deleting storage templates
- Locking storage templates
- Unlocking storage templates
- Migrating volumes
- Provisioning storage
- Section II. Application Migration Add-on
- Introduction to Application Migration Add-on
- Creating and managing an application migration plan
- Supported versions and platforms
- User privileges
- Prerequisites for creating an application migration plan
- Prerequisites for migration to AWS
- VVR Replication: Environment variables used in application migration
- Creating an application migration plan
- Understanding user-defined tasks
- Understanding application migration operations
- Understanding the cleanup operation
- Understanding the tasks executed in each operation
- Validations performed before migration plan execution
- Executing the application migration plan
- Editing an application migration plan
- Deleting application migration plan(s)
- Exporting application migration plan(s)
- Importing application migration plan(s)
- Viewing historical runs
- Viewing properties of an application migration plan
- Application migration logs
- Index
Prerequisites for creating an application migration plan
In this document, source cluster refers to the cluster from which the service group managing the application must be migrated and target cluster is the cluster to which the service group managing the application must be migrated to.
Ensure that the following prerequisites are met before creating an application migration plan:
Add all the nodes of the source and target cluster to Arctera InfoScale Operations Manager (VIOM) as managed hosts.
Application data must reside on a Veritas Volume Manager (VxVM) disk group.
The add-on migrates application data only on VxVM volumes (DiskGroup or CVMVolDG resources). The add-on does not migrate application data on native disks or other volume managers.
Source cluster must be in running state.
VCS and VxVM versions in the target cluster must be same or higher than the version in the source cluster.
All DiskGroup or CVMVolDG type resources in the service groups being migrated must be online.
Install and configure VCS cluster on the target managed hosts. The target cluster must also be in running state.
If Cluster Volume Manager (CVM) is configured in the source cluster, install and configure CVM in the target cluster also.
In the target cluster configuration file, include type definition files for the resource types that are being migrated.
On the source cluster, all service groups must be online.
On the managed hosts of the source and target clusters, the XPRTLD daemon must be always running.
On the target cluster, install and configure the application that is being migrated according to the application and operating system (OS) requirements.
Ensure that the application has proper service group dependencies because application migration from source to target cluster happens by migrating the service groups in which the application is configured. Dependencies for the selected service group are automatically included as a part of the migration plan.
Execute the
vxlist(/opt/VRTSsfmh/bin/vxlist) utility in the source and target cluster node. The output must not contain any errors.On the target cluster, identify the IPs that the application will use.
VVR Replication - On the source and target cluster nodes, identify IPs to create replication links. Ensure that these IPs are not used.
Depending on the Data Migration type you select, the migration plan detects any pre-existing linked break-off snapshot or VVR replication configured for each disk group between the nodes in the source and target clusters. If no pre-existing configuration is detected, the migration plan creates it and you must identify the list of disks to be used to create either the mirror disk group or remote site disk group. The disks must be under VxVM control and must have enough free space. The total size of the disks you provide must be more than the used size of the disk group in the source cluster. The number of disks must be at least same or more considering the volume layout in the source cluster.
VxVM Mirroring - Disks must be shared across all the nodes in the source and target cluster.
VVR Replication - Disks must be shared between all nodes in the target cluster only.