3CX v20 backup to SMB Access denied but TMP file is saved in backup location

[wesThreecx]

Good morning,

Our 3CX v20 update 5 backup is failing. It is configured to back up to a Windows SMB share on the same VLAN.

In the backup folder on the SMB share there is a TMP file that is created at the time the backup runs.

Your 3CX backup failed due to the following reason(s): 3cxconfigs\3CXScheduledBackup.zip.tmp : STATUS_ACCESS_DENIED

The call recordings are being archived successfully to this backup location.

Thank you in advance for any assistance you may give.

 

[SweetAction]

Make sure that the account used by 3CX to write data in that folder has read, modify, and delete permissions

 

[wesThreecx]

Make sure that the account used by 3CX to write data in that folder has read, modify, and delete permissions

Thank you - we used an Administrator account, share and NTFS permissions are full control.

 

[CentrexJ]

Thank you - we used an Administrator account, share and NTFS permissions are full control.

Best to double check permissions.

 

[rkochman]

Same issue. Manual backups work, yet scheduled backups fail. Full file is created with .zip.tmp, yet stays that way with an event error 50022 STATUS_ACCESS_DENIED.
Using UNAS Pro and given OWNER status to user.

Using Version 20.0 Update 7 (Build 1080 Release)

 

[KyriacosS_3CX]

Please review the permissions of the files already on the remote server.

 

[rkochman]

Please review the permissions of the files already on the remote server.

The File & folder has the user 3CX as "owner"

 

[AWS2P]

we used an Administrator account, share and NTFS permissions are full control.

from whom pc are you using admin account? on the SMB part or on 3cx pbx?
is your PBX running on a windows machine or debian?
Try setting SMB shared space rights for " everyone " with full access and try a backup, if it's succeding then you know your SMB rights are wrongly set up

 

[KyriacosS_3CX]

If the backup target is FTP/SFTP etc to a linux type file system, your target FOLDER is probably missing Execute permission for the FTP account being used. Read-Write permissions are not enough.