While the actual conversion process itself is quick, the time to boot the target server varies depending on many factors unrelated to any CloudEndure process. Some of these are controllable and should be taken into account when recovery or cutover times are of importance.
- Operating system - The amount of time required to boot the operating is dependent on the OS itself. While Linux servers typically boot quickly, Windows servers may take additional time, due to the nature of the Windows OS. If opportunity permits, test the boot time of the source server.
If Linux OS takes a long time to boot ensure to check that dhclient (Dynamic Host Configuration Protocol Client) is installed and the system so it can pull an IP.
- Scheduled Windows Updates - If the Windows server has pending patches, ensure those are performed prior to launching the target server. If pending patches remain, the boot time in the cloud may be severely impacted as the patch process may commence upon the initial boot.
- Boot volume type - Depending on services/applications, boot time may be impacted by disk performance. By default, CloudEndure sets the boot volume to provisioned SDD within the blueprint. It is recommended that boot volumes be launched with these types of high-performance disk. This may be more critical during the first initial boot of the server in the cloud, as all initial settings are applied. In many cases, the boot volume type may be scaled back after the initial boot and should be tested.