migrate (Class Management)--Migrate a Class

Migrate a class from/to a remote grid

class migrate remote_grid class [ .name=newclass ] [ --export | --import ] [ --nocompress ] [ --nocleanup ] [ --debug ]

remote_grid: Name of remote grid
class: Name of the class to migrate. The class may be in a global or local catalog or may be a singleton.
.name=newclass: Optional new name for migrated class. The name may refer to a global or local catalog or may refer to a singleton.
--export: Migrate the class TO the remote grid.
--import: Migrate the class FROM the remote grid.
--nocompress: Do not compress class volumes during migration. This option is useful when migrating classes that have large volumes.
--nocleanup: skip cleanup upon failure or completion (troubleshooting)
--debug: show debug information during migration (troubleshooting)

class migrate myoldgrid.3tera.net /mycat:myclass

migrate catalog class to the current grid.

class migrate myoldgrid.3tera.net /mycat:myclass .name=myapp:myclass

migrate catalog class to the current grid as an application singleton.

class migrate mynewgrid.3tera.net /myapp/local:myclass .name=/mycat:myclass --export

migrate local catalog class to the remote grid as a global catalog class.

If neither the --export or --import options are specified, the class is migrated FROM the remote grid.
The class MUST NOT exist on the destination grid.
When accessing the grid via SSH, SSH agent and agent forwarding must be enabled on the client machine for the remote grid access to work. In addition, either the user's or the grid's public SSH key must also be installed on the remote grid to set up a "trust" between the two grids.
The --nocompress option is useful when migrating classes that have very large volumes.
Classes migrated to a grid of a different architecture (for example x86 vs. s390x) must have boot volumes capable of booting on both architectures to be usable.