After upgrading from Netbackup 7.1.0.4 to 7.5.0.5 facing below few backup issues –

[ranjith_rao]

I need a solution for below issues.

1.Maximum jobs are failing with Status 2106: Disk storage server is down.

2.Maximum jobs are failing with Status 25: cannot connect on socket.

3.Child Jobs are completed successfully but parent job is showing as running and however it’s in hang status.

If anyone faced the same probes, please let me know what the resolution of these errors is.

[inn_kam]

First stop the netbackup services then restart them,and check again

and also check that do you go through the process of upgrade properly as under:

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

[Marianne]

We need more detail for points 1 and 2. 

1. Which type of Advanced disk / Storage Server?
If OST - have you updated OST plugin?
If MSDP - see this note in NBU 7.5 LBN: http://www.symantec.com/docs/TECH178334
After upgrade to NetBackup 7.5, MSDP storage volume is down
...http://www.symantec.com/docs/TECH183704

2. Provide more detail, please.
All text in Details tab of failed job will be a good start.

3. Fix available. See this note in above LBN:
Latest Issues:
(NEW) (ET3106719) <<Fix Downloadable>> After upgrading a master server to NetBackup 7.5.0.5 (or applying NetBackup 5200/5220 Appliances 2.5.2 to an Appliance running as a master server), the Activity Monitor reports inconsistent information on job status for some jobs. Additionally, some jobs may not display in OpsCenter.
 http://www.symantec.com/docs/TECH203521

[inn_kam]

Thanks for point 3. Fix Downloadable. for NB 7.5.0.5

want to ask that we are using 7.5.0.4 ,so will it be ok .or we will upgrade to patch 7.5.0.5?

[ranjith_rao]

Hi kam,

Thank you for your reply.

Yes...I know that we have faced the point 3 issue on NBU 7.5.0.4 version; however I upgraded from 7.1.0.4 to 7.5.0.5 and facing the point 3 issue in the latest version also.

[ranjith_rao]

Hi Marianne,

Point 2 - 

please find the below logs for Status 25 Client Detailed Job-

3/27/2013 8:05:54 PM - Info nbjm(pid=3604) starting backup job (jobid=398887) for client WCDCC-IN-VPBI01, policy T1_ImageNow_Reporting_2003, schedule Daily_Incremental  

3/27/2013 8:05:54 PM - Info nbjm(pid=3604) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=398887, request id:{9896AEB1-337C-4EAD-971C-641E145568E9})  

3/27/2013 8:05:54 PM - requesting resource DC2_CIFS_DataDomain_DD3_Tier1_IN_RPRT_2K3

3/27/2013 8:05:54 PM - requesting resource wcdcc-no-ppbu01.NBU_CLIENT.MAXJOBS.WCDCC-IN-VPBI01

3/27/2013 8:05:54 PM - requesting resource wcdcc-no-ppbu01.NBU_POLICY.MAXJOBS.T1_ImageNow_Reporting_2003

3/27/2013 8:05:54 PM - granted resource wcdcc-no-ppbu01.NBU_CLIENT.MAXJOBS.WCDCC-IN-VPBI01

3/27/2013 8:05:54 PM - granted resource wcdcc-no-ppbu01.NBU_POLICY.MAXJOBS.T1_ImageNow_Reporting_2003

3/27/2013 8:05:54 PM - granted resource MediaID=@aaacd;Path=\\10.126.102.9\backup\CIFS_DataDomain_DD3_Tier1\IN_RPRT_2K3;MediaServer=wcdcc-no-ppbu02

3/27/2013 8:05:54 PM - granted resource DC2_CIFS_DataDomain_DD3_Tier1_IN_RPRT_2K3

3/27/2013 8:09:10 PM - estimated 62306 Kbytes needed

3/27/2013 8:09:10 PM - Info nbjm(pid=3604) started backup (backupid=WCDCC-IN-VPBI01_1364436549) job for client WCDCC-IN-VPBI01, policy T1_ImageNow_Reporting_2003, schedule Daily_Incremental on storage unit DC2_CIFS_DataDomain_DD3_Tier1_IN_RPRT_2K3

cannot connect on socket(25).

[inn_kam]

Hi ranjith

for point 2 check these : 

1.The CLIENT must have the media server hostname added to the SERVER list to allow the media server to establish a connection to the NetBackup processes on the client.

2.cannot connect on socket(25) 

Step by step check all possibilties

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

[Marianne]

Verify connectivity between media server and client with bptestbpcd.
If you are backing up ALL_LOCAL_DRIVES, test connectivity between master and client as well.
Remember to create bpcd log folder on client before running bptestbpcd.
See: http://www.symantec.com/docs/TECH42657 and http://www.symantec.com/docs/HOWTO43696

There are no known issues in 7.5.x that would introduce status 25.

About no.3: Problem was introduced in 7.5.0.5.

[ranjith_rao]

Hi Kam,

Before upgrading the NBU these servers backup was successful on every day, we are facing this error after upgrading the NBU 7.1.0.4 to 7.5.0.5

[ranjith_rao]

Hi Marianne,

I tested communication between master to Client and Client to Master and Client to master and Client to Media also media to client using bpclntcmd -hn, -ip. Command communication is going on as expected.

[Marianne]

bpclntcmd is testing name lookup, not connectivity.

bptestbpcd tests port connectivity.

[ranjith_rao]

Yes...I know that, I was used both the commands for name resolution and port connectivity...getting the response positive. 

Can you please give me exact resolution of this issue.

[Mark_Solutions]

Has the upgrade re-set you client read and client connect timeouts? The failure seems to happen after about 5 minutes - worth checking those settings on the Media Servers Host Properties

[Marianne]

Can you please give me exact resolution of this issue.

Sorry, not possible with amount of details provided. If you had a look at the TN http://www.symantec.com/docs/HOWTO50802 posted by inn_kam above, you will see that there are many possible causes.

You have posted details of one failed backup. 
Are all backups failing for this specific client?
Or for this media server?
Or when this STU is used?

Please ensure that these log folders exist:
On media server: bpbrm
On client: bpcd