> Actually, this problem occurs with both unicode and nonunicode > SYSTEM OBJECT filesystems. If you delete the nonunicode filesystem > it will rebackup as unicode. The new unicode SYSTEM OBJECT > filesystem will continue accumulate extra versions as well. > > I could run CLEANUP BACKUPGROUPS with an earlier v5 version, > but it didn't work (I ran it, but then ran it again and it > found more errors). The CLEANUP didn't work (got the loop problem) > under v5.1.1.6, but then the AUDITDB didn't work! This is what I'm writing up...
TSM Server 4.2.1.9 on AIX 4.3.3 I've been toying with upgrading my production server to TSM V5 but I'm wondering if there is a recommended patch level that is worth my effort. I feel pretty stable where I am, and remembering what I went through after upgrading to 4.2 with crashes I'm not is a hurry to jump on to V5 yet. I'm not sure if I've ever seen anyone who seems to be happy with any level yet, even 5.1.1.6 which seems to still have problems. Inputs? Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
