Comments on: Vmware ESX Server Backup with Netbackup Howto

By: savas

savas — Wed, 14 Oct 2009 16:31:16 +0000

Hi,
On windows:
to stop all netbackup services from command line: NetBackup_Installation_PATH\bin\bpdown.exe
to start all netbackup services from command line: NetBackup_Installation_PATH\bin\bpup.exe
Typically:
C:\Program Files\Veritas\NetBackup\bin\bpdown.exe
C:\Program Files\Veritas\NetBackup\bin\bpup.exe

On Un*x:
to stop all netbackup services from command line: NetBackup_Installation_PATH/bin/bpdown
or
/etc/init.d/netbackup stop
to start all netbackup services from command line: NetBackup_Installation_PATH/bin/bpup
or
/etc/init.d/netbackup start
Typically:
/usr/openv/netbackup/bin/bpdown
/usr/openv/netbackup/bin/bpup

By: AA

AA — Wed, 14 Oct 2009 04:00:18 +0000

How to reboot NBU master server on commandLine

By: Anonymous

Anonymous — Mon, 28 Sep 2009 13:09:36 +0000

If your master server is not Windows based, then you need to install an “enterprise client for windows” license.

By: Anonymous

Anonymous — Fri, 26 Dec 2008 09:04:56 +0000

If you suddenly start having an error on your Netbackup Administration console while trying to backup a unix type virtual machine:
snapshot error encountered(156)
And on your Vmware Console you see an error like this:
Creating a quiesced snapshot failed because the (user-supplied) custom pre-freeze script in the virtual machine exited with a non-zero return code

According to vmware this error is about vmware tools on the unix vm not returning a “0″ return code while it should.

Fix:
Just add the following line at the end of VCB_INSTALL_PATH\config\config.js file
NO_QUIESCE=”";

Now you can go to your Netbackup Administration Console and restart your backup.

By: Anonymous

Anonymous — Mon, 22 Dec 2008 10:49:29 +0000

And I want to see the Vmware Restore howto as well :P

By: Anonymous

Anonymous — Mon, 22 Dec 2008 10:46:30 +0000

Nice howto, wanted to add something in case someone else might have the same problems.

If you are having an error code 156, check that the vm names didnt change since you configured vm backup policies… and also double check that the names on the clients list can be resolved from the dns or hosts file…

Keep up the good work :)