3CX v15.5 FTP Backup Won't Work If Call History Is Selected

[[email protected]]

We had this problem originally about 2 months ago on v14. If the Call History is selected on a FTP backup it will log in to the FTP server and do nothing. After about 5 minutes it will disconnect after uploading nothing. The solution I found was to clear all call records from 12/31/16 and prior out of the system and it fixed my issue.

I upgraded to v15.5 last weekend and now I'm experiencing the same issue. If the Call History Logs are checked in the backup then it will log into the FTP server and do nothing before disconnecting after around 5 minutes. What can I do to get the call history logs to backup with the nightly backup?

The backup will complete if I send it to the C: drive instead of FTP.

For the time being I've removed Call History Logs from the nightly FTP backup so it will run correctly.

 

[cobaltit]

Is 3CX disconnecting or is your FTP server disconnecting due to inactivity?

 

[[email protected]]

The server is closing the connection due to inactivity. When 3cx logs in it generates a zip file that's 0KB and it never increases in size. If I backup without Call History I can see it the file size grow as it uploads. For whatever reason 3cx is hanging on something when generating the file with call history records.

 

[SweetAction]

I had a similar issue.

Backups take a while to build and the FTP connection is opened as soon as the backup starts. It times out, closes, and then the backup can't be stored.

In my case FTP is internal and only used by 3CX. So set to 6 hours allows this to run without issue.
Really 3CX should only open the connection once the backup is ready to start uploading. Or at least issue a re-login command. But since it doesn't, either make your backups smaller (mine are about 1GB) or increase idle time on the FTP server.

 

[cobaltit]

Yeah this is the direction I was going. I figured the FTP server was timing out the connection. So if you can adjust the timeout on your FTP server that should do the trick until 3CX lets the backup complete first and then starts the FTP session.

 

[[email protected]]

I'm using IIS on Server 2016 and I've tried resetting my default ftp timeout to 2 hours. I've also set the timeout for the FTP instance to 2 hours as well and the backup disconnects after about 5 minutes and errors out.

Last night I tried resetting IIS and restarted the FTP from the IIS management console and I still get the same response. The backup times out after about 5 minutes. Is there something I'm missing for the timeout settings? A google search makes it look like I've changed all of the proper timeout settings.

When I make the settings I go to Administrative Tools -> IIS Manager. I can adjust the timeout settings for all ftp sites at Server Name -> Sites -> Click on sites so it's highlighted -> Right hand side click "Set FTP Site Defaults". I can also adjust the settings for the FTP instance under Server Name -> Sites -> FTP Site Name -> Right Click on FTP Site Name -> Manage FTP Site -> Advanced Settings.

 

[cobaltit]

Not that familiar with IIS but just to test you could try Filezilla.

 

[SweetAction]

We use FileZilla for FTP instead of IIS.

 

[[email protected]]

Let me put some ideas together before I do anymore with this. I normally wouldn't have an issue trying FileZilla but we have a few ftp sites setup on this server for systems to backup and to transfer data to an as/400. I would prefer to troubleshoot IIS more before I start the conversation about changing this servers setup.

 

[Lee Cramman]

Is it worth trying a test backup including call logs to Google Drive? If that works then it pretty much rules out everything except FTP as the root problem (although it sounds like you're already reasonably sure of this).

Also, it might be coincidence but 15.5 enabled FTP support for EPSV and your problems started at the same time as you upgraded...

 

[[email protected]]

I've done some more testing and I want to relay what my solution will be.

First off is that if you're working in IIS there is a config file to verify that the service has the right configs. It's located in %SystemDrive%\Windows\System32\inetsrv\config\applicationHost.config. I was able to verify in there that the timeout was correctly set for the FTP server. No matter what I set it to the connection timed out after 6 minutes.

The FTP server we use is also a file server. I was able to share the directory that contains the 3cx backups as it's own share. In the 3cx backup I set it to backup to Local Disk and configured the backup location as a UNC path (\\fileservername\sharename). Now when I run the backup it starts very quickly and finishes without issue.

Due to the way that the system is acting and the speed that the file system transfer goes it looks like the FTP backup is hanging for unknown reasons because the file system starts almost immediately while the FTP backup just sits with a .zip file at 0KB until the connection cuts out.

 

[[email protected]]

I'm not sure why my last post didn't submit so I'm retyping it.

In IIS the config file is located in %SystemRoot%\System32\inetsrv\config. I was able to verify in there that the timeout was correct but it still disconnected like clock work 6 minutes after starting. I can't find any way to get it to wait the whole timeout.

The server this is on is also a file server. I shared the 3cxbackup drive using SMB. I then went into 3cx and changed the backup to local disk and used the UNC path of the file share (\\fileserver\sharename). When I run the backup now it runs almost instantly and transfers without issue.

Due to the way that the SMB share starts instantly I think there's a larger problem with the ftp backup that's causing it to hang and create a 0KB file before deleting it and disconnecting after 6 minutes.

 

[Paul Fouche]

Hey,
I had the same problem.
On Filezilla I just extended the timeout and then the backup completed successfully