This part describes how to copy an already configured cluster system.
The copy methods described here enable you to clone a cluster system or migrate it to another environment (P2P, P2V, V2V).
For migration, replace the copy source with the migration source and the copy destination with the migration destination.
Clones the cluster system of the copy source (the master cluster system) into an environment with the same configuration. You can install the same OS and software on multiple servers during initial deployment, which speeds deployment.
Figure K.1 cloning
Copy a cluster system that is already configured and migrate it to another environment.
Physical to Physical (P2P) is the copying and migration of an environment on an existing physical server into another physical environment. PRIMECLUSTER supports migration from an existing physical environment to another physical environment.
Physical to Virtual (P2V) is the copying and migration of an environment on an existing physical server into a virtual environment. PRIMECLUSTER supports physical to virtual (VMware) migrations.
Virtual to Virtual (V2V) is the migration of virtual machines between virtual or cloud environments. PRIMECLUSTER supports migrations between VMware, KVM, and FJcloud-O environments.
Figure K.2 P2P/P2V/V2V
Note
The following items are not included in the supported range:
Building a single-node cluster from multiple clusters (cases of which can be seen with Disaster Recovery and so on)
After building a single-node cluster, copying it to multiple nodes to build multiple-node clusters
Building multiple-node clusters by copying a node within the multiple-node clusters to the multiple nodes
Copying a cluster system that is built in a cloud environment other than the FJcloud-O environment
Before starting up the copy destination system, make sure that the NIC cables are disconnected or the copy source is stopped, or connect from the copy source system to an isolated network, taking care that there are no IP addresses in duplicate with the copy source system.
When you carry out copying your system environment, you should follow the conditions of the cloning or migration software/function to be used.
For migrations with system updates in the background, ensure the following. Upgrade to the appropriate version if necessary.
Sufficient transition period
Ensure business can be taken over in the destination system (renewal system)
License of the target system
Validity of the product version used at the destination (Support periods, consistency with target hardware configurations, etc.)