Overall Satisfaction with Druva inSync
We primarily use CloudRanger to take EBS snapshots of volumes in our AWS accounts, as well as manage the life cycle of these snapshots, so we don't accumulate them and are automatically removed after a configurable amount of time. The secondary use we give to CloudRanger is to scheduled start/stop of EC2 instances. While these features can be accomplished within AWS natively (with some code, scripts, configuration, etc.) CloudRanger provides a turnkey solution that requires almost zero effort, without compromising security or the management tasks that need to be accomplished. One of the things in particular that CloudRanger does nicely is it takes EBS Snapshots on a schedule and saves them, but not only does it save it in the region where the instance resides, but it can also save a copy of the snapshot in another region, which is particularly useful for redundancy. Currently, it's used by the Engineering department, specifically software engineering.
- Automate taking EBS Snapshots on any schedule and managing the life cycle of those snapshots so they don't accumulate over time.
- Automate starting/stopping of EC2 instances on any schedule.
- Automating other services within AWS.
- Reduced implementation and maintenance time significantly by providing a turnkey solution that's ready to use upon logging in.
The alternative to CloudRanger is really developing something in-house. Automating starting/stopping EC2 instances and managing EBS snapshots can easily be accomplished with AWS' extensive API, but if you're not interested in spending the time to do these things on your own, CloudRanger provides a secure, easy to use, and cost-effective solution for these tasks.
CloudRanger is best suited for companies that want to reduce maintenance and don't mind paying for something that can be developed in-house. While the features provided by CloudRanger can be easily developed with a small team of developers (1 or 2), CloudRanger provides the convenience of doing all the leg work up front, without the need for any software development, testing, maintaining code/scripts, etc.