It is AIX 4.3.3
-Original Message-
From: Joshua Bassi [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 24, 2002 10:13 AM
To: [EMAIL PROTECTED]
Subject:Re: TSM upgrade from 3.7 to 5.1
Sachin,
What platform are you on?
The upgrade procedure varies based upon the
I assume the tapes from your onsite and offsite pool have also been taken???
Otherwise just mark the tape destroyed and restore it, all the data will
come back from the onsite or offsite copy pool.
..Rikk
-Original Message-
From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]]
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
More importantly, can some of the windows guys amongst you advise
how to do something similar for NT4 and Win2K? Preferably without
having any special services running and without having any
reskits installed.
set | grep
Enviro:
TSM client 4.2.1.25 running on H50 AIX 4.3.3.10.
I get this 1 client dsmerror, no other error message of any kind, except
this one:
09/23/02 11:05:19 TCP/IP received rc 25 trying to accept connection from
server.
I don't have any other kinds of client errors with this client in the
Abdulaziz,
Officially TSM doesn't support MetaFrame. I found the main problem to be the remapping
of the drives, TSM seems to be hard coded to backup system objects from drive c:. If i
don't remap drives on MetaFrame, TSM seems to work fine.
john
[EMAIL PROTECTED] 09/24/02 12:05AM
Date:
test
Hi there, all you tsm-ers!
Maybe someone has a few hints for me:
Planning to upgrade TSM-Server from 4.2.1.11 to 5.1.
Are there any known problems?
Next thing is Data Warehouse runs DB2 UDB EEEin an SP-Environment, will be upgraded to
DB2 7xx. on a new S85 machine with FastT FibreChannel, all
I am using 4.2.2.0 client to backup W2K Citrix servers. System doesn't
have a C drive. Has I, J K. Installed TSM on I drive. Remember to
set
correct Drive paths for logs etc. as they will default to C.
Backs up System Objects o.k.
David Longo
[EMAIL PROTECTED] 09/23/02 03:13AM
Hi guys,
i
I'm on 5.1.1.4 on AIX 4.3.3. The biggest headaches with expiration are
resolved, but it appears that once MAXSESS is hit, it is never decremented
until the server is recycled. I could go back to 5.1.1.x, the interim
release I ran on for most of August and September, or I could put in
5.1.1.6.
Hello TSMers,
is TSM Server 4.2 able to do multiprocessing? How can I configure it?
MfG
Sascha Bräuning
Sparkassen Informatik, Fellbach
OrgEinheit: 6322
Wilhelm-Pfitzer Str. 1
70736 Fellbach
Telefon: (0711) 5722-2144
Telefax: (0711) 5722-1634
Mailadr.: [EMAIL PROTECTED]
Hi Fred,
I just took a v4.2.2.12 AIX server to v5.1.1.6 last Saturday.
All I can say is 'not pretty'. This is due to the SYSTEM OBJECT
problem. If you don't know what this is, you will soon if you
have WinXP and Win2K clients backing up to v4 and pre v5.1.1.6
servers.
The basic problem is that
Gretchen,
I've seen the SYSTEM OBJECT problem, it's especially pretty when you can't
run expiration for six weeks. But I haven't had a scheduled session
accepted since I hit MAXSESS at 3:04 yesterday morning. Are you seeing
this in 5.1.1.6?
At 10:39 AM 9/24/2002 -0400, you wrote:
Hi Fred,
I
Is there a way to start TSM server without it doing anything? Kinda
like a single-user mode? Sometimes, I like to run an audit after
rebooting TSM and the tape library, but as soon as I start TSM, it
begins to do various things like space reclamation etc.
I *could* remember to disable sessions
Michael,
Upgrade to 5.1 should not be a problem. The default hint - take a backup
of your (v4.2.1) TSM DB to have the ability to step back.
What do you mean library is attached to both server and DB2-machine? If
drives are direct-attached (without SAN switch) you can define several
library
Hello,
in the meantime I upgraded to 5.1.1.6. With this level I could delete the
filespace without problem.
However, I couldn't resist to try cleanup backupgroup again. Under 5.1.1.4
it worked. It only seemed strange that it obviously didn't finish its work,
as Joel described:
On 5.1.1.4, I did
You can set TCPPORT to 1600, or something, in the options file and use the
WebAdmin to see what you want. I don't know if you can use SETOPT to
reopen 1500 or not.
At 10:56 AM 9/24/2002 -0400, you wrote:
Is there a way to start TSM server without it doing anything? Kinda
like a single-user
Hi Fred,
I've seen the SYSTEM OBJECT problem, it's especially pretty when you can't
run expiration for six weeks.
It's a pain, I've got a routine set up to find the oversized SYSTEM
OBJECT filespaces and then delete them, but I have two servers with
thousands of WinXP/2K nodes that bloated the
I ran into this in my conversion, too:
ANRD imutil.c(6663): ThreadId67 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 ending.
In previous versions, when MAXSESS is hit, everybody either goes into a
wait (I once saw over a thousand waiting because of a communications
problem) or they are retried until the number of active goes below the
maximum. On this patch, once the max is hit, it stays. So in an empty
system, a SQL
Hi TSMers,
I have an STKL700e library that I would like to share between two different
TSM servers - Has some body that before? could I please get some feed back on that .
STK is providing us ACSLS - but the catch is that it has to be installed on a
different server than TSM ( IBM
That did the trick.
I guess that if you had removed the old client's name and filespace areas,
you would have to redefine the client before you could do this. When you
use the virtualnodename, you are asked for the clients name and password
which makes sense.
Thanks for the assist...
--
Kevin
You can share the library with more than 1 TSM server if using ACSLS. This will allow
you to assign the tape drives in the library to one TSM server or another by defining
the library type as external. If you want to dynamically share drives in the
Storage Tek library between multiple TSM
We get this message when using the MS Exchange TDP, and I think also when running the
MS SQL TDP. We are running a V4.1.3 server on AIX, with V2.2.0 of the TDP clients. Is
there something we can do to stop getting this message without upgrading the server?
Will upgrading to V4.2.x of the
The multiprocessing capabilities in TSM are built in and do not need to
be configured. IBM recommends that a TSM server be installed on a
system with 4 CPUs at most.
--
Joshua S. Bassi
IBM Certified - AIX 4/5L, SAN, Shark
Tivoli Certified Consultant - ADSM/TSM
eServer Systems Expert
Hi All;
An easy one perhaps but I would like to know How can I find out all the TSM
table names?
TIA
regards;
Hussein A.
-Original Message-
From: Sam Haziprodromu [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 23, 2002 3:21 PM
To: [EMAIL PROTECTED]
Subject: Missing volume
Hi
At 10:55 AM 9/24/02 -0400, you wrote:
Hi Fred,
I've seen the SYSTEM OBJECT problem, it's especially pretty when you can't
run expiration for six weeks.
It's a pain, I've got a routine set up to find the oversized SYSTEM
OBJECT filespaces and then delete them, but I have two servers with
Hussein Abdirahman wrote:
Hi All;
An easy one perhaps but I would like to know How can I find out all the TSM
table names?
TIA
regards;
Hussein A.
-Original Message-
From: Sam Haziprodromu [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 23, 2002 3:21 PM
To: [EMAIL PROTECTED]
select tabname from syscat.tables
-Original Message-
From: Hussein Abdirahman [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 24, 2002 12:22 PM
To: [EMAIL PROTECTED]
Subject: TSM Database tables
Hi All;
An easy one perhaps but I would like to know How can I find out all the TSM
from a client point of view, look at resourceutilization (1-10)
Things like a base dsmc incr will fire off a thread to process each
~mount point~ to be processed...
you still only see one task on the client but will see multiple sessions on
the server.
I believe the max sessions will be 8 if you
Hi all,
just an Fyi.
not sure if anyone else have experienced this, We have TSM server 4.2.20
running on sol-2.8 and we were trying to eval servergraph,
the servergraph process started killing the TSM server leading to core
dumps! we have a PMR open with Tivoli and have updated servergraph
For the record - we're innocent!
dsmadmc -console sometimes crashes this release of TSM on Solaris.
We are unrepentant in our use of dsmadmc -console.
We have Servergraph installed at maybe 100 other sites, and have never seen
this happen before.
TSM says it's a known problem: I quote from
Hi,
Having the communication time out(comtimeout) on the server set very low
could cause a tcp/ip time out problem. Please increase the commtimeout to
500 seconds, the default is 60 seconds.
To have a successful restore, the password signon process'tdpipswd' must be
successful.
Regards.
Cai
Why not add DISABLESCHED YES to the DSMSERV.OPT file, log in and DISABLE
SESSIONS to keep others out.
Now this won't stop any migrations or reclamations from kicking off if the
thresholds have been exceeded, but no schedules will take off.
One of the steps in our disaster recovery instructions
Gretchen,
I just took a v4.2.2.12 AIX server to v5.1.1.6 last Saturday.
All I can say is 'not pretty'.
This is due to the SYSTEM OBJECT problem.
Can you elaborate on the system object problem that you were dealing
with? I've searched for an APAR that fits the description that you've
given,
Up until a few days ago, we were backing up only small amounts of data
for several nodes each night. Then an emergency request came in to start
nightly incremental backups using the TSM Domino TDP for a Domino mail
server that does not do transaction logging. (Note: The Domino support
staff
Check your network settings on your server. Some network cards do not
Auto-negotiate with certain switches. If everything is set to
Auto-negotiate, set the network card and the port of the switch it is
plugged into to 100 MB/s Full duplex. I was getting the same throughput on
some of my TSM
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Barbara Andrews
Even with client compression
turned on, the best throughput rate we've seen is 566 Kb/sec.,
and that was
when the backup was run on a Sunday when there is very little activity on
all systems involved
I've already seen one reply to check the NIC settings - those will get you
every time. An easy check that can really pay off.
Another thing to check is to see if the client is CPU or I/O bound. If
your CPU utilization is at 100% (or near it), client side compression can
slow you down. If the
Around here, we call TSM backups our Computer/Server/Node/Client Stress
Tester. I totally agree Mark, we currently used TSM backup stress tester
to test our Gigabyte interface and it did show pros and cons of the setup
of the GB network.
Thank You,
Bill Rosette
Data Center/IS/Papa Johns
We are experiencing the backup failed 402 error condition nightly on at
least 1 of our Exchange Servers. We are running:
The latest TDP for Exchange
Exchange 5.5 SP4
NT 4 60a
TSM Server
AIX 4.3.3 ML10
TSM 4.2.2.12
Gigabit
The NT hardware is
Another simple test to do to prove to Network guys and others
that TSM is not the problem is to do some FTP's from some of the
clients to the TSM server. Performance here is strictly
network/CPU/disk
not TSM. Only exception is if you have heavy backups or restores
going at the time.
David
Gretchen,
I've looked at our servers and have over 1.2 terabyte in system object
data, and 11,700,000 files. This from 1400 nodes. Do you mean to say by
delete them you actually go out and del fi * SYSTEM OBJECT?
I looked at one object and there were 14 inactive versions...we keep 4 and
run
Hi John,
I've looked at our servers and have over 1.2 terabyte in system object
data, and 11,700,000 files. This from 1400 nodes. Do you mean to say by
delete them you actually go out and del fi * SYSTEM OBJECT?
Yup, delete them, they'll back up again. We had over 15TB in
these files and I'm
Another thing to consider is that each time an email comes in to the
Domino server, some user file is getting changed. If a file is changed
while TSM is backing it up, it starts over (depending on your settings).
This bit us when we started backing up our Domino server. Since you are
using the
Mark;
run the command netstat -v on the backup interface and take a look at
- Drop packets
- Recieve errors
- Transmit errors
- CRC errors
- DMA overruns
- The recieve and transmit queue size.
- Any collisions (single or otherwise)
Like others said, Hard code all the devices involved to 100 MB
SNIP
It's a risk, because our bare metal restore procedures depend
on a current SYSTEM OBJECT backup, but I can't let the database
swell to infinite proportions - the performance is horrible.
Luckily, the problem is fixed in v5.1.1.6.
Gretchen Thiele
Princeton University
You can always rename
Looking for contractor to work on TSM in NT environment in Houston area,
time and materials, maybe 100 hours per year.
Regards,
Orin
Orin Rehorst
Port of Houston Authority
(Largest U.S. port in foreign tonnage)
e-mail: [EMAIL PROTECTED]
Phone: (713)670-2443
Fax: (713)670-2457
TOPAS web
You can always rename the filespace and allow a backup or two to
complete before deleting the old filespace.(At least on the NT platform)
This is an excellent suggestion! Also, you don't want to do so many
at a time that your database becomes 'unbalanced' (a level 2 caveat).
Again, identify
Hi Fred,
I just took a v4.2.2.12 AIX server to v5.1.1.6 last Saturday.
All I can say is 'not pretty'. This is due to the SYSTEM OBJECT
problem. If you don't know what this is, you will soon if you
have WinXP and Win2K clients backing up to v4 and pre v5.1.1.6
servers.
Does this problem
I found that the SYSTEM OBJECT which were not unicode were never deleted
unless I did it manually. A QUERY OCC * SYSTEM OBJECT (without the
NAMETYPE=UNICODE 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
W2K is known as NT 5.0 to TSM. Do a q node blah f=d
for your client node on TSM server and see what it comes up
as. Haven't had any XP clients yet to see what it is known as.
David Longo
[EMAIL PROTECTED] 09/24/02 08:21PM
Hi Fred,
I just took a v4.2.2.12 AIX server to v5.1.1.6 last
I found that the SYSTEM OBJECT which were not unicode were never deleted
unless I did it manually. A QUERY OCC * SYSTEM OBJECT (without the
NAMETYPE=UNICODE 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
We have a cache directory on an AIX server that has about 8 million
objects. We want to archive this maybe twice a week for DR purposes and
only keep one copy. The trouble being it blows out our database with all
the objects and the schedule log blows out the files space where it is
saved to.
Hi Anthony,
I'm assuming that this filesystem needs to be online all the time. Are you mirrored,
and can you do an AIX Split mirror backup?
If so, split the mirror, change the lv type to something other than JFS and do an
image backup. I've not tried this, but it should work.
Regards
Steve
Well, I'll take a shot at this. Haven't worked with 3590 tape in a
while
but your questions are applicable to any tape.
1. If these tapes were removed then your onsite and/or offsite
reclamations should start failing soon as they try to use a tape that
isn't there.
2. If your know which
Hi Sascha,
This holds true for all the OS's except MVS-OS/390-z/os - on the
mainframe you need to specify multithreading yes/no to enable
multi CP usage.
If set to no TSM will only use one CP.
Cheers
Christo
--
The
Hi all,
I have a 3494 library,my adsm version is 3.1.6,now my library slot will be full,so I
want to move some cartridges out of the library.The operations I will have as follow:
backup db devclass=tapeclass
move media * stgpool=backup
move media * stgpool=archive
Is this all?Or I need any
57 matches
Mail list logo
