Migration

Migration moves a VM running PSQL from one physical host to another. The memory, storage, and network connectivity of the VM are typically migrated to the destination. Depending on the hypervisor, migration is sometimes referred to as “live” migration or “hot” migration.

With a “live” or “hot” migration, client connections to PSQL remain intact. This allows changes to hardware or resource balancing. With a “cold” migration, network connectivity is interrupted because the VM must boot. Client connections to PSQL must be reestablished.

A migration environment has only one instance of PSQL running, which makes the environment somewhat vulnerable if the host machines crashes or must be quickly taken offline. Also, if the shared storage fails, the database engine cannot process reads from or writes to physical storage. Some hypervisors offer a migration solution that does not use shared storage.

As long as host names remain the same after the VM migrates, PSQL continues to operate normally. The product key remains in the active state.

No special steps are required to install or configure PSQL in a migration environment. Refer to the hypervisor documentation.