Scheduled Backup Failed

[dansoftware]

Hello.

I have 3CX v16.0.910 under Debian v9.3. I backuped to FTP the following items: "License Key Information, FQDN & Conference" and "Custom Templates, Logos and Firmwares". There was no any problem for a long time. I added "Recordings (Backup and Restore will take longer)" recently. Schedule Backup does not work since that time:

Spoiler: Scheduled Backup Failed

3CX Phone System tried to backup but failed due to the following reason(s):
System.IO.IOException: Unable to write data to the transport connection: Broken pipe. --->
System.Net.Sockets.SocketException: Broken pipe
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.FtpClient.FtpSocketStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.FtpClient.FtpDataStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.Stream.CopyTo(Stream destination, Int32 bufferSize)
at _3cxNetBackupAndRestore._3cxBackup.FinishingTask()

There is no any problem with FTP connectivity. Backup works fine if I disable "Recordings (Backup and Restore will take longer)". Is there any way to diagnose and solve the problem?

 

[dansoftware]

I updated to the latest beta version: build 16.0.3.525. There is a change in it: "Added validation for FTP paths with spaces." But the problem still exists. I have solved it by disabling "Recordings (Backup and Restore will take longer)".

 

[AWS2P]

Is FTP destination one of your servers or one you rent in datacenter?
Perhaps you have to much data to transfer? is there enough space on FTP Side?
Recordings are on your PBX or from outside location?

Can you try with a google account and see if backup is working fine ?

 

[dansoftware]

Recordings are about 6,8 Gbytes and placed on the PBX. There is no any problem with FTP. It is my own server. There is a lot space on it. There is no any quota. aws2p, thanks for help. I have solved the problem already. I prefer not make any changes in a backup schedule in order not to break it again. 3CX software has too fragile mental state. It is better not to touch it without a strong necessary.

 

[AWS2P]

what is your FTP server?
on my Freebsd server i use proftpd as ftp server and and got in the past broken pipe messages and transfert aborted.

do you use a fiber line or only dsl, because with nearly 7Gb only for recordings, how much space do you use for one complete backup?

 

[dansoftware]

ProFTPD 1.3.5b Server (Debian).

The PBX and FTP are both located in a data center and connected to a network on a speed 1 Gbit/s.

 

[AWS2P]

ok problem is with Proftpd side, not on 3CX, i opened a bug ticket on this exactly same behavior, when big files where added to backup , every time backup aborted, it was working with small size backup perhaps 20 or 30Mo no more.

this is the thread i opened on bug tracker in 2018
https://github.com/proftpd/proftpd/issues/668

Release 1.35e of proftpd seems to work fine for me

 

[dansoftware]

I am not sure that the problem is connected with ProFTPD. The size of my current backups without recordings is about 157 Mbytes. Such archives are transferred by 3CX to the FTP without any problems in my configuration. But if I add recordings a zero size archive is created on the FTP. Or transferring may not start at all. It seems to me that there is a problem with big files inside 3CX software.

 

[dansoftware]

I tested my FTP server with files up to 4.4 Gbytes. There was no any problem with uploading and downloading. Larger files are not tested.

 

[Evolute IT]

I tested my FTP server with files up to 4.4 Gbytes. There was no any problem with uploading and downloading. Larger files are not tested.

Try uploading the backup to a Google Drive, see if the error occurs.

If it does, problem is on 3CX side.

If not, check your FTP. Might be active/passive issue.

 

[dansoftware]

Frederick Marcoux, thanks for help. I have solved the problem already. I prefer not make any changes in a backup schedule in order not to break it again. Active/passive mode of FTP was tested. There is no problem with it.

 

[AWS2P]

do you got zero bytes backup file created and backup aboretd with broken pipe message ?

 

[dansoftware]

Each time when I get the broken pipe message a zero size archive is created on the FTP sometimes or transferring may not start at all sometimes.

 

[AWS2P]

so all this are exactly same behavior i got last year and reason why i opened a bug ticket, try to update PROFTPD version

 

[dansoftware]

There is no any problem with the FTP server. 10 Gbytes file has been uploaded and downloaded successfully.

Spoiler: lftp

> put test.bin
10737418240 bytes transferred in 235 seconds (43.63 MiB/s)

> get test.bin
10737418240 bytes transferred in 291 seconds (35.17 MiB/s)

 

[AWS2P]

when i used filezilla to transfer files it was ok but not with 3cx embedded FTP

 

[Alphabetic]

Just out of curiosity - Why did you choose FreeBSD over Ubuntu Server?

 

[JohnS_3CX]

Hello @dansoftware

Can you share what action you performed to fix it?

 

[dansoftware]

when i used filezilla to transfer files it was ok but not with 3cx embedded FTP

Well, I am not going to change anything in my current environment. The problem that this thread is opened for has been solved for now. 3CX backups are not the only purpose of the FTP server. If there are interoperating issues between 3CX and ProFTPD it is easier for me to make backups locally and mirror them to a remote FTP. Thanks everybody for help anyway.

 

[dansoftware]

Just out of curiosity - Why did you choose FreeBSD over Ubuntu Server?

aws2p uses FreeNAS. It is based on FeeBSD. It was my favorite server OS in old times. But I prefer Debian Linux for now. Do not ask why