TSM server 5.1.5 is now on the FTP under LATEST in the normal area. The
Linux version is available from:
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/patches/server/LNX/LATEST
Kauffman, Tom wrote:
Under the last publishe set of naming conventions I've seen from IBM, this
sho
Does any body has a work around with the dwon level client code errror?
Here's what happened: I have an old ADSM client version 3.1 runnning in
Solaris 2.5. We don't want to upgrade it to a higher level, say TSM version
4.2.2, because if we upgrade we need to upgrade first the Solaris to a
higher
All,
I watched my customer load the 5.1.5.0 client over a 5.1.1 on a Dell
2550 W2K SP2 system. He performed a reboot as requested by the
installer and when the system tried to IPL it crashed with a Blue Screen
of Death:
*** STOP: 0x07B (0x85DCC1B0,0xC102,0x,0x)
INACCESSIB
"This is patch level 5.1.5.1", source
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/patches/LNX/LATEST/TSMSRVLNX5151.README.SRV
So this is not the whole server. Maintenance levels are located in
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintenance/
Base leve
Responded to offline
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
Two choices:
- if you do not need many versions of the node's data - simply rename the
node and register new node with same name, perform full backup, delete
renamed node;
- if you need to keep all backup versions or have archives - identify
which tapes contain that node's data, mark them "unavaila
From: Zlatko Krastev/ACIT <[EMAIL PROTECTED]> on 10/12/2002 04:32 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Down Level Client Code
Two choices:
- if you do not need many versions of the node's data - simply rename the
node and re
Zlatko,
Thanks for your suggestion.
By the way I can't do your second alternative because the Storage pool is
not collocated. There are other data in the tape. Although could be done
if we upgrade the TSM server from 4.2 to 5.1 because of move data command.
My only worry is we always have a re
Hi,
Does anyone have a list of valid client traceflags for the 5.1.5 client?
I am trying to use the PERFORM flag and it no longer provides the
instrumentation client detail INSTR_CLIENT_DETAIL. We have used this
flag in the past to get performance information about client sessions.
Has it been re
Hello all
thanks in advance for your valuable tips!
We are planning to introduce the archive feature within TSM on our new
install base., and I have a few issues and concerns on how to protect
in-accidental or deliberate use of this service.
Currently 90% of our client backups run via a central s
In the past support has had a way to correct this problem for clients that
got the wrong OS in them because another system used the field by accident.
I would call support again and see why this workaround is not available for
you.
Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180
Thanks Paul.
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
Zlatko Krastev/ACIT
> WARNING: next time use -virtualnodename= instead of
> node= and this would never happen (Mark, this is nearly a FAQ
> candidate).
Agreed.
--
Mark Stapleton ([EMAIL PROTECTED])
Certified TSM consultant
C
Miles, go into smitty install and select "all" (not latest) - you'll see
the messages fileset - install it and you'll get the help text cleaned up.
Joerg Pohlmann
604-535-0452
Miles Purdy <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
2002-09-30 08:45
Please respon
14 matches
Mail list logo
