Facebook
Twitter
-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion
Resolved Backup error
- Thread starter PedroN
- Start date
U
UFHH01
Guest
Hi PedroN,
pls. try to RE-read your "error" - message, because it will help you to understand, that backups from CACHED - content can always result in issues/problems, due to the case, that a cached content may not be existent anymore, when the compress - process reaches the content.
You have the choice to exclude certain files/folders, with the option:
Consider to exclude a complete cache folder, as for example: */cache/* or */wp-content/cache/*
"TEMP" or/and "TMP" - folders should as well being excluded from backups.
pls. try to RE-read your "error" - message, because it will help you to understand, that backups from CACHED - content can always result in issues/problems, due to the case, that a cached content may not be existent anymore, when the compress - process reaches the content.
You have the choice to exclude certain files/folders, with the option:
Exclude certain files from the backup
Consider to exclude a complete cache folder, as for example: */cache/* or */wp-content/cache/*
"TEMP" or/and "TMP" - folders should as well being excluded from backups.
Best advice when running a backup from the console. However, if the user runs it from GUI's "Backup Manager" he won't be able to exclude certain files.
For that reason I would like to add that the error shown in the screenshot can simply be ignored. It does not matter whether the cache directories are backed up or not, as they are just temporary files that can be re-created by Wordpress after a restore.
For that reason I would like to add that the error shown in the screenshot can simply be ignored. It does not matter whether the cache directories are backed up or not, as they are just temporary files that can be re-created by Wordpress after a restore.
Hello,Hi PedroN,
pls. try to RE-read your "error" - message, because it will help you to understand, that backups from CACHED - content can always result in issues/problems, due to the case, that a cached content may not be existent anymore, when the compress - process reaches the content.
You have the choice to exclude certain files/folders, with the option:
Exclude certain files from the backup
Consider to exclude a complete cache folder, as for example: */cache/* or */wp-content/cache/*
"TEMP" or/and "TMP" - folders should as well being excluded from backups.
Thanks for asnwering, but like @Peter Debik says I can not exclude this folders through plesk gui, another problem now that I have is when trying to download them:
http://prntscr.com/cdj8qu
Waiting a reply,
Pedro
Please see the content of /etc/psa/psa.conf and check the value of DUMP_D and DUMP_TMP_D. Is one of these set to
var/lib/psa/tmp? In that case try /var/lib/psa/tmp (watch the first '/' that might be missing according to your screenshot). Default values however should be
DUMP_D /var/lib/psa/dumps
DUMP_TMP_D /tmp
Also check the free disk space of the partition that your DUMP_TMP_D resides on. Maybe the disk space is exhausted, so that temporary backup files cannot be created.
var/lib/psa/tmp? In that case try /var/lib/psa/tmp (watch the first '/' that might be missing according to your screenshot). Default values however should be
DUMP_D /var/lib/psa/dumps
DUMP_TMP_D /tmp
Also check the free disk space of the partition that your DUMP_TMP_D resides on. Maybe the disk space is exhausted, so that temporary backup files cannot be created.
I have done what you said and gave 777 permissions to tmp but now it shows this when trying to download: http://prntscr.com/cdvum5
When creating the backup it shows me this other errors: http://prntscr.com/cdvuy0
I have changed the var/lib/psa/tmp to /var/lib/psa/tmp and given permissions 777 to that folder
continue with this same error: http://prntscr.com/ce175v
You are presenting two different operating situations. These two errors may be interconnected, but they may not be the same. The one error you are discussing is an error message when creating backups, the other one is from restoring backups. We were last discussing creating backups and the seemingling missing or inaccessible-for-write dump directory. Has that error been resolved?
Well this 2 errors: http://prnt.sc/ce175v http://prnt.sc/cdvum5 is not when restoring, it is when I am trying to download the file to my computer.
And this other error http://prnt.sc/cdvuy0 is another different error I have independent from the one of the cache that we where discussing at the beginning that was this one: http://prnt.sc/ccbl3z
I suggest to focus on the upload issue only. Does this issue still exist after changing the dump temporary repository path and restarting Plesk as described earlier? If it still exists, how much disk space is free on the partition that the dump directory is on and how large is the backup you are trying to do?
The download issue no? Because the issue is when I try to download the backup
I have the dump temporary repository path at /var/lib/psa/tmp and restarted plesk as you said, and also have enough space on the partition http://prntscr.com/ce6568 and the backup is 6gb only
(a) In my opinion http://prnt.sc/cdvuy0 is an upload issue, not a download issue. Plesk is trying to upload a backup to your external FTP storage and fails. With a correct path and correct directory permissions to /var/lib/psa/tmp this should not occur. You are now saying that this error occurs when you try to download a backup, but that does not make sense to me.
(b) http://prnt.sc/ce175v and http://prnt.sc/cdvum5 are showing a download screenshot. The download is interrupted while loading the file. I guess that the file cannot be downloaded, because a temporary copy of it cannot be stored or accessed for the same reason that (a) does not work. This is why I suggest to first solve (a). If (b) is not for the same reason that (a) is, it can have hundreds of reasons, e.g. a misconfigured web server, a bad internet connection, a security software on your computer. But I'd not start working on that issue before (a) is solved.
If (a) and (b) are indeed the same issues and Plesk is looking at a download to your local computer the same way it looks at uploading a file to FTP, you still need to solve (a), because Plesk obviously is unable to store a temporary copy of files to the directory. In my opinion the directory path given is wrong. It is still missing the leading slash ('/'), and I wonder how that can be after you changed the path in /etc/psa/psa.conf and restarted Plesk. I suggest that you change the path again to a completely different dump directory, e.g. one that you create descending from / (root) directory and giving it 777 permissions just for testing. Does the error still occur after that change and more important does the error message change? This test is simply to make sure that the file path in the Plesk configuration has *really* been updated and the new configuration imported by Plesk.
(b) http://prnt.sc/ce175v and http://prnt.sc/cdvum5 are showing a download screenshot. The download is interrupted while loading the file. I guess that the file cannot be downloaded, because a temporary copy of it cannot be stored or accessed for the same reason that (a) does not work. This is why I suggest to first solve (a). If (b) is not for the same reason that (a) is, it can have hundreds of reasons, e.g. a misconfigured web server, a bad internet connection, a security software on your computer. But I'd not start working on that issue before (a) is solved.
If (a) and (b) are indeed the same issues and Plesk is looking at a download to your local computer the same way it looks at uploading a file to FTP, you still need to solve (a), because Plesk obviously is unable to store a temporary copy of files to the directory. In my opinion the directory path given is wrong. It is still missing the leading slash ('/'), and I wonder how that can be after you changed the path in /etc/psa/psa.conf and restarted Plesk. I suggest that you change the path again to a completely different dump directory, e.g. one that you create descending from / (root) directory and giving it 777 permissions just for testing. Does the error still occur after that change and more important does the error message change? This test is simply to make sure that the file path in the Plesk configuration has *really* been updated and the new configuration imported by Plesk.
Yes sorry that is an upload issue, I confused with (b) that is the download issue.
I changed to /root/dump with 777 permissions this is now my config file: http://pastebin.com/SasAriuN but the problem when trying to download is the same http://prntscr.com/cff0ke but if I go into /root/dump I can see this files of dump http://prntscr.com/cff0py
So no idea of what is going on.
I'd love to find out why (b) does not work, but as said before, this can have hundreds of reasons. Did you make changes to MIME types on the server, e.g.?
I still recommend to first solve (a). Is (a) still giving the same error that it gave before? I mean, can we rule out that the issue is caused by an inaccessible path?
I still recommend to first solve (a). Is (a) still giving the same error that it gave before? I mean, can we rule out that the issue is caused by an inaccessible path?
The (a) issue seems to be solved because the last days the backups have been sent to the ftp repository and no errors found, look http://prntscr.com/cfnwkw
The problem comes when for example trying to download the backup of 7/set that you can I see I downloaded it from the repository, but when trying to download to my computer there is the error of the page not found
I have not changed anything about this mime types.
Another question, is not there any tool to repair plesk functions of something like that?
