Hi Everyone,

Not sure what happened our Netbackup EMM DB is pointing to another Location on Same backup server.

NBDB points to C drive and EMM DB points to P drive.

Can someone help to fix this?

Regards,

Raghav

Master server: WIN@K3R2

Client : AIX 5.3

Netbackup version: 7.1.0.4

Hello, backup ran successfully, but validation consistently failing with " allocation failed"

From RMAN:

Hi All,

We recently stood up a 5230 appliance with 2.6.0.2 (7.6.0.2) and noticed while running the Windows Activity Monitor that the filter results are displayed in light blue. Wondering where this action is controlled or what the trigger is for this action occuring since we have never seen this before.

Several of the admins have commented that the light-blue color on the text is difficult to read due to low contrast between the white background.

Has anyone seen this before and/or figured out how to revert back to good-old black font for the filter results ?

Ken W

Hi All,

I am getting below error:

ERR - Error opening the snapshot disks using given transport mode: Status 23

the backup failed to back up the requested files  (6)

Netbackup 7.5.0.4

Windows 2008r2 Master and Media servers

Hello,

I have been for some time having performance issues using VM query. But lately, it has reached the point where I avoid clicking on the "client" tab in a vm policy like the plague, becuase it will lterally take 30 minutes to an hour to actually show me the settings. Then, if I change a search parameter, its another half hour, then when I save the changes, yet another half hour. Sometimes it will give a message that the "operation has timed out', and other times it will finally open. I can forget running a 'test query' anymore, which I'd really like to be able to do again!

Ive already added in the 'disableIPResolution" value on the VM backup host media server's registry, but it had no effect.

Also, when looking in the job details of completed VM backup jobs, I see the following.......(these are examples from a couple different jobs, but this is about average). Take a look at the "resolver discovery" elapsed time. Does that seem excessive?

7/23/2014 8:41:05 PM - end Application Resolver, Resolver Discovery; elapsed time: 04:11:03

7/23/2014 8:46:06 PM - end Application Resolver, Resolver Discovery; elapsed time: 04:16:01

I dont know if the "resolver discovery" and the very slow VM query responsiveness are related issues, but I'm hoping someone will recognize these characteristics as something they may have seen before.

What has me looking at all of this, is that Ive created a couple new VM backup policies, and no matter what Ive tried so far, they fail out with that status 200, about the scheduler not finding anything due to run. I'm even using a very simple query with only the vcenter and displayname.  The schedules are unique, and I see no overlap in these calandar-based schedules. Changing the policy to a manual selection will allow the job to complete with no issues, and in good time, but we have 1100 VM's in our environment, so I really need to run query. Each time a make a change and test it, its taking 1+ hours to make the adjustment to the query builder, and then another 4+ hours for the job to fail. Very frustrating, as you can imagine.

Thank you!

Todd

Hi All

Netbackup 7.5 / Solaris box

I need to get critical backup failures alerts script through bpstart.notify script.

Please suggest..

Hello,

We're looking for suggestions on how to efficently backup large multi-TB remote clients over a network with limited bandwidth.

•   Are there any non-hardware NBU client backup methods to either de-dup, compress, backup only changed blocks, use a possible Puredisk option, or otherwise limit data transfer ?

•   Are there any low cost hardware options that could be installed on the remote side to stage backup for dedup ?

•   Not sure if this would gain anything, but would it help to setup a remote Master and/or media server and send the data to the local storage using an SLP ?

Anyway, as always, thanks for all your help !

The local environment:

NBU 7.6.0.2 on Red Hat 4.1.2-54 Master/Media servers writing to Data Domain disks (DDos  5.4.1.1)

The remote clients:

NBU 7.6.0.2 on Windows and Linux

Hello Team,

The backups are getting failed with error code 2106 at some point of time as mentioned error below. But when I retrigger the backups the backups are getting successful. Sometime it is failing on second time also when i retrigger but  third or fourth time when i retrigger the bakcups they are getting successful.

but frequently the backups are getting failed with EC 2106.  Kindly suggest on which I need to check.

Error nbjm(pid=2992) NBU status: 2106, EMM status: Storage Server is down or unavailable 
Disk storage server is down(2106)

Hi all,

I would like to use the instant recovery feature for VMware so I read the "Requirements for Instant Recovery for VMware" at

http://www.symantec.com/business/support/index?page=content&id=HOWTO92127#v85467039

They say you need a Windows restore host to perform this activity.

We use Netbackup appliances as a media servers so I suppose that the restore host in our case is the media server that is the appliance so we cannot use the instant recovery unless I use another winodws host as restore host. Am I right?

Thank You

Regards

Mauro

Hi Experts,

Environment.

Master:- 7.6.0.1 

Server:- Win2008 

Vmhost:- 7.6.0.1 Win 2008

We are experiencing the below issue. Let me tell you. We have some issue in vcenter as snapshot files are not getting deleted by Netbaup and are orphaned. So this vmhost is connected to the datastore where the snapshot issue is happening.

7/25/2014 1:27:06 PM - requesting resource Any
7/25/2014 1:27:06 PM - requesting resource xx.NBU_CLIENT.MAXJOBS.xx.mm
7/25/2014 1:27:06 PM - requesting resource xx.NBU_POLICY.MAXJOBS.MSLync_BKP_VM
7/25/2014 1:27:06 PM - awaiting resource Any - No drives are available
7/25/2014 1:42:37 PM - awaiting resource Any Reason: Drives are in use, Media Server: xx, 
     Robot Number: 0, Robot Type: TLD, Media ID: N/A, Drive Name: N/A, 
     Volume Pool: Exchange_Pool, Storage Unit: xx-hcart3-robot-tld-0, Drive Scan Host: N/A
    
7/25/2014 1:42:39 PM - awaiting resource Any - No drives are available
7/25/2014 1:50:06 PM - awaiting resource Any Reason: Drives are in use, Media Server: xx, 
     Robot Number: 0, Robot Type: TLD, Media ID: N/A, Drive Name: N/A, 
     Volume Pool: Exchange_Pool, Storage Unit: xx-hcart3-robot-tld-0, Drive Scan Host: N/A
    
7/25/2014 1:50:40 PM - awaiting resource Any Reason: Robotic library is down on server, Media Server: xx, 
     Robot Number: 0, Robot Type: TLD, Media ID: N/A, Drive Name: N/A, 
     Volume Pool: Exchange_Pool, Storage Unit: xx-hcart3-robot-tld-0, Drive Scan Host: N/A
    
7/25/2014 1:52:30 PM - granted resource Txx.NBU_CLIENT.MAXJOBS.t
7/25/2014 1:52:30 PM - granted resource xx.NBU_POLICY.MAXJOBS.MSLync_BKP_VM
7/25/2014 1:52:30 PM - granted resource TNM015
7/25/2014 1:52:30 PM - granted resource Drive002
7/25/2014 1:52:30 PM - granted resource xx-hcart3-robot-tld-0
7/25/2014 1:52:30 PM - estimated 3046243 Kbytes needed
7/25/2014 1:52:30 PM - begin Parent Job
7/25/2014 1:52:30 PM - begin VMware, Start Notify Script
7/25/2014 1:52:31 PM - Info RUNCMD(pid=20148) started            
7/25/2014 1:52:31 PM - Info RUNCMD(pid=20148) exiting with status: 0         
Status 0
7/25/2014 1:52:31 PM - end VMware, Start Notify Script; elapsed time: 0:00:01
7/25/2014 1:52:31 PM - begin VMware, Step By Condition
Status 0
7/25/2014 1:52:31 PM - end VMware, Step By Condition; elapsed time: 0:00:00
7/25/2014 1:52:31 PM - begin VMware, Read File List
Status 0
7/25/2014 1:52:31 PM - end VMware, Read File List; elapsed time: 0:00:00
7/25/2014 1:52:31 PM - begin VMware, Create Snapshot
7/25/2014 1:52:33 PM - started process bpbrm (21261)
7/25/2014 1:52:34 PM - Info bpbrm(pid=21261) tn is the host to backup data from     
7/25/2014 1:52:34 PM - Info bpbrm(pid=21261) reading file list for client        
7/25/2014 1:52:34 PM - Info bpbrm(pid=21261) start bpfis on client         
7/25/2014 1:52:34 PM - Error bpbrm(pid=21261) bpcd on VMHOST01P exited with status = 48     
7/25/2014 1:52:34 PM - Error bpbrm(pid=21261) bpcd on VMHOST01P exited with status = 48     
7/25/2014 1:52:34 PM - Error bpbrm(pid=21261) bpcd on VMHOST01P exited with status = 48     
7/25/2014 1:52:34 PM - Info bpbrm(pid=21261) Starting create snapshot processing         
7/25/2014 1:52:34 PM - Error bpbrm(pid=21261) bpcd on VMHOST01P exited with status 48: client hostname could not be found
7/25/2014 1:52:35 PM - Info bpfis(pid=0) done. status: 48: client hostname could not be found    
7/25/2014 1:52:35 PM - end writing
Status 48
7/25/2014 1:52:35 PM - end VMware, Create Snapshot; elapsed time: 0:00:04
7/25/2014 1:52:35 PM - begin VMware, Stop On Error
Status 0
7/25/2014 1:52:35 PM - end VMware, Stop On Error; elapsed time: 0:00:00
Status 48
7/25/2014 1:52:35 PM - end Parent Job; elapsed time: 0:00:05
client hostname could not be found(48)

Below is the error of 58 Error code.

7/25/2014 12:31:40 PM - Info nbjm(pid=3724) starting backup job (jobid=48611) for client tn, policy CCT_ESX01_VM_121, schedule Incremental_backup  
7/25/2014 12:31:40 PM - Info nbjm(pid=3724) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=48611, request id:{48A5FCB2-07A4-416F-B4FB-477D65558D32})  
7/25/2014 12:31:40 PM - requesting resource Any
7/25/2014 12:31:40 PM - requesting resource TN.NBU_CLIENT.MAXJOBS.tn
7/25/2014 12:31:40 PM - requesting resource TN.NBU_POLICY.MAXJOBS.CC
7/25/2014 12:31:40 PM - awaiting resource Any - No drives are available
7/25/2014 12:34:17 PM - granted resource TN.NBU_CLIENT.MAXJOBS.
7/25/2014 12:34:17 PM - granted resource TN.NBU_POLICY.MAXJOBS.CC
7/25/2014 12:34:17 PM - granted resource TNM083
7/25/2014 12:34:17 PM - granted resource Drive006
7/25/2014 12:34:17 PM - granted resource TN-hcart3-robot-tld-0
7/25/2014 12:34:18 PM - estimated 5075452 Kbytes needed
7/25/2014 12:34:18 PM - begin Parent Job
7/25/2014 12:34:18 PM - begin VMware, Start Notify Script
7/25/2014 12:34:18 PM - Info RUNCMD(pid=18152) started            
7/25/2014 12:34:18 PM - Info RUNCMD(pid=18152) exiting with status: 0         
Status 0
7/25/2014 12:34:18 PM - end VMware, Start Notify Script; elapsed time: 0:00:00
7/25/2014 12:34:18 PM - begin VMware, Step By Condition
Status 0
7/25/2014 12:34:18 PM - end VMware, Step By Condition; elapsed time: 0:00:00
7/25/2014 12:34:18 PM - begin VMware, Read File List
Status 0
7/25/2014 12:34:18 PM - end VMware, Read File List; elapsed time: 0:00:00
7/25/2014 12:34:18 PM - begin VMware, Create Snapshot
7/25/2014 12:34:19 PM - started process bpbrm (18932)
7/25/2014 12:35:41 PM - Info bpbrm(pid=18932) tn is the host to backup data from     
7/25/2014 12:35:41 PM - Info bpbrm(pid=18932) reading file list for client        
7/25/2014 12:36:22 PM - Info bpbrm(pid=18932) start bpfis on client         
7/25/2014 12:37:03 PM - Info bpbrm(pid=18932) connect failed STATUS (18) CONNECT_FAILED        
7/25/2014 12:37:03 PM - Info bpbrm(pid=18932)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10060) Connection timed out.; FROM 10.84.77.10 TO VMHOST01P 10.84.77.200 bpcd VIA pbx
7/25/2014 12:37:03 PM - Info bpbrm(pid=18932)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10060) Connection timed out.; FROM 10.84.77.10 TO VMHOST01P 10.84.77.200 bpcd VIA vnetd
7/25/2014 12:37:03 PM - Info bpbrm(pid=18932)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10036) A blocking operation is currently executing. ; FROM 10.84.77.10 TO VMHOST01P 10.84.77.200 bpcd
7/25/2014 12:37:03 PM - Error bpbrm(pid=18932) cannot connect to VMHOST01P, status = 25      
7/25/2014 12:37:44 PM - Info bpbrm(pid=18932) connect failed STATUS (18) CONNECT_FAILED        
7/25/2014 12:37:44 PM - Info bpbrm(pid=18932)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10060) Connection timed out.; FROM 10.84.77.10 TO TN 10.84.77.200 bpcd VIA pbx
7/25/2014 12:37:44 PM - Info bpbrm(pid=18932)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10060) Connection timed out.; FROM 10.84.77.10 TO TN 10.84.77.200 bpcd VIA vnetd
7/25/2014 12:37:44 PM - Info bpbrm(pid=18932)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10036) A blocking operation is currently executing. ; FROM 10.84.77.10 TO TN 10.84.77.200 bpcd
7/25/2014 12:37:44 PM - Error bpbrm(pid=18932) cannot connect to TNMMVMHOST01P, status = 25      
7/25/2014 12:38:25 PM - Info bpbrm(pid=18932) connect failed STATUS (18) CONNECT_FAILED        
7/25/2014 12:38:25 PM - Info bpbrm(pid=18932)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10060) Connection timed out.; FROM 10.84.77.10 TO VMHOST01P 10.84.77.200 bpcd VIA pbx
7/25/2014 12:38:25 PM - Info bpbrm(pid=18932)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10060) Connection timed out.; FROM 10.84.77.10 TO VMHOST01P 10.84.77.200 bpcd VIA vnetd
7/25/2014 12:38:25 PM - Info bpbrm(pid=18932)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10036) A blocking operation is currently executing. ; FROM 10.84.77.10 TO VMHOST01P 10.84.77.200 bpcd
7/25/2014 12:38:25 PM - Error bpbrm(pid=18932) cannot connect to VMHOST01P, status = 25      
7/25/2014 12:38:25 PM - Info bpbrm(pid=18932) Starting create snapshot processing         
7/25/2014 12:39:06 PM - Info bpbrm(pid=18932) connect failed STATUS (18) CONNECT_FAILED        
7/25/2014 12:39:06 PM - Info bpbrm(pid=18932)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10060) Connection timed out.; FROM 10.84.77.10 TO VMHOST01P 10.84.77.200 bpcd VIA pbx
7/25/2014 12:39:06 PM - end writing
Status 58
7/25/2014 12:39:06 PM - end VMware, Create Snapshot; elapsed time: 0:04:48
7/25/2014 12:39:06 PM - begin VMware, Stop On Error
Status 0
7/25/2014 12:39:06 PM - end VMware, Stop On Error; elapsed time: 0:00:00
Status 58
7/25/2014 12:39:06 PM - end Parent Job; elapsed time: 0:04:48
can't connect to client(58)
7/25/2014 12:39:06 PM - Info bpbrm(pid=18932)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10060) Connection timed out.; FROM 10.84.77.10 TO VMHOST01P 10.84.77.200 bpcd VIA vnetd
7/25/2014 12:39:06 PM - Info bpbrm(pid=18932)     status: FAILED, (44) CONNECT_TIMEOUT; system: (10060) Connection timed out.; FROM 10.84.77.10 TO VMHOST01P 10.84.77.200 bpcd
7/25/2014 12:39:06 PM - Error bpbrm(pid=18932) Cannot connect to VMHOST01P         
7/25/2014 12:39:06 PM - Info bpfis(pid=0) done. status: 58: can't connect to client   

Pls help on this.

Hi,

We need to perform a backup using some scripts (like pre post command).

This is our Netbackup Infrastructure:

MasterServer: Windows Server 2008 R2 with Veritas Cluster (NB7.5.0.7)
MediaServer: Linux Redhat & Windows 2008 R2 (NB7.5.0.7)
Client: Linux Redhat (NB7.5.0.7)

We need to perform backup on client following a sequence of script before, during and after backup.

I've a create a standard policy.
On /usr/openv/netbackup/bin I've created a bpstart_notify.<policy_name>.<schedule_name> and bpend_notify.<policy_name>.<schedule_name> but some folders were skipped.

This is the sequence that we need to follow:

1. Pre-backup script (Set DB with backup mode)
2. backup of db configuration folder
3. When first backup is finished a script must be executed (Stop data stream to index)
4. Wait 30 sec
5. Backup of data stream folder
6. When second backup is finished another script must be executed to end backup procedure (Start data stream and unset backup mode on DB)

How can I proceed?

regards,

Amilcare

Hello,

I need some advice. We have just installed a Dell EqualLogic PS6210x SAN and a new VMware infrastructure running vSphere5.5. I have added a new VMware backup host to our Netbackup domain (Windows Server 2008 R2) with iSCSI connectivity to the VMware switch. I have masked the SAN volumes to the VMware backup host and added the VMware credentials in Netbackup. I am able to browse the ESX hosts and add VMware guests to a policy. I have a LAN network connection for connectivity to the master server and the rest of the domain, and an iSCSI network connection on the vmware backup host purely for use with this new VMware enviroment, I am able to backup and restore to the new VMware environment successfully using the SAN transport method. All good so far but here is my problem.

Upon backup and restore snapshot data is being pulled accross both the LAN and the iSCSI network interfaces to the backup host in equal measure. I would like the snapshot to just go accross the iSCSI network only. I have configured the iSCSI initialtior on my backup host and can see all the volumes, but how can I get Netbackup to just use the iSCSI connection?

Any help appreciated

Regards

Carl

Yesterday I posted about status code 2106 after this upgrade which Symantec was able to resolve.  Now however, many of the clients are getting the subject errors.  Has anyone else had this experience with this upgrade?

We're running NBU 7.1.0.4 on Windows 2008 R2 and backing up a Windows file server of approx. 1 TB. This server has got all the user profiles, each one with different shared permissions.

If we attempt to restore entire user data profiles to a different machine using tape backups, will the original permissions be restored or the default local admin privileges(NBU account) be assigned?

An administrator I work with is running Windows Server 2008 R2 with Netbackup 7.5.  He renamed the server and tried to upgrade to 7.6 but it didn't work so he removed Netbackup and now it will not re intall.  When it gets to the point in the installation of creating the database it fails (NBDB.exe).  I'm  looking for steps to remedy the problem the admin created.  Thanks for the help! 

Hello all,

I have a clustered master server (clustered using VCS global clustering option) in active-passive mode. The catalog(size is roughly 500 GB) is replicated to the passive node using SRDF/A.

OS is Windows Server 2008 R2 Enterprise. The whole environment runs on tape infrastructure only.

I am deciding on an approach to run the upgrade and hence need experts views on that.

Approach 1- Break the SRDF/A replication of catalog. Upgrade active node. Bring active down after upgrade. Make the 2nd node active. Upgrade passive node.

Approach 2- Do not break the replication. Take a clone of the catalog LUN before upgrade. Let the catalog replicate as and when the upgrade is in progress. After upgrade at active node, bring it down. Bring up the passive node. As upgraded database will already have replicated, upgrade here require only upgrade of binaries.

The full backup of the catalog takes about 6 hours to complete.

Can you suggest me the best approach among these? Or any other if you have a better approach. Also, how can I estimate time that will be taken for my environment?

-Regards,

Neetu

we used Netbackup to backup the client.

client is crashed now. we need to restore the enitre data drives, which is 40 TB(which is most critical data).   we need to restore them ASAP.  

Is there a way to directly extract/untar backup images from tapes to hardisk on client. or any other fast way.

Hi Experts,

Environment is as below.

win 2008 Server with Master 7.6

We have 100 policies having retention period of 1 month so we were told to make the retetion periord to 1 year. So i was trying to take the full backup of each policy with one year reteion period and make it again 1 month.

I have changed one policy which has 1 month retention period and now its running So i am stuck now.

1:- I did not enable the allow multiple retention per media in master properties. My question is if I dont enable this option what would be the error?

    I believe it wont mix the retention period. So Do i need free tapes?

2:- we have clustered enviornment i ran nbpemreq -suspend_scheduling command before doing that but still i could see many new jobs are being queued there. What is the reason?

3:- What should i do to save the tape space. What would happen if we mix up the retion period?

Pls help.

Hi,

I just received NetBackup 7.6 CD and want to deploy it.

Would you help to point me to its support OS for Master/Media/Client installation?

Thanks,

Abby

Quick breakdown of my environment.   We have 6 Exchange Mailbox servers in a DAG with 32 Databases total.  All Databases are in the DAG.  I am doing backups to Tape for now until i can find more drive space for Disk2Disk so no GRT.

So yesterday i was finally able to get everything talking and kicked off a FULL backup of the DAG and it was going great.  All Exchange servers were showing up in the Activity Monitor, jobs were Queued up, and Databases were backing up.  Life was good.  I broke the network while trying to increase bandwidth and when the host was finally back up a couple hours later, all of the jobs were failed and waiting for a retry.  I wanted to start over again clean, so i cancelled all of the pending jobs, and rebooted the host.  

Now that the host is back up, I am not able to do any DAG backups.  I am getting error 46 - server not allowed access.  I saw in the articles that I need to check the IP addresses that netbackup is getting, but since I am using the DAG name instead of a host, i am not sure how to check that.

Has anyone seen this before that can help?

Thanks

Drabert