As mentioned, NpPeek messages in the b/a errorlog indicates that the b/a client didn't receive an expected response from the journal daemon, and if the backup didn't complete it probably means that contact with the journal daemon was lost for some reason (and possibly that the journal daemon process ended).
Did the Journal Daemon errorlog (jbberror.log) indicate anything unusual ? If you can recreate this problem email me directly and I'll try to work thru it with you. Regards, Pete Pete Tanenhaus Tivoli Storage Solutions Software Development email: [EMAIL PROTECTED] tieline: 320.8778, external: 607.754.4213 "Those who refuse to challenge authority are condemned to conform to it" ---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 02/13/2003 03:17 PM --------------------------- chris rees <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/13/2003 06:06:59 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: NpPeek : no data with journaling Hi All Following on from the previous mails regarding journaling and pipes, thanks Pete, I am getting the following scenario on a win2k client, TSM client 5.1.5.2 The incremental starts and uses the journal. I then get loads of NpPeek : No data messages and the backup does not finish. The schedule has a status of missed but in the dsmsched.log the last lines are : 11-02-2003 23:46:50 --- SCHEDULEREC OBJECT BEGIN DAILY_INCR 11-02-2003 11-02-2003 23:46:51 Using journal for '\\etvdcrsfcs01\i$' Any ideas as to what I can do to stop this happening? What is the best way to recover from this? Should I stop journal service, start journal service and run a manual backup.? Thanks alot Chris _________________________________________________________________ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus
