Migrate VM cluster(s)

Migrate VM cluster(s) in the target infrastructure using the specified source VM cluster details, including the creation of VM cluster(s) and database dbHome(s).

Ensure that the target infrastructure is in available state, input template for VM cluster(s) has been generated and modified according to the target platform requirements.

The migrate_vmcluster command supports the following options:

Syntax

exacloudmigration migrate_vmcluster [-ahVd] -i <inputFile> [-a|-l <vmClusterNames>] [-p <includePatches>] [--dry-run]

Table 2-15 exacloudmigration migrate_vmcluster Commands

Command	Description
`-a, --all`	Migrates all VM clusters to the target infrastructure from the source infrastructure.
`-i, --inputFile`	Specifies the VM cluster input file name with the complete path.
`-l, --vmClusterNames`	Specifies a comma-delimited list of VM cluster names to migrate. Examples: To migrate a VM cluster: `-l vmcluster1` To migrate multiple VM clusters: `-l vmcluster1,vmcluster2,vmcluster3`
`-d, --includeDbInputs`	Specifies to include database inputs (need `database_inputs` inside each `vm_cluster` folder).
`-p, --includePatches`	Specifies to consider One-off patches file. This option is applicable only when the source is ExaDB-C@C. Options: `-p yes`: Specify to consider `patches_file` inside the input template `vmcluster_<source_vmcluster_name>` directory. `-p nopatch`: Specify to create all target database homes with the source home base RU.
`--dry-run`	Performs dry run without creating the VM cluster(s).
`-h, --help`	Displays help information about the command and its options.
`-V, --version`	Displays the version of the utility.

Examples:

To validate the VM cluster and database input template files and perform a --dry-run:

/home/opc>./exacloudmigration migrate_vmcluster -a -i inputs/infra_phxref/cloudvmcluster_inputs --dry-run

To validate the comma-delimited list of VM clusters and database input template files and perform a --dry-run:

/home/opc>./exacloudmigration migrate_vmcluster -i inputs/infra_phxref/cloudvmcluster_inputs -l vmcluster1,vmcluster2 --dry-run

To migrate all VM clusters and database dbhome(s) in the source (ExaDB-D) infrastructure to the target (ExaDB-D) infrastructure, following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_vmcluster -a -i inputs/infra_phxref/cloudvmcluster_inputs
```
To migrate a comma-delimited list of VM clusters and database dbhome(s) in the source (ExaDB-D) infrastructure to the target (ExaDB-D) infrastructure, following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_vmcluster -i inputs/infra_phxref/cloudvmcluster_inputs -l vmcluster1,vmcluster2
```
To migrate all VM clusters and database dbhome(s) in the source (ExaDB-C@C) infrastructure to the target (ExaDB-C@C) infrastructure or source (ExaDB-C@C) infrastructure to the target (ExaDB-D) infrastructure, following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_vmcluster -a -i inputs/infra_phxref/cloudvmcluster_inputs -p yes
```
Generate the patches_file using the Generate patches file step and copy it to the input template directory (vmcluster_<source_vmcluster_name>) on the client machine for each VM cluster.
To migrate all VM clusters and database dbhome(s) in the source (ExaDB-C@C) infrastructure to the target (ExaDB-C@C) infrastructure or source (ExaDB-C@C) infrastructure to the target (ExaDB-D) infrastructure without patch file, following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_vmcluster -a -i inputs/infra_phxref/cloudvmcluster_inputs -p nopatch
```
To migrate a comma-delimited list of VM clusters and database dbhome(s) in the source (ExaDB-C@C) infrastructure to the target (ExaDB-C@C) infrastructure or source (ExaDB-C@C) infrastructure to the target (ExaDB-D)infrastructure, following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_vmcluster -i inputs/infra_phxref/cloudvmcluster_inputs -l vmcluster1,vmcluster2 -p yes
```
Generate the patches_file using the Generate patches file step and copy it to the input template directory (vmcluster_<source_vmcluster_name>) on the client machine for each VM cluster.

Note:

Along with migrating VM cluster(s) and database dbHome(s), free-form tags, SSH keys, and other VM cluster metadata are also replicated to the target.

Parent topic: Exadata Cloud Infrastructure Migration Automation Utility Functionality