We are delighted to announce that CloudRanger has joined the AWS Public Sector Partner Program. As a Public Sector Partner, we have demonstrated not only a strong overall AWS practice but have proven our experience and proficiency in supporting government and education organizations.
As a company that specializes in simplifying and demystifying Amazon Web Services (AWS), we here at CloudRanger are constantly answering questions about the AWS platform and its various features. And despite the diverse nature of our client base, one question seems to pop up on a regular basis: Where are my Amazon EBS snapshots stored?
As such, we decided to give this frequently-asked question its very own blog post. In the following article, we’ll explain in detail how and where AWS EBS snapshots are stored, and explain why the answer to this question isn’t quite as straightforward as it may seem at first glance. We’ll also explain how using CloudRanger can greatly simplify the EBS snapshot backup process.
In previous posts, we’ve discussed the importance of Amazon Elastic Block Store snapshots, also known as EBS snapshots. Since these snapshots allow users to easily and efficiently make incremental backups of their data as needed rather than performing a complete backup, they have become one of the more popular features associated with Amazon Web Services (AWS). However, while making incremental backups via EBS snapshots can save your company time and money, there are still a few potential problems that must be overcome. Specifically, for users who are attempting to use EBS snapshots with a Windows server instance, steps must be taken to ensure that files that are in use during the snapshot process are not excluded, which would lead to an incomplete backup.
If you’re already using Amazon Web Services (AWS), you’re probably more than familiar with its Simple Storage Service (S3). And while S3’s scalable storage infrastructure is certainly a popular method for saving your data in the cloud, Amazon Glacier is an alternative method that’s worth exploring.
While both services offer cloud-based storage, S3 and Amazon Glacier each have their own unique benefits. So depending on what type of data you need to store, and your reasons for storing it, using both services in conjunction might make practical and financial sense. In the following post, we’ll explain what Amazon Glacier is (and what it isn’t), and look at instances where the service might be a better option than S3.
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