When I tested a failover, it didn't work. I set up a test, deleted the source, and went to fail it back, and it didn't work. 

The solution doesn't need any new features.

AWS is no longer using the solution anymore. 

The solution never reduced our system's downtime. It would take us about a day to get the network configured properly for even doing a network failover test. The solution's orchestration capabilities did not simplify our disaster recovery process.

The solution's network setup and a lot of the control tower setup could be improved. The solution should provide more ease of use for the creation of cloud appliances for firewalls.

I have not seen any areas that need improvement at this time.

The failback could be improved. It should be more intuitive.

One item that they did fix was, and this was when we first started, they had only one type of license. Then they did come out with a Tier 2 type of license, which costs a little less money. It updated a little less frequently, which seems to fit our needs. That was definitely helpful. 

There are some servers where we do get failures with the CloudEndure client. I don't know necessarily if it's the CloudEndure issue, but it's something that my engineers fixed on our end. It's always something that's easily repairable, though. There is a constant update of the servers. 

It's a fairly simple product once the infrastructure's in place. We did hire a third-party to help us build the AWS infrastructure to work with CloudEndure, but once it was up and running, it  pretty much runs on its own now.

Definitely there should be better logging. From a customer perspective I would like to see more logs on what is happening. If there is an issue, I would like to know what the problem is. Right now, we have to depend on the support of the vendor to check and let us know, because we don't have access to a lot of logging information.

Also the UI could be a little sleeker.

Sometimes, one of the servers will get behind for one reason or another, and it does not notify us when that happens. This could be a helpful improvement.

It could be a bit more automated. When we wanted to start using replicated data, the process was complex. For example, with Amazon we needed to stop replication of CloudEndure, and needed to create another instance of our server. Only after that are we able to start using the data, and by then the data is outdated. Therefore, the data becomes outdated quickly. To actually start replicating the data, I need to start a manual process which takes time.

I would like to see better support for creating and working with archives. Right now, it is difficult and painful to do. When you are working with multiple terabytes, there are no good solutions.

The three things that could improvement are:

• The user interface
• Customer support
• Recovery time for the current customer query