Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Backup and Recovery Community Blog
Showing posts tagged with 7.5
Showing posts in English
inn_kam | 17 Apr 2013 | 0 comments

Hi Guys

Many people and myself many times came through this error

i have also locked the call to symantec and ask on forum , they told me the same.

when i ran the command vssadmin list writers

it gives Microsoft Exchange Writer: Retryable Error

, i have checked many symantec tech notes on it .

and in short i summarised it that we have to reboot the exchange server 

Find the TECH NOTE here


This issue is normally caused because the “Microsoft Exchange Writer” is not working properly. You can verify its status with the “vssadmin list writers” command: 

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id...

inn_kam | 03 Apr 2013 | 0 comments


One of our customer wants to give UNC Path in storage Unit in Netbackup,in absolute path name as shown in below screen shot.

So after giving the UNC path for eg \\<server name>\<Folder name>  , when we ran the policy we got error as follows

Error reading Volume information.STS API failed. 
Status 2060013
no more entries.

So we contact Symantec Engineer , He resolved this case by going on to Media Server and  give admin credentials to two services, 
  • NetBackup Client Service
  • NetBackup Remote Manager and Monitor Service

He also share a TECH Note with us which i will also share in this forum , which ver helpful for Symantec Netbackup Users

Alex Sakaguchi | 02 Apr 2013 | 0 comments

Are you interested in seeing first hand the new advancements around virtualization backup and recovery coming in NetBackup 7.6?  Well, we've decided to host a Google Hangout as a sneakpeak into the latest and greatest, and broadcast it live from Vision 2013 in Las Vegas on 4/17.  This Hangout is open to the public and we're encouraging everyone to come check it out!

We'll be showing you things like how to backup 300 VMs in 3 minutes, backing up 3TB of data in 15 minutes, and much more.

Broadcasting live from the Expo Hall floor of the MGM Grand on April 17th from 12:00pm to 1:15pm Pacific time.  

RSVP on our Google + page: Protecting 300 VMs in 3 min

We'll be taking questions from panel members as well as those submitted through Google + and...

inn_kam | 28 Mar 2013 | 2 comments

We have one issue of restoring email, and we took support from Symantec Expert Engineer , He sort out and resolved the problem in great manner. So i want to share it with All Netbackup Users who are having problem in restoring the email from Exchange.

GRT individual email recovery failed
Status code 2810

Netbackup Master Server on WIndows
Netbackup Media Server whichis Exchnage 2010 Mail Server as well.
Netbackup Mail server another
Netbackup HUB CAS server

2/14/2013 16:11:56 - Info bpbrm(pid=1448) (CAS SERVER Name) is the host to restore to
2/14/2013 16:11:56 - Info bpbrm(pid=1448) reading file list from client
2/14/2013 16:11:57 - connecting
2/14/2013 16:11:57 - Info bpbrm(pid=1448) start nbfsd on client
2/14/2013 16:11:58 - Info bpbrm(pid=1448) start nbgre on...

Gavrilov | 27 Mar 2013 | 2 comments

My last few cases were cluster related. It's funny, but some customers (and even engineers)  always forget how to manage NBU when it's under cluster control. They also believe that they can easily bring NBU up by same old start\stop scripts  during the cluster's problem. It wouldn't work out. As soon as we place NBU under Cluster  control it means that it's being controlled by cluster Agent. But Agent's functions aren't limited by start\stop\monitor routines.  Let's look at possible scenario. We've upgraded both nodes and want to perform a switchover to the another node for the check. It fails. What would we do? Everyone knows that first of all we need to understand why we can't start application in the cluster. Is it NBU's problem or is it cluster related issue? We can disable AutoFailover and switch NBU's service group to the problem node again. It'll stop in OFFLINE|FAULTED state on it. What's next?...

GrazianoPecciarini | 26 Mar 2013 | 0 comments
  • In the Computer and Storage World a snapshot is the state of a system at a particular point in time. More in detail, a snapshot is a point-in-time, read-only, disk-based copy of a client volume (see Blog Link). 

    In the backup world, after the snapshot is created, NetBackup backs up data from the snapshot, not directly from the client’s primary or original volume. Users and client operations can access the primary data without interruption while data on the snapshot volume is being backed up. The contents of the snapshot volume are cataloged as if the backup was produced directly from the primary volume. After the backup is complete, the snapshot-based backup image on storage media is indistinguishable from a backup image produced by a traditional, non-snapshot backup. 


inn_kam | 25 Mar 2013 | 4 comments


i am working as Systems Engineer in one of the Vendor Side Company , and give support for Symantec Netbackup + Desktop Laptop + Ops Center for lots of Customer .and if got any complicated issue , we took help from Symantec  with excellent support.

In this blog i would like to contribute my Experience for trouble shooting various cases at customer side with the help of Symantec

And it wil help lots of people who are new in using Symantec Netbackup.

Gaurav Kaushal | 21 Mar 2013 | 4 comments

Scary …!

One of the reasons that can cause this is the absence of FARMS key under


Sometime it may happen that the key is not present and will cause the backups to fail. The significance of this key is that it contains the information about the SharePoint farm.

This Key is created on SQL Backend Servers and contains the names of frontend servers that put their data on this backend server.

If you encounter such issue, you can use the following command to create the key and reattempt the backup.

bpresolver.exe query -c svw8scr5 -ct 8 -init_beds "Microsoft SharePoint Resources:\*"

Recently, while working on one of the cases, I used this command and it resolve the backup failure for us.

Arigarpen | 05 Mar 2013 | 0 comments


All backups ending with Status: 96 - Unable to allocate new media for backup, storage unit has none available(96)

Job Overview Status:

Unable to allocate new media for backup, storage unit has none available(96)

Detailed Status:

Error bptm(pid=3324) incorrect media found in drive index 0, expected 6500L4, found 003395, FREEZING 6500L4

Other Noticable Manifistation:

All scratch media that encounters this error immediately becomes Frozen and gets moved from the Scratch volume pool into the Netbackup.


1. Confirm that the Media ID Generation Rule is configured properly.

Access from: (Media and Device Manager > Media > Robots > TLD (X) > Inventory Robot > Advanced Options > Media Generation ID)

Note: The standard rule with 1:2:3:4:5:6 was causing issues by intermittently...

robydv | 04 Mar 2013 | 0 comments
When selecting a backup solution for an enterprise environment performance and scalability are between the most important requirements.
I'd like to recall the two Kyle Blog entries about NetBackup scalability and why the NetBackup three-tiered approach is the winning one.
A backup software with its configuration catalog distributed on different hosts may have scalability issues due to the problem of keeping all this pieces of information up-to-date.
The other things to consider are: