What is our primary use case?
We rely on Arpio Disaster Recovery & Readiness for the automated disaster recovery feature and the automated failover. We have multiple regions in our infrastructure, for example, AP South-1 as one region and Singapore or another region. We set up failover policies between both regions with the help of Arpio, which is a cloud-native disaster recovery as a service tool.
If one region fails, traffic automatically gets routed to the other region. There is also one-click recovery possible with Arpio.
Arpio Disaster Recovery & Readiness is primarily used for disaster recovery and backup. Other backup solutions restore only files or VMs, but Arpio restores everything including networking, security groups, IAM configuration, load balancers, and databases. The application can come back online without manual rebuilding, and it automatically configures everything from scratch. That is a valuable aspect of Arpio.
What is most valuable?
Arpio Disaster Recovery & Readiness offers one-click recovery, automated failover and failback features, continuous replication, and disaster recovery testing capabilities. Disaster recovery testing has made the biggest difference for us.
We are able to test the failover and recovery, validate DR plans, and run isolated sandbox testing, which causes very little production downtime. This is helpful at the POC stage or the test stage. Another key feature is automated disaster recovery, which includes failover and failback, allowing us to recover everything with just one click. This is generally called application-aware recovery.
Arpio Disaster Recovery & Readiness has positively impacted our organization as we are able to quickly recover applications after outages, ransomware attacks, accidental deletions, or regional failures. A metric shows around 20% to 30% of our traffic downtime has been reduced due to this, and we are attempting to uplift that metric up to 50% if possible. Maintaining that metric ensures our downtime is less and latency is minimized.
The main feature that stands out is application-aware recovery. Unlike backup solutions that only restore files or VMs, Arpio can restore everything including networking, security groups, IAM configurations, and more. This feature is incredibly useful because configuring everything from scratch involves substantial time and costs.
What needs improvement?
I would wish for Arpio Disaster Recovery & Readiness to be better suited for on-premises environments. It is generally well-suited for AWS and Azure, but not very much for a hybrid environment such as AWS and on-premises, which may not provide the same value. Arpio could improve significantly in on-premises environments, which is a primary concern.
The pricing is somewhat high currently, and there could be extended discounts for regular customers or subscribers. Those are the limitations that could be addressed for Arpio.
Usability of Arpio is very good, and the UI is user-friendly. However, initial DR planning always requires a comprehensive understanding of cloud architecture, which can be a challenge for non-technical individuals such as product managers or sprint managers. That could be improved.
For how long have I used the solution?
I have been using Arpio Disaster Recovery & Readiness for approximately eight months to one year.
What do I think about the stability of the solution?
Arpio Disaster Recovery & Readiness is stable.
What do I think about the scalability of the solution?
Arpio Disaster Recovery & Readiness has good scalability; it can scale up to multiple instances.
How are customer service and support?
Customer support for Arpio is good. I have resolved many issues with their support team, and they have been very helpful.
Which solution did I use previously and why did I switch?
We have not used any other solution previously, but we have relied on AWS in-house solutions for cross-region needs. I find that Arpio is a good solution that we discovered.
How was the initial setup?
Usability of Arpio is very good, and the UI is user-friendly. However, initial DR planning always requires a comprehensive understanding of cloud architecture, which can be a challenge for non-technical individuals such as product managers or sprint managers. That could be improved.
What was our ROI?
We save about 40% of our time due to Arpio, and we have also managed to save between 20% to 25% in costs.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is good at the moment. However, it could be better for regular customers if it were discounted.
Which other solutions did I evaluate?
We have not used any other solution previously, but we have relied on AWS in-house solutions for cross-region needs. I find that Arpio is a good solution that we discovered.
What other advice do I have?
The advice I would give to others looking into Arpio Disaster Recovery & Readiness is to first review your requirements carefully. Document everything about your needs and compare it with what the product offers. Match your needs with the product features; this will help you understand what aligns best. For Arpio, be cautious during the configuration; it is easy to deploy, but maintenance can be difficult. Neglecting this can have long-term impacts on your organization.
I would rate this product as an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
