Release Provides Over 4,000 Customers with Comprehensive Protection and Management Across Major Enterprise Data Sources–Including AWS Workloads

Druva, the global leader in cloud data protection and management, today announced the integration of Druva CloudRanger with the Druva Cloud Platform (DCP), the industry’s first and only Data Management-as-a-Service solution. The DCP unifies Druva’s product offerings and provides a single point of management that enables organizations to centrally protect, manage and gain visibility into their entire data footprint.

With the integration of Druva CloudRanger, Druva now provides a holistic end-to-end solution that builds a bridge between data management for traditional on-premises and modern cloud infrastructures. Enterprises can now centrally manage their entire data footprint without incurring the increased complexity and costs of additional administration and infrastructure.


We are delighted to release the CloudRanger Public REST API that customers and partners can use to integrate the CloudRanger platform with third-party applications and systems. Customers and managed service providers (MSPs) can use the CloudRanger API to manage customized backup policies and schedule server resources on AWS cloud.

Access to the CloudRanger Public REST API is controlled by your API key generated in the CloudRanger dashboard and token. This will allow you to manage your Amazon EBS, EC2, RDS and Redshift resources and backup policies across multiple AWS regions and accounts with ease.


In previous blogs, we have explained why properly tagging AWS resources is necessary, and we have explored some of best practices and recommended strategies for applying tags for your AWS cloud environment. Amazon Web Services have now taken this further and provided some great new support features for tagging Amazon EBS Snapshots so you can exercise more control them. You can now tag your Amazon Elastic Block Store (Amazon EBS) Snapshots at the time of creation. You can do this from the Amazon EC2 console or through the CreateSnapshot API. By tagging resources at the time of creation, you can eliminate the need to run custom tagging scripts after resource creation.


Businesses are now using AWS cloud to enable faster disaster recovery of their critical IT applications without incurring the additional costs of on-premise infrastructure. One of the many benefits of AWS cloud is that it supports a number of disaster recovery scenarios from “pilot light”, to “hot standby”. AWS cloud offers a range of cloud-based disaster recovery services that enable the rapid recovery of your IT infrastructure and data. In this article, we will explain what you need to consider when planning your AWS DR strategy, including the frequency of testing, the types of backups you are going to require and explain how CloudRanger can help to improve your AWS DR strategy with automated testing.

In theory, everyone seems to agree on the need for a comprehensive disaster recovery (DR) plan. But for IT professionals tasked with ensuring AWS business continuity, theory and reality are two very different things. After all, finding vocal managerial support for a DR plan is one thing. Finding the actual funds to implement it is another.

When pitching a DR plan, it can be difficult, if not impossible, to project ROI. It’s hard to accurately gauge the value of something that will hopefully never be used. As with fire extinguishers or airbags, DR plans are usually taken for granted until something goes horribly wrong. For that reason, it might be better to frame a DR plan in terms of an insurance policy that will mitigate possible losses rather than an investment that will produce tangible gains or cost savings. And as with other types of insurance, it might also make sense to bring in a third-party vendor to handle your disaster recovery needs. READ MORE