General Questions

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.

Can CloudEndure protect or migrate physical servers?

Because CloudEndure works at the OS layer it can protect and migrate not only virtual servers but physical ones as well. In the case of DRThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event., CloudEndure can also FailbackThe process of restoring operations to a primary machine or facility after they have been shifted to a secondary machine or facility during Failover. to a physical server.

Does CloudEndure have a more restrictive IAM policy for AWS?

The general AWS IAM policy required for CloudEndure can be found here.

For organizations requiring a stricter policy, there are two JSON files that can be used:

• Restricted_IAM_Policy_Tag_Dependent.json can be utilized for generic (on-prem or other cloud provider) to AWS.
• AWS-AWS-Restrictive.json can be utilized for AWS to AWS replication.

Note: The [BRACKETED VALUES], including the brackets [] need to be replaced with your respective account values.

What data is stored on and transmitted through CloudEndure servers?

CloudEndure store only configuration and log data on the CloudEndure Service ManagerThe CloudEndure server.'s encrypted database. Replicated data is always stored on the customer’s own cloud VPC. The replicated data is encrypted in transit.

What is the Recovery Time Objective (RTO) of CloudEndure?

The Recovery Time ObjectiveRelated to downtime. The metric refers to the amount of time it takes to recover from a data loss event and how long it takes to return to service. The metric is an indication of the amount of time the system's data is unavailable or inaccessible, thus preventing normal service. (RTORelated to downtime. The metric refers to the amount of time it takes to recover from a data loss event and how long it takes to return to service. The metric is an indication of the amount of time the system's data is unavailable or inaccessible, thus preventing normal service.) of CloudEndure is typically measured in minutes. The RTORelated to downtime. The metric refers to the amount of time it takes to recover from a data loss event and how long it takes to return to service. The metric is an indication of the amount of time the system's data is unavailable or inaccessible, thus preventing normal service. is highly dependent on the OS boot time.

What is the Recovery Point Objective (RPO) of CloudEndure?

The Recovery Point ObjectiveA metric indicating of the amount of data at risk of being lost. Determined by the amount of time between data protection events and reflects the amount of data that potentially could be lost during a disaster recovery. The maximum targeted period in which data might be lost from an IT service due to a major incident. (RPOA metric indicating of the amount of data at risk of being lost. Determined by the amount of time between data protection events and reflects the amount of data that potentially could be lost during a disaster recovery. The maximum targeted period in which data might be lost from an IT service due to a major incident.) of CloudEndure is typically in the sub-second range.

Does Disaster Recovery work with the Microsoft Windows Failover Clustering?

Yes, it does.

However, when the DRThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. system is brought up on your TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). cloud, the DRThe CloudEndure solution that enables the recovery or continuation of vital technology infrastructure and systems in case of a crippling event. copy of the cluster will be a single SQL Server machineA physical or virtual computer. as a cluster requires shared storage and shared storage is not supported on the cloud.

Because of that, there are two ways to achieve this using CloudEndure, each with a different trade off:

1. Install a CloudEndure AgentThe Agent is a software program that is installed on machines in the Source location that need to be migrated or replicated to the Target location. on all the machines in the cluster and replicate the SQL disk every time. The limitation is that if the source cluster is X machines that have Y storage each, CloudEndure will maintain the Y storage X times on the cloud for replication (resulting in X times Y used storage).
2. Install an AgentThe Agent is a software program that is installed on machines in the Source location that need to be migrated or replicated to the Target location. only on the primary node. The limitation is that while there is a failoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time. to a different node, the RPOA metric indicating of the amount of data at risk of being lost. Determined by the amount of time between data protection events and reflects the amount of data that potentially could be lost during a disaster recovery. The maximum targeted period in which data might be lost from an IT service due to a major incident. grows.

Note that once migration completed, the cluster on the Target machineThe Machine created during Test, Cutover or Recovery. has to be broken and HA needs to be set up differently. There are several common alternatives which do not require shared storage, such as primary-replica configuration or synchronous replication.

Where can I find the ClouldEndure API documentation?

You can find our API documentation here.

Our API is a standard RESTful API and can be used by any language allowing HTTPS requests.

You can use the following Python script to list your machines:

Can CloudEndure run a script upon Target machine boot?

CloudEndure can run scripts on a Target machineThe Machine created during Test, Cutover or Recovery. after it's launched. This is done by placing scripts in the following folder 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.:

Linux: /boot/post_launch (any files that are marked as executable)

Windows: c:\Program Files (x86)\CloudEndure\post_launch (any .exe, .cmd or .bat files)

Once you put these scripts in the above folders 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., the folder will be replicated to 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). and be executed once after the target machineThe Machine created during Test, Cutover or Recovery. boots the first time.

What to consider when replicating Active Directory

There are two main approaches when it comes to migrating or protecting Active Directory or domain controllers from a disaster:

1. Replicating the entire environment, including the AD server(s) - in this approach it is recommended to launch 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). AD servers first, wait until it's up and running and then launch the other 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, to make sure the AD servers are ready to authenticate them.
   
   In this case, it is important to conduct any tests using an isolated subnet 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). cloud, so to avoid having 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). machines communicate into the source AD server outside of a CutoverThe process of transitioning from one system to a replacement system. or a FailoverA backup operational mode in which the functions of a system component are assumed by secondary system components when the primary component becomes unavailable through either failure or scheduled down time..
   
2. Leaving the AD server(s) in the SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. environment - in this approach, 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). machines will communicate back to the AD server in the source environment and will take 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.'s place in the AD automatically.
   
   

Does CloudEndure work with LVM and RAID configurations?

Yes, CloudEndure works with any such configuration.

What is there to note regarding SAN/NAS Support?

If the disks are represented as block devices on the machineA physical or virtual computer., as most SAN are, CloudEndure will replicate them transparently, just like actual local disks.

If the disks are mounted over the network, such as an NFS share, as most NAS implementations are, the CloudEndure’s AgentThe Agent is a software program that is installed on machines in the Source location that need to be migrated or replicated to the Target location. would need to be installed on the actual NFS server in order to replicate the disk.

What email notifications does CloudEndure send?

You can enable built-in email alerts, which are automatically triggered by common events in the ProjectA Project is the basic organizational unit for running a CloudEndure solution. that may prevent you from meeting your objectives. The notifications can be enabled within the CloudEndure User ConsoleCloudEndure SaaS User Interface. A web-based UI for setting up, managing, and monitoring the Migration and Disaster Recovery solutions. on the Setup & Info > OTHER SETTINGS tab. Notifications are sent no more than once per hour. Notifications are only sent when there is a status change that triggers an alert. The following are the email alerts sent by CloudEndure:

• LicenseAllows the installation of the Agent on one machine. One License enables one Agent. Licenses are a part of the License Package. Expiration - Receive a single notification 30 days prior to the expiration of the CloudEndure LicenseAllows the installation of the Agent on one machine. One License enables one Agent. Licenses are a part of the License Package. associated with the ProjectA Project is the basic organizational unit for running a CloudEndure solution..
• LagA delay between the changes that occur on the Source and the replication of that changes to the Target. Lag appears when replication does not occur for a certain period of time. Exceeds Threshold - Receive a notification when Data ReplicationThe process of copying all data blocks from selected disks on a Source Machine to Staging Disks. lagA delay between the changes that occur on the Source and the replication of that changes to the Target. Lag appears when replication does not occur for a certain period of time. (RPOA metric indicating of the amount of data at risk of being lost. Determined by the amount of time between data protection events and reflects the amount of data that potentially could be lost during a disaster recovery. The maximum targeted period in which data might be lost from an IT service due to a major incident.) for a Machine exceeds preset threshold.
• LagA delay between the changes that occur on the Source and the replication of that changes to the Target. Lag appears when replication does not occur for a certain period of time. No Longer Exceeds Threshold - Receive a notification when the previously noted Data ReplicationThe process of copying all data blocks from selected disks on a Source Machine to Staging Disks. (RPOA metric indicating of the amount of data at risk of being lost. Determined by the amount of time between data protection events and reflects the amount of data that potentially could be lost during a disaster recovery. The maximum targeted period in which data might be lost from an IT service due to a major incident.) lagA delay between the changes that occur on the Source and the replication of that changes to the Target. Lag appears when replication does not occur for a certain period of time. no longer exceeds the threshold.
• Replication Stalled - Receive a notification when data replication for a Machine in the ProjectA Project is the basic organizational unit for running a CloudEndure solution. becomes completely stalled.
• Replication No Longer Stalled - Receive a notification when a machineA physical or virtual computer. for which Data ReplicationThe process of copying all data blocks from selected disks on a Source Machine to Staging Disks. was previously stalled, is no longer stalled.
• Machines Not Tested - Receive a notification if a Machine has not been tested.

Does CloudEndure support Windows License Migration?

CloudEndure conforms to the Microsoft Licensing on AWS guidelines.

Can you perform an OS (Operating System) upgrade with CloudEndure?

No. CloudEndure copies the entire machineA physical or virtual computer. as-is. However, you can copy the data disks exclusively and attach them to a new machineA physical or virtual computer. with an upgraded OS.

What are the limitations of the CloudEndure service?

1. CloudEndure only supports up to 100 ProjectsA Project is the basic organizational unit for running a CloudEndure solution. per single CloudEndure AccountThe entity that signed up with CloudEndure..
2. CloudEndure does recommend including no more than 300 machines per ProjectA Project is the basic organizational unit for running a CloudEndure solution..
3. CloudEndure does not recommend replicating more than 350 machines concurrently to the same AWS AccountThe entity that signed up with CloudEndure. and RegionA Region denotes a geographical area (US east, EU west, etc.). Each Region has multiple, isolated locations known as Zones. Zones are isolated from one another, but Zones within the same Region are connected through low-latency links. Cloud Regions exist in AWS, Microsoft Azure, and GCP..
4. CloudEndure only supports the replication of machines with up to 50 disks in accordance with these EC2 limitations.
5. CloudEndure only supports 512 BytesPerSEctor disks according to these EBS volume limitations.

How do I determine if my disks are GPT or dynamic?

CloudEndure does not support Windows disks that have GPT partitions and are dynamic for BIOS machines.

GPT

Machines running Windows Server 2003 or later versions can choose from MBR and GPT partition styles. You can find your partition style in Disk Management i> Disk > Properties > Volumes > Partition style in Windows :

You can learn how to change the partition style to the supported MBR style in this Microsoft article.

Dynamic disks

You can find your disk type through Disk Management in Windows:

Dynamic disks have been deprecated from Windows. You can learn how to change a dynamic disk back to a basic disk in this Microsoft article.

How do I test Active Directory?

If you need to run a test without shutting down the source server, then the best practice is to launch the test server in a subnet that is isolated from the source.

Does CloudEndure support disk encryptions?

CloudEndure does not support OS-based disk encryption features such as BitLocker. These should be disabled before using any CloudEndure services.

Which AWS Regions does CloudEndure use for production and disaster recovery?

CloudEndure uses AWS US East (N. Virginia) for production and AWS US West (N. California) for disaster recovery. Data is copied from the production RegionA Region denotes a geographical area (US east, EU west, etc.). Each Region has multiple, isolated locations known as Zones. Zones are isolated from one another, but Zones within the same Region are connected through low-latency links. Cloud Regions exist in AWS, Microsoft Azure, and GCP. to the disaster recovery region over a private AWS network.

What happens if a CloudEndure license expires?

Once an AccountThe entity that signed up with CloudEndure. license expires, the account will have reduced functionality for 90 days unless the license is renewed.

If the license has not been renewed 90 days after expiration, the account will be deleted.

How do I terminate my CloudEndure Account?

Any customer can terminate a CloudEndure AccountThe entity that signed up with CloudEndure. at any time by contacting Support.