Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Backup and Recovery Community Blog
Showing posts tagged with Basics
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.

Sheena K. | 31 Mar 2009 | 0 comments

For the past 5 years we've been using on of the Backup Exec for Windows products to complete our disaster recovery data backups. We've always done an online, offsite and tape backup of the data files changed that day then a complete (master) backup of the data servers. When I first started doing this 4 years ago our daily modified tape was one AIT-3 tape in that time we've grown to 3- AIT-5 tapes.

As part of our continued security for SAS70 certification we two step the master backups. First creating an online backup then compressing and encypting those .bkf files to tape for archiving. It wasn't till recently we discovered that with Backup Exec 12.5 there is a character limit that was not imposed on previous versions. This is only an issue with the 2 step process. If the "master" job is run directly to tape then it doesn't seem to be an issue restoring files. It is only after restoring the online or .bkf files that the data becomes unrecoverable. By not doing the...

Swathi Turlapaty | 26 Mar 2009 | 4 comments

Time is flying.. it’s already been three weeks since we launched the new community. Things seem to look damn pretty in here, with all of you settle down in a routine and busy sharing information with your peers. Great job everyone…keep the ball rolling.

Though there has been lot  of activity on the new community, it seems  like the users are not yet accustomed to posting the right content on different "Utilities" -- Forums, Blogs, Articles, Downloads, and Events.

I have noticed in many instances that the content is not being posted in the right place.  Content that is supposed to go into a forum is posted as a Blog or Article  and vice versa. In such cases, I take the liberty to un-publish the original post and re-publish the entire post, including the comments in the right location, perhaps on behalf of the original author(s).

So, why is it important to post content in the right place? Ask yourself if...

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/

0 17 * * 1-5 /usr/local/scripts/


# cat /usr/local/scripts/

#! /bin/sh

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


/usr/bin/echo $i


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