Scheduled backups fail

[TigerTech]

Running Debian on-prem 18.0 U8 build 939. We had long been doing daily scheduled backups to our Windows file server, but we recently migrated to a newer server. The scheduled backups immediately started failing ("STATUS_ACCESS_DENIED"), although manual backups work. I have confirmed that

• The backup user configured in 3CX scheduling has Full Control of the target folder, subfolders, and files.
• When 3CX creates a scheduled backup the user has Full Control of the file.
• I can log into a Windows workstation and connect to the file server with the 3CX backup user. From there I'm able to create and rename files in the target folder, including the tmp file left over by the failed 3CX scheduled backup.

This seems to indicate that the user has all of the permission it needs, so I don't understand why scheduled backups are failing. Any ideas?

 

[Charles_3CX]

Regarding your question, manual backups work differently from scheduled backups. With scheduled backups, a backup is first written to a temp location on the local systems drive and named 3cxScheduledBackup.tmp. Then, once completed, this backup is written to the remote backup location. Once this is complete, the file is renamed to 3cxscheduledbackup.zip.

So here, I suggest checking the ACLs you have set on the backup location for the backup user and ensuring that full permissions and share permissions are applied to the backup folder.

 

[TigerTech]

Thank you for your reply. However, I already listed my extensive and I believe, comprehensive, tests confirming the necessary file permissions, including the very telling fact that the backup user works perfectly from a Windows workstation. If that does not prove that all permissions are set correctly, would you please be specific about what additional things I could possibly check, and explain how even though the backup user has the rights necessary to manipulate the files from Windows, 3CX scheduled backups cannot manipulate the files with the same user?

 

[Charles_3CX]

I believe I explained the reasons why the scheduled backups are different from manual backups.

If you want to do an extensive test to get comprehensive results requires turning on verbose logging and running a packet capture while running a scheduled backup, then YOU can analyse them to see exactly where the issue is.

Kindly don’t misunderstand the above, I am not asking for you to provide this logging here for my review, it is for your knowledge only to know how to do it and what to do next, as we don’t provide direct support via the forum, but rather only supply advise based on what you have said.

For technical support you may open a support ticket.

 

[TigerTech]

In case anyone should find this post when dealing with a similar problem... The fix was that we needed to give "Full Control" permission on the file share.

 

[Charles_3CX]

Glad that you found the issue. As stated, it was a permissions issue.