Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Backup and Recovery Community Blog
Showing posts tagged with Tip/How to
Showing posts in English
RahulG | 06 Jul 2009 | 1 comment

Mailboxes for the user's deleted from the active directory do not show up in the restore selections when the data is backed up to a tape.

Details: This behavior is by design.

Explanation : When Running the GRT backup to tape , the exchange data is backed up in the native format ,along with the ese.dll and other supporting files,Later the MAPI is initialize on the exchange server by RAWS (Remote agent for Windows Server) to gather granular restore information .MAPI gathers the exchange data using Active directory and then writes to the catalog. As MAPI cannot retrieve the information about the deleted user from the Active directory the catalog information for the user is not written to the catalog. this is not a problem with restore selection from backup to disk folder due to the Dynamic way we can read the exchange DB using the VFF technology

Workaround : Duplicate the backup set from tape...

LetThereBeZeros | 29 Jun 2009 | 1 comment

We do our anual DR tests, and now we are looking to step them up a bit.  Might be nice to see what others do or dont do in this arena. 

We have a DR box that is on a seperate network.  We can take that box build it as a master server and import our catalog from NBU 6.5.3.  We can then patch that into our library via fiber single path slowness, combined with the old leftover of a DR box we should have our critical restore done within 24 hours.  

In a true DR scenario where our primary DC was gone.  I would probably more than likely promote our media server to a master server then do the catalog import piece.  I have not done this since the new and improved 6.5 way of doing things with that small catalog file that i get emailed daily to my inbox.  Have others ?  Does it take long?  Realizing we all have different size catalogs, but in general have you had sucess.  Please add any thoughts...

Deepak W | 17 Jun 2009 | 4 comments

History of NetBackup

 * In 1987, a backup software solution was written by a small group of engineers at Control Data for Chrysler Corporation, and later adopted by other customers of Control Data.
* In 1990, Control Data formed the Automated Workstation Backup System (AWBUS) business unit. The first version of AWBUS supported two tape drives in a single robotic carousel with the SGI IRIX operating system.
* In 1993, Control Data renamed the product to BackupPlus 1.0. (This is why many NetBackup commands have a 'bp' prefix.) Support for media Volume Management and Server Migration/Hierarchical Storage Management was added.
* In the end of 1993, the product and Control Data’s Storage Management 12-person team were acquired by Openvision. This is why, on UNIX platforms, NetBackup installs into /usr/openv. During this time, Open Vision renamed Backup Plus to...

Abesama | 15 Jun 2009 | 2 comments

Recently I had all 3 of my PureDisk environments giving me storage problems due to internal/external causes.

First one was relatively simple, it's a 6.2.2 all-in-one node and it ran out of disk space for /Storage - 95% full.

The storage array was not a SAN but a dedicated one.
Challenging task with this was finding out how to order physical disks and finding a resource to put the disks in the array.

Array was a 12-slots one, with 6 slots occupied with 300GB disks.
Once the new 6 disks were put in, the engineer rebooted PureDisk server with a HP CD loaded, to connect to the array and create a single 1.5TB RAID5 virtual LUN, then the server's been rebooted again for PDOS to start.

When I started Yast2 interface, it automatically picked up the new LUN, and I simply added the new LUN in the LVM volume group - this task instantly grew the xfs filesystem as well, and suddenly I had 49% full /Storage filesystem, happy.


Deepak W | 10 Jun 2009 | 4 comments

Guys, go through the below menioned link. This site has many NBU scripts available for FREE.

Also scripts are available bat, ksh, sh, etc.

I have tried some of the scripts and turned out to be very handy.

GFK | 01 May 2009 | 0 comments

Active Directory (AD) is now the standard directory service in the Windows O/S. Exchange, SharePoint and SQL, all of whom are dependent on its on-going good health, and yet, we protect our databases, email systems, applications - all of which are reliant on AD in the Windows O/S, but don’t do anything specific to protect AD? Hmmm, not clever nor grown-up.

Now, backing up Active Directory is pretty simple. However, everyone appreciates that an efficient backup and quick recovery of AD to maintain business productivity is essential and any administrator who has ever had to attempt to recover Active Directory (AD) data is well versed on how frustrating and time consuming just the basic recovery process can be.

Should data in Active Directory corrupt - which can happen - it can have a ripple effect across the Windows environment including down to the application level of Microsoft Exchange, SQL, and SharePoint. Because AD is a replicated database any human error,...

DavidParker | 30 Apr 2009 | 5 comments

Tired of manually entering every client in my environment to the LiveUpdate policies in NetBackup, I decided to see if there was an easier way to add more than 1 client at a time.

On a hunch, and knowing that the client listing for normal policies is a text file, I poked around to see if the same was true for LiveUpdate policies.
Sure enough, /usr/openv/netbackup/db/class_internal/ had a listing for all my LiveUpdate policies!

So, I just copied and pasted my client listing from existing, "normal" policies and added them into the LiveUpdate policy client lists.
And presto!  100+ clients added in 1 shot!

GFK | 03 Apr 2009 | 4 comments

One of the really cool functions of BE is the Granular Recovery Technology (GRT). By the way, anytime you need more information on any aspect of BE please see the Backup Exec for Windows Servers Administrator’s Guide. In fact, don’t take my word for it, download from here: a few tips to help you get the best out of BE’s GRT:

  1. Review the requirements for staging locations in the Administrator’s Guide.
  2. You must use a staging location for GRT-enabled jobs in the following scenarios:
    • You back up to or restore from a volume with file size limitations.
    • You restore granular items from tape.
    • You run an off-host backup job.
  3. You are better off creating a separate backup-to-disk folder specifically for all GRT enabled backup jobs - this really simplifies media management....
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.

GFK | 01 Apr 2009 | 0 comments

If you are not on Backup Exec 12.5 you really should think about upgrading, if not for the new comprehensive recovery of virtual and physical systems, or enhanced granular data recovery, or the fact that Backup Exec is now integrated with the Symantec ThreatConTM system to automatically manage continuous data protection functionality in an increased threat cycle, but for the fact that the new version of Backup Exec enhances the management capabilities around managing disk and tape based backup - across the board.

The great thing about upgrading is its simplicity. Now you can run the Backup Exec Environment Check on the computer on which you want to install Backup Exec, before you actually install Backup Exec for real. This makes sure that the installation process can complete. If there are any configuration issues the environment check kicks out warnings that tell you if there are configuration issues that can be fixed or that will prevent the BE installation.

I would...