Questions tagged with Backup & Recovery
Content language: English
Sort by most recent
Team,
I wanted to know if you have any data reduction technologies like compression, Dedup, etc available as a part of the EBS/EFS/S3 Storage options?
Or Does the customer need to use any 3rd party SW from the marketplace to do this?
hello, I was reading through https://www.wellarchitectedlabs.com/reliability/200_labs/200_testing_backup_and_restore_of_data/2_configure_backup_plan/ and point 7 essentially says that hourly backups have negative performance impact on systems.
My question is to get clarification on hourly backups, are they good or bad? Has someone applied hourly backups in large scale and seen poor performance of underlying systems.
Hello. First of all, this is my first time in this forum and I'm not an expert user. During november 2021 someone hacked my account and the billings rised up from USD$1,5 (I usually payed that) to USD$32.000 in just 1 month. I was forced to block my payment methods. The thing is I talked to a lot of people asking for support and finally (because there was no valid payment method) Amazon had to close my account and deleted almost everything I had in there.
I need to restore some specific data, but I don't know if Amazon has something like a "backup of the backup". Is there a last chance to recover what I've lost??
Thanks in advance.
Regards!
I am trying, desperately, to do a simple upload of a sub folder on my MS OneDrive to AWS S3 Glacier Deep Archive. I have not been able to find a simple way to do this. I have investigated Veeam as an option, but I can't get away from the technical "gibberish" that seems to plague the AWS backup space. Is there a way to do a simple upload to AWS S3 Glacier Deep Archive in a simple manner? HELP!!!
On RDS for SQL Server, I understand that restores from EBS snapshots use lazy loading when downloading data from S3.
If I restore a native backup file (.bak) from S3, will this use the same lazy loading as with snapshots or is all the data available on the instance once the restore is completed?
Is lazy loading a feature of snapshot restores only?
My old EC2 server, that was launched in 2011, has finally died. It is unreachable and cannot be rebooted.
It was running an Amazon AMI.
I created a new VPC server with a new Amazon Linux2.
My plan was to copy my website files from an old snapshot to the new drive on the new server.
I created a volume from an old snapshot taken a few days before the server died.
I can see the volume has a filesystem.
$ sudo file -s /dev/xvdf
/dev/xvdf: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs)
But it fails when I try to mount it.
$ sudo mkdir /olddata
$ sudo mount /dev/xvdf /olddata
mount: /old_data: mount(2) system call failed: Bad message.
$ sudo e2fsck -p /dev/xvdf
e2fsck: Bad magic number in super-block while trying to open /dev/xvdf
I tried the same things for older snapshots a month before the server died and got the same result. I know the website was running. So the old filesystem must have been somewhat OK.
I tried:
$ sudo e2fsck -b 8193 /dev/xvdf
No luck. I also tried "Fast snapshot restore" so that I knew I was working with a fully restored snapshot. But it made no difference.
Any suggestions for how to recover the files from the old snapshot? Or how to get the old server to launch so I can FTP the files?
Hello everybody,
I run an server outside of AWS which can be accessed over SSH.
I don't want to do backups from the server to AWS. It should work the opposite.
How can I run a serverless tool in aws, which is daily connecting to the server and copy all data to a cheap AWS storage.
Is there something build in or do I have to build something on my own with Lambda? and S3 Glacier? (Or how would you do this?
Thank you
We had scheduled, daily auto back-up of our SqlServer Db on RDS, to S3 bucket for at least last 6 years. It was working fine since then. Suddenly it stopped working, which means we don't see any Backup in our S3 bucket since 24th March. Up on diagnosing the problem, we realized that it is failing since then and the error is
STEP1
exec msdb.dbo.rds_restore_database
@restore_db_name='RestoreDbFromS3',
@s3_arn_to_restore_from='arn:aws:s3:::awsbucketName/SqlServerDb.bak';
STEP 2
exec msdb.dbo.rds_task_status @task_id=7;
Response indicates Error with following Task Description
[2022-05-28 12:51:22.030] Task execution has started.
[2022-05-28 12:51:22.237] Aborted the task because of a task failure or an overlap with your preferred backup window for RDS automated backup.
[2022-05-28 12:51:22.240] Task has been aborted
[2022-05-28 12:51:22.240] The provided token has expired.
We studied a lot to identify the root cause and solution but could not find anything accurately relevant.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/SQLServer.Procedural.Importing.html#SQLServer.Procedural.Importing.Native.Troubleshooting
above link shows troubleshooting options as per the error responses, but this does not include the error response that we are getting.
Note: between 25th & 26th March, our aws instance was suspended for couple of hours due to delayed payment of monthly invoice. we restored the same quickly. Everything on the same aws account is working fine since then, but we just found out that db backup service has impacted as we see the last successful backup available in S3 bucket is of dated 24th March.
We suspect that some token has expired up on account suspension, but are unable to identify which one and how to restore the same back to normal.
Help, Assistance and Guidance would be much appreciated.
Hello.
I have questions about policy, lifecycle and retention for AWS Backup. I am configuring backups for EC2.
1. Can I create one full backup for every week?
2. I understand the first backup is full, then all backups are incrementals, but if the retention is reached, this generates a new full backup?
3. Is the retention applied to cold storage or warn storage?
4. Is there any way for backup estimation?
5. What is the purpose for "start within" and "complete within", if I have a backup window start time?
Thank you.
Everything is set for the backup of RDS to S3. But when executed :
exec msdb.dbo.rds_backup_database @source_db_name='altahrirVersion', @s3_arn_to_backup_to= 'arn:aws:s3:::mumbaisqlserverbakup1/back1.bak', @overwrite_S3_backup_file=1;
the % complete remained as 0% till next day
Then I used:
exec msdb.[dbo].[rds_cancel_task] @task_id= 1
the task now shows: CANCEL_REQUESTED and 0%
Now i am stuck. I cannot create a new backup or cancel the standing one!
Please help me Thanks
Hi all, my company has been running a single page questionnaire/registering website for one of our services. For this, AWS was chosen to host the website and database.
All good so far anyway, it's been working absolutely fantastic! Now, a time has come up where the questionnaire isn't very relevant anymore and we would like to make a backup of all database information, and the website runs on the ec2 instances. I am pretty new to AWS as, unfortunately, a previous person in my position set this up who had better understanding of this platform.
The interface to AWS can be a bit confusing to me as a beginner, I really just need to make backups and turn off the instances so costs can be reduced but do not know where to go and what to do. Any help available?
Hi everyone, I need to create a backup for AWS MSK, and I found this article https://aws.amazon.com/en/blogs/big-data/back-up-and-restore-kafka-topic-data - using-amazon-msk-connect/ but the problem is that we have too many topics and new topics are created every day.
How do I use this MSK backup solution in disaster recovery cases?