Shell Commands › Application Control › migrate (Application Control and Management)--Migrate Application

migrate (Application Control and Management)--Migrate Application

Migrate an application from/to a remote grid. Application configuration parameters may be specified for the new application.

Syntax

app migrate <remote_grid> <app> [.name=<new name>] [.local_ip=<local>.remote_ip=<remote>] [.encr_key=<encr_key>] [<option>]* [<prop>=<val>]*

Options

.name=<new name>

New name for the migrated application

.local_ip=<local>

IP information to be used for the migrator application on the local grid. The value has the following format:

[_vlan.][<vlan id>.]<ip address> |  _net.<network name>.<ip_adress> | _net.<network name>.<ip_address>

.remote_ip=<remote>

IP information to be used for the migrator application on the remote grid. The value has the following format:

[_vlan.][<vlan id>.]<ip address> | _net.<network name>.<ipdress>

.encr_key=<encr_key>

Specifies the name of a volume containing encryption keys to be supplied to the migration applications performing the volume migration.

--export

Migrate the application TO the remote grid. This requires bi-directional trust between the two grids.

--import

Migrate the application FROM the remote grid

--nocompress

Do not compress volumes when migrating application

--novols

Do not migrate the application volumes (only descriptors)

--nocleanup

Skip cleanup upon failure or completion(troubleshooting)

--debug

Show debug information during migration(troubleshooting)

--preserve_acl

Preserve the application ACL if it is present.

--preserve_local_acl

Preserve local principals in the application ACL.

Parameters

<prop>=<val>

Config parameter pairs as used for the 'app config' command.

Examples

app migrate myoldgrid.3tera.net myapp

Migrate application from a remote grid to the local grid.

app migrate grid1.3tera.net crm7 usr_ip=64.4.47.21 out_ip=64.4.47.22

Migrate application from a remote grid and configure IP settings.

app migrate myoldgrid.3tera.net myapp .name=mynewapp

Migrate application from a remote grid and rename it in the process.

app migrate mynewgrid.3tera.net myapp --export

Migrate application from the local grid to the remote grid.

app migrate mynewgrid.ca.net myapp .local_ip=1.2.3.4 .remote_ip=2.3.4.5

Migrate application between grids with different architectures

Notes

• .local_ip and remote_ip must be present if an application migration is being done between grids with different architectures.
• Applications that contain singleton or catalog class volumes may not be migrated between grids with different architectures.
• If neither the --export or --import options are specified, the application is migrated FROM the remote grid.
• If the original application is running, it will be stopped prior to the migration. Upon completing the migration, the new application will be started.
• If the original application is not running, the new application will not be started.
• SSH agent and agent forwarding must be enabled on the client machine for the remote grid access to work.
• --nocompress option is useful when migrating applications that have very large volumes.
• - see 'help app config' for online help on properties and resources. The full and per-property reset are not supported (--reset and -d <prop>).
• By default application ACL's are not preserved during migration.
• The “--preserve_global_acl” argument is not useful on CA AppLogic for System z® as it does not yet support external directories. Providing “--preserve_global_acl” to “application import” will produce a warning but it will otherwise be ignored.