AWS Database Migration Service helps users migrate databases to AWS. The source database remains fully operational during the migration to minimize downtime to applications that rely on the database. The vendor states that AWS Database Migration Service can migrate data to and from most widely used commercial and open-source databases.
N/A
Carbonite Availability
Score 10.0 out of 10
N/A
Carbonite acquired Double-Take, a data replication and disaster recovery option, in early 2017. The technology now powers Carbonite Availability, the now Carbonite supported high availability and data replication product.
N/A
Pricing
AWS Database Migration Service
Carbonite Availability
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
AWS Database Migration Service
Carbonite Availability
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AWS Database Migration Service
Carbonite Availability
Considered Both Products
AWS Database Migration Service
No answer on this topic
Carbonite Availability
Verified User
Anonymous
Chose Carbonite Availability
Carbonite Availability does an outstanding job competing against competitors like Druva and Veeam. It provides useful tools that every organization needs in this day and age. Companies will rely on Carbonite Availability more and more as IT organizations become ever more …
Zerto is a very nice tool when performing virtual to virtual replication. If you were to add a physical server in the mix, it would not be able to handle that server or the data on it.
Veeam is a way is similar to Zerto where it only has the ability to handle virtual to virtual …
It's a cost effective solution for our smaller clients. However since doubletake is quite different from RecoverPoint. I can't do an apples to apples comparison.
As stated previously, AWS Database Migration Service excels when replicating very specific data elements between environments. AWS Database Migration Service handles replication tasks to load equipment assets or customer job sites from production to QA databases very well. Full load replication - e.g., we need an exact copy of the production database in another region - works well. But when we need to load the QA database with the latest production data - it does work as well. AWS Database Migration Service comes up short because we do not want to wipe the QA database completely and make an exact copy. We want to keep what's already in the QA database and add production data so that we can QA with that level of volume. And at least with our database design, we end up having to do a lot of manual data manipulation and de-duplication.
I believe it would work well with continuous replication in a DR scenario with no time limits and having the ability to fail back is a bonus, but in a one off move the decision to restrict the time it can sync for has proven to be an issue for us.
License management is poor and the online system is very restrictive, We are using a one time "Move" product that has a fixed life ... but sometimes in a small team other high priority tasks come along.
We lost all access to all licenses in the portal and all support because we hadn't used them in ninety days. Very poor service. We did get access back eventually but it took a lot of "bargaining".
Failover isn't always as smooth as it could be. VMDKs don't release properly and the move fails and has to be done manually. Not hard just frustrating. VMWare to VMWare.
Cabonite Availability is a very practical and useful tool that can help any business weather any type of IT disaster. The ease and quickness of restoring data helps us provide as seamless an experience as possible. Many times our customers will never know there was an outage. This brings confidence in our brand and improves our organization's standing and reputation.
Once through to support it is very good and they have assisted us through a number of issues. I don't always think that they provide a solution, more a workaround, but in a move situation where each copy is moving once, that isn't an issue. I'd be more concerned if we were using it to manage a DR scenario.
Zerto is a very nice tool when performing virtual to virtual replication. If you were to add a physical server in the mix, it would not be able to handle that server or the data on it. Veeam is a way is similar to Zerto where it only has the ability to handle virtual to virtual replication. The big difference is that it's not continuous replication. It uses a snapshot technology to grab the changes from the last snapshot and replicate that over.