Questions tagged with Backup & Recovery

I am making a Snapshot of a mounted volume to a path called /home/ec2-user/restore - when I use the web interface all works as expected. When I use AWS CLI to create a **new** volume from the snapshot and mount the **new** volume to /home/ec2-user/restore again, the new volume from the snapshot has all the files that are supposed to be there, but the files have nothing in them. Do you know why a snapshot would omit all the data within the files?

I am running the free t2.micro instance. Since last night I have been unable to connect to the instance using any method. I've tried using PuTTY, FileZilla, and the built-in console, but none work. My dashboard says the server is online and connectable though. I can't ask support directly because of the aforementioned free tier. What should I do? I at least need to connect with FileZilla and backup my server data before wiping the instance, but I'd prefer to not do that. Nothing was changed on the server before I was kicked off it.

I am trying to extend the retention of already made backups in FSx for Windows. AWS Backup can have unlimited retention but in the console for FSx you can only do a maximum of 90 days. For existing backups can they be copied and then categorized as a user-initiated backup and then use the Custom Backup schedule [1] extend the retention based on whats defined? Importing the Automatic backups defined in the FSx console would be ideal but I have not found a way to do this. [1] - https://docs.aws.amazon.com/fsx/latest/WindowsGuide/additional-info.html

RDS event / Log shows Emergent Snapshot Request: Databases found to still be awaiting snapshot.

What are the backup and recovery options available for Babelfish for Aurora PostgreSQL?

Hi everyone! I'd like to understand better the billing composition regardless of AWS Backup on DynamoDB resources since I got an unexpected increase in my billing. I'm aware of AWS Backup billing itself thanks to the [documentation](https://aws.amazon.com/backup/pricing/), anyway, when I access the Billing service I can notice an exponential billing pricing in DynamoDB service, on the section `Amazon DynamoDB USE1-TimedBackupStorage-ByteHrs` the description allows me to see that I'll be paying $0.10 per GB-month of storage used for on-demand backup, showing me that I've used 14,247.295 GB-Month (This makes sense with the billing I got) but where my doubt comes from is, **where does all those GB come from?** The last snapshot-size just shows 175.5 GB I've configured my backup plan with the following parameters: ``` { "ruleName": "hourly-basis", "scheduleExpression": "cron(0 * ? * * *)", "startWindowMinutes": 60, "completionWindowMinutes": 180, "lifecycle": { "toDeletedAfterDays": 30 } } ``` I'm also copying snapshots into a second region on `us-west-2` As you can see, I'm handling a schedule expression on an hourly basis backup because of compliance requirements. *Is this enough justification for the high billing?* I'm aware that backups with low RPO are commonly expensive but I just want to be sure that this billing is not higher than it should be because of any wrong Backup configuration. Thanks in advance!

I configured AWS Backup in CDK to enable continuous backups for s3 buckets with this configuration : - backup rule : with `enableContinuousBackup: true` and `deleteAfter 35 days` - backup selection : with `resources` array having the ARN of the bucket directly set and roles setup following the docs of aws : https://docs.aws.amazon.com/aws-backup/latest/devguide/s3-backups.html Later I deleted the stack in CDK and ,as expected, all the resources were deleted except for the vault that was orphaned. The problem happens when trying to delete the recovery points inside the vault, I get back the status as `Expired` with a message `Insufficient permission to delete recovery point`. - I am logged in as a user with AdministratorAccess - I changed the access policy of the vault to allow anyone to delete the vault / recovery point - even when logged as the root of the account, I still get the same message. --- - For reference, this is aws managed policy attached to my user : `AdministratorAccess` , it Allows (325 of 325 services) including AWS Backup obviously. - Here's the vault access policy that I set : ``` { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": "*" }, "Action": [ "backup:DeleteBackupVault", "backup:DeleteBackupVaultAccessPolicy", "backup:DeleteRecoveryPoint", "backup:StartCopyJob", "backup:StartRestoreJob", "backup:UpdateRecoveryPointLifecycle" ], "Resource": "*" } ] } ``` Any ideas what I'm missing here ? **Update ** : - A full week after creating the backup recovery point, and still unable to delete it. - I tried deleting it from the AWS CLI but no luck. - I tried suspending the versioning for the bucket in question and tried, but no luck too.

We are considering a move of our corporate data to AWS (that will then reside in a PostgreSQL DB), however we would like to maintain a backup of the data to one of our own servers residing outside the AWS cloud (in our own data center). Is this possible?

I deleted the workmail 3 months ago, and now I would like to recover the emails, is it possible?

I've just tested RDS MariaDB snapshot export to S3. The snapshot is good, a test restore re-creates the database correctly. However, exporting that snapshot to S3 appears to succeed but no data is exported! The job summary and the metadata stored in the bucket both say the test DB was skipped, and the metadata claims the DB is empty (it isn't). I'm working with a minimal test case and following the [AWS Console process as documented by AWS](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ExportSnapshot.html), including export all data (not a partial export). However, the resulting S3 export contains only the JSON meta-data files; no data appears in S3. **Is this a known problem with RDS MariaDB service?** export_tables_info_MyDbName-snapshot-test-2-after-stopping_from_1_to_1.json: ``` { "perTableStatus": [ { "warningMessage": { "skippedDatabase": [ { "reason": "DATABASE_IS_EMPTY" } ] }, "target": "MyDbName" } ] } ```

The snapshots of our databases, created by Automated Backups, are set to retain the tags associated to the database, and on the primary snapshot, they do. The replicated automated backups do not retain the tags. Is there a way to set it so that the replicated automated backups retain the original databases' tags?

Hello, As I know, we can create a replication in any EFS to replicate the data to another EFS in another region. Is this approach available for Replication across accounts ? If not, what the best practice to replicate EFS accross accounts? Thanks

I am having issues setting up the required IAM access for cross account backups. As I understand the requirements there are four places to configure IAM access: Source Account (management account) Backup Vault Source Account (management account) Resource Assignment Target Account Backup Vault Target Account IAM access role From the AWS Backup Developer Guide p162 I understand that the IAM roles in the Source and Target accounts, Backup Vaults, and the Backup Vault permissions need to match. I have the following configured: Source Account Backup Vault Access – “Allow Access to Backup Vault from Organisation” Source Account Resource Assignment – Role with default policy called “AWSBackupOrganizationAdminAccess” Target Account Backup Vault Access - “Allow Access to Backup Vault from Organisation” Target Account IAM access role - Role with default policy called “AWSBackupOrganizationAdminAccess” I have followed the setup guide to enable cross account backups for my AWS organization. When I run a backup job for an EC2 server in the target account I get the following error: Your backup job failed as AWS Backup does not have permission to describe resource <aws ec2 arn> I assume that somewhere I do not have the IAM access configured correctly. As there are four places where I can configure IAM access how do I track down where the issue is?

In the last two weeks, we have been seeing a database instance resetting once or twice a day. Looking at the recent event logs shows the following event, which notes the reset: > MySQL restart initiated to address MySQL induced log backup issues. Note that as part of this resolution, a DB Snapshot will be performed after MySQL completes restarting. We have not added any new logging to our database instance or changed any settings in the last two weeks. We are not sure what could be causing log backup issues. How can we root cause this issue to drive to a solution?

Hi, I have an existing AWS Backup setup for Aurora, which I created via the console UI. I have now put together a cloudformation template for that which I'd like to import - I'm following through the import with existing resources wizard, but hitting an error I'm unable to understand. After selecting the new template I am asked to enter on the UI AWS::Backup::BackupVault - BackupVaultName AWS::Backup::BackupPlan - BackupPlanId AWS::Backup::BackupSelection - Id On entering these value and then hitting next a few times to get to the final screen. It will load for a few moments calculating the change set and then say "Backup Plan ID and Selection ID must be provided" Although I do enter those values during the wizard. Any suggestions? Thanks Template below - This work all as expected if the Backup Plan does not currently exist ``` AWSTemplateFormatVersion: 2010-09-09 Description: >- Create RDS Backup Parameters: OnlyCreateVault: Description: This is for the DR region. Only other required parameters are Environment and CostAllocation Type: String Default: false AllowedValues: [true, false] DestinationBackupVaultArn: Type: String ResourceSelectionIamRoleArn: Type: String ResourceSelectionArn: Description: Comma separated list of resource ARNs Type: String CostAllocation: Type: String AllowedValues: - 'Dev' - 'Demo' - 'Test' - 'Live' Environment: Type: String AllowedValues: - 'develop' - 'testing' - 'testenv' - 'demo' - 'live' - 'dr' Conditions: CreateAllResources: !Equals [!Ref OnlyCreateVault, false] Resources: Vault: Type: AWS::Backup::BackupVault DeletionPolicy: Delete Properties: BackupVaultName: !Sub backup-vault-${Environment}-rds-1 BackupVaultTags: CostAllocation: !Ref CostAllocation Plan: Condition: CreateAllResources Type: AWS::Backup::BackupPlan DeletionPolicy: Delete Properties: BackupPlan: BackupPlanName: !Sub backup-plan-${Environment}-rds-1 BackupPlanRule: - RuleName: !Sub backup-rule-${Environment}-daily-1 CompletionWindowMinutes: 720 CopyActions: - DestinationBackupVaultArn: !Ref DestinationBackupVaultArn Lifecycle: DeleteAfterDays: 7 EnableContinuousBackup: true Lifecycle: DeleteAfterDays: 35 StartWindowMinutes: 120 ScheduleExpression: cron(0 1 ? * * *) TargetBackupVault: !Sub backup-vault-${Environment}-rds-1 - RuleName: !Sub backup-rule-${Environment}-weekly-1 CompletionWindowMinutes: 720 CopyActions: - DestinationBackupVaultArn: !Ref DestinationBackupVaultArn Lifecycle: DeleteAfterDays: 35 EnableContinuousBackup: false Lifecycle: DeleteAfterDays: 42 StartWindowMinutes: 120 ScheduleExpression: cron(0 1 ? * * *) TargetBackupVault: !Sub backup-vault-${Environment}-rds-1 - RuleName: !Sub backup-rule-${Environment}-monthly-1 CompletionWindowMinutes: 720 CopyActions: - DestinationBackupVaultArn: !Ref DestinationBackupVaultArn Lifecycle: MoveToColdStorageAfterDays: 365 EnableContinuousBackup: false Lifecycle: DeleteAfterDays: 365 StartWindowMinutes: 120 ScheduleExpression: cron(0 1 ? * * *) TargetBackupVault: !Sub backup-vault-${Environment}-rds-1 BackupPlanTags: CostAllocation: Ref: CostAllocation ResourceSelection: Condition: CreateAllResources Type: AWS::Backup::BackupSelection DeletionPolicy: Delete Properties: BackupPlanId: !Ref Plan BackupSelection: IamRoleArn: !Ref ResourceSelectionIamRoleArn Resources: !Split [",", !Ref ResourceSelectionArn] SelectionName: !Sub backup-resource-${Environment}-rds-1 ```

Hello, Currently, I set the redshift auto-snapshot retention period to 1 day. The redshift version is ra3.xplus. As far as I know, redshift auto-snapshots are automatically deleted when the retention period is exceeded in redshift. However, if you check the snapshot in the redshift console, the snapshot still exists even after the retention period has expired. Can someone please assist with this issue?

I am creating backup vaults in AWS Backups for our various resources (RDS, S3, and others). It's going well. However, I was curious - if I create two backup vaults for a single resources (e.g. Snapshots Vault, Continuous Vault) is that inefficient? Is there reasons I should/should not do it that way - additional costs, inefficiency in backup, something else? (Note: The above is just an example. I have more specific reasons why I might break it out that way, but I didn't want to spell all that out here.)

Does the Organizations level functionality for AWS Backup have to be managed from the Organizations Master Account? I want to be able to delegate the AWS Backup management to a separate AWS account in my Organization.

We have a couple of contact flows created in our amazon connect instance. We built our contact flows and were trying to take back up of the flows and we are receiving an error as "The number of blocks or resources in the flow exceeds the maximum allowed, or the file exceeds 1MB.". I understand that this is a limitation with in amazon connect. We wanted to set up dev and UAT enviornment for same contact flows in a different instance of Amazon Connect account. Can you please advise how the call flows can be exported when the "The number of blocks or resources in the flow exceeds or the file exceeds 1MB" Also, what are the possibilities for implementing a CI/CD pipe line for our future developments. We are expecting the initial work to be done in the Dev enviornment and later promote to QA, UAT and after the testing phase promote to the Production instance. All environments are in different aws accounts or at least a couple of them AWS account #1 - Dev and QA AWS account #2 - UAT AWS account #3 - Production Is there a cloud formation templates or stacks can be useD?

I have recently enabled AWS Backup for S3 on several buckets to test how it works. I am using tags to select the appropriate buckets. Everything works great. From that point, I then added the tag to our largest bucket (~1.1TB and ~8MM objects) so that it could get its first backup. The first night the backup ran, but did not complete. The status of the backup is: Expired and the error message is `Backup job failed because there was a running job for the same resource`. The backup plan includes Daily, Weekly, Monthly for data retention purposes, and I have not had this issue with any of the smaller buckets. This is the only backup plan on this S3 bucket so I don't understand that error message. Is it possible that it's taking so long it clashes with the next Daily backup? Is there any other way that I can take that initial backup so that all subsequent backups are incremental? (Do a manual backup that expires in 5 weeks or something - would all automated backups after be incremental?)

Hi Everyone, Last year, We moved one of our main reporting systems to Elasticseach 7.9 , its located in N. California region. In this region only 2 AZ is available, in our domain we have dedicated 3 master nodes. Now we are looking for some disaster recovery options. I read https://docs.aws.amazon.com/opensearch-service/latest/developerguide/disaster-recovery-resiliency.html, and it looks with our current setup we have 50/50 downtime possibility. so far I came up with two options 1- cross cluster replication(which will double our cost) 2- continuous snapshot backup. Below are my questions 1- Is there any other possible option for disaster recovery that I haven't considered? 2- For snapshot backup, is there an easy way to schedule/manage the backups, so we can bring up the domin in shortest period of time and with less data loss.

Hi there, I took a snapshot of an instance to deploy it on a new instance which I did but whenever I write out the IP address of the new instance and adding :2087 as the port it takes me to my old instance console login (I use cpanel). My goal is to enter the new instance to extract a database file and then terminate the new instance. Would love to get some help to solve this issue. Thank you!

A customer wants to migrate their production RDS DBs from euw3 to euw1. The process is simple enought, just copy a created snapshot to another region. We had to cancel the migration since both snapshots (20GB and 300GB) have been in the "Creating - 1%" state since 5:45 UTC this morning (more than 5 hours now). We couldn't halt their production workload any longer. I've copied EC2 and RDS snapshots between regions several times in the past and never experienced this behavior. I know there are alternatives, I could always create a dump and restore that to a new RDS instance in euw1, but the snapshot copy approach is easier and I would like to make use of that. **My question would be if there's any steps we can take to speedup the process**. I don't know what could be going on for a 20GB snapshot to take more than 5 hours to copy from one region to another. Thanks!

Hello, as the title of the topic, I am writing this post to ask you help in order** to create a backup system of all the Glue jobs**, written in python, **on a bitbucket repository**. In detail, I would like that, when a Glue jobs is updated , it is automatically uploaded on the bitbucket repository. Resuming: **1)** is it possible to export the Glue jobs? **2) **if so, is it possible to find an automatic way? Thank you in advance!

I was part of the beta and still have the same problem. When I backup "all resources" it does not backup my s3 buckets. When I specifically select s3 in my backup plan it still does not work. However, on demand backup of s3 works fine. How do I backup my s3 buckets with everything else on the same schedule?

Under the limitations page for hibernation within EC2 [[1]]( https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-hibernate-limitations.html), it is mentioned that: "If you create a snapshot or AMI from an instance that is hibernated or has hibernation enabled, you might not be able to connect to the instance.". Could anyone clarify the meaning of this statement. Does it mean: - You might not be able to connect to the instance whilst the snapshot or AMI creation is in progress - You might not be able to connect to the instance after restoring the snapshot or launching a new instance from the AMI - Something else 1. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-hibernate-limitations.html

Hi Everyone, Last year, We moved one of our main reporting systems to Elasticseach 7.9 , its located in N. California region. In this region only 2 AZ is available, in our domain we have dedicated 3 master nodes. Now we are looking for some disaster recovery options. I read https://docs.aws.amazon.com/opensearch-service/latest/developerguide/disaster-recovery-resiliency.html, and it looks with our current setup we have 50/50 downtime possibility. so far I came up with two options 1- cross cluster replication(which will double our cost) 2- continuous snapshot backup. Below are my questions 1- Is there any other possible option for disaster recovery that I haven't considered? 2- For snapshot backup, is there an easy way to schedule/manage the backups, so we can bring up the domin in shortest period of time and with less data loss. Thanks in advance.

Hello, here is the situation, we have AWS Backup configured to backup Aurora Clusters, the Aurora Cluster is encrypted with a CMK of KMS. Now, that we want to restore a backup using the AWS Backup Console, the process says it finished successfully but the restored Aurora Cluster has 0 instances. So I think there is an issue of permissions to use the KMS key, but I have tried different permissions to no avail. Is there a document that specifies the correct permissions for this to work ? Thanks in advanced. Kind Regards,

How we can set alert if any backup job get fails?

Using AWS Backup to backup and restore Windows 2016 and above EC2 instances which are domain joined to AWS Managed AD. When the instances are restored (as a copy) they appear to retain the same NetBIOS. There will then be two EC2 instances of the same name (different instance IDs) in the same VPC. This has been a problem in the past outside of the cloud. Any best practices in the community for using AWS Backup and Restore with Windows you can point to?

My website, www.natalielynn.net has been down for some time. It was originally built in 2019 and I have kept up to date on paying for hosting and such. I have spoken with the developer and she says it looks like it "has expired". How would it expire? I also checked with wordpress but they do not have access to my site as it was developed off of a remote version of wordpress. When I spoke with AWS, they stated everything looked ok on their end. Nobody seems to know what is happening. As I paid a lot of money to have the site created, it is very valuable and important for me to keep it live. Best, Natalie Lynn

I want to share my solution which allows you to restore EFS from backup in your cloudformation template. I want feedback. Please test it https://github.com/horeca2/aws-cloudformation-restore-efs

Most of my other post was answered but stuck on one concept. I have a few Dynmo tables that will always be appended so have PITR and will have a daily tag to backup with. However, if have tables that change with the month. So after the month, that data will not change. So if I have a tag call backup_monthly, I can make a rule to say backup daily, transition to cold storage after a few days. But, if I keep that tag of backup_monthly, no data changes, will just that process trying to sync cause that to be a new backup since the old is in cold storage? I don't want to have to change tags monthly, etc. but rather just set it and forget it, knowing daily backups are warm and always updating, january is warm and backing up, come Feb, Jan will transition to cold and Feb will be warm until March. Thanks all

I ran a test whereby I restored a RHEL 7 EC2 instance. After it started, I was able to ssh into the instance using the same private key that I use for the instance that was backed up. However I noticed that the /etc/ssh/ssh_ key files had all changed, and an application, Oracle's secure global desktop, could not longer connect, due to the changed host keys. What would have caused the host keys to change? Is it something that AWS restore does? Is it something that sshd does on startup? E.g. it detects that the hostname changed (AWS assigns a new hostname to the instance) and recreates the host keys as a result? Is it something that RHEL 7 does? I suppose I could just backup the /etc/ssh directory and restore the files after a restore, but I would like to think that I can use AWS backup / restore out of the box to preserve the configuration of an instance during the restore operation. There is a very old AWS forums post: https://forums.aws.amazon.com/thread.jspa?threadID=40450 that refers to this problem, but the post says that the issue was resolved in the AWS linux AMI. Thanks for the help.

On December 1st, I created both a daily and monthly backup plan. With the plans integrated into AWS, no Backup Jobs have been started or completed since. Therefore, there must be an issue with the scheduled Backup Plans. I tried to troubleshoot following this guide: https://aws.amazon.com/premiumsupport/knowledge-center/aws-backup-troubleshoot-scheduled-backup-plans/ Point 1 - all resources are enabled. Point 2 - the backup window is set accordingly. Point 3 - there is an IAM role assigned to the Resource. Point 4 - I don't remember using tags. Point 5 - not using cross-accounts, so this does not apply. Can someone with technical expertise please help me find the issue with my backups? Thank you.

I've been searching for a way to exclude resources from AWS Config managed rules for backup plans but so far to no avail. I'm governing multiple accounts and to see if they have backup plan on resources i have attached the "resources protected by backup plan" rules that do exist (e.g., https://docs.aws.amazon.com/config/latest/developerguide/aurora-resources-protected-by-backup-plan.html). The rules will be in NON-COMPLIANT state if they have no backup plan attached, but some resources we do not want to backup. The rule is good to have if we add resources but accidently forget to attach a backup plan- but I would also like the account owners to have the possibility to actively "allow-list" a resource so the rule can be COMPLIANT. There is two parameters for these rules: "resourceTags" and "resourceId", but with these it's only possible to include resources for the rule. What I would like is the opposite, something like "excludeResourceTags" and "excludeResourceId". That would make it possible to give the account owners the possibility to keep the rule in COMPLIANT state, but we wouldn't miss backups for resources where we need it. Any suggestions are welcomed!

Hello! IHAC who would like to know the following: How do I check my Glacier progress? How long does it take to restore from Glacier? How do I restore Amazon Glacier? Any help is welcome!

My 3rd backup software from on-premises to S3 is slow, how can I diagnose where the problem is?

A customer wants to automate the backup for S3 buckets, EBS snapshots and RDS snapshots to another, independent account to be able to restore the application data in case an administrator account in the organization is compromised and a ransomware attack is executed. The customer wants to do this in an automated, maintenance free way. At first I suggested using scheduled Lambdas in the independent accounts that use IAM roles to access the "to-be-backuped" buckets and snapshots and pull them into the independent account. However, this solution requires the implementation and maintenance of code. I was looking into AWS backup as I thought it would be able to create RDS and EBS Snapshot backups on a schedule to S3. I would then have recommended the customer to use this and setup cross-account replication of the buckets with a transfer of ownership of the objects in the replicated bucket to the independent account. However, it seems that AWS backup uses S3 as a storage location for the backups, the backups themselves are not visible/accessible this way. I am looking for a low effort, maintenance free way of achieving cross account (destination account being outside of the org) backups for S3, EBS, and RDS

A customer is exploring the FSx HDD option. While looking at the cost of backup of FSx(https://aws.amazon.com/fsx/windows/pricing/), it seems the backup cost is higher then the actual storage cost. Like for single Az deployment , HDD storage capacity cost is 0.013per GB-month, while backup is 0.050 per GB-month, Is there any specific reason? Is it due to the fact that backup is going to be stored in S3?

My customer is uing Veritas Netbackup 8.2 and CloudCatalyst to backup to S3 buckets over the internet and they want to leverage existing Direct Connect connection - bandwidth and data transfer rate is not an issue (see below). I see two options, either via Public VIF or an EC2 Proxy instance. What would you recommend? 2x DX = 500Mbps Data Transfer = 200GB/daily

A customer wants to ensure that data that is locked in Veeam can also not be deleted from S3. What's the best way to achieve that?

A customer wants to use S3 as a backup solution for their on-premise files: - they have a huge number of small files stored in a NAS (NFS server). - These files are their customer profiles (json files) and will be updated from time to time - For performance issue, they set noatime on their NAS, which means we dont have the information about when the file is modified. Is there any way to help customer to backup the files in an efficient way? S3 sync may help, but may brings two questions : NFS server is not aware of file modification date, does S3 sync work ? Does S3 sync generate large number of S3 request (resulting increase of billing )?

A customer is experimenting a high data transfer cost when using Commvault backup solution. Commvault is deployed in an EC2 instance and is copying EBS snapshots to another S3 bucket, being all the resources in the same region. According to S3 pricing documentation: *You pay for all bandwidth into and out of Amazon S3, except for the following: .. • Data transferred out to an Amazon Elastic Compute Cloud (Amazon EC2) instance, when the instance is in the same AWS Region as the S3 bucket. ...* Customer was not expecting any data transfer cost for the backup solution but they detect high costs associated to the concept EU-DataTransfer-Regional-Bytes Maybe I'm missing something but I do not see why this cost is there, as this concept is related with *The amount of data transferred from Amazon S3 to AWS resources within the same AWS Region* but that message seems counterposed with the s3 pricing documentation. Any clarification around that would be appreciated and also other options if this scenario really implies a high transfer cost.

What is happening if I'm syncing a File System with S3 versioning enabled, and I delete a file? I suppose that a delete marker is added, so the previous versions are kept. This mean that the client will have probably to do additional activities to clean up files deleted over a period of time if they want to keep their storage cost low. correct? THanks.

One of our customer asked us the following questions. I am not sure about the answer. Could you provide some guidance? 1- Does AWS maintain hypervisor backward compatibility for the backup? If yes how many years. This is to ensure we are able to meet our data retention compliance with APRA (7 years) *My understanding is that a customer should be able to restore EBS snapshot. Do we have an official response for that?* 2- Can VMs be exported to standard format and moved to an alternate platform. This is also as part of business continuity *I believe that EBS snapshot cant be used for that purpose. I understand VM export can be used to export an AWS EC2 instance but there are some limitations (e.g. instance’s AMI must have been previously imported with VM import).* Thanks for your help in advance,

Hello team, does anyone knows for sure if EBS Snapshot are charged proportionally across the month? I assume they are since this is how S3 and EBS volumes are charged. Ex: if a customer creates a 10 GB Snapshot on April 30 he will be charged $1.3 (SA region so 0.13 GB/mo) or 1.3/30 = $0.04 ? Thanks

Hi, A customer has asked the following question. I have looked on the Storage Gateway whitepaper but could see and answer relevant. "We're looking to off-site a copy of our physical file server for DR purposes. I very recently came across the option for AWS Storage Gateway and was wondering if this would be what we're after. We have currently 8TB of local file data with the potential to grow up to 18TB. If we used this as our off-site backup how would we mount that in the future to a device/server on AWS?