![]() ![]() ![]() So I started going deeper in the folder hierarchy and deleting all the subfolders on every level. I thought something must be wrong, because I could see objects in the directory. I went into AWS Console and tried deleting the folder again a few days later. I forgot to do that though, and a few days later I got a billing alert that my threshold was reached. So I left it and thought I'd go back and check the next day to see if it was still there. "Great!" I thought.īut I noticed the top level folder was still there, and many things within. This Delete operation showed me that there were 0 problems deleting anything, and showed many thousand deleted objects. After that manual move was complete, I selected the top-level folder and chose 'Delete' in the AWS Console.Because that operation requires restoring data temporarily so it can be moved, I decided to just download/re-upload the data into the new path manually.I tried moving a folder with terabytes of video data in them from one path to another within an S3 Glacier Deep Archive bucket.So here's how I ended up having two or three copies of many terabytes of backup data: As a warning that even if AWS console says there were no problems deleting an object, you should always double-check to make sure it actually got deleted.Īnd to the second point, it gets more complicated with S3 Glacier Deep Archive, because I'm used to some operations taking 12 hours or longer, so I got lazy and didn't double-check on the delete operations. ![]() As a reminder to always set up billing alerts in AWS, no matter how small your AWS account! Without that notification, I would've only found out about this problem at the end of the month-and paid about 10x my normal monthly rate until I fixed the problem!.Knowing that I had just rearranged my entire backup plan because I wanted to change the structure of my archives both locally and in my S3 Glacier Deep Archive mirror on AWS, I suspected something didn't get moved or deleted within my backup S3 bucket.īut I wanted to write this up for two reasons: A few days ago, my personal AWS account's billing alert fired, and delivered me an email saying I'd already exceeded my personal comfort threshold-in the second week of the month! ![]()
0 Comments
Leave a Reply. |