CloudBerry Lab™ is excited to announce a partnership with A Cloud Guru (ACG), the training portal dedicated to cloud technologies. ACG has developed a training course about Amazon S3 with an embedded lab that explains how CloudBerry Backup can enhance your Amazon S3 experience.
The offer expires on April 25th, 2017
World Backup Day is upon us again. With the rise of technology and the increasing amount of data that is stored on our computers, World Backup Day reminds us of the importance of backing up our data. Celebrated on March 31st, this day is part of an initiative that seeks to raise awareness regarding data ownership, security, backup consistency, and access.
Cloud data technologies have a lot of concepts which are usually misapprehended. Today, we will figure out what’s the difference between cloud storage, cloud backup and cloud synchronization, and what suits best for common business tasks.
Amazon Web Services charge users monthly on a Pay-As-You-Go basis. Sometimes your bills can unexpectedly go high. For example, if you have a running, but not used “t2.medium” Amazon EC2 instance, you will pay additional $51.24/month and excessive provisioned IOPS on EBS volume can lead to an extra $120/month.
In this article we explain how to avoid unexpected bills with AWS CloudWatch Billing Alarms and SNS Notifications. Continue reading
Before We Begin
Amazon S3 Reduced Redundancy Storage (RRS) is a storage class within Amazon S3 that costs 30% less than Amazon S3 Standard Storage, but with lower durability: 99.99% (RRS) vs 99.999999999% (S3 Standard). That means AWS can lose 1 from 10 000 files during one year.
It’s great to save 30% on storage cost, but no one wants to lose their data, especially if you’re using Amazon S3 RRS as a backup storage. In this post we’ll show how to setup an automatic notification when the object was lost and how to recover it in the cloud using CloudBerry Backup. Continue reading
In this article we will describe the use case for AWS Lambda that allows you to manage your Amazon EC2 instances in a more intelligent way and save some money.
Before we begin
In case you’re using Amazon Web Services to run a development or testing environment in addition to your high-availability production instances, you can benefit from using only what you need and when you need it. Why should you pay for an instance running for 24 hours when you need it during 8 business hours only.
One of the options is to manually monitor your environment and shut down instances that aren't used, but it's better to automate the process. You can use AWS Lambda combined with proper resource tagging to achieve that. Here is how.