Solved Backup Failure

[[email protected]]

Version 15 - Windows Server 2012 R2 - 8GB memory

Have had no problems with backups before. For the last few days have had a backup failure with the following message.

3CX Phone System tried to backup but failed due to the following reason(s):

System.Exception: Error creating backup ---> System.AggregateException: One or more errors occurred. ---> Npgsql.NpgsqlException: The connection pool has been exhausted, either raise MaxPoolSize (currently 100) or Timeout (currently 600 seconds)

at Npgsql.ConnectorPool.<WaitForTaskAsync>d__24.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

The back up file is not very large, there is 500GB of disk space available. Have cleared temp files, and rebooted.

 

[nb]

Can you guys elaborate on the backup options you are enabling?
The people that got an exception - can you please note what you are backing up? Example Voicemails, Recordings, Prompts etc
This will help us understand what amounts of data are causing this issue.

It is not exactly related to the size of the backup. You can have a backup with 111MB however if they are call logs, you will have Billions of call records..

NPGSQL is a database connector library we use. It works differently depending on the database size, the specs of the machine, and therefore these 2 elements dictate the time a query runs, when it ends, when it times out and how many connections are spawned.

If you have enabled 5 options, try to find the option which causes the issue. Example if I get an exception with 5, then I dont know which is the problematic option (or options)

So disable un-check everything and use the basic - Just the database. LEt the schedule run and see if it exceptions. If it does not, enable another option (ONE BY ONE) until the exception is generated.

When you see the error, you know the option that has caused the problem .Reply back and we will guide you accordingly.

 

[craigreilly]

happened to me the last 2 backups.
v 15.5.1694


Turning off 'Call Log' option worked - but keeping all other options.
However, backup with only 'Call Log' also worked.
And... all options checked works.

I haven't restarted 3cx or the server.

 

[craigreilly]

Update: So manual backups worked yesterday... but the automated backup did not last night.

 

[jem1]

I've been noticing it on and off with various clients since 15.0 came out, it is random and I set the automated backups to backup everything. If I see this again we'll go ahead and try turning off options like the call logs for backup one at a time to find the culprit. The vast majority of our 3CX deploys have at least a third generation Core i3 or better and 4GB of RAM or better.

A restart of all services does also fix the issue right away I've found.