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
Validations performed before migration plan execution
Before a plan is executed, validations are performed in order to check the state of the clusters, service groups, and the resources monitoring the disk groups.
In some scenarios:
If the validation fails, the plan will be marked as an Invalid Plan.
Even though the plan is marked as Invalid, the plan can be executed after taking necessary corrective steps.
After taking the corrective steps, you must edit the plan before executing it.
Table: Validations performed lists the validations performed before a plan is executed and the state of the plan if the validation fails. It also lists when the plan will be marked as invalid or not and the necessary corrective steps.
Table: Validations performed
Object | State | Is the plan invalid? | Will the plan remain invalid forever? | Corrective Action |
|---|---|---|---|---|
Source cluster | Deleted | Yes | Yes | Edit the plan, select any service group of an existing source cluster that needs to be migrated and execute the plan again. |
Source cluster | Faulted | No | No | Resolve the issues in the source cluster. Ensure that the cluster is not in faulted state in VIOM and execute the plan. |
Target cluster | Deleted | Yes | Yes | Edit the plan, select an existing target cluster to which migration needs to be performed and execute the plan. |
Target cluster | Faulted | No | No | Resolve the issues in the target cluster. Ensure that the cluster is not in faulted state in VIOM and execute the plan. |
Service group | Deleted | Yes | Yes | Edit the plan and reselect any existing service group in the source cluster that needs to be migrated and execute the plan. |
Dependent service groups | Deleted | Yes | No | Add the dependent service group that was deleted and execute the plan. |
Disk group resource | Deleted | Yes | No | Add the disk group resource that was deleted and execute the plan. |
Disk group resource offline | Offline | No | No | Bring the disk group resource online and execute the plan. |
Disk group | Deleted | Yes | Yes | Edit the plan so that the current state of the managed hosts is detected by the wizard. Save the plan and execute it. |
Volume | Deleted | Yes | Yes | Edit the plan so that the current state of the managed hosts is detected by the wizard. Save the plan and execute it. |