Title: Bericht

I have seen similar problems when a client is at a down level version of NetBackup.  Not sure if that is the case here but in the cases I have seen it does not actually cause the backup to fail.  Note that none of these are actually errors.  The <2> indicates that this is an information message only.  I usually look for a <16> in the logs that indicates and error occurred.

 

Monte

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan (Contractor)
Sent: Monday, January 30, 2006 8:26 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Strange Error Message

 

I've got three error messages from this weekend's backups that I don't understand.  All three look very similar to this:

 

08:28:58.498 [2380.3176] <2> logparams: -i -c NT_PBIS3_CDEG -s FULL_WEEKLY_SUN_VLT -h PBIS3 -S semibkup1
08:28:58.498 [2380.3176] <2> OV_SendProcessInfo2BPCD: Information - thread access token does not exist
08:28:58.498 [2380.3176] <2> OV_SendProcessInfo2BPCD: Information - About to write 7706 bytes to named pipe
08:28:58.857 [2380.3176] <2> OV_SendProcessInfo2BPCD: Information - successfully wrote information to named pipe
08:28:58.857 [2380.3176] <2> ParseConfigExA: Unknown configuration option on line 76: RenameIfExists = 0
08:28:58.904 [2380.3176] <2> logconnections: BPRD CONNECT FROM 132.158.202.21.3781 TO 132.158.202.21.13720
08:28:58.920 [2380.3176] <2> ParseConfigExA: Unknown configuration option on line 76: RenameIfExists = 0
08:28:58.920 [2380.3176] <2> E:\VERITAS\NetBackup\bin\bpbackup.exe: sending admin backup request to bprd
08:28:58.920 [2380.3176] <2> E:\VERITAS\NetBackup\bin\bpbackup.exe: buf = root other PBIS3 semibkup1 semibkup1 NONE NT_PBIS3_CDEG FULL_WEEKLY_SUN_VLT 0  0 13 0 ENU ENU ENU ENU ENU 0 0 0 0 0

 

Any ideas what thread access token means?

 

Thanks!

 

-Jonathan

 

Reply via email to