v-backup-user: Not enough space on device Topic is solved

[steens]

It used to be /backup, why change that? Many people mount their /tmp as tmpfs as well.

Well, the backups still reside in /backup, but while they're being generated, they are in /tmp. Probably to make it faster by putting it in memory assuming it is a tmpfs.

[alexcy]

That's a good thought; however I have a website which is 90 GB!

[mehargags]

/tmp is tmpfs residing on RAM... which can be a bit of problem for bigger sites. Previously, /backup was used to generate tmp files.
If the /tmp runs out, it may mean out of memory issues on smaller VPS.

@Imperio, @Dpecca, can you clarify a bit on this issue ?

[steens]

/tmp is tmpfs residing on RAM... which can be a bit of problem for bigger sites. Previously, /backup was used to generate tmp files.
If the /tmp runs out, it may mean out of memory issues on smaller VPS.

@Imperio, @Dpecca, can you clarify a bit on this issue ?

Maybe it would be a good idea to just test if there's room in tmpfs and then choose a file system based on that?

[mehargags]

/tmp is tmpfs residing on RAM... which can be a bit of problem for bigger sites. Previously, /backup was used to generate tmp files.
If the /tmp runs out, it may mean out of memory issues on smaller VPS.

@Imperio, @Dpecca, can you clarify a bit on this issue ?

Maybe it would be a good idea to just test if there's room in tmpfs and then choose a file system based on that?

Good Idea, I second that!!

[steens]

/tmp is tmpfs residing on RAM... which can be a bit of problem for bigger sites. Previously, /backup was used to generate tmp files.
If the /tmp runs out, it may mean out of memory issues on smaller VPS.

@Imperio, @Dpecca, can you clarify a bit on this issue ?

Maybe it would be a good idea to just test if there's room in tmpfs and then choose a file system based on that?

Good Idea, I second that!!

Is there any way to push for this change or similar? It's pretty urgent, as we have around 50 different sites which are currently not being backed up properly because of this.

I imagine that the following would be a reasonable approximation to check if there's room:

Code: Select all

TMPAVAIL=$(df /tmp --output=avail | tail -n1)
BACKUPSIZE=$(du -s /home/$user | cut -n1)
if [ "$TMPAVAIL" -gt "$BACKUPSIZE" ]; then
	tmpdir=$(mktemp -p /tmp -d)
else
	tmpdir=$(mktemp -p /backup -d)
fi

[dfrye]

Any news here? Or a possible workaround? I also am not able to make a backup because my websites are simply too big.

Regards,

Detlev

[steens]

Any news here? Or a possible workaround? I also am not able to make a backup because my websites are simply too big.

Regards,

Detlev

I created an issue on GitHub in the hopes that someone will do something.
https://github.com/serghey-rodin/vesta/issues/1494

[skurudo]

I created an issue on GitHub in the hopes that someone will do something.

In the next release this problem will be fixed.

[bestamit]

First make Backup TMP location

Code: Select all

cd /
sudo mkdir tmpHD

Then

Code: Select all

sudo vi /usr/local/vesta/bin/v-backup-user 

edit line tmpdir=$(mktemp -p /tmp -d)
-with-
tmpdir=$(mktemp -p /tmpHD -d)
save the file

run the backup process again from UI or

Code: Select all

sudo /usr/local/vesta/bin/v-backup-users

This will also fix scheduled backup cron processes