If you are green to linux, it may take a bit of time to get your head around it, or you might take right to it, but is an option.
Copying the sd card to image you store until needed is the best way.
Then if you fat finger something, you can go back several saves before you may have done it without realizing it.
I only have 2 Pi 3’s and a bunch of zeros doing utility tasks but I can always go back and load a version of asl I made for specific purpose from those images.
The rest of my servers (aslx86) back-up by rsync to one of the other servers on a schedule in the we hours of the morning.
But you don’t need to get complex with it, just good to have some redundancy.
I found the solution to my issue. This is what I did. I shutdown my asl3 node. Then I hooked up my two micro readers to my second pi. Used a software app to make exact duplicate of micro card. Now I have tested the duplicated micro card and it works fine. Thanks for everyone’s input!!!
Dave
N8EPF
I like rsync, and use it for moving around weekly broadcast audio files.
Which directories are best to rsync? I could specifically target files like rpt.conf, iax.conf, & sip.conf; but what would you suggest would be directories to rsync offsite if for some reason someone would have to burn the install and reload?
That varies depending on what versions of software you are using and your personal habits.
I keep all scripts for asterisk/app_rpt in a sub under asterisk, and the same with many add-on customizations.
So, I backup the entire asterisk directory with subs.
And similar methods to other things on disk.
But rarely do I restore that way. Usually just a file. And you should explore to use the best options and keep ownership/privileges in tact. Saves some headache when you forget.
I see where you’re going. Most of my automated scripts pull from or push to an ASL server from a separate non-ASL server, so most of my ASL is stock v3.
But it wouldn’t take much stress to rsync the /etc/asterisk directory across the VPN to somewhere else. I think the “-a” flag will preserve permissions (among other things).
If your primary focus is to backup the ASL3 configuration then you may want to look at ASL’s “Backup and Restore Menu” available from the asl-menu (or asl-backup-menu) command. This provides a way to backup the key ASL3 / asterisk / app_rpt configuration files.
But, if you are looking to include other components (e.g. DVSwitch, Broadcastify) and you are looking for a way to avoid having to re-install / re-configure then you will need to look at other options.
I see that now. Is there a way to hit that from the command line and fill it with options (with the ultimate result to be able to cron control it), or is it only available via menu?
Not currently. But, most of the bits needed to put something together are present in the current asl-backup-menu script. I’ll ask that you create an issue @ GitHub : asl3-menu with what you’d like to see (e.g. create a local backup, create a local backup and push the archive to the ASL backup server, etc).
Alternatively, if you are comfortable with shell scripting then we’ll most certainly welcome a pull request.
I’ve walked through your asl-backup-menu script, and I’m certainly not to the level of whomever authored that utility. But I found the config file that determines what it backs up, and that is a nice explanation of what does get copied.
Let me see what I can do with that. Perhaps it could rise to the level where you could do something with it.