Migrate Exadata Infrastructure

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

Ensure that the input templates for the Infrastructure, VM cluster(s) and database(s) have been generated and modified according to the target platform requirements.

The migrate_infra command supports the following options:

Syntax

exacloudmigration migrate_infra [-ahVd] -i  -c  [-a|-l ] [-p ] [--dry-run]

exacloudmigration migrate_infra Commands

Command	Description
`-a, --all`	Migrates all VM clusters in the newly created target infrastructure from the source infrastructure.
`-i, --inputFileInfra`	Specifies the infrastructure input file name with the complete path.
`-c, --inputFileVmCluster`	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_` directory. `-p nopatch`: Specify to create all target database homes with the source home base RU.
`--dry-run`	Performs dry run without creating the infrastructure.
`-h, --help`	Displays help information about the command and its options.
`-V, --version`	Displays the version of the utility.

Examples:

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

/home/opc>./exacloudmigration migrate_infra -a -i inputs/infra_phxref/infrastructure_inputs -c inputs/infra_phxref/cloudvmcluster_inputs --dry-run

To migrate the infrastructure, all VM clusters, and database dbhome(s) in the source (ExaDB-D) to the target (ExaDB-D), following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_infra -a -i inputs/infra_phxref/infrastructure_inputs -c inputs/infra_phxref/cloudvmcluster_inputs
```
To migrate the infrastructure, all VM clusters, and the selected database dbhome(s) in the source (ExaDB-D) to the target (ExaDB-D) by specifying create=yes in database input file, following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_infra -a -i inputs/infra_phxref/infrastructure_inputs -c inputs/infra_phxref/cloudvmcluster_inputs -d
```
To migrate the infrastructure, a comma-delimited list of VM clusters, and the corresponding database dbhome(s) in the source (ExaDB-D) to the target (ExaDB-D), following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_infra -i inputs/infra_phxref/infrastructure_inputs -c inputs/infra_phxref/cloudvmcluster_inputs -l vmcluster1,vmcluster2
```
To migrate the infrastructure, all VM clusters, and database dbhome(s) in the source (ExaDB-C@C) to the target (ExaDB-D), following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_infra -a -i inputs/infra_phxref/infrastructure_inputs -c 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 the infrastructure, a comma-delimited list of VM clusters, and the corresponding database dbhome(s) in the source (ExaDB-C@C) to the target (ExaDB-D), following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_infra -i inputs/infra_phxref/infrastructure_inputs -c 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.
To migrate the infrastructure, all VM clusters and database dbhome(s) in the source (ExaDB-C@C) to the target (ExaDB-D) without the patch file, following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_infra -a -i inputs/infra_phxref/infrastructure_inputs -c inputs/infra_phxref/cloudvmcluster_inputs -p nopatch
```

Note:

Along with migrating the infrastructure, VM cluster(s), and database dbHome(s), associated metadata is also replicated to the target environment.