Error Code 27

You need to give us more info:

NBU version and patch level on these clients
Windows version on clients
Type of Backup - Filesystem or Database/Application?

All text in Details tab of failed job

We hardly ever see this error in NBU. 
Speak to server owners - chances are that someone is killing NBU processes in Task Manager.

Another possibility is AntiVirus software killing NBU processes. 
McAfee is known for doing this...

See explanation of Status 27 (also available through Troubleshooter button in Activity Monitor):

Message: child process killed by signal

Explanation: A child of the process that reported this error was terminated. This
error may occur if the backup job was terminated or another error terminated the
child process. This problem may also occur if a NetBackup process was terminated
through Task Manager or another utility.

Recommended Action: Check the NetBackup All Log Entries report for clues on
where and why the failure occurred. For detailed troubleshooting information,
create a debug log directory for the process that you think may have returned
this status code. Then, retry the operation and check the resulting debug log.

NBU Version 7.5, 

Client Windows 2003/2008

Filesystems Backups: ALL LOCAL DRIVES

**********************************************************************************************

05/23/2014 22:29:40 - Info nbjm (pid=5391) starting backup job (jobid=817007) for client PRDWSTBSM002, policy px_prd_WinFiles_msdp35d, schedule AcceleratorRescan
05/23/2014 22:29:40 - Info nbjm (pid=5391) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=817007, request id:{67159922-E304-11E3-B12B-0C9B6746D4EB})
05/23/2014 22:29:40 - requesting resource STU_PX_DD_pxddeit_sqlserver
05/23/2014 22:29:40 - requesting resource prdbkme001.unix.gsm1900.org.NBU_CLIENT.MAXJOBS.PRDWSTBSM002
05/23/2014 22:29:40 - requesting resource prdbkme001.unix.gsm1900.org.NBU_POLICY.MAXJOBS.px_prd_WinFiles_msdp35d
05/23/2014 22:29:41 - granted resource  prdbkme001.unix.gsm1900.org.NBU_CLIENT.MAXJOBS.PRDWSTBSM002
05/23/2014 22:29:41 - granted resource  prdbkme001.unix.gsm1900.org.NBU_POLICY.MAXJOBS.px_prd_WinFiles_msdp35d
05/23/2014 22:29:41 - granted resource  MediaID=@aaaa5;DiskVolume=lsu_sqlserver;DiskPool=DP_PX_DD_pxddeit_sqlserver;Path=lsu_sqlserver;StorageServer=pxddeit.unix.gsm1900.org;MediaServer=prdbkse001
05/23/2014 22:29:41 - granted resource  STU_PX_DD_pxddeit_sqlserver
05/23/2014 22:29:41 - estimated 0 kbytes needed
05/23/2014 22:29:41 - Info nbjm (pid=5391) started backup (backupid=PRDWSTBSM002_1400909381) job for client PRDWSTBSM002, policy px_prd_WinFiles_msdp35d, schedule AcceleratorRescan on storage unit STU_PX_DD_pxddeit_sqlserver
05/23/2014 22:29:42 - started process bpbrm (pid=2424)
05/23/2014 22:29:44 - connecting
05/23/2014 22:29:45 - connected; connect time: 0:00:00
05/23/2014 22:29:49 - begin writing
05/23/2014 22:30:03 - Info bpbrm (pid=2424) PRDWSTBSM002 is the host to backup data from
05/23/2014 22:30:03 - Info bpbrm (pid=2424) reading file list from client
05/23/2014 22:30:03 - Info bpbrm (pid=2424) accelerator enabled
05/23/2014 22:30:03 - Info bpbrm (pid=2424) Accelerator enabled backup with checksum based change detection needs to read each file and calculate the checksum, and will have longer backup time.
05/23/2014 22:30:04 - Info bpbrm (pid=2424) There is no complete backup image match with track journal, a regular full backup will be performed.
05/23/2014 22:30:05 - Info bpbrm (pid=2424) starting bpbkar on client
05/23/2014 22:30:05 - Info bpbkar (pid=6784) Backup started
05/23/2014 22:30:05 - Info bpbrm (pid=2424) bptm pid: 2433
05/23/2014 22:30:06 - Info bptm (pid=2433) start
05/23/2014 22:30:06 - Info bptm (pid=2433) using 1048576 data buffer size
05/23/2014 22:30:06 - Info bptm (pid=2433) setting receive network buffer to 524288 bytes
05/23/2014 22:30:06 - Info bptm (pid=2433) using 64 data buffers
05/23/2014 22:30:08 - Info bptm (pid=2433) start backup
05/23/2014 22:30:09 - Info bptm (pid=2433) backup child process is pid 2483
05/23/2014 22:30:30 - Info bpbkar (pid=6784) change journal NOT enabled for <C:\>
05/23/2014 22:31:17 - end writing; write time: 0:01:28
05/23/2014 22:31:36 - Error bpbrm (pid=2424) child killed by signal (139)
05/23/2014 22:31:36 - Info bpbkar (pid=6784) done. status: 27: child process killed by signal
05/23/2014 22:31:37 - Info bpbrm (pid=2893) Starting delete snapshot processing
05/23/2014 22:31:37 - Info bpfis (pid=0) Snapshot will not be deleted
05/23/2014 22:31:39 - Info bpfis (pid=6204) Backup started
05/23/2014 22:31:40 - Error bpbrm (pid=2893) from client PRDWSTBSM002: Delete bpfis state from prdbkme001.unix.gsm1900.org failed. status = 71
05/23/2014 22:31:40 - Info bpfis (pid=6204) done. status: 0
05/23/2014 22:31:40 - Info bpfis (pid=0) done. status: 0: the requested operation was successfully completed
05/23/2014 22:31:41 - Error bptm (pid=2483) system call failed - Connection reset by peer (at child.c.1298)
05/23/2014 22:31:41 - Error bptm (pid=2483) unable to perform read from client socket, connection may have been broken
child process killed by signal  (27)

*****************************************************************

05/23/2014 01:12:40 - Info nbjm (pid=5391) starting backup job (jobid=801320) for client PRDWSTBSM002, policy px_prd_WinFiles_msdp35d, schedule Cumulative
05/23/2014 01:12:40 - Info nbjm (pid=5391) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=801320, request id:{0201417E-E252-11E3-B658-40F5DA0A3CFB})
05/23/2014 01:12:40 - requesting resource STU_PX_DD_pxddeit_sqlserver
05/23/2014 01:12:40 - requesting resource prdbkme001.unix.gsm1900.org.NBU_CLIENT.MAXJOBS.PRDWSTBSM002
05/23/2014 01:12:40 - requesting resource prdbkme001.unix.gsm1900.org.NBU_POLICY.MAXJOBS.px_prd_WinFiles_msdp35d
05/23/2014 01:12:40 - granted resource  prdbkme001.unix.gsm1900.org.NBU_CLIENT.MAXJOBS.PRDWSTBSM002
05/23/2014 01:12:40 - granted resource  prdbkme001.unix.gsm1900.org.NBU_POLICY.MAXJOBS.px_prd_WinFiles_msdp35d
05/23/2014 01:12:40 - granted resource  MediaID=@aaaa5;DiskVolume=lsu_sqlserver;DiskPool=DP_PX_DD_pxddeit_sqlserver;Path=lsu_sqlserver;StorageServer=pxddeit.unix.gsm1900.org;MediaServer=prdasbkse002
05/23/2014 01:12:40 - granted resource  STU_PX_DD_pxddeit_sqlserver
05/23/2014 01:12:41 - estimated 0 kbytes needed
05/23/2014 01:12:41 - Info nbjm (pid=5391) started backup (backupid=PRDWSTBSM002_1400832761) job for client PRDWSTBSM002, policy px_prd_WinFiles_msdp35d, schedule Cumulative on storage unit STU_PX_DD_pxddeit_sqlserver
05/23/2014 01:12:42 - started process bpbrm (pid=13100)
05/23/2014 01:12:47 - Info bpbrm (pid=13100) PRDWSTBSM002 is the host to backup data from
05/23/2014 01:12:47 - Info bpbrm (pid=13100) reading file list from client
05/23/2014 01:12:48 - Info bpbrm (pid=13100) accelerator enabled
05/23/2014 01:12:49 - connecting
05/23/2014 01:12:52 - Info bpbrm (pid=13100) starting bpbkar32 on client
05/23/2014 01:12:52 - connected; connect time: 0:00:00
05/23/2014 01:12:53 - Info bpbkar32 (pid=9016) Backup started
05/23/2014 01:12:53 - Info bptm (pid=15976) start
05/23/2014 01:12:53 - Info bptm (pid=15976) using 1048576 data buffer size
05/23/2014 01:12:53 - Info bptm (pid=15976) setting receive network buffer to 262144 bytes
05/23/2014 01:12:53 - Info bptm (pid=15976) using 64 data buffers
05/23/2014 01:13:20 - Info bpbkar32 (pid=9016) change journal NOT enabled for <C:\>
05/23/2014 01:13:21 - Info bptm (pid=15976) start backup
05/23/2014 01:13:39 - Info bptm (pid=15976) backup child process is pid 12536.14784
05/23/2014 01:13:39 - Info bptm (pid=12536) start
05/23/2014 01:13:39 - begin writing
05/23/2014 01:26:05 - Info bpbkar32 (pid=9016) done. status: 27: child process killed by signal
05/23/2014 01:26:06 - end writing; write time: 0:12:27
05/23/2014 01:36:13 - Info bpbrm (pid=20152) PRDWSTBSM002 is the host to backup data from
05/23/2014 01:36:13 - Info bpbrm (pid=20152) reading file list from client
child process killed by signal  (27)

Can we disable accelerator and then try a backup or May be instead of ALL LOCAL DRIVES have a particular drive as a source ?

DeepS

Is status 27 seen for specific clients?
Or for specific media server?
Or just related to accelerator enabled policies?

You need these logs to troubleshoot:

On media server: bptm and bpbrm
On client: bpbkar and bpfis.

If all backups on one specific media server is failing, it could be caused by corrupt bptm binary.
See: http://www.symantec.com/docs/TECH50482

I seem to be stuck with the same issue - Called logged currently - Troubleshooting...

The issue seems to be with 'All Local Drives'

When a backup, with Accelerator, of a specific drive/directory is performed, it completes successfully.

This anomoly, IMO, seems to be from the last few Microsoft patch updates, incl heart bleed update.

I have multiple Windows Media servers, so i really dont think corrupt bptm binary is the issue - I had refreshed the installation files on all of them. The issue also appears when backing up a Unix client -

I do not have a Unix media server to test the failing clients - could someone who has this issue kindly test.

Until I can get some feedback from my logged call, I have removed accelerator and doing traditional backups.

Hopefully an answer this week when I get back from leave.

Curious to know the outcome of your Support case, Mo.

Seems the original poster has lost interest....

I had a similar issue with accelerator enabled backups.  Upgrading from 7.5.0.6 to 7.6.0.2 has corrected my status 27 codes. 

As David noted, upgrading to 7.6.0.2 does resolve the issue -

However, when you have and environment that cannot upgrade due to OS SCL shortcomings for the Media server (32Bit), the problem still persists...

Upgrading the client only to 7.6.0.2 does not work when media server is still on 7.5.0.6.

I would like to test Bkp2020' solution this week -

Would like to know if NB was

a)   completely uninstalled, rebooted and then re-installed or

b)   just uninstalled and re-installed

I had tried option 'b' which made no difference.

@Marrianne, I had closed the call in the interim due to my time restrictions and 'kinda' accepted the solution of upgrding to 7.6.0.2 which is in due course.