• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

full back up using up all space in /tmp

C

chrisl@

Guest
Hello,

I am trying to take a full backup before I do an upgrade and I am having problems where the /tmp directory is filling completely up. Is there away with backup to specify a different directory for creating the temp files?

-chrisl
 
same here

Hi I have the exact same problem.

I would think this is a plesk bug. They should deliever an parameter for the backup script that would allow pointing to another directory as tmp.

Obvisouly our tmp wiht 2GB is big enough, when we want to backup a single hosting wiht 13GB.

Feedback is much appreciacted
 
It is always best to give some info on your server when posting so good advice can be given. If running CentOS (or alike) do this:

#export VISUAL=nano; crontab -e

See if one of the entries is like:

5 3 * * * /usr/local/psa/bin/pleskbackup all /tmp >/dev/null 2>&1

Change /tmp to what ever directory you want the backup to be placed in.
 
hi phoenix

basicly my command on plesk 8.1.1 looks like this
/usr/local/psa/bin/pleskbackup all /srv/backup/file.dump

I think the problem is with tar that is used internally with pleskbackup. tar write tempoary files to /tmp. It seems that is no way to control it.
 
I have mine set to:

5 3 * * * /usr/local/psa/bin/pleskbackup all /usr/backup/file.dump >/dev/null 2>&1

I never have anything left behind in /tmp - if it's indeed supposed to use /tmp. Is it possible your permissions/ownership of /tmp is not allowing cleanup?
 
ty again for the reply...

The problem is not that tmp stays full and doesn't get cleaned up.

it is more like the plesk backup is using 100% for a while and after the backup is gone the tmp is clean again.

the problem is with the resulting dump file created it is way to small to include all data.

e.g. if i backup a 12GB hosting or the wohle server the backup is like 600 mb in size, if i backup a hosting with close to 2GB it will result in a backup file larger as 1GB

here is a real life example of what i mean

/usr/local/psa/bin/pleskbackup -v clients --from-file=/srv/backup/backup.txt - > /srv/backup/nosfact2.dump

/tmp is growing slowy

p15200145:/srv/backup # ll /srv/backup/ && ll /tmp/ && df
total 36111388
drwxr-xr-x 4 root root 4096 May 29 22:26 .
drwxr-xr-x 8 root root 77 May 10 19:55 ..
-rw-r--r-- 1 root root 8 May 29 22:25 backup.txt
drwxr-xr-x 2 root root 4096 May 29 04:04 db
drwxr-xr-x 61 root root 8192 May 8 19:21 etc
-rw-r--r-- 1 root root 2825 May 10 03:18 map.txt
-rw-r--r-- 1 root root 15420184 May 29 13:22 nosfact.psa.archive
-rw-r--r-- 1 root root 10395617 May 29 22:18 nosfact.psa.dump
-rw-r--r-- 1 root root 10289152 May 29 22:26 nosfact2.dump
-rw-r--r-- 1 root root 0 May 17 04:33 result.txt
-rw------- 1 root root 36750455559 May 9 20:37 weekday.3.psa.archive.new
-rw-r--r-- 1 root root 15037310 May 29 11:32 weekday.7.psa.archive
-rw-r--r-- 1 root root 176420385 May 29 22:21 xrow.psa.dump
total 490236
drwxrwxrwt 6 root root 280 May 29 22:27 .
drwxr-xr-x 20 root root 4096 May 11 06:09 ..
drwxrwxrwt 2 root root 40 May 11 06:09 .ICE-unix
drwxrwxrwt 2 root root 40 May 11 06:09 .X11-unix
-rw------- 1 epsiplus psacln 12288 May 14 12:16 .crontab.XXXXJcsClg.swp
-rw------- 1 epsiplus psacln 12288 May 14 14:39 .swp
-rw------- 1 epsiplus psacln 0 Mar 19 2005 crontab.XXXXJcsClg
-rw-r--r-- 1 root root 0 May 29 22:26 fileLz1deW
-rw-r--r-- 1 root root 0 May 29 22:26 fileb6mT8z
-rw-r--r-- 1 root root 500989952 May 29 22:27 fileefV20R
-rw-r--r-- 1 root root 0 May 29 22:26 fileqZFz3d
srw-rw-rw- 1 root root 0 May 11 06:09 spamd_full.sock
drwx------ 2 root root 60 May 29 21:42 ssh-GuclEY1087
drwx------ 2 root root 60 May 29 22:08 ssh-SQrVpN2701
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 962504 91536 822076 11% /
tmpfs 2025252 0 2025252 0% /dev/shm
/dev/sda5 4873184 1798932 3074252 37% /usr
/dev/sda6 4873184 3849852 1023332 80% /var
/dev/sda7 19521472 7308 19514164 1% /home
/dev/sda8 211863416 71216612 140646804 34% /srv
none 2025252 490232 1535020 25% /tmp


/tmp is now full
p15200145:/srv/backup # ll /srv/backup/ && ll /tmp/ && df
total 36111388
drwxr-xr-x 4 root root 4096 May 29 22:26 .
drwxr-xr-x 8 root root 77 May 10 19:55 ..
-rw-r--r-- 1 root root 8 May 29 22:25 backup.txt
drwxr-xr-x 2 root root 4096 May 29 04:04 db
drwxr-xr-x 61 root root 8192 May 8 19:21 etc
-rw-r--r-- 1 root root 2825 May 10 03:18 map.txt
-rw-r--r-- 1 root root 15420184 May 29 13:22 nosfact.psa.archive
-rw-r--r-- 1 root root 10395617 May 29 22:18 nosfact.psa.dump
-rw-r--r-- 1 root root 10289152 May 29 22:26 nosfact2.dump
-rw-r--r-- 1 root root 0 May 17 04:33 result.txt
-rw------- 1 root root 36750455559 May 9 20:37 weekday.3.psa.archive.new
-rw-r--r-- 1 root root 15037310 May 29 11:32 weekday.7.psa.archive
-rw-r--r-- 1 root root 176420385 May 29 22:21 xrow.psa.dump
total 2025256
drwxrwxrwt 6 root root 280 May 29 22:29 .
drwxr-xr-x 20 root root 4096 May 11 06:09 ..
drwxrwxrwt 2 root root 40 May 11 06:09 .ICE-unix
drwxrwxrwt 2 root root 40 May 11 06:09 .X11-unix
-rw------- 1 epsiplus psacln 12288 May 14 12:16 .crontab.XXXXJcsClg.swp
-rw------- 1 epsiplus psacln 12288 May 14 14:39 .swp
-rw------- 1 epsiplus psacln 0 Mar 19 2005 crontab.XXXXJcsClg
-rw-r--r-- 1 root root 0 May 29 22:26 fileLz1deW
-rw-r--r-- 1 root root 0 May 29 22:26 fileb6mT8z
-rw-r--r-- 1 root root 2069778432 May 29 22:29 fileefV20R
-rw-r--r-- 1 root root 0 May 29 22:26 fileqZFz3d
srw-rw-rw- 1 root root 0 May 11 06:09 spamd_full.sock
drwx------ 2 root root 60 May 29 21:42 ssh-GuclEY1087
drwx------ 2 root root 60 May 29 22:08 ssh-SQrVpN2701
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 962504 91536 822076 11% /
tmpfs 2025252 0 2025252 0% /dev/shm
/dev/sda5 4873184 1798932 3074252 37% /usr
/dev/sda6 4873184 3849856 1023328 80% /var
/dev/sda7 19521472 7308 19514164 1% /home
/dev/sda8 211863416 71214896 140648520 34% /srv
none 2025252 2025252 0 100% /tmp

now the backup is done the dump file is too small and tmp is clean again


p15200145:/srv/backup # ll /srv/backup/ && ll /tmp/ && df
total 36111388
drwxr-xr-x 4 root root 4096 May 29 22:26 .
drwxr-xr-x 8 root root 77 May 10 19:55 ..
-rw-r--r-- 1 root root 8 May 29 22:25 backup.txt
drwxr-xr-x 2 root root 4096 May 29 04:04 db
drwxr-xr-x 61 root root 8192 May 8 19:21 etc
-rw-r--r-- 1 root root 2825 May 10 03:18 map.txt
-rw-r--r-- 1 root root 15420184 May 29 13:22 nosfact.psa.archive
-rw-r--r-- 1 root root 10395617 May 29 22:18 nosfact.psa.dump
-rw-r--r-- 1 root root 10289152 May 29 22:26 nosfact2.dump
-rw-r--r-- 1 root root 0 May 17 04:33 result.txt
-rw------- 1 root root 36750455559 May 9 20:37 weekday.3.psa.archive.new
-rw-r--r-- 1 root root 15037310 May 29 11:32 weekday.7.psa.archive
-rw-r--r-- 1 root root 176420385 May 29 22:21 xrow.psa.dump
 
yes this nosfact sample has a size of 13 GB uncompressed... but the resulting dump file is just 10 MB

nothing can compress so good.

I had a suggestion from my ISP to make a new partion and create a super big tmp dir, but this a workaround not a solution and no very pratical
 
Hi i just found out that tis issue is solved in plesk 8.2 wiht a new setting you can do
 
Back
Top