• 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.

Resolved Backup fails to stored to FTP storage

K

Kimon Nouskalis

New Pleskian
After istalling update #18 the backup can't any more (worked fine for the last year) store the backup to remote FTP storage with the following error:
'Unable to upload the backup to the FTP storage: Unable to save data to an archive. Check whether the target directory is accessible for writing. For more information, see the log file (/opt/psa/PMM/sessions/2017-03-21-011003.061/migration.log)'

migration.log ends with:

[2017-03-21 01:30:45.730| 4170] INFO: Repository 'ftps://xx.xx.xx.xx': Get packed backup info from file backup_1703210110.tar
[2017-03-21 01:30:45.730| 4170] INFO: Ftp init url ftps://xx.xx.xx.xx/backup_1703210110.tar
[2017-03-21 01:30:45.953| 4170] INFO: Ftp init url ftps://xx.xx.xx.xx/backup_1703210110.tar
[2017-03-21 01:30:46.176| 4170] INFO: File dump-header not found on first position in archive. First entry is "clients/awebsite/domains/awebsite.gr$
[2017-03-21 01:30:46.177| 4170] INFO: Repository 'ftps://xx.xx.xx.xx': Get backup info from file backup_1703210110.tar
[2017-03-21 01:30:46.178| 4170] INFO: Dump type '' does not match object type 'server', skip.
[2017-03-21 01:30:46.178| 4170] INFO: Repository 'ftps://xx.xx.xx.xx': Rotate structured backups is finished for owner d0407e97-5448-4d67-9938-512c8$
[2017-03-21 01:30:46.179| 4170] INFO: pmm-ras finished. Exit code: 0

Actually the backup procedure writes the first 16K of the backup (12GB size) to the FTP storage and then stops. There isn't any error at the log of the remote ftp server.

I have also install the update #20 but the problem still exists.

Any clue ?????
 
It is thinkable that the temporary storage space is used up (for example by downloaded update files that were not removed after an update). Please look into /etc/psa/psa.conf and find the variables DUMP_D and DUMP_TMP_D. Check the directories and/or partitions where these point to whether these directories are writeable and have enough space left on the device or partition. Permissions on DUMP_D and DUMP_TMP_D should be rwxr-xr-x, owner should bee root:root.
 
Dear Peter,

Thank you for your reply.

My server settings
The /etc/psa/psa.conf
# Backups directory
DUMP_D /var/lib/psa/dumps
DUMP_TMP_D /usr/local/psa/PMM/tmp

Permissions
root@myserver:/var/lib/psa# ls -ld /var/lib/psa/dumps
drwxr-xr-x 5 psaadm psaadm 12288 Mar 21 09:58 /var/lib/psa/dumps
(in /var/lib/psa/dumps/{customer name} child directories the user is root.

root@myserver:/usr/local/psa/PMM# ls -ld /usr/local/psa/PMM/tmp
drwxr-xr-x 125 psaadm psaadm 20480 Mar 21 09:58 /usr/local/psa/PMM/tmp

Also the available space
root@myserver:/var/lib/psa# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/myserver--vg-root 117G 51G 61G 46% / (51 GB available)
udev 5.9G 4.0K 5.9G 1% /dev
tmpfs 1.2G 756K 1.2G 1% /run
none 5.0M 24K 5.0M 1% /run/lock
none 5.9G 176K 5.9G 1% /run/shm
/dev/sda1 236M 89M 135M 40% /boot



The problem is not the plesk backup, the plesk backup is finished and it remains visible in the backup manager (image bellow).

upload_2017-3-21_17-53-57.png

The problem is that the backup it is not uploaded to the remote ftp storage space.

Backup was working without any problem for over a year. Issue started after installing Update#18 (or probably an older included, I had to update since December 2016).

Please keep in mind that the backup is starting to upload the remote ftp storage space and stops after 16KB of transfer
 
The problem was the sftp connection.
I have remove the "Use FTPS" check option in "FTP Storage Settings" and now works like before.

I will try to find why FTPS creates the error

My plesk server and my ftp server (on another IP) have the same comodo wildcard essential certificate. Maybe this is the problem.
 
Last edited:
Very interesting, because in your log excerpt it said "ftps://", this really looks like FTPS. Anyway, good to know.
 
Also strange is that the FTP server log has no error !!!
Plesk backup starts a connection(#1) and the it opens another one (#2)

Plesk Backup Connection #1 - FTP server session log
{myPleskServerIP} [1298] 01:10:08 Connected
{myPleskServerIP} [1298] 01:10:08 >>> 220 ftp.internetarea.hosting FTP ermis.internetarea.net
{myPleskServerIP} [1298] 01:10:08 <<< AUTH SSL
{myPleskServerIP} [1298] 01:10:08 >>> 234 Enabling SSL
{myPleskServerIP} [1298] 01:10:08 <<< USER plesk.backup.user
{myPleskServerIP} [1298] 01:10:08 >>> 331 User name ok, need password or otp-md5 173 {a key} skey
{myPleskServerIP} [1298] 01:10:08 <<< PASS ************************
{myPleskServerIP} [1298] 01:10:08 >>> 230 User logged in, proceed
{myPleskServerIP} [1298] 01:10:08 <<< PBSZ 0
{myPleskServerIP} [1298] 01:10:08 >>> 200 Protection block size set
{myPleskServerIP} [1298] 01:10:08 <<< PROT P
{myPleskServerIP} [1298] 01:10:08 >>> 200 Protection level set
{myPleskServerIP} [1298] 01:10:08 <<< PWD
{myPleskServerIP} [1298] 01:10:08 >>> 257 "/"
{myPleskServerIP} [1298] 01:10:08 <<< EPSV
{myPleskServerIP} [1298] 01:10:08 >>> 229 Entering Extended Passive Mode (|||4306|) (firewall allows ftp passive ports)
{myPleskServerIP} [1298] 01:10:08 <<< TYPE A
{myPleskServerIP} [1298] 01:10:08 >>> 200 Type successfully set
{myPleskServerIP} [1298] 01:10:08 <<< NLST
{myPleskServerIP} [1298] 01:10:08 >>> 150 Data connection created
{myPleskServerIP} [1298] 01:10:22 <<< QUIT
{myPleskServerIP} [1298] 01:10:22 >>> 221 Service closing control connection
{myPleskServerIP} [1298] 01:10:22 Disconnected (user = plesk.sites, bytes transfered = 546)

Plesk Backup Connection #2 - FTP server session log
{myPleskServerIP} [1178] 01:10:22 Connected
{myPleskServerIP} [1178] 01:10:22 >>> 220 ftp.internetarea.hosting FTP ermis.internetarea.net
{myPleskServerIP} [1178] 01:10:22 <<< AUTH SSL
{myPleskServerIP} [1178] 01:10:22 >>> 234 Enabling SSL
{myPleskServerIP} [1178] 01:10:22 <<< USER plesk.backup.user
{myPleskServerIP} [1178] 01:10:22 >>> 331 User name ok, need password or otp-md5 226 {a key} skey
{myPleskServerIP} [1178] 01:10:22 <<< PASS ************************
{myPleskServerIP} [1178] 01:10:22 >>> 230 User logged in, proceed
{myPleskServerIP} [1178] 01:10:22 <<< PBSZ 0
{myPleskServerIP} [1178] 01:10:22 >>> 200 Protection block size set
{myPleskServerIP} [1178] 01:10:22 <<< PROT P
{myPleskServerIP} [1178] 01:10:22 >>> 200 Protection level set
{myPleskServerIP} [1178] 01:10:22 <<< PWD
{myPleskServerIP} [1178] 01:10:22 >>> 257 "/"
{myPleskServerIP} [1178] 01:10:22 <<< EPSV
{myPleskServerIP} [1178] 01:10:22 >>> 229 Entering Extended Passive Mode (|||4307|) (firewall allows ftp passive ports)
{myPleskServerIP} [1178] 01:10:22 <<< TYPE I
{myPleskServerIP} [1178] 01:10:22 >>> 200 Type successfully set
{myPleskServerIP} [1178] 01:10:22 <<< STOR backup_1703230110.tar
{myPleskServerIP} [1178] 01:10:22 >>> 150 Data connection created
{myPleskServerIP} [1178] 01:10:22 <<< QUIT
{myPleskServerIP} [1178] 01:10:22 >>> 221 Service closing control connection
{myPleskServerIP} [1178] 01:10:22 Disconnected (user = plesk.sites, bytes transfered = 16921)

Previous day
{myPleskServerIP} [15D4] 01:10:25 Disconnected (user = plesk.sites, bytes transfered = 16921)

With FTPS always stops at 16921 bytes !!!!!
 
According to the list of fixes in the latest micro update (#20), there is a fix for failing FTPS uploads:
"Backups could not be uploaded to an FTP repository via the FTPS protocol. (PPPM-5922)"
Please check whether the issue described in this thread here is resolved once micro update #20 is installed.
 
Hello,

Same problem for us.

Message in Plesk Backup:
Warning:
Unable to upload the backup to the FTP storage: Unable to save data to an archive. Check whether the target directory is accessible for writing. For more information, see the log file (/usr/local/psa/PMM/sessions/2017-03-27-000402.084/migration.log)

We don't have the "Use FTPS" option checked.

On the remote FTP, we have one file (cf uploaded file "cp2.jpg").
 

Attachments

  • cp.jpg
    cp.jpg
    23.7 KB · Views: 4
  • cp2.jpg
    cp2.jpg
    27 KB · Views: 2
You must log in or register to reply here.

Similar threads

S
Issue Plesk 18.0.64 Restore failing
Replies
1
Views
733
Sebahat.hadzhi
Sebahat.hadzhi
K
Resolved Backup error message gives curl command that will fail
Replies
2
Views
4K
kirsteng
K
M
Issue Backup to FTPS server fails after upgrade to Plesk 18.0.64
Replies
1
Views
860
mjehlenz
M
X
Issue Issue creating backup FTP/Local
Replies
8
Views
948
Xelar25
X
enerspace
Internal backup over CIFS / SSHFS mount
Replies
12
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top