Failed with error 24

[V_P_S]

Hello Team,

Backup has been failing with error code 24. It transfer some data but after that failed with error code 24.

client having  Linux, RedHat2.6 and nbu version is  7.1.0

Master server having VERSION NetBackup 7.1.0.2 and OS solaris

Find bpbkar logs below.

[root@<client name>8 bpbkar]# more log.082912
01:37:15.770 [18289] <4> bpbkar main: real locales <LC_CTYPE=en_US.UTF-8;LC_NUMERIC=en_US.UTF-8;LC_TIME=en_US.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=C;LC_M
ESSAGES=en_US.UTF-8;LC_PAPER=C;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=C;LC_IDENTIFICATION=C>
01:37:15.770 [18289] <4> bpbkar main: standardized locales - mnt_lc_messages <en_US.UTF-8> mnt_lc_ctype <en_US.UTF-8> mnt_lc_time <en_US.UTF-8> mnt_lc_collat
e <en_US.UTF-8> mnt_lc_numeric <en_US.UTF-8>
01:37:15.773 [18289] <2> logparams: bpbkar -r 1209600 -ru root -dt 606857 -to 0 -clnt <client name> -class <POLICY> -sched Differential-Inc -s
t INCR -bpstart_to 300 -bpend_to 300 -read_to 3600 -ckpt_time 900 -blks_per_buffer 511 -use_otm -use_ofb -b <client name>_1346204228 -kl 28 -fso -nfsok
01:37:15.774 [18289] <4> bpbkar: INF - setenv KEYWORD=NONE
01:37:15.774 [18289] <4> bpbkar: INF - setenv STREAM_PID=18289
01:37:15.774 [18289] <4> bpbkar: INF - setenv STREAM_NUMBER=0
01:37:15.774 [18289] <4> bpbkar: INF - setenv STREAM_COUNT=0
01:37:15.774 [18289] <4> bpbkar: INF - setenv STREAMS=0
01:37:15.774 [18289] <4> bpbkar: INF - setenv BPSTART_TIMEOUT=300
01:37:15.774 [18289] <4> bpbkar: INF - setenv BPEND_TIMEOUT=300
01:37:15.774 [18289] <4> bpbkar: INF - setenv RESTARTED=0
01:37:15.774 [18289] <4> bpbkar: INF - setenv BACKUPID=<client name>_1346204228
01:37:15.774 [18289] <4> bpbkar: INF - setenv UNIXBACKUPTIME=1346204228
01:37:15.774 [18289] <4> bpbkar: INF - setenv BACKUPTIME=Wed Aug 29 01:37:08 2012

01:37:15.775 [18289] <4> bpbkar: INF - BACKUP START 18289
01:37:15.775 [18289] <4> bpbkar: INF - Estimate:-1 -1
01:37:15.794 [18289] <2> bpbkar add_to_filelist: starting sizeof(filelistrec) <128>
01:37:15.794 [18289] <4> bpbkar: INF - Processing /
01:37:15.807 [18289] <8> bpbkar: WRN - [/apps] is in a different file system from [/]. Skipping
01:37:15.807 [18289] <8> bpbkar: WRN - [/boot] is in a different file system from [/]. Skipping
01:37:15.808 [18289] <8> bpbkar: WRN - [/dev] is in a different file system from [/]. Skipping
01:37:15.900 [18289] <8> bpbkar: WRN - [/home] is in a different file system from [/]. Skipping
01:37:16.259 [18289] <8> bpbkar: WRN - [/logs] is in a different file system from [/]. Skipping
01:38:17.879 [18289] <8> bpbkar: WRN - [/proc] is on file system type PROC. Skipping
01:38:17.929 [18289] <8> bpbkar: WRN - [/sys] is in a different file system from [/]. Skipping
01:38:17.930 [18289] <8> bpbkar: WRN - [/tmp] is in a different file system from [/]. Skipping
01:38:21.801 [18289] <8> bpbkar: WRN - [/var] is in a different file system from [/]. Skipping
01:38:21.801 [18289] <4> bpbkar: INF - Processing /boot
01:38:21.815 [18289] <4> bpbkar: INF - Processing /apps
02:54:50.485 [18289] <16> bpbkar: ERR - Cannot write to STDOUT. Errno = 110: Connection timed out
02:54:50.485 [18289] <16> bpbkar: ERR - bpbkar FATAL exit status = 24: socket write failed

Please help me to resolve this
 

[Marianne]

Is multiple data streams enabled in policy attributes? If not please enable before next Full backup.

This will cause filesystems without problem to complete successfully.

Problem seems to be somewhere in /apps filesystem.

To troubleshoot, create a separate test policy for /apps and increase logging level to 5 so that we can see if problem is with specific file in /apps.

Another option: with logging level at 5, do the following from cmd on client:

/usr/openv/netbackup/bin/bpbkar -nocont -dt 0 -nofileinfo -nokeepalives /apps > /dev/null

Command will produce no output on the screen and you will be returned to the prompt.
You will see bpbkar in process table (ps -ef |grep bpbkar).

When done, please rename the bpbkar log to bpbkar.txt and post as attachment.

[V_P_S]

Hello Marianne,

Thanks for reply..

I created two test policy one  with only /apps mount point and other with rest of mount points. Backup is going good after doing this but once backup of /apps going to incomplete state i resumed it now it is going well.

I also increase verbose =5.

But i did not understand why the backup is going good after  initiated only with /apps and earlier it was failed.

Kindly clear my doubt.

[Marianne]

The reference to /apps may have been a 'red herring' - problem may well be with next filesystem... We should know for sure when you enable 'multiple data streams' in policy attributes. You will see a separate job for each filesystem. Please only do this when a full backup is due.

[V_P_S]

Hello Marianne.

Backup of /apps as well other mount points / , /boot , /logs completed successfully.

Only once backup of /apps and /logs going to incomplete state and i resumed it but finally backup completed successfully.

I did not understand why this happens..

Might be this happens only when all scheduled backups on weekend kickked off and then these backups failed with 24

[Marianne]

Have you checked bpbkar log yet?

What do you see in Job details for partial jobs?

[mph999 · Accepted solution]

"Might be this happens only when all scheduled backups on weekend kickked off and then these backups failed with 24"

... probably a congested network then ...

[contact2purohit]

I too have same Issue. Backup Failed after writing some data. Backup failed only one Single Drive that is G Drive. All other drives backup completed successfully.

Backup failed error code -24--

client having  windows 2003 and nbu version is  6.5.6

Master server having VERSION NetBackup 6.5.6

[V_P_S]

Hi All.

This issue has been resolved.

I just change the schedule for all backups that failed with 24 and its done now

[Marianne]

Changing schedule implies that Martin was right?

... probably a congested network then ...

Seems he deserves the Solution?

[V_P_S]

Thanks marianne.

Martin was right