Arctera 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
Editing an application migration plan
After you create a plan, you can edit it if you need to modify any of the entries. When you edit a plan, the service group dependencies and disk group details are not populated from the previously saved plan, but are fetched afresh. This is to ensure that the current state of the service groups and disk groups in the source cluster are populated when you edit the plan.
Before you edit a plan, note the following:
If you edit the plan before the Setup Storage operation:
Mirroring - Re-select the disks for any mirror disk group which needs to be created for each source disk group.
Replication - Re-select the disks and re-enter the RLINK details.
Mirroring - If you edit a plan after the Setup Storage or Rehearse operation, mirror disk groups are also be displayed in the Target Disk Information panel. You must select the Use Existing option for source disk groups and select Ignore for mirror disk groups, if these were created as part of Setup Storage. The mirror disk groups will have a naming convention as
amMir_source_diskgroup_name.If you edit the plan after it is imported, any custom script execution task which was part of the imported plan must be removed and new custom script execution tasks must be added as necessary by uploading the custom scripts copied when the plan was exported.
To edit an application migration plan
- In the Management Server console, go to the Availability perspective, expand Solutions in the left pane, and click Application Migration Plan.
- In the Migration Plan pane, right-click and click Edit.
The Edit Migration Plan wizard opens.
- Edit the fields in the migration plan as necessary.
- Click Save to the save the changes in the existing plan or click Save As to save the changes as a new plan.
Note:
If you want to use the Save As option, you must change the plan name.