WevDav Backup destination error

[move3a]

Hi.
I have a WebDav destination in Backup process. But error occours only in an account
9gb file size.
Thanks

This is the log:

Validating destination path /WHM/2017-05-05
[2017-05-05 13:20:23 +0200] info [cpbackup_transporter] Path exists
[2017-05-05 13:20:23 +0200] info [cpbackup_transporter] Uploading /backup/2017-05-05/accounts/omsor2017.tar.gz to /WHM/2017-05-05/omsor2017.tar.gz
[2017-05-05 13:20:23 +0200] info [cpbackup_transporter] Attempting to upload /backup/2017-05-05/accounts/omsor2017.tar.gz to /WHM/2017-05-05/omsor2017.tar.gz for destination:  OpenDrive
[2017-05-05 13:20:23 +0200] info [cpbackup_transporter] Upload attempt #1 starting for /backup/2017-05-05/accounts/omsor2017.tar.gz to /WHM/2017-05-05/omsor2017.tar.gz for destination:  OpenDrive
[2017-05-05 13:20:24 +0200] info [cpbackup_transporter] Setting custom header Content-Length to '9091003093'
[2017-05-05 13:32:03 +0200] warn [cpbackup_transporter] Upload attempt failed: put /backup/2017-05-05/accounts/omsor2017.tar.gz failed at /usr/local/cpanel/Cpanel/LoggerAdapter.pm line 27.
        Cpanel::LoggerAdapter::warn(Cpanel::LoggerAdapter=HASH(0x2723858), "Upload attempt failed: put /backup/2017-05-05/accounts/omsor2"...) called at /usr/local/cpanel/Cpanel/Backup/Queue.pm line 494
        Cpanel::Backup::Queue::transport_backup::attempt_to_upload_file(Cpanel::Backup::Queue::transport_backup=HASH(0x277d4b8), Cpanel::Transport::Files::WebDAV=HASH(0x3283f40), "/backup/2017-05-05/accounts/omsor2017.tar.gz", "/WHM/2017-05-05/omsor2017.tar.gz", Cpanel::LoggerAdapter=HASH(0x2723858)) called at /usr/local/cpanel/Cpanel/Backup/Queue.pm line 256
        Cpanel::Backup::Queue::transport_backup::process_task(Cpanel::Backup::Queue::transport_backup=HASH(0x277d4b8), cPanel::TaskQueue::Task=HASH(0x31feb90), Cpanel::LoggerAdapter=HASH(0x2723858)) called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/cPanel/TaskQueue.pm line 586
        eval {...} called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/cPanel/TaskQueue.pm line 589
        cPanel::TaskQueue::__ANON__() called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/cPanel/StateFile.pm line 238
        eval {...} called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/cPanel/StateFile.pm line 238
        cPanel::StateFile::Guard::call_unlocked(cPanel::StateFile::Guard=HASH(0x319da68), CODE(0x30ea688)) called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/cPanel/TaskQueue.pm line 594
        cPanel::TaskQueue::process_next_task(cPanel::TaskQueue=HASH(0x25beab8)) called at /usr/local/cpanel/bin/cpbackup_transporter line 151
        eval {...} called at /usr/local/cpanel/bin/cpbackup_transporter line 149
[2017-05-05 13:32:03 +0200] info [cpbackup_transporter] Error encountered
[2017-05-05 13:32:03 +0200] info [cpbackup_transporter] Error is not a reference put /backup/2017-05-05/accounts/omsor2017.tar.gz failed
[2017-05-05 13:32:03 +0200] info [cpbackup_transporter] Using WebDAV URL https://webdav.opendrive.com:443/WHM
[2017-05-05 13:32:05 +0200] info [cpbackup_transporter] Upload attempt #2 starting for /backup/2017-05-05/accounts/omsor2017.tar.gz to /WHM/2017-05-05/omsor2017.tar.gz for destination:  OpenDrive

 

[cPanelMichael]

Hello,

It's possible the connection to the remote server is timing out due to the amount of time it's taking to transfer a backup of that size. Could you browse to "WHM >> Backup Configuration", scroll down to the WebDav destination, and edit the destination's "The time to wait for a response from the remote server, valued in seconds." value from "30" to "300" to see if that helps?

Thank you.

 

[move3a]

Hi Michael thanks for the reply.

I changed the parameter to "300" but the error also occurs. All other 1GB size accounts are loaded in less than 10 minutes.

Any help will be welcome, thanks

 

[cPanelMichael]

Hello,

Could you open a support ticket using the link in my signature so we can take a closer look at the affected system? You can post the ticket number here so we can update this thread with the outcome.

Thank you.