8&lang=en
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Alexander Lazarevich
Sent: Tuesday, September 13, 2005 2:39 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: 5.1.9 to 5.3.1 migrate install - Cleanup Backupgroups?
From: ADSM: Dist Stor Manager
DSM-L] 5.1.9 to 5.3.1 migrate install - Cleanup
Backupgroups?
By the way, I have another question, I am looking over my steps for a
migrate install from 5.1.9 to 5.3.1 in win2K server. I've got everything
worked out, except I don't understand how the TSM device drivers are
going to be inst
lexander Lazarevich
Sent: Tuesday, September 13, 2005 2:39 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: 5.1.9 to 5.3.1 migrate install - Cleanup Backupgroups?
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
> Behalf Of Alexander Lazarevich
>> Excellent Information, thanks Ruth.
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Alexander Lazarevich
Excellent Information, thanks Ruth. However, I do have one question: in
both the install guide and the TSM server upgrade tech note (1177863),
they say to run the command "Cleanup Backupgroups"
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Alexander Lazarevich
>Excellent Information, thanks Ruth. However, I do have one question: in
>both the install guide and the TSM server upgrade tech note (1177863),
>they say to run the command "Cleanup Backupgrou
Excellent Information, thanks Ruth. However, I do have one question: in
both the install guide and the TSM server upgrade tech note (1177863),
they say to run the command "Cleanup Backupgroups" on TSM 5.1 before the
upgrade to 5.3, especially "if there are any Windows 2000 or high
I am in the process of upgrading my TSM servers that run Version 5,
Release 1, Level 7.0 on ZOS Version 1 Release 4.
Do I need to upgrade my TSM 5.1 to a more current Level before I run the
CLEANUP BACKUPGROUPS process?
The information transmitted is intended only for the person or entity to
Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Antw: Please help: Question concerning cleanup backupgroups
Is your log running in roll-foward-mode???
if yes turn it to normal (only Pending transactions will be loged),
that shoud do it.
when you restart the process, it has to do all work again, i think
... 8)
cu
Bernd Wiedmann
Hi !
Yes our log is in roll-forward-mode. So I turn it to normal and now the log
is constant. The process 'cleanup backupgroups' runs now for 5 hours and no
more does not seem to stop (our TSM-Database is 12GB). I'm waiting now.
Best regards,
Frank Mueller
Is your log running in roll-foward-mode???
if yes turn it to normal (only Pending transactions will be loged),
that shoud do it.
when you restart the process, it has to do all work again, i think
... 8)
cu
Bernd Wiedmann
Hi *,
I start the cleanup backupgroups process (AIX 4.3.3 and TSM Version is
4.2.4). The process runs for a long time and our TSM-log is now full.
What happens when I cancel the process? Must the process by restart do the
complett work again or is the part up to the stop o.k.?
or is the part up
Hi *,
our TSM Server runs on AIX 4.3.3_ML11 and TSM-Server-Version 4.2.4.0.
Now I want to start cleanup backupgroups before I migrate to TSM 5.X.X.X
Concerning this I have two questions:
- What makes the 'cleanup backupgroups' exact?
- How largely do I have to make the log, so that t
Hi *,
I need your help!!!
We have 2 TSM-server, both on AIX 4.3.3. The first Server is on TSM V
4.2.2.6 and second Server is on TSM V 4.2.4.0. On both server are librarys
attached.
Three steps to backup the clients.
1. backup the client to SSA-disks on the first server
2. migrate this data to the
>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
>
BJECT filespace back and use it for a restore.
-Original Message-
From: Dameon White [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 9:05 AM
To: [EMAIL PROTECTED]
Subject: System Objects and Cleanup Backupgroups
My TSM server is at 4.2.3.0 and we want to upgrade to
5.1.x o
> Can I delete the SYSTEM OBJECT filespaces
> all together and gamble that I won't have to restore the
> registry that day? Will deleting the "good" system
> objects help with the orphans?
There is a less draconian version of this strategy that some
sites have used successfully. Execute 'rename f
n code 11.
-Original Message-
From: Kyle Payne [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 9:12 AM
To: [EMAIL PROTECTED]
Subject: Re: System Objects and Cleanup Backupgroups
Did you run help clean or help cleanup?
Kyle
-Original Message-
From: ADSM: Dist Stor M
Did you run help clean or help cleanup?
Kyle
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Hart, Charles
Sent: Thursday, February 13, 2003 8:31 AM
To: [EMAIL PROTECTED]
Subject: Re: System Objects and Cleanup Backupgroups
Dumb question, what
mind -- it's backed up on tape somewhere." - ???
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Hart, Charles
Sent: Thursday, February 13, 2003 9:31 AM
To: [EMAIL PROTECTED]
Subject: Re: System Objects and Cleanup Backupgroups
Dumb question, what version is
Another dumb question...what is "Orphaned system objects"
Regards
Niklas Lunström
Swedbank
-Original Message-
From: Hart, Charles [mailto:[EMAIL PROTECTED]]
Sent: den 13 februari 2003 15:31
To: [EMAIL PROTECTED]
Subject: Re: System Objects and Cleanup Backupgroups
Dumb ques
Dumb question, what version is the CLEANUP BACKUPGROUPS in? I ask because there is no
output from "h CLEAN BACKUPGROUPS" on 4.1 or 5.1.5
Thank You!
-Original Message-
From: Dameon White [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 8:05 AM
To: [EMAIL PROTECTE
My TSM server is at 4.2.3.0 and we want to upgrade to
5.1.x of TSM. But we have over 50 million orphaned SYSTEM
OBJECTS that we have been trying to delete via the CLEANUP
BACKUPGROUPS command. We tried to upgrade with the
orphans and after 72 hours we backed out. Now we are
tryng to delete the
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
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 Manag
TSMers...
We are running OS390 2.10 with a 4.2.3 TSM Server.
We upgraded to 4.2.3 in November and have been running cleanup
backupgroups off and on since that time to try to get the system object
issue resolved. (Sure wish there was a duration parameter for the
cleanup so, we could stop it
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
On TSM 5.1.5.2 AIX 4.3.3
I just ran this and here's the report.
11/21/02 12:07:19 ANR4802I CLEANUP BACKUPGROUPS evaluated 7856 groups
and deleted 3 orphan groups with 1185 group members deleted with completion
state 'FINISHED'.
11/21/02 12:07:19 ANR0987I Process 1
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
7:41 PM
Subject: Cleanup backupgroups, system objects
> We assumed we had the dreaded "system objects" problem because we
> were running 4.2.2.0, we have a bunch of Windows clients, and our
> database was growing at a rate that we didn't like.
>
> So a couple of days ago, w
We assumed we had the dreaded "system objects" problem because we
were running 4.2.2.0, we have a bunch of Windows clients, and our
database was growing at a rate that we didn't like.
So a couple of days ago, we upgraded to 4.2.3, and ran CLEANUP BACKUPGROUPS.
It didn'
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 p
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)?
Chuck Fisher
[EMAIL PROTECTED]
DE option) will let you know if you have that problem.
Also,
>did you run the command CLEANUP BACKUPGROUPS? For me, on 5.1.1.4 it
ran
but
>never cleaned everything up and it wouldn't run on 5.1.1.6. I finally
had
>to do an AUDITDB FIX=YES.
Actually, this problem occurs with bot
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
10/15/2002 02:55 PM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:CLEANUP BACKUPGROUPS SYSTEM OBJECT
TSM Community,
I was able to obtain more detailed information regarding System Object
Filespace
issue and the Cleanup
TSM Community,
I was able to obtain more detailed information regarding System Object Filespace
issue and the Cleanup Backupgroups utility, compliments of Tivoli.
4.2.3 was released 10/14/2002. This official PTF level resolves issues
with expiration of file groups which are typically used for
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
Is there any special syntax for the cleanup backupgroups question. I
upgraded to 4.2.2.12 and tried to run the
cleanup command and received the following error:
Anrd tb.c(1167) threadid(31) invalid encoded data length
Anr0104e imutil.c(8363) Error deleting
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
#x27;s a problem in 4.2.2.x versions of TSM
> which causes SYSTEM OBJECTS not to expire, requiring the CLEANUP
> BACKUPGROUPS. I've seen some messages that indicate the cleanup
> needs to run after conversion to 5.1.
>
> We're running TSM 4.2.2.0 on Solaris. We hope to upg
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.
]
Subject: Re: 5.1.1.6 Upgrade (cleanup backupgroups)
Hmm, I tried running the "cleanup backupgroups" command and got the
result:
ANR0106E imutil.c(8262): Unexpected error 0 fetching row in table
"Object.Ids"
Seems to be a known problem. (and I'm running 4.2.2.12)
Su
/tivoli-storage-management/patches/server/
NT/4.2.2.13/ , the AIX version is there also.
Haven't tried CLEANUP BACKUPGROUPS and I make no claims to this version,
only sharing my experiences.
Mark B.
-Original Message-
From: Seay, Paul [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 07, 2
Not 4.2.1.12, 4.2.2.12 is stable. There is one little piece that CLEANUP
BACKUPGROUPS has a problem with. They have a fix for that coming out soon.
You may not hit that problem, so put in 4.2.2.12 and run the CLEANUP
BACKUPGROUPS. I had to put on a special 4.2.2.13 version (not available on
Hmm, I tried running the "cleanup backupgroups" command and got the
result:
ANR0106E imutil.c(8262): Unexpected error 0 fetching row in table
"Object.Ids"
Seems to be a known problem. (and I'm running 4.2.2.12)
Suad
--
APAR= IC34375 SER=
>
> thanks
> lisa
>
>
>
> "Seay, Paul"
> EON.COM> cc:
> Sent by: Subject: Re: 5.1.1.6 Upgrade (cleanup
>backupgroups)
> "ADSM: Dist
>
Sent by: Subject: Re: 5.1.1.6 Upgrade (cleanup
backupgroups)
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>
10/02/2002
07:29 PM
Hi,
recently, on the list we discussed a problem with cleanup backupgroups
command on 5.1.1.6. Symptoms: cleanup backupgroups ends with return code 4.
In the actlog there are the following 3 messages:
ANR2017I Administrator GERHARD issued command: CLEANUP
BACKUPGROUPS
ANRD imutil.c(6663
OK, I ran cleanup backupgroups for a week and it returned 1.5M pages to my
database. However, that was not continuous time. I would run it for
several hours and cancel it as needed to prevent conflicts with other stuff.
My experience was it literally shuts down backup stg and database backups
I ran into this in my conversion, too:
>ANRD imutil.c(6663): ThreadId<67> Failure deleting
> member 0 585368742 for group 1637 3 - encountered
> repeatedly in loop.
It took an audit (fix=yes detail=yes) to correct. If you
try to run expire invent, you will notice that it has a
tough time end
58 matches
Mail list logo
