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
Exporting application migration plan(s)
You can export any application migration plan to your system. It can be a single plan or multiple plans. Exported plans are saved in JavaScript Object Notation (JSON) format. Use a JSON viewer to view the contents of the exported file. The file created upon export can be used for importing the plan, if a plan needs to be imported on same or a different Management Server.
When you export multiple plans simultaneously, only a single JSON file is created. This file contains all the entries of the exported plans. You can edit the JSON file, but you must not modify the JSON syntax structure of the file. If you modify the JSON syntax structure, the import operation fails. If multiple plans are part of a single JSON file, you can remove the entries of a plan from the JSON file without modifying the syntax structure. Arctera recommends to change the value of only the following entries in the JSON file. Based on the value of these entries, the value of the remaining entities are fetched when the plan is being imported:
planName - Name of the plan
description - Description of the plan
selectedSGName - Name of the selected service group
sourceClusName - Name of the source cluster
targetClusName - Name of the target cluster
When you edit the plan after exporting, you need to edit only the names of the entities listed above; the IDs are fetched during the import operation. If the entities mentioned are not available on the Management Server where the plan is being imported, the import operation fails.
Note:
Custom scripts part of the plan are not exported. You have to manually copy the custom scripts either from the Management Server (path is available in the exported JSON file) or from the location from which you uploaded the custom scripts and use it when you edit the plan.
To export application migration plan(s)
- 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, select a plan, right-click, and click Export.
The Export Plan(s) window opens.
- Click Yes.
The selected plan(s) are exported.