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.
Category: Snapshot Management
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.
In the following article, we’ll further explore how Amazon Redshift snapshots work, and why they are useful. We’ll also explain how to easily manage and automate these snapshots, and how third-party services such as CloudRanger can further simplify the process.
As we’ve discussed in previous blogs, Amazon Redshift is a fully managed data warehouse service offered by Amazon Web Services (AWS) which allows users to quickly and easily analyze data using common industry tools such as SQL. The service executes these data queries through various computing resources known as nodes which are grouped together to form clusters. In a similar manner to AWS Elastic Compute Cloud (EC2) and AWS Relational Database Service (RDS), Redshift allows data from these node clusters to be automatically backed up with snapshots.
Regardless of what type of platform you are using, the need to make regular backups of your business’s data is self-evident. But a major benefit of working with Amazon Web Services (AWS) is the ability to easily and efficiently make incremental backups of your company’s data by utilizing Amazon EBS snapshots.
Despite their popularity, not everyone is familiar with how Amazon EBS snapshots work. So in the following article, we’ll take a more in-depth look at native EBS snapshots, and how they are able to save your company time and money with incremental backups. We’ll also take a look at how using a third-party service like CloudRanger can further simplify the process and lower costs.