Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.
Backup and Recovery Community Blog
Showing posts tagged with 7.1.x and Earlier
Showing posts in English
FrSchind | 27 Mar 2009 | 4 comments

Hi,

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...

J.H Is gone | 23 Mar 2009 | 5 comments

I know I am not the best typist or speller...
But does anybody know who to report typographical errors in documentation or the software?

Point in question -
NOM/Alerts/Select Condition
for High Frozen Media -
Description
"Action is taken if, Number of frozed medias exceeds predefined threshold value."

Frozed is not a word - froze or frozen -  not frozed

Stumpr2 | 20 Mar 2009 | 0 comments

Let's face it. Sometimes backups fail. Your job, if you chose to accept it, is to troubleshoot and retry the backup. When you have hundreds of policies it is hard to determine which backups are forbidden to run during business hours. It's only a matter of time before you errantly submit a manual backup of a client that is NOT supposed to be backed up during business hours.

The trick is that you need to keep Netbackup running as normal, but you do not want specific policies to run. This is what I do to keep certain backup jobs from being submitted during business hours.

 

# crontab -l

0 6 * * 1-5 /usr/local/scripts/policy-deactivate.sh

0 17 * * 1-5 /usr/local/scripts/policy-activate.sh

 

# cat /usr/local/scripts/policy-deactivate.sh

#! /bin/sh

for i in `/usr/bin/cat /usr/local/scripts/policylist`

do

/usr/bin/echo $i

/usr/...

Stumpr2 | 19 Mar 2009 | 28 comments

From "Man of La Mancha" lyrics by Joe Darion

To dream the impossible dream,
To fight the unbeatable foe,
To bear with unbearable sorrow,
To run where the brave dare not go.

Have you ever had a dream to improve the Netbackup product? What are some suggestions for what you would like to see in NetBackup 7.x? Has there been something you wanted to see done with the software for many years but were afraid to sound it out because you know in your heart that you are simply dreaming an impossible dream?

Here are a some suggestions to get this blog started:

1) a link on the policy "attributes" page to bring up a text window to put additional information concerning the policy.

 

2) the ability to temporarily disable a single client in the client list

 

3) a list of policy_type numbers when you are using bplist so you don't have to bring up the bplist man page...

Douglas_A | 06 Mar 2009 | 1 comment

Today i had to place a call with symantec for Netbackup 6.5.3.1 i guess the special character bug was not fixed when the new version came out which was a real bummer.

The support guy i spoke with however was pretty eager to get me a new binary and as of this morning i recieved it.. now this is maybe normal for some of the larger companies, however our smaller company this is FANTASTIC.. great job symantec keep up the good work.

 

 

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 (...

TimBurlowski | 02 Dec 2008 | 0 comments

A few days ago I interviewed Saradhi Sreegiriraju, a Product Manager from Data Domain about their OpenStorage capable devices. A few days later, Matt Kixmoeller, the VP of Product Management for NetBackup sent me this photo from his BlackBerry. The photo was taken at Vision Japan. Looks like de-dupe with optimized replication is big everywhere.

 

...