#Hey, i want help with estimating disk usage of Pterodactyl Wings and split them.

32 messages · Page 1 of 1 (latest)

fleet swan
#

I am really confused what you're asking.

#

I can assume lots of others are too and due to that there hasn't been an answer.

#

Still no need to go spam multiple times "no answer" :p

high snow
#

And how to estimate how much backup storage I should assign, if i give 2 backups per server, and let's say i have 2 servers that i dedicated 50GB in each, and they both use it 100%.

fleet swan
#

if you have 2 servers, both using 50G and want to have 2 backups per server, then simply put you need 200G for backups

high snow
#

And if when making a backup, that goes through the tmp directory first, or through the archive directory first, or straight to the backup folder.

high snow
fleet swan
#

You are thinking of this very.. complicatedly

high snow
#

Which creates first a 3rd backup

#

And then delete the older one

fleet swan
#

You said you have 2 backups slots

#

so yeah it deletes oldest one

high snow
#

But it does after the new one is created

#

Then after it verifies it's created

#

Then deletes the oldest one

#

Not sure if u get what im saying.

#

Ima try to explain better
Lets say,

I have a 20GB container, full of data, i gave it 2 backups,
So it can have up to 40GB of backup data, but when a new one is going to get created by the schedule, for a bit while its being created it will use up to 60GB, then after its being created without corruption it will delete the older one and go back to 40GB.

#

Or, that temporary 20GB backup while being created, its going to be created on the archive directory, or on the tmp directory, then oldest one from backup directory is going to get deleted, and then the new backup is going to get transferred from the tmp or the archive directory so the backup directory is never going to exceed the 40GB limit.

#

I think that this is more simple to understand, :O

humble widget
# high snow I think that this is more simple to understand, :O

Backups do not pre-check for file space, it lets the file system handle that. It creates a tar.gz of your data in the backups directory and attempts to create a backup. If it should fail, due to space limitations or other errors, it will pend/fail the backup task.

high snow
#

Im a little confused

#

Clearly it deletes first

humble widget
#

That’s the panel and it checks for the backup limit aka number of backups it’s allowed to have made and persistently have on file.

Wings is what actually makes the backup (file system and compression etc)

high snow
#

Yes

#

But it does actually delete the oldest backup before creating a new one right,

#

Before the scheduled task telling wings to create a new one, if limit exceed, it tells it to delete the older one first, correct me if wrong.

humble widget
#

You’d have to look at the $backup->delete function found in the deletebackupservice handler to see all that it does. I’m not able to search for it right now.

high snow
#

Okey, thank you.

humble widget
# high snow Okey, thank you.

Actually, after looking into the backup service further, it does appear to delete the oldest backup regardless if it’s a scheduled or manual backup, if your number of backups limit has been reached. Whenever the backup creation event is fired, it deletes the oldest and attempts to create a new one. That being said it still doesn’t check the file size, it only deletes the oldest backup. I don’t believe your backups count towards container space though as they’re in a different directory than your container volume and depend on file system space.