Category: Disaster Recovery

We are delighted to announce that our new functionality for Automated Disaster Recovery Testing for AWS Cloud is now available. A new section is now available in the main CloudRanger dashboard, for Disaster Recovery. In this section, you will be able to create an AWS cloud Disaster Recovery Plan (DRP), much in the same way you already do for creating backup policies in our platform but in this case for disaster recovery testing purposes.

With our existing backup system in place, our new Automated Disaster Recovery Testing functionality allows you to test that any Amazon Machine Image (AMI) backups you are taking actually work successfully in practice.


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

Thanks to cloud-based platforms like Amazon Web Services (AWS), backing up your company’s critical data has never been easier. But as we’ve stated in previous blogs, during an actual crisis, backups may prove useless in the absence of a comprehensive disaster recovery (DR) plan. And while there are many factors that must go into crafting the right DR plan to meet your company’s specific needs, the two most important are the recovery time objective (RTO) and the recovery point objective (RPO). In the following article, we’ll break down what these terms mean and how they differ. We’ll also explain why determining the RTO and RPO is so important, and how CloudRanger can help enact an AWS DR plan once it’s been crafted.


Since we have released the latest version of our CloudRanger software, we have received multiple requests from customers to allow AWS cross account backup and recovery functionality across multiple AWS accounts using CloudRanger in order to best prepare for a disaster scenario. 

We already provide the functionality to copy a snapshot to another region within AWS, but many of our customers are also looking to ensure their data and snapshots are stored in an additional AWS account. This means it is guarded separately from the origin AWS account to ensure backup data is safe from any potential security breaches and or compromised accounts.

So today, we are delighted to announce that our AWS cross account backup and restore functionality, allowing customers to automatically copy and recover snapshots between AWS accounts is now available.


Since they were first introduced in 2008, Elastic Block Store (EBS) volumes, specifically EBS snapshots, have become one of the most popular storage methods offered by Amazon Web Services (AWS). Not only are they generally cheaper than traditional Amazon Machine Images (AMIs), but the snapshot’s ability to capture incremental block-level changes also eliminates the need to continuously backup entire volumes. However, another popular EBS attribute is the ability to quickly and easily copy a snapshot to another region, a feature that may prove useful to your business for a variety of reasons. In the following article, we’ll discuss some of those reasons, as well as how third-party vendors like CloudRanger can help simplify the process.