Status 63 - process killed by signal

[Dan_Ryan_2]

I'm not sure what is going on with the clients, but I thought I would throw this out there and see if anyone has seen this before.  We migrated some VM clients to a new VM farm yesterday.  The clients were able to back up with no problems prior to migration.  There was a chipset change between the VM Farms as well as going from physical ESX servers to HP Blades.  The clients are Windows 2003 SP2, NBU 6.5.3.  Our environment is master Windows 2003 SP2, NBU 6.5.3.1 and the media servers are RHES 5.2 64bit 6.5.3.  What we don't understand is the garble that is coming from the client.  I've disabled VSP and VSS from backups, just to ensure that no open file agents are impacting the backups.  From what I can tell though we either have a chipset problem or some sort of network error that is causing this.  Here is the log from clientx:

4/15/2009 9:30:36 AM - requesting resource EDL_DDC
4/15/2009 9:30:36 AM - requesting resource cinbkp01.NBU_CLIENT.MAXJOBS.clientx
4/15/2009 9:30:36 AM - requesting resource cinbkp01.NBU_POLICY.MAXJOBS.V_NP_D_Win_03
4/15/2009 9:30:36 AM - granted resource cinbkp01.NBU_CLIENT.MAXJOBS.clientx
4/15/2009 9:30:36 AM - granted resource cinbkp01.NBU_POLICY.MAXJOBS.V_NP_D_Win_03
4/15/2009 9:30:36 AM - granted resource V10017
4/15/2009 9:30:36 AM - granted resource EDL0.IBM.ULTR.TD3.006
4/15/2009 9:30:36 AM - granted resource media08-hcart3-robot-tld-3
4/15/2009 9:30:38 AM - estimated 9179991 kbytes needed
4/15/2009 9:30:38 AM - started process bpbrm (24021)
4/15/2009 9:30:46 AM - mounting V10017
4/15/2009 9:30:48 AM - connecting
4/15/2009 9:30:49 AM - connected; connect time: 00:00:01
4/15/2009 9:30:55 AM - mounted; mount time: 00:00:09
4/15/2009 9:30:55 AM - positioning V10017 to file 1012
4/15/2009 9:30:55 AM - positioned V10017; position time: 00:00:00
4/15/2009 9:30:55 AM - begin writing
4/15/2009 9:31:48 AM - Error bpbrm(pid=24033) from client clientx: aced Encrypted File.txt.lnk      
4/15/2009 9:31:49 AM - Error bpbrm(pid=24033) from client clientx:         
4/15/2009 9:31:50 AM - Error bpbrm(pid=24033) from client clientx: 2 *        
4/15/2009 9:31:51 AM - Error bpbrm(pid=24033) from client clientx: 2 €pl        
4/15/2009 9:31:53 AM - Error bpbrm(pid=24033) from client clientx: 2l        
4/15/2009 9:31:54 AM - Error bpbrm(pid=24033) from client clientx: 2É5œÑÝŠ¨c§ë
€ú梵        
4/15/2009 9:31:55 AM - Error bpbrm(pid=24033) from client clientx:         
4/15/2009 9:31:56 AM - Error bpbrm(pid=24033) from client clientx: curity Config/v2.0.50727.42/       
4/15/2009 9:31:57 AM - Error bpbrm(pid=24033) from client clientx:         
4/15/2009 9:31:58 AM - Error bpbrm(pid=24033) from client clientx:         
4/15/2009 9:31:59 AM - Error bpbrm(pid=24033) from client clientx: age-Configuration.bmp        
4/15/2009 9:32:00 AM - Error bpbrm(pid=24033) from client clientx:         
4/15/2009 9:32:01 AM - Error bpbrm(pid=24033) from client clientx:         
4/15/2009 9:32:02 AM - Error bpbrm(pid=24033) from client clientx: 2 *        
4/15/2009 9:32:03 AM - Error bpbrm(pid=24033) from client clientx: 2 €pl        
4/15/2009 9:32:04 AM - Error bpbrm(pid=24033) from client clientx: 2l        
4/15/2009 9:32:05 AM - Error bpbrm(pid=24033) from client clientx: 2É5œà¹3Û1s„j        
4/15/2009 9:32:06 AM - Error bpbrm(pid=24033) from client clientx:         
4/15/2009 9:32:07 AM - Error bpbrm(pid=24033) from client clientx:         
4/15/2009 9:32:08 AM - Error bpbrm(pid=24033) from client clientx: ayer/        
4/15/2009 9:32:09 AM - Error bpbrm(pid=24033) from client clientx: ptions
TempPE/        
4/15/2009 9:32:10 AM - Error bpbrm(pid=24033) from client clientx: 8U/        
4/15/2009 9:32:11 AM - Error bpbrm(pid=24033) from client clientx: f        
4/15/2009 9:32:12 AM - Error bpbrm(pid=24033) from client clientx: 
<Truncated>
4/15/2009 9:35:11 AM - Error bpbrm(pid=24033) from client cvgapp77q.ga.afginc.com: 2        
4/15/2009 9:35:12 AM - Error bpbrm(pid=24033) from client cvgapp77q.ga.afginc.com: 0
Ò“í—Úö€‚5?        
4/15/2009 9:35:13 AM - Error bpbrm(pid=24033) from client cvgapp77q.ga.afginc.com:         
4/15/2009 9:35:14 AM - Error bpbrm(pid=24033) from client cvgapp77q.ga.afginc.com:         
4/15/2009 9:35:15 AM - Error bpbrm(pid=24033) from client cvgapp77q.ga.afginc.com:         
4/15/2009 9:35:18 AM - end writing; write time: 00:04:23
process was killed by a signal(63)

We've opened a case, but wanted to see if anyone has seen this before.