Forum Discussion

X2's avatar
X2
Moderator
4 years ago

Start/stop NetBackup with Ansible

Calling on Ansible experts: I created an Ansible playbook to "standardize" our Linux client NetBackup configuration after initial install. The configuration steps work fine except that I'm having d...
Linux
  • X2's avatar
    X2
    4 years ago

    vtas_chas apologies for the late reply. No infoscale on the client. These are standard VMs on vSphere without Infoscale. I haven't tried this on our Solaris servers but they are provisioned so rarely!

    As a workaround, I ended up using sysvinit module rather than service or systemd.

        - name: Stop NetBackup (initd)
      sysvinit:
        name: netbackup
        state: stopped

     

vtas_chas's avatar
vtas_chas
Level 6
4 years ago

Not 100% sure, but the error makes me think the init script isn't enabled for systemd. Have you enabled the NetBackup service being managed by systemd?  

The other thing could be the way you're dealing with the service.  IIRC, you can do this:

- name:  Stop NetBackup

systemd:

name: netbackup

state: stopped

As long as the service has been enabled (systemctl enable netbackup) and the symlinks are there, that may fix your problem.

 

  • X2's avatar
    X2
    Moderator
    4 years ago

    vtas_chas Thanks for the reply.

    I will try that out on my test system.

    NB: Starting and stopping NetBackup using command "service netbackup start" via ssh works fine. However, when the system is rebooted, NetBackup does not start. I had a case opened earlier and InfoScale engineering team gave me a fix. But when Infoscale was upgraded to a newer version, the fix was not in it.

    • X2's avatar
      X2
      Moderator
      4 years ago

      vtas_chas tried your suggestion yesterday and the behaviour was the same. Ansible came back with the same response. NetBackup did not go down. Maybe I will try with a pause of a few seconds after the task and see if it changes anything.

       

      • vtas_chas's avatar
        vtas_chas
        Level 6
        4 years ago

        The pause is a good idea.  Depending on what's going on in the system, services can take some time.

        I'm curious about the InfoScale team comment -- is this on a cluster or you're running Infoscale on the client?