How to restart netbackup services on a client machine

In this article, we are going to discuss how to restart netbackup services on a client machine in case if any issue encountered during backup.

Netbackup works on the client-server architecture. You need to have Netbackup Master Server and clients who need to get backed up.

Netbackup client is the requirement if you want any of your physical servers needs to get backed up. Netbackup client must be installed on the client.

There are some other options in the case of Virtual Machines which is not in the scope of this article.

We are intended to discuss how to restart netbackup services on a client machine. If you have made any netbackup related configuration change on the client it is good if you restart the netbackup client.

Netbackup client can be restarted without any impact on the client-server or with no downtime.

You just need to make sure that no backup is currently running on the client otherwise running backup gets killed and you will have a backup termination alert by your incident tool as a gift.

 If you are interested to know how to check the backup status in netbackup you can follow the link.

How to Restart Netbackup Client

Let us come to our topic of how to restart netbackup services on a client machine. Veritas has come up with solutions to this problem and they have to.

As this is the licensed tool for enterprise backup solutions so they have to provide the option for restarting netbackup agents on the client machine if needed.

We will discuss the tools or simply you can say small utility scripts they have provided to stopping and starting netbackup client.

As I said these are really handy as part of troubleshooting you can easily achieve that. In case if you do not find it for any reason ask your backup team member to provide one.

Before reaching them you can use the find command to find the location of the script and if you do not find you can reach it.

Especially for Linux use the locate command to have the path of the script. Default file location I will mention below.

Will display command output in form of sample output which may clear doubt about the location of the file.

How to Stop all Netbackup Process & Daemons

Let this script keep running till you get your # prompt back it will stop all the netbackup related services.

# /usr/openv/netbackup/bin/bp.kill_all
Looking for NetBackup processes that need to be terminated.
Looking for more NetBackup processes that need to be terminated.
Stopping nbdisco...
Stopping bpcd...
Stopping vnetd...
Still running...
root 4005 1 0 Jul18 ? 00:01:01 /usr/openv/netbackup/bin/vnetd
root 4006 1 0 Jul18 ? 00:00:38 /usr/openv/netbackup/bin/vnetd
root 4062 1 0 Jul18 ? 00:15:44 /usr/openv/netbackup/bin/vnetd
root 4083 1 0 Jul18 ? 00:02:03 /usr/openv/netbackup/bin/bpcd -s
root 4163 1 0 Jul18 ? 00:03:14 /usr/openv/netbackup/bin/nbdisco
Still running...
root 4005 1  0 Jul18 ? 00:01:01 /usr/openv/netbackup/bin/vnetd
root 4006 1  0 Jul18 ? 00:00:38 /usr/openv/netbackup/bin/vnetd
root 4163 1  0 Jul18 ? 00:03:14 /usr/openv/netbackup/bin/nbdisco
Still running...
root 4163 1  0 Jul18 ? 00:03:14 /usr/openv/netbackup/bin/nbdisco
Still running...
root 4163 1  0 Jul18 ? 00:03:14 /usr/openv/netbackup/bin/nbdisco
#

How to Start all Netbackup Daemons

Again the same requirement below script will start all the netbackup related services on the client. Run the script and wait for the prompt to come back.

# /usr/openv/netbackup/bin/bp.start_all
Starting vnetd...
Starting bpcd...
Starting nbftclnt...
Starting nbdisco...
Starting bmrbd...
#

You can see above it will start all the netbackup services including vnetd bpcd nbftclnt nbdisco bmrbd needs to run for communicating properly with the netbackup master server to have a backup of client run successfully.

That,s it about how to restart netbackup services on a client machine. I hope you will find it useful in stopping and starting or you can say restarting netbackup services on the client machine.