Google Cloud Disk Snapshots are default located in which regions? Is there region same as Disk region?
Whenever you take snapshot in Google cloud, the snapshot data is incremental and the snapshot data is kept in Google cloud object storage and the details of which object storage, where and how is not at all revealed to users.
Because, Google needs to meet some SLAs for those snapshots they would want to disclose details of the snapshot , as to meet SLA s they would be changing and managing snapshots internally that user would be oblivious to
And that's true with other clouds too!!
Related
I've two VMs created at the Compute Engine session with hourly snapshot as backup copies. I never created any storage bucket, I wonder where do those snapshots stored and how does it count for the storage space charges?
And, is there a way I can backup the VMs to on-prem storage? e.g. can I use any API command to download the VM snapshot to my local storage as a backup of backup just in case Google Cloud screwed up.
When you create a snapshot, you can specify a storage location. The location of a snapshot affects its availability and can incur networking costs when creating the snapshot or restoring it to a new disk. You will find the pricing for snapshot storage here.
This article describes how to create an image from your VM's root disk and export it to Google Cloud Storage or you can directly download it to your remote computer.
I read that Azure has geo-redundant storage where data will have three copies synchronously created in the region and three copies asynchronously created in another geographic region for disaster recovery. I searched the web resources for AWS EBS storage but could not find any information for async geo-redundancy for EBS. Do they use another term for it or does AWS simply not have geo-redundant block storage?
No public cloud provider that I'm aware of has geo-redundant block storage. (Google Cloud has zone-redundant persistent disks though.) You probably saw geo-redundant blob/object storage.
AWS has S3 cross-region replication, but not a geo-redundant S3 storage class.
I have just set up an instance of a WordPress site on Amazon Lightsail.
I'm looking for a backup solution.
The option to create a snapshot of the instance is there and works fine, but I see in the control panel that each snapshot takes 30GB and "Total snapshot data Snapshots are billed monthly per GB".
Is it feasible to do a daily snapshot without costing a bundle?
Or would it be better just to copy the whole WordPress directory to another directory or a S3 bucket on a daily basis?
Yes, it is possible to automate the creating snapshots of an Amazon Lightsail instance. Amazon has the CLI tool for all services including Lightsail. You can use it for automation or the AWS SDK tools for different programming languages.
If you want to create your own script you can take a look at these links
https://docs.aws.amazon.com/cli/latest/reference/lightsail/create-instance-snapshot.html?highlight=lightsail
https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Lightsail.html
https://aws.amazon.com/getting-started/
I also created a script for the AWS Lambda NodeJS to automate the process using AWS SDK. See the instructions and adjust it for your needs.
https://github.com/vidanov/lambda-nodejs-lightsail-backup
Yes, you should use snapshots rather than copying files. It is always fiddly to recreate a computer with only some of the files and it is easy to miss some important files (eg web server configuration).
Assuming that an Amazon Lightsail snapshots are the same as EBS snapshots (which would be a pretty safe assumption):
Snapshots only consume space for used blocks of the disk
Snapshots are incremental, only taking a copy of blocks that have been added or modified since a previous snapshot
Storage is charged on a pro-rata basis, so if it is only stored for 7 days, it would only be charged 7/30 of the cost (7 days divided by 30 days).
To reduce costs, you could take a snapshot each day and only keep the last n snapshots (eg the last 5 snapshots). You would need to code this yourself but it would be quite simple. (See example for Amazon EBS volumes,
but Lightsail would involve different API calls.)
For not so technical people like me, AWS now provides automatic snapshot for last 7 days.
This can be easily enabled via console in few simple steps.
Here is the detailed article.
https://aws.amazon.com/about-aws/whats-new/2019/10/amazon-lightsail-now-provides-automatic-snapshots/
which reads
Amazon Lightsail now supports automatic snapshots, allowing you to
schedule daily snapshots of your Lightsail Linux/Unix instances.
With automatic snapshots, Lightsail will automatically take a daily
snapshot for you at a time you specify, eliminating the need to take
snapshots manually. Lightsail keeps the seven most recent snapshots,
so you can rest easy knowing that you’ll have a full weeks’ worth of
snapshot history. Snapshots can be used to restore your instance to a
previous state and to create multiple new instances that are replicas
of the original instance.
Enabling the feature is free; you only pay for the storage of your
snapshots on Lightsail ($0.05 USD per GB per month). Although
Lightsail retains your seven most recent automatic snapshots, you can
choose to keep specific automatic snapshots as long as you wish or
continue to take manual snapshots of the instance (storage for manual
snapshots is charged at the same rate, $0.05 USD per GB per month).
Moreover, Lightsail optimizes your snapshot storage so that for each
consecutive snapshot, you’re charged only for the data that’s changed
from the previous one.
You can enable automatic snapshots using the Lightsail console or API
in all regions where Lightsail is available. To learn more about
automatic snapshots on Lightsail, click the link below.
https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-configuring-automatic-snapshots
Here is how to do it
Sign in to the Lightsail console.
On the Lightsail home page, choose the Instances tab.
Choose the name of the instance for which you want to enable or disable automatic snapshots.
On the instance management page, choose the Snapshots tab.
Under the Automatic snapshots section, choose the toggle to enable it. Likewise, choose the toggle to disable it if it's enabled.
At the prompt, choose Yes, enable to enable automatic snapshots, or Yes, disable to disable the feature.
The automatic snapshot is enabled or disabled after a few moments.
I'm newbie in the cloud computing world.
I have a question about the backups. When we take an EBS snapshot is stored in amazon s3 ($0.095 per GB according the site).
For use this I need to contract amazon s3 service (with 500gb for example) in addition de ec2 and ebs or this automatically charged when I take a snapshot?
that's all. Bye.
UPDATE ------------
Sorry. Maybe my question was not enough well explained.
I will try to be more clear.
How I said, I read
from here http://aws.amazon.com/ebs/pricing/?nc2=h_ls
From the text I understand this: The snapshots are incremental and we must to pay for each gb/month $0.095. the snapshots are saved in Amazon s3.
My question come because I'm trying to use the amazon calculator. In the amazon calculator in the left corner I see the option Amazon S3, where I can reserve an amount of storage. Per example 500GB.
My doubt : Where will be saved the snapshots? in the Amazon s3 storage reserved by myself (500GB) ? Are discounted from the storage of my ebs? or are saved in a new Amazon S3 storage, independent of the 500gb S3 reserved?
In other words:
Is mandatory reserve "Amazon S3" storage for save snapshots or the needed space to keep all my snapshots are automaticly consumed without need of specify an "Amazon s3" storage?
I hope I was more clear, and sorry if my question is silly. Sorry for my english. Is still too rough. Bye
Snapshots are performed behind the scene so there's no need to do anything with S3 directly.
You'll be paying for the first snapshot and diffs moving forward so the estimator is really just that, a simple estimation of storage cost for snapshots.
What are other public clouds with similar AWS EBS offerings?
The ability to have the disks and compute to be separate and independent and you could attach/detach disk at runtime
What about the ability to set IOPS (provisioned IOPS)?
There are disks in both Google Compute Engine and Microsoft Windows Azure.
In Azure when you create and attach a Disk; behind the scenes it is a page-blob which gets created in the apecified Azure Storage Account. There isn't any exact same like AWS EBS in Azure. This disk can attached, reattached to instances.
https://developers.google.com/compute/docs/disks
http://blogs.msdn.com/b/windowsazurestorage/archive/2012/06/28/exploring-windows-azure-drives-disks-and-images.aspx
On the ability to set set IOPS, it seems that with GCE and Azure IOPS is tied to capacity. There doesn't seem to be a way to set IOPS limits as you can with AWS io1 (even though io1 is also capacity bound).
https://cloud.google.com/compute/docs/disks/performance
https://azure.microsoft.com/en-us/documentation/articles/storage-premium-storage/