Hi Richard, Thank you for info.
Well it seams that problem that is cousing this errors are orphaned objects in TSM tables that contain Windows SystemState objects, or problems with date/time stamps on system objects. A solution would be to run CLEAN BACKUPGROUPS and/or delete filesystems with those files and run backup after that. Anyway last night backup finished just fine on this node and i did not touch a thing!?! Cheers ______________________________________ Branko Stanic System Administrator Ured registrara za ratne zlocine i organizovani kriminal Sarajevo, Bosna i Hercegovina +387 33 707 111 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: 26. listopad 2005 12:48 To: [email protected] Subject: Re: [ADSM-L] HELP!!!! Take advantage of IBM's online information... Searching www.ibm.com for "Error 8 retrieving Backup Objects" turns up new, open APAR IC47577, which looks like a match. Review your dsmerror.log for further correlation. The best overall solution is to stop using Windows. :-) Richard Sims On Oct 26, 2005, at 5:11 AM, Branko Stanic wrote: > Hi all, > > This morning i noticed that our TSM failed to backup one of our nodes. > A look at the activity log revealed following errors: > > ANR9999D imgroup.c(1180): ThreadId<52> Error 8 retrieving Backup > Objects row for object 0.11583818 (SESSION: 2736) Oct 25, 2005 > 11:05:09 PM ANR9999D ThreadId<52> issued message 9999 from: (SESSION: > 2736) Oct 25, > 2005 11:05:10 PM > ANR9999D smnode.c(7343): ThreadId<52> Session 2736: Invalid Group Id > 0,11583818 for ADD function (SESSION: 2736) Oct 25, 2005 11:05:10 PM > ANR9999D ThreadId<52> issued message 9999 from: (SESSION: 2736) Oct > 25, > 2005 11:05:10 PM > ANR0403I Session 2736 ended for node ***** (WinNT). (SESSION: 2736) > > Also, activity log shows that node has sent objects to the server but > server reports that 0 objects has been backed up (probably as a result > of above error). > > We have never had failed node backup with this error as a reason. Also > at the same time, all other backups finished just fine.. > > While i was searching a adsm.org list for info on this error I > stumbled upon this discussion. > > I wonder if anyone has discovered what this error actually means?!? > > We are using Tivoli Storage Manager: 5.3.2 on Win 2003 server. > > Thank you very much...
