Re: upgrade from TSM 4.1.3 to TSM 5.1.5

2002-10-14 Thread [EMAIL PROTECTED]
I'm not too sure about the whole cleanup backupgroups myself. I understand that Tivoli has re-done the way the database handles Windows SYSTEM OBJECTS. So if you don't delete them, then the CLEANUP BACKUPGROUPS, as I understand, cleans that up for you Is this change in system object storage

Re: upgrade from TSM 4.1.3 to TSM 5.1.5

2002-10-14 Thread Daniel Sparrman
:Re: upgrade from TSM 4.1.3 to TSM 5.1.5 I'm not too sure about the whole cleanup backupgroups myself. I understand that Tivoli has re-done the way the database handles Windows SYSTEM OBJECTS. So if you don't delete them, then the CLEANUP BACKUPGROUPS, as I understand, cleans that up

Re: cleanup... (was: upgrade from TSM 4.1.3 to TSM 5.1.5)

2002-10-14 Thread Hans Hedlund
Sparrman [mailto:[EMAIL PROTECTED]] Sent: Monday, October 14, 2002 12:48 PM To: [EMAIL PROTECTED] Subject: Re: upgrade from TSM 4.1.3 to TSM 5.1.5 Hi The cleanup backupgroups is intended for one reason only, to fix a bug in prior versions. In version 4.2.2.X, there was a bug that had the effect

Re: upgrade from TSM 4.1.3 to TSM 5.1.5

2002-10-14 Thread Steve Roder
The cleanup backupgroups is intended for one reason only, to fix a bug in prior versions. In version 4.2.2.X, there was a bug that had the effect that system objects wasn't expired. What happens is that when you upgrade from version 4.2.2.X to version 5.1, the installation will be unable to

Re: cleanup... (was: upgrade from TSM 4.1.3 to TSM 5.1.5)

2002-10-14 Thread Daniel Sparrman
To: [EMAIL PROTECTED] cc: Subject:Re: cleanup... (was: upgrade from TSM 4.1.3 to TSM 5.1.5) Just to add to the total confusion, you can (will?) experience the same (similar?) problem in a 4.2.2.x server which I don't see properly clearified on ADSM-L

Re: cleanup... (was: upgrade from TSM 4.1.3 to TSM 5.1.5)

2002-10-14 Thread Steve Roder
PROTECTED] cc: Subject:Re: cleanup... (was: upgrade from TSM 4.1.3 to TSM 5.1.5) Just to add to the total confusion, you can (will?) experience the same (similar?) problem in a 4.2.2.x server which I don't see properly clearified on ADSM-L. Everyone's talking about

cleanup... (was: upgrade from TSM 4.1.3 to TSM 5.1.5)

2002-10-14 Thread Steve Roder
Sorry Hans if I was unclear, but for you that haven't upgraded to version 4.2, this problem doesn't exist. The system object bug was first introduced with version 4.2.2.0. For thoose of you using a lower version, my suggestion is to not upgrade to version 4.2.2, as you will also get this

upgrade from TSM 4.1.3 to TSM 5.1.5

2002-10-11 Thread [EMAIL PROTECTED]
Hi, I'll be upgrading soon from a TSM 4.1.3 server to TSM 5.1.5 server(if I can get the CD's from somewhere or download it) on Windows 2k. I've read the post of Johnn D. Tann where he states that it went fine. Here is a copy/paste of his message: Here's the conceptual overview of what we

Re: upgrade from TSM 4.1.3 to TSM 5.1.5

2002-10-11 Thread Johnn D. Tan
I'm getting confused about the cleanup backupgroups thing as there seem to be some problems with it. Why do you need to do a 'delete system object' prior to the upgrade and what is the command for it? I'm not too sure about the whole cleanup backupgroups myself. I understand that Tivoli has

Re: upgrade from TSM 4.1.3 to TSM 5.1.5

2002-10-11 Thread Prather, Wanda
Does anybody know if this also affects filespaces backed up with SUBFILEBACKUP YES? -Original Message- From: Johnn D. Tan [mailto:[EMAIL PROTECTED]] Sent: Friday, October 11, 2002 4:08 PM To: [EMAIL PROTECTED] Subject: Re: upgrade from TSM 4.1.3 to TSM 5.1.5 I'm getting confused