Networker automated recovery testing using the REST API - first script

I have worked a lot on my automated recovery script recently and finally got to a version that is a really good proof of concept and that I'm not scared to publish.  Plus, I have created a Gitub repo for documentation, issue management and, of course, Git features. The script is not perfect but it is even better than what I was planning when I wrote my first post on the topic:
  • A lot of checks have been put in place to make sure all variables are provided, and in the right format
  • There is an inline help with -h
  • The script chooses a backup randomly amongst all the available backups, not only the 30 last ones
  • It only requires bash, cURL and jq, on a machine that has access to the Networker REST API
    • Only tested on RHEL 6 for now
The script is not complete (I already created more than 10 issues to add features, improve current features or fix things), but it is a very good start for an organisation that wants to make recovery tests easier.
The Github repo will also allow other people to contribute. If you have any question, feel free to comment on this post.  If you can help for anything (documentation, code, testing, etc.) please let me know.

Comments

Post a Comment

Popular posts from this blog

General linux performance troubleshooting

Here's a list of commands that you should execute and then share the output to someone who can help you figure out what resource is the bottleneck in your system. Note, it requires the  sysstat  and  procps  packages (ubuntu and RHEL and its derivatives): uptime vmstat 1 10 iostat -xN 2 10 mpstat -P ALL 3 10 pidstat 1 10 free -mw (or free -m, if your OS doesn't support -w)  uptime is to see the load averages on the system. vmstat is mostly used to tell if the system is swapping or not. If you see significant numbers in the 'si' and 'so' columns, your system is most likely swapping (using the hard drive as RAM), which usually slows performance a lot. iostat is mostly used to determine if your disk subsystem is not able to cope with the load. If you see one or more lines that shows 100 or close almost constantly, it is probably the case.  If it is your swap volume, you probably saw numbers in the 'si' and 'so' columns in the  vmsta
Read more

Asterisk works under OpenVZ (no zaptel)

Hi, Just to let you know that I did a basic test with asterisk on an OpenVZ VE and it works. We only tested SIP connectivity (it would probably be complex to have Zaptel support and I don't really need it). We were able to connect to a VoIP provider using SIP ( unlimitel ) and music on hold works. The only thing I had to change to make it work is to comment out this line in /usr/sbin/safe_asterisk: #TTY=9 # TTY (if you want one) for Asterisk to run on (I guess there is no TTY9 (console # 9) on openVZ since it is a virtual machine and TTY9 is usually a physical console (monitor)). I'll soon put my asterisk server in a VE, I'll let you know how it goes. I also use Unlimitel and ATAs to link my PSTN line and cordless phones.
Read more