Call Recording Module crashes Asterisk

I have a server up on Vultr and I have purchased 300gb of block storage in addition to the main 80GB storage that came with the VM.

I have the call recordings set to go to /mnt/blockstorage/CallRecordings/ via Advanced Settings which works fine. Calls are being saved to that location.

However at the beginning of each month when the Call Recording Module does it’s archiving the system fills up the main storage device at /var/spool/asterisk/tmp/monitor.

Checking the log I get this:

2025-04-01 00:01:20 Archiving all recordings older than 1 months
2025-04-01 00:01:20 Moving recording files to /var/spool/asterisk/tmp/monitor …

Then nothing. The system crashes because the 80GB main drive fills up.

Has anyone else seen this? Is there a fix? Why is it trying to copy all the recordings to the main 80GB storage device?

Because it’s performing a backup of the call recordings. It will move them into a temp directory, just like all the other files (voicemail, configs, database dumps, etc) that will be backed up so the backup can do any compression, etc needed for the final backup file.

Remove /var/spool/asterisk/monitor from the backup job and that will solve the issue.

It’s not the system backup, backing up call recordings. The call recording module is trying to do it’s archiving and is moving to the TMP folder.

It’s the behavior of that commercial module, it will move to a tmp folder before it moves the tarball to the final destination.

Can this be addressed?

Can I create a symlink in the /var/spool/asterisk/tmp folder that points monitor folder to the blockstorage?

I have a support call w/ Sangoma now.

I created a symlink pointing /var/spool/asterisk/tmp/monitor to /mnt/blockstorage/monitor.

We’ll have to wait and see what happens at the beginning of the month.