INTRODUCTION
HC3 Move Powered by Carbonite Migrate allows you to migrate a Windows or Linux physical, virtual, or cloud server workload to the HC3 solution with real-time replication and near-zero downtime failover-all managed from a single, intuitive user console. Carbonite software is hardware agnostic and operates from within all supported operating systems on physical or virtual hosts. All steps and screenshots used in this document will utilize the Carbonite Migrate version 8.2 interface.
TERMINOLOGY
Due to the partnership inherent in HC3 Move Powered by Carbonite Migrate, this guide provides the intended definition for common terminology in use between Scale Computing and Carbonite.
- Move - Carbonite software product providing a near-zero downtime migration to the HC3 solution from a physical or virtual host. Scale Computing has partnered with Carbonite to offer Move as a migration solution for new HC3 customers.
- Console Server - The single management interface for all Carbonite Migrate tasks. No licensing is required to install the Carbonite Migrate Console service.
- Source Server - The existing server in the local environment, physical or virtual, intended to be migrated to the HC3 system. A Source server will require a single Source license. A Source license is active for 30 days once applied to a server before it expires.
- Target - The HC3 VM used as a container destination for the existing Source environmental workload. A Target server will require a Target license code. A Target license does not expire.
- Job - A broad term that entails the connection between a specific Source and Target server for the purpose of workload migration through Carbonite Migrate. This includes the data being mirrored between the Source and Target as well as the final failover from Source to Target server.
- Mirroring - Also known as replication or syncing and not to be confused with the HC3 to HC3 replication feature. This is the process of copying all server attributes and data from the Source server to the Target server and keeping the attributes and data cohesive until the final failover is completed.
- Failover - The process of cutting over from running the server workload on the Source server to running the workload on the Target server. This includes all final mirroring data, any attributes that may have been locked by the Source server operating system until this point, shutting down the Source server, and bringing all workload access up on the Target server. The intention is for the environment to see nothing more than a "reboot," although all workloads and connections have moved from the Source server to the Target HC3 VM.