mirror of
https://github.com/pelican-dev/panel.git
synced 2026-07-16 04:03:50 +03:00
The backup schedule should delete the oldest backups #278
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SirEndii on GitHub (Mar 17, 2025).
Creating Backups using a schedule does not work if the server is on its backup limit.
Like in pterodactyl(iirc) the oldest backups should be deleted when a new backup is created using a schedule.
Currently, it just stops creating backups, which I just noticed. I deleted some backups to make some free space for more.
I have a daily midnight schedule to create backups - you can see that there are only week old backups there since the backup space is full.
Not sure if it is relevant, but I am using S3 for backups.
@rmartinoscar commented on GitHub (Mar 17, 2025):
Pterodactyl didn't remove backup either, you have to make a schedule task that removes a backup before taking a new one
@mristau commented on GitHub (Mar 17, 2025):
can you delete a backup using the delete action, else an action like "delete backup" would be nice
@Boy132 commented on GitHub (Mar 17, 2025):
That's wrong, on Pterodactyl the oldest (non-locked) backup will be deleted once it reaches the backup limit.
If this doesn't happen in Pelican it's a bug.
f2f3ee548f/app/Services/Backups/InitiateBackupService.php (L92-L110)@rmartinoscar commented on GitHub (Mar 18, 2025):
I can't see anywhere the
$overrideis set totrueeven on our repo@GameAreaCZ commented on GitHub (Mar 20, 2025):
I do not know, but for me according the timestamps and backups names it looks like it is working?
@SirEndii commented on GitHub (Mar 20, 2025):
Interesting
It at least does not for me - after I deleted some backups it created new ones
Maybe because I use S3?
@GameAreaCZ commented on GitHub (Mar 20, 2025):
That is possible I'm not using the S3.
@TigerGamer134 commented on GitHub (Apr 8, 2025):
Works as it should with S3 for me
@SirEndii commented on GitHub (Apr 8, 2025):
Due to the mixed feedback, I will deep test that in the next few days again
@EL-JAYY commented on GitHub (Apr 9, 2025):
Same issue here with local Backups
@EL-JAYY commented on GitHub (Apr 12, 2025):
i get this once the Backup Limit is reached
after that the shedule won't work anymore, and i need to delete and re create it
@SirEndii commented on GitHub (Apr 22, 2025):
I am unable to reproduce this anymore on my canary installation
@Boy132 commented on GitHub (May 13, 2025):
I can't reproduce it either so I'm closing this for now.
@TheTwoBoom commented on GitHub (Sep 13, 2025):
Hey, I also got this exact same issue
1.0.0-beta24 on Debian 12
Maybe the bug only occurs if you uploaded the schedule via the import function? (Because that's what I did)
@TheTwoBoom commented on GitHub (Sep 13, 2025):
I'm using S3 (Cloudflare R2 to be exact)