>On 18-Nov-02 Charles F. Fisher wrote:
>> The site I'm at is getting ready to upgrade to 4.2.3. One reason is to be
>> able to run CLEANUP BACKUPGROUPS on the database; are there any special
>> actions or precautions that should be taken before doing so (once the
>> upgrade is in place)?
>
>We did
your shop.
Cinda Mullen <[EMAIL PROTECTED]> on 12/18/2002 05:25:54 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: John Naylor/HAV/SSE)
Subject: Re: Cleanup Backupgroups and Expiration Processing
yeah, we hav
AIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject: Re: Cleanup Backupgroups and Expiration Processing
yeah, we have the problem big timewe think it started with 4.1.6
but, were not able to pin point it
>>> [EMAIL PROTECTED] 12/18/02 10:53AM &g
yeah, we have the problem big timewe think it started with 4.1.6
but, were not able to pin point it
>>> [EMAIL PROTECTED] 12/18/02 10:53AM >>>
Are you sure that you need to run cleanup backupgroups.
I did not think this problem impacted os390 TSM servers.
I am on 4.2.2 and I do not think I
Top of message
>>--> 12-18-02 08:59 S.SHEPPARD (SHS)Re: Cleanup Backupgroups
We also just went from 4.2.0 to 4.2.3 on OS/390 2.10. Ran Cleanup on
both of our servers. It ran for maybe 10 minutes and finished with
Are you sure that you need to run cleanup backupgroups.
I did not think this problem impacted os390 TSM servers.
I am on 4.2.2 and I do not think I kave a problem with this.
Cinda Mullen <[EMAIL PROTECTED]> on 12/18/2002 04:36:26 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECT
Top of message
>>--> 11-21-02 14:07 S.SHEPPARD (SHS)Re: Cleanup backupgroups,
Matt: I second Bill's comment about the clarity of the history of this
problem. I have also been running the 4.2.2.0 OS/390 server for 6
At 14:11 -0800 11/21/02, Sam Sheppard wrote:
I believe that
the OS/390 4.2.2.0 server probably just doesn't have this problem. You
should be able to verify that with support.
I guess I should have clarified that we're running the TSM server on
Solaris. My signature is misleading. I'm an OS/390
ilto:[EMAIL PROTECTED]]
> Sent: Thursday, November 21, 2002 11:41 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Cleanup backupgroups, system objects
>
> Matt - I recently did the same server upgrade and got the same
> result doing cleanup backupgroups -- 0 anything deleted.
>
> I have n
Matt - I recently did the same server upgrade and got the same
result doing cleanup backupgroups -- 0 anything deleted.
I have never been clear on the history of the problem, that is
what server levels caused it. So I have to wonder if the cleanup
command still has a bug in it for the OS/390 serv
Matt,
I had your problem often in the last year!
>From time to time a new update of the servercode expired the old system
objects (only happened on windows 2000 servers with active directory!!!)
properly but then they started to grow again.
The first server I found that really solved the Problem i
On 18-Nov-02 Charles F. Fisher wrote:
> The site I'm at is getting ready to upgrade to 4.2.3. One reason is to be
> able to run CLEANUP BACKUPGROUPS on the database; are there any special
> actions or precautions that should be taken before doing so (once the
> upgrade is in place)?
We didn't and
JFYI, I ran this successfully today on an ITSM 5.1.5.1 [AIX] server.
Mahesh
>>> [EMAIL PROTECTED] 09/25/02 11:15AM >>>
I am interested in reading your write-up. Is it complete, and if so,
under
what subject? If not, do you have an estimate on when?
Thanks for doing this Gretchen,
Todd
|-
Zoltan,
There will be a lag for MVS...usually 2 weeks.
Sam.
- Original Message -
From: "Zoltan Forray/AC/VCU" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 15, 2002 12:43 PM
Subject: Re: CLEANUP BACKUPGROUPS SYSTEM OBJECT
> I keep seeing
I keep seeing references to 4.2.3 being released yet I can't find
it..At least not for OS390 - z/OS based servers ???
Can someone tell me if they have found these updates ?
TAZ <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10/15/2002 02:55 PM
Please respo
SERVER
Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180
-Original Message-
From: Tab Trepagnier [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 15, 2002 1:33 AM
To: [EMAIL PROTECTED]
Subject: Re: cleanup backupgroups
The one thing I've missed in this discu
The one thing I've missed in this discussion thread is whether the version
4.2.2 that introduced the bug is the server or the client version.
I am still running server version 4.1.5.0 on AIX, but my newest file
servers are running version 4.2.2.0 clients. Those nodes are Windows 2000
Server mach
Naptheon Inc.
757-688-8180
-Original Message-
From: Matt Simpson [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 14, 2002 10:53 AM
To: [EMAIL PROTECTED]
Subject: Re: cleanup backupgroups
I'm a newcomer to this list, and a newcomer to TSM. So there's a very good
chance that I
If the command as follows does not work, you need to call support:
cleanup backupgroups
Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180
-Original Message-
From: Anderson, Michael - HMIS [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 14, 2002 4:08 PM
To: [EMAIL PROTE
does that expiration problem with System objects exist on 4.2.1.9?
Joseph Dawes
I/T Infrasctructure - Unix Technical Support
Chubb & Son, a Division of Federal Insurance Company
15 MountainView Road
Warren,New Jersey 07059
Office:908.903.3890
> Matt,
>
> you got it right - there is a problem with SystemObject expiration
> introduced in v4.2.2 and you have to run CLEANUP BACKUPGROUP to prevent
> enourmous high space usage in DB and storage pool. This applies if you
> have many W2k nodes backing up to TSM. It would last until you upgrade
AIL PROTECTED]>
14.10.2002 17:52
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: cleanup backupgroups
I'm a newcomer to this list, and a newcomer to TSM. So there's a very
good chance that I'm totall
I'm a newcomer to this list, and a newcomer to TSM. So there's a very
good chance that I'm totally confused. I'm catching the tail end of
this cleanup backupgroups discussion, and I need some clarification.
I think I'm reading that there's a problem in 4.2.2.x versions of TSM
which causes SYSTEM
23 matches
Mail list logo
