Re: Off -Topic - Netbackup Command Help -Solved

From: Jared Still <>
Date: Tue, 24 Jun 2008 15:15:02 -0700
Message-ID: <>

On Tue, Jun 24, 2008 at 12:36 PM, Frank Pettinato <> wrote:

> I figured it out.

Glad you got an answer.

This is one of several annoying traits of NetBackup.

The backup policy design is in general, not very robust.

Attempts to simplify operations often backfire.

eg. Trying to reduce the number of different policies in use may (will) result backups
appearing on a different schedule than the one that started the backup job.

The backup policy management would be greatly enhanced IMO if scripts could be attached
to a schedule rather than a policy.

Or when a policy covers multiple clients, it would really be great if a single client could be
individually disabled temporarily. As it is, a client must be removed from a policy if when
there are multiple backups, and you want to skip one client for a day.

Either that, or create (yet another) policy for that client.

Then there's problems with the MML. Some documented behaviors occasionally do not
work properly when using NetBackup. Configured channels comes to mind as one that
sometimes breaks with NBU.

Enough, I will get off my soapbox now. :)

BTW, you mention storing the scripts on the host.

If you are not aware, you can also use the NBU script templates if they fit your needs.
They are stored on the master server.

I quit using them as they are not as flexible as shell, or even windows CMD files, but
they are available and suitable if you don't need to do a lot of scripting.

Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

Received on Tue Jun 24 2008 - 17:15:02 CDT

Original text of this message