I have a large number of version 14 & 15 systems installed in a cloud system. They all work well. I have setup a S3 bucket to save Backup files. I use an Rclone script along with cron to move the backup file. The script also emails me when there isn’t a file to move. I know about Filestore and the s3 connection there. It just didn’t work fo rme. Anyway the question of the day is: What would occasionally keep the backup (Freepbx module) from running? I will have a couple of systems a month that do not produce a backup file. If I go in and manually start the backup it works fine. The Rclone script when run manually moves the file as it should. Could there be a process that would stop the backup from running ??
No one has experienced this before?? I thought I had an idea of what was happening. I thought that the systems were updating and a apply config was waiting and holding things up. I did a test this morning and the backup worked while there was a apply config waiting. So that theory is blown. I have looked in the log files and can find nothing indicating that the backup failed. is there another way to start the backup process? If I can’t depend on the schedule I setup maybe I can create backups another way??
Well, for the people that might have this issue in the future here is what I found. The cron job for the backup was missing. using “crontab -l -u asterisk” I could see if the job was there or not. If it was it looked like this “ 0 18 23 * 1 ID=freepbx_backup_1 /var/lib/asterisk/bin/backup.php --id=1 >/dev/null 2>&1”. Going to the Backup/Restore module in the GUI and saving it restored the cronjob. I would never have known the backup wasn’t running if I hadn’t been moving the file to my own S3 bucket and sending an email if it failed. Hope this helps anyone in a similar situation.
@edlentz Email alerts failed as well, if those were set up?
Whats the issue with S3 and filestore? There were a few changes recently in the filestore module buts its been pretty much rock solid in both 16 and 17 for me and is generally verbose within the backup log when it does fail and the tiered storage option helps with costs as well
I havent heard of Rclone but do use the aws-cli and its awesome for taking care of things like call recordings and getting them into S3, you should check it out
ps - its time to upgrade those 13 and 14 systems , your best bet is to take a backup and restore it to a 17 test system… you may need to tweak it a few times but then once the test system is happy take another backup from test system on version 17 and restore it to the production 17 system thats going to replace the original; thats the recipe thats been working for me anyway
Nothing wrong with S3 and Filestore. I had such a hodgepod of systems that I wanted a single method to move the files. Look at Rclone, it can be on virtually any Linux or windows machine and it is secure and fast, not to mention versatile and FREE. I get 1TB of space at Vutr for cheap. I setup all the systems to retain their backup files locally and then I come along using Rclone to move and remove them locally (All verified of course). in this case I found that the cronjob for firing the backup itself was missing. It is like it never was there at all. My script that fires the rclone commands also sends me a failure email, that is how I was alerted to the problem. I am in process of “saving” my original backup from the gui. I have over 400 systems to do. I am sure we will get the older systems upgraded, just takes time. Thanks Chris for the reply
Ed
1 Like
TangoPBX is a trademark of TangoPBX LLC, FreePBX is a trademark of Sangoma US Inc, Asterisk is a trademark of Digium Inc.