I realize it’s been two weeks since I posted this. I honestly haven’t had time to sit and figure it out, but it does look like this is, or was, an error in the program? I will say, AMP did something that ate up all of my harddrive space. I only have a 53GB hard drive, but was storing all of my backups externally on a 2TB one. There was no way I didn’t have space for a backup, AMP was just acting as though I didn’t for some reason, and not deleting old files. The only way it might not have had space was by hitting the limit I had set, and deleting one backup would’ve left plenty of room for a new one.
Today I decided to return to this and completely uninstalled, removed the amp user folder, and suddenly freed up 75% of my primary hard drive. So AMP was taking up around 35GB of space for a single Minecraft instance with a world that was less than 10GB. Not sure if this was some kind of issue where every time it failed to back up it didn’t remove temporary files, or what, but I’ve been struggling with this hard drive space issue for the past couple of weeks and only now realized that AMP was somehow the cause. Trying with a fresh install to see if that can fix things.
EDIT: Having reinstalled AMP, I’ve been able to take manual backups, which I wasn’t able to do before. However, the scheduled backup I tried last night, at 3AM, did not work, so I’ve followed the advice from Daedalus and deleted the backups.json file on my install (I’d restored it from the broken install along with the backups, because I couldn’t find a way to restore an external backup from within AMP, which seems like an oversight to me). This did not fix my problem, mine still will not take a scheduled backup. I just set one for a minute ago, and nothing happened. I can at least now manually take backups, but I cannot do so automatically for some reason. A step in the right direction, I suppose. Still not sure how to fix the automatic backups, however.
Would like to note that I had also specified a different location than the default for my backups, so perhaps that does have something to do with why this is happening to people?
EDIT 2: Apparently, even though all the timestamps in the console and on files are correct, I noticed in the log that AMP thinks it is 4 hours in the future, so I’d set the time wrong on my automatic backup. This also explains why it hadn’t backed up last night, as I set it for 3AM every, but it was already midnight. So AMP thought it was already 4AM, so to it 3AM had already passed. Just ran a successful automatic backup.
Also wanted to note that I also have the same “double size” issue on backups that others mentioned. I believe it’s an issue with the Backups.json? I think it’s writing the size before being compressed, rather than after. But the compression is still taking place, as looking in the backups folder, I can confirm the file size is the same as it was before reinstalling. For me, this was initially only happening on manual backups, but the scheduled backup I just took is also displaying as twice its actual size. Attaching images for reference. This doesn’t bother me as much as the not being able to take backups, but I do wonder if it’ll cause problems with the storage limits for backups, and if maybe that caused my initial issues?
