Target Related

Important! The information provided in this section is for general Troubleshooting guidance only. The information is provided on "AS IS" basis, with no guarantee of completeness, accuracy or timeliness, and without warranty or representations of any kind, expressed or implied. In no event will CloudEndure and/or its subsidiaries and/or their employees or service providers be liable to you or anyone else for any decision made or action taken in reliance on the information provided above or for any direct, indirect, consequential, special or similar damages (including any kind of loss), even if advised of the possibility of such damages. CloudEndure is not responsible for the update, validation or support of troubleshooting information.

What does the CloudEndure Machine Conversion Server do?

The Machine ConversionThe process of converting machines from Source hardware configuration to Target hardware configuration. Server converts the disks to boot and run in the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructure.

Specifically, the Machine ConversionThe process of converting machines from Source hardware configuration to Target hardware configuration. Server makes bootloader changes, injects hypervisor drivers and installs cloud tools.

Is it possible to populate a Target machine Blueprint using the API?

Yes. All API sample scripts can be found here.

For AWS to AWS replication, does CloudEndure configure the Target VPC?

When performing AWS to AWS replication, CloudEndure will configure the target VPC as well.

The replicated environment consists of any AWS settings you defined in the VPC of the SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. site. It can include, among others: VPC, subnets, security groups, route rules, ACL rules, NAT instances (not Gateways), ELB, and other AWS configurations.

How do I change the server AMI on AWS after Migration?

After the machineA physical or virtual computer. has been launched by CloudEndure switching the AMI can be done by launchingAfter the replication to the Staging area, launching is the process of setting up the Replication Servers, for Testing or Cutover and Recovery purposes. a vanilla machineA physical or virtual computer. from the required AMI, stopping that machineA physical or virtual computer., detaching all the disks (including the root) and then attaching the disks from the target machineThe Machine created during Test, Cutover or Recovery. created by CloudEndure.

Which AWS services are automatically installed when launching a Target instance?

CloudEndure automatically installs EC2Config. After installation, EC2Config automatically installs the SSM EC2 Configuration Service. EC2Launch + SSM are installed on Windows 2016/2019. EC2Config (that has SSM bundled with it) is installed on older Windows versios.

CloudWatch, AWS Powershell or CLI are not automatically installed. This can be done by combining the CloudEndure APIs and the AWS APIs - you can use the CloudEndure APIs to determine the EC2 instance IDs of the machines and then use AWS API/CLI to turn on the detailed monitoring. An alternative approach would be to do it via AWS API only based on the tags you associate with the machineA physical or virtual computer.. A third approach would be to do so from the post-launch script.

CloudEndure installs EC2Launch (Windows 2016/2019 only.) Customers need to configure EC2Launch based on the specific requirements explained here. This configuration step needs to be performed post MigrationThe CloudEndure solution that allows you to move data, applications, and other business elements from an onsite network or a cloud environment to another physical location or cloud environment. or Recovery using the wizard in C:\Program Data\Amazon\EC2-Windows\Launch\Settings\Ec2LaunchSettings.exe on the Target machineThe Machine created during Test, Cutover or Recovery..

How long does it take to copy a disk from the CloudEndure Staging Area to production?

CloudEndure uses internal cloud provider snapshots. This process typically takes less than a minute and the size of the volume does not impact the time.

What are the differences between Conversion Servers and Replication Servers?

• Replication ServersThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. run on Linux and Conversion Servers (for Windows machines) run on Windows.
• The conversion is done by CloudEndure automatically bringing up a vanilla Windows Conversion ServerThe CloudEndure machine launched in Target region for the purpose of performing Machine Conversion. machines in the same subnet with the Replication ServersThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. as part of the launch jobDesignates several procedures within the CloudEndure Console, including launching Test or Recovery machines, the deletion of Target machines, and other tasks..
• Both Conversion and Replication serversThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. have Public IPs
• The Conversion Servers will use the same Security Groups as the Replication ServerThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location..
• The Conversion ServerThe CloudEndure machine launched in Target region for the purpose of performing Machine Conversion. must be able to access the CloudEndure Service ManagerThe CloudEndure server..

• The Conversion ServerThe CloudEndure machine launched in Target region for the purpose of performing Machine Conversion. machines, just like the Replication serversThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. are managed automatically by CloudEndure. Any attempt to disrupt their automated functionality will result in failed conversions.

Can I prevent CloudEndure from cleaning up Target test resources in AWS?

CloudEndure will, by default, removes any resources created during the test process either when requested by the user or when a new test machineA physical or virtual computer. is launched.

To prevent this in AWS, you can enable Termination Protection, for the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). instance, and the resources will not be removed upon a new TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). launch.

Can you select availability zones for AWS as a Target?

In AWS, every subnet is in a specific availability zone. This means that once you select a subnet, you also select the availability zone.

How can I safely test my Domain-Joined server replica without conflicting with the original server?

You can achieve this in three ways:

1. Create a local account on the Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine., create the Target machineThe Machine created during Test, Cutover or Recovery. on an isolated network and use the local account rather than the domain account to login.
2. Use CloudEndure to replicate the domain controller along with the machineA physical or virtual computer. into an isolated network and then the Target machineThe Machine created during Test, Cutover or Recovery. will use the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). domain controller.
3.  
   1. Use CloudEndure to replicate the machineA physical or virtual computer. into an isolated network (different subnet or block AD access using FW/SecurityGroup rules)
   2. Log into the Target machineThe Machine created during Test, Cutover or Recovery. locally as an admin (requires local admin account)
   3. Leave the domain locally with the aid of this Remove-Computer tool
   4. Rename the machineA physical or virtual computer. (change the hostname)
   5. Remove the network isolation (either connect it back to the AD, remove the firewall, or create an AMI and run it in the new (TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery).) VPC/subnet)

   6. Join the same old AD Domain Controller as a new machineA physical or virtual computer. (with a new hostname)

What impacts the conversion and boot time of Target machines?

Prior to launchingAfter the replication to the Staging area, launching is the process of setting up the Replication Servers, for Testing or Cutover and Recovery purposes. the Target machineThe Machine created during Test, Cutover or Recovery., CloudEndure goes through a machineA physical or virtual computer. Conversion ServerThe CloudEndure machine launched in Target region for the purpose of performing Machine Conversion. process on the boot and root volumes. The conversion process is fairly quick.

While the actual conversion process itself is quick, the time to boot the Target machineThe Machine created during Test, Cutover or Recovery. varies depending on many factors unrelated to any CloudEndure processes. Some of these are controllable and should be taken into account when Recovery or CutoverThe process of transitioning from one system to a replacement system. times are of importance.

• Operating system - The amount of time required to boot the operating system is dependent on the OS itself. While Linux machines typically boot quickly, Windows machines may take additional time, due to the nature of the Windows OS. If opportunity permits, test the boot time of the Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine.. If Linux OS takes a long time to boot ensure to check that dhclient (Dynamic HostThe physical data center within vCenter that serves as the replicator and as a Target. 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 installed prior to launchingAfter the replication to the Staging area, launching is the process of setting up the Replication Servers, for Testing or Cutover and Recovery purposes. the Target machineThe Machine created during Test, Cutover or Recovery.. 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. It is recommended that boot volumes be tested with a higher performance SSD and even by provisioning IOPs to ensure throughput. 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.

Note: The first boot of Windows machines on AWS may take up to 45 minutes due to Windows adjusting to the AWS virtual hardware.

How is the AWS Licensing Model Tenancy chosen for CloudEndure?

CloudEndure confirms to the Microsoft Licensing on AWS guidelines.

Do vCenter machines utilize DHCP?

vCenterVMWare's virtual environment management platform. TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines inherit the network from the SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines, and therefore do not necessarily utilize DHCP.

vCenterVMWare's virtual environment management platform. Replication ServersThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. always utilize DHCP.

What does the Tested Recently status mean?

The Tested Recently status indicates that the machineA physical or virtual computer. has been tested within the last 90 days.

Will CloudEndure reserve EC2 capacity for recovery?

CloudEndure relies on EC2 On-Demand pools by default. If a specific EC2 instance type is unavailable to support your recovery, CloudEndure will automatically attempt scale up the instance repeatedly until an available instance type is found, but in extreme circumstances, instances may not always be available. To guarantee availability of the required instance types you need for your most critical applications, you may purchase AWS EC2 Reserved Instances.