InfoScale™ Operations Manager 9.0 Add-ons User's Guide
- Section I. Storage Provisioning and Enclosure Migration Add-on 9.0
- Provisioning storage
- Creating a storage template using VxFS file systems
- Migrating volumes
- Provisioning storage
- Section II. Application Migration Add-on
- Introduction to Application Migration Add-on
- Creating and managing an application migration plan
- Understanding application migration operations
About Application Migration add-on
The Application Migration add-on allows you to migrate applications that are under Cluster Server (VCS) management from one cluster to another. The application migration operation is less complex and can be accomplished with minimal manual intervention. Application migration can be across operating systems, architectures, or virtualization technologies. You can migrate data using:
VxVM Mirroring
VVR Replication
You can migrate an application between different:
Platforms - AIX, Linux, and Solaris
Environments - Physical-to-physical, physical-to-virtual, virtual-to-virtual, and virtual-to-physical, on-premise to AWS cloud
InfoScale versions
From Application Migration add-on version 7.3.1 onwards, you can migrate your applications from an on-premise cluster to a cluster on AWS EC2 instance. You need to select data-migration type as VVR Replication in order to migrate your VCS workload to AWS. For more information about VVR and to understand the basic concepts, refer to the Arctera InfoScale Replication Administrator's Guide.
See Supported versions and platforms.
To migrate an application, you must create an application migration plan using the Create Migration Plan wizard. After you create a plan, you must execute the migration plan.
See Creating an application migration plan.
See Executing the application migration plan.
The add-on also allows you to:
Pause and resume the operation for manual verification and correction, if required.
Integrate custom scripts in the operation as per application requirements.
Migrate application dependencies.
Understand source cluster configuration and create target cluster configuration.
Perform endian changes to the data as per architecture requirements.
Rehearse the steps before the actual migration operation.