Video Screencast Help
Backup and Recovery Community Blog
Showing posts tagged with NetBackup
Showing posts in English
J.H Is gone | 14 Apr 2009 | 0 comments
When I first got here:
 
At 3 remote locations they had Backup Exec and local tape drives.We had to rely on “users” to remember to change tapes and handle them correctly.
At corporate office, we had standalone tape drives on the servers.  And would use OS backup software to backup to tape.Every morning I would come in and hit the eject button on all the tapes, then go back and take them out. Some of them I had to put in the second tape so the backup could finish. Then go and put tonight’s scratch tapes in them. This could take up to 2 hours before I was finished. And then had to check emails to make sure they all actually worked. Once a week I would spend an extra hour doing cleaning tapes in all the drives. I spent a LOT of time doing tapes.
 
These were the days of ‘Manual Labor’.

Then we purchased NetBackup 3.5. I took the self paced course on...

Taqadus Rehman | 10 Apr 2009 | 2 comments

In our day to day backup administration life we have to face lots or problems, some create panic and some do not; and we often have to log a case with symantec support, initally we log the case and describe the issue we are facing, in response to that support engineer request for logs. From call logging to inital response we some times have to wait  2 hours which irritate more at time you are in panic situation. Let me explain the support material required by symantec support to resolve any issue.

Support team often require various materials, there are 3 generic types:

  1. NetBackup support material 
  2. NetBackup diagnostic material
  3. Individual commands and/or procedures 

Netbackup Support Material

The NetBackup support materials used to be collected by the nbsupport tool, nowadays that is replaced by the "nbsu" tool, this is available to download at following link. you need to...

Taqadus Rehman | 04 Apr 2009 | 0 comments

We recently experienced some images that had failed to be expired on their own due to the known bug in 6.5 that won’t expire old 5.1 images from disk and it reminded me how very important it is to do your homework when taking drastic steps such as this. As we all know, once you use bpexpdate to get rid of an image, the only way to get it back is to import the tape(s). Before expiring those images, even if it is just one, use bpimmedia and bpimagelist to document what the images are and where they reside.

I find with this, Do your home work before playing with catalog images.

LeslieMiller | 02 Apr 2009 | 0 comments

Have you migrated from another product to one of Symantec’s Backup products? We want to hear about it—and we’re sure others in the community would like to hear your story as well. So, we’re holding a contest—one where everyone wins. Just for entering you’ll receive 1,000 Reward points. (That’s twice as much as a normal submission.)   And if you have the best story (as determined by a panel of Symantec experts) you will receive the grand prize of 25,000 Connect points. (You could redeem those points for a Hawaiian cruise, or more than $1500 in Amazon gift cards.) Symantec will also award runners up with additional bonus points.

Want to find out more? Check it out here.

TrevorD | 27 Mar 2009 | 3 comments

 

  1. Align business and IT requirements
  2. Prioritize requirements
  3. Determine true costs for delivery options
  4. Predict the impact of data loss
  5. Establish service levels
  6. Modify infrastructure to meet agreed service levels
  7. Test the recovery process regularly
  8. Analyze logs
  9. Perform incident management
  10. Perform root cause analysis
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...

Vilobh Meshram | 17 Mar 2009 | 2 comments

Tha policy DB will not get upgraded with the Netbackup patch update.Say you are using Netbackup 6.5 and if you upgrade to 6.5.3 the policy entries will not get updated automatically.

 

e.g The storage unit selection was "Any" in 6.5 and if you have some problem using the storage unit so if you plan to upgrade to 6.5.3 the attribute will be "Any" only.But inorder for NBU to understand this the parameter should be passed as "*Any*".

 

Thanks,

Vilobh