cancel
Showing results for 
Search instead for 
Did you mean: 

BAckup fails with status 24

Rocky67
Level 4

We have a windows 2012 server. However, we are unable to backup. Connection is established between the backup server and client server however, the data transfer does not take place and after about 2 hours, the backup fails with status 24.

bptetsbpcd command  to cleint from backup/media server is completing successfully. However, backup fails.

Please advise what could be the solution:

Client NBU version: 7.5.0.6

Master\media version: 7.5.0.6

1 ACCEPTED SOLUTION

Accepted Solutions

You need to look at the bpfis log to find hints for why it took an hour and 40 minutes to take a snapshot.

I second the recommendation to move up. 7.5.0.6 was the very first release to support Windows 2012. It was followed quickly by 7.5.0.7. You can have 7.5.0.7 clients with 7.6.0.6 master server. Even so, you should be at least at 7.6.0.3 even if you're trying to get by without support. VSS snapshots are taken by a component called BEDS that NetBackup shares with Backup Exec. The timing of the BE release was such that NetBackup 7.5.0.6 through 7.6.0.2 used BEDS from a pre-release version of the BE release needed for Windows 2012.

View solution in original post

16 REPLIES 16

J_MCCOLL
Level 4

Have you looked through the following article?

https://www.veritas.com/support/en_US/article.TECH150369

This error code is usually associated with a communications issue between client/media/master.

What is the network load on the server before a backup commences?

Can you provide the following logs:

bpbkar,bpcd

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

When was NBU deployed on the 2012 client? 
Has it ever worked?
Did you use the special NB_7.5.0.6 Full Installer Package for Win2012?

Have you tried the bpbkar test on the client to see if NBU can read data successfully?
Have you checked bpbkar log on the client?

One more thing.... 
Are you aware that all support for NBU 7.x up to 7.6.1.2 has ended more than a year ago?

 

 

 

This is a newly built VM. NBU was deployed recently. We were unable to backup, then we changed the attributes from host properties to continue backup if snapshot error encountered. However, we were not able to backup still. then we tested  backup of C and D drive alone and it completed successfully once. However, since then, backup has been failing with status 24 after about 2 hours.

 

Yes, I am aware that there is no support for the current version which we are using.

 

I have attached the bpcd, bpbkar logs. I have also attached the bptestbpcd command result.

The bptestbpcd command exits with status 0. However, we could find the below statement in the bpbkar log.

 OS Error: 10060 (A connection attempt failed because the connected party did not properly respond after a period of

time, or established connection failed because connected host has failed to respond.

Can you please follow this document

https://www.veritas.com/support/en_US/article.100032031

It would from the below error that you are ultimately having Connection Refused issue (58)

        status: RETRY, (42) CONNECT_REFUSED; system: (10061) No connection could
 be made because the target machine actively refused it. ; FROM 0.0.0.0 TO vngnp
mac-cm 172.20.5.53 bpcd VIA pbx

As Marianne stated, has this every worked?  And you really need to upgrade to the latest version, or at the very least a supported version of NetBackup.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Did you use the special NB_7.5.0.6 Full Installer Package for Win2012?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
The problem is still with the snapshot portion.

08:17:59.935: [5260.5880] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - Attempting to create snapshots for 'C:'
08:17:59.935: [5260.5880] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - CREATE request: C:\Program Files\Veritas\NetBackup\bin\bpfis create -owner NBU -fso -WOFB -fim VSS -id abcd1_1528359304 C:\
09:59:05.920: [5260.5880] <4> V_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot creation, FIS_ID: abcd1_1528359304
09:59:05.920: [5260.5880] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - Snapshot creation was not successful

Look at the timestamps - by the time the snapshot failed, bpbrm on the media server has long timed out, explaining the network-related errors.

Please ensure that the special 2012 client software is used.

@Marianne yes, NB_7.5.0.6 Full Installer Package for Win2012 is used.

@J_MCCOLL  

Regarding the below error::

status: RETRY, (42) CONNECT_REFUSED; system: (10061) No connection could
be made because the target machine actively refused it. ; FROM 0.0.0.0 TO client 172.x.x.x bpcd VIA pbx

Yes, it is showing refused for pbx. however, bptestbpcd command is successful with status 0 over port 13724.

And we have other 2012 servers where the bptestbpcd command shows same results and backup is completing for them.

 

 

 

@Marianne  when backup had failed, we had used disable snapshot and continue in snapshot error control in client attributes to test backup.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Your problem is that it takes a very long time for the snapshot to fail. By that time bpbrm on the media server has timed out.

There are a couple of things you can try:

1. Troubleshoot at OS level to see why VSS is taking such a long time.
2. Try VMware policy backup (if you are licensed for it).
3. Deselect open file backup completely.
4. Upgrade to a supported NBU version (if memory serves me right, W2012 only really worked well from 7.6 onwards).

You need to look at the bpfis log to find hints for why it took an hour and 40 minutes to take a snapshot.

I second the recommendation to move up. 7.5.0.6 was the very first release to support Windows 2012. It was followed quickly by 7.5.0.7. You can have 7.5.0.7 clients with 7.6.0.6 master server. Even so, you should be at least at 7.6.0.3 even if you're trying to get by without support. VSS snapshots are taken by a component called BEDS that NetBackup shares with Backup Exec. The timing of the BE release was such that NetBackup 7.5.0.6 through 7.6.0.2 used BEDS from a pre-release version of the BE release needed for Windows 2012.

View solution in original post

@Marianne Thanks. We have deselected WOFB for now . We have asked Wintel team to check at OS why snapshot is taking long time.

Look at your bpfis log. Your OS admins will be able to help you better if you can tell them which snapshot action takes a long time. Or the delay might not be the snapshot itself. It could be in some other processing within NetBackup.