Video Screencast Help
Backup and Recovery Community Blog
Showing posts tagged with Tip/How to
Showing posts in English
FrSchind | 27 Mar 2009 | 4 comments


sometimes it's necessary to deactivate a client for some time. NetBackup doesn't make this easy for us admins, since there is no such option in the GUI. The most common way is to delete the client from the policies and put it back in later.

The definition of clients per policy can be found in the file system of your NetBackup master in /usr/openv/netbackup/db/class/ - so this is a possibility to fiddle around when deactivating a client. Editing the files directly with an editor is not a good idea - as you will notice there are checksums at the end of each file. The client name can be changed with the command "bpplclients <policy> -rename <oldname> <newname>". When you change the name of the client from "<client>" to "#<client" the client is commented out in the configuration file and no backups will be scheduled. The bad thing is, you will not see this client in the GUI. 

To make all this a...

Nathan Kippen | 03 Mar 2009 | 0 comments

So here we go.  My first post on Symantec Connect.  I haven't decided exactly what I want to write about, but for now I'll just write about daily experiences at work involving NetBackup. 

We installed the 6.0 MP7 S01 hotfix on our only remaining enviornment running NBU 6.0.  The only problem I ran into was that there was a user still logged in to the NBU java console and it was locking a few files on the master server.  These files could not be updated when applying the patch.  Therefore I suggest you completely shutdown netbackup and run a bp.kill_all.  Also make sure that nobody is running the java admin console, because this will continue to spawn bpjava processes.

We're gearing up to start using NetBackup puredisk with netbackup.  Our goal is to do replication with our DR site so we don't have to send tapes anymore.  Also lately I've been trying to work on a problem that I've had with NDMP local backups (...