Page 2 of 3

Re: v-backup-user: Not enough space on device

Posted: Tue Jan 23, 2018 4:42 pm
by steens
alexcy wrote: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.

Re: v-backup-user: Not enough space on device

Posted: Tue Jan 23, 2018 5:09 pm
by alexcy
That's a good thought; however I have a website which is 90 GB!

Re: v-backup-user: Not enough space on device

Posted: Wed Jan 24, 2018 6:55 am
by 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 ?

Re: v-backup-user: Not enough space on device

Posted: Thu Jan 25, 2018 3:23 pm
by steens
mehargags wrote:/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?

Re: v-backup-user: Not enough space on device

Posted: Thu Jan 25, 2018 3:38 pm
by mehargags
steens wrote:
mehargags wrote:/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!!

Re: v-backup-user: Not enough space on device

Posted: Tue Feb 13, 2018 7:45 pm
by steens
mehargags wrote:
Thu Jan 25, 2018 3:38 pm
steens wrote:
mehargags wrote:/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

Re: v-backup-user: Not enough space on device

Posted: Wed Feb 14, 2018 12:12 am
by 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

Re: v-backup-user: Not enough space on device

Posted: Thu Feb 22, 2018 12:16 pm
by steens
dfrye wrote:
Wed Feb 14, 2018 12:12 am
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

Re: v-backup-user: Not enough space on device

Posted: Wed Feb 28, 2018 12:18 pm
by skurudo
steens wrote:
Thu Feb 22, 2018 12:16 pm
I created an issue on GitHub in the hopes that someone will do something.
In the next release this problem will be fixed.

Re: v-backup-user: Not enough space on device

Posted: Fri Mar 02, 2018 2:52 am
by 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