hi all,
i'm doing an test restore of rootvg from TSM via classic network boot
the communication is fine and everything seems okay except this ...
it simply hangs on following ...
---
Type menu item number and press Enter
Hi Thomas!
For your information: IBM just released all 5.3.3.0 servers on their FTP
sites.
I checked for you: it contains the fix for APAR IC47731.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
At 12:34 AM 4/1/2006 +0200, Jurjen Oskam wrote:
Uhm, may I ask *why* you'd want an off-the-shelf product instead of
your own code? Is the Perl-code not functioning correctly? What
problem are you trying to solve?
I can't speak for the original poster, but I've worked for shops that
preferred
Perhaps I am reading this wrong, but here are some hints that I have
learned over the years:
1) The bootp server must be at or above the oslevel of the restored
server:
AIX 5.3 can be used as a bootp server for AIX 5.2
AIX 5.2 cannot be used as a bootp server for AIX 5.3
This sounds like a show
- Jurjen Oskam wrote: -
Uhm, may I ask *why* you'd want an off-the-shelf product instead
of your own code? Is the Perl-code not functioning correctly?
What problem are you trying to solve?
Management objections to the current script seem to center on two
issues:
1.None of the other
Where do I find the recommended defaults for AIX and Window ba clients at
client versions 5.2 and 5.3 on the IBM website.
AIX client - TSM client version 5.2.2.0
dsmerror.log
04/02/06 04:38:38 ANS1809W Session is lost; initializing session reopen
proced
ure.
04/02/06 04:38:39 ANS1809W
Do a search for the redbook Sc32-9101-02. Thsi should have everything
you need.
Bob Martoncik
Lucas County Information Services
419-213-4633
[EMAIL PROTECTED] 4/3/2006 11:25 AM
Where do I find the recommended defaults for AIX and Window ba clients
at
client versions 5.2 and 5.3 on the IBM
I'm still having 5.3.2.3 repair volume hanging problems when it repairs
offsite volumes during reclaimation.
Matthew Glanville
Eastman Kodak Company
Worldwide Information Systems (WWIS)
343 State Street
Rochester NY 14650
585-477-9371
Privacy/Confidential Disclaimer:
The information contained
Hi world,
I am experiencing some problems ocasionally with the dismount of the volumes
coming from TSM.
It happens with the reclamation process, and yesterday with the backup of the
databases.
It seems that TSM finish his operations normally and close the volume, but the
process fails in
Note that in 5.3, many client default settings have been changed to
recommended values that, in general, will perform better out of the box
than prior default values (see Summary of changes for Tivoli Storage
Manager near the beginning of the client manuals).
Regards,
Andy
Andy Raibeck
IBM
Iban
We too are having problems with something like 1% of dismounts on our
externally managed libraries using EDT. I posted on it back in January but
didn't see any responses. The problem started following an upgrade from EDT
6.4 to 7.4.
Are you seeing any LH_ERR_TRANSPORT_BUSY errors in the
TSM server v5.2.7 on Windows2003
I swapped out our HP LTO-2 drives for HP LTO-3 drives this weekend,
which mostly went ok. Did have an issue where the tsm 5.2.7 device
driver didn't recognize the drives, but that was fixed by installing the
tsm 5.3.2.4 device driver. I also updated the LTO
I had an interesting situation: A volume in primary pool had a read error.
I used q vol f=d and found the last date of data written is around
January. Since then, I had several good backup on this tape. However, I
found on March 26, it had requested to make copy of this tape. Since this
tape is in
On Sun, 2 Apr 2006 09:52:52 +0200, Jurjen Oskam [EMAIL PROTECTED] said:
On Sat, Apr 01, 2006 at 09:46:00PM -0500, Allen S. Rout wrote:
Speaking as someone buried in my own PERL up to my nose:
[snip: quite a good argument]
I don't think I could be as effective with a third-party product
On Apr 3, 2006, at 1:09 PM, Frank Tsao, email is [EMAIL PROTECTED] wrote:
I had an interesting situation: A volume in primary pool had a read
error.
I used q vol f=d and found the last date of data written is around
January. Since then, I had several good backup on this tape.
However, I
found
On Mon, Apr 03, 2006 at 10:48:13AM -0400, Thomas Denier wrote:
2.I am spending significant amounts of time on enhancements to the
script.
Yes, that would be a reason to consider an off-the-shell solution.
The Perl-automation here runs more or less autonomic and doesn't
require much
Does anyone have any suggestions on the steps to migrate from a
standalone TSM instance with a 3584, to a library manager instance
to control the library and the origional TSM instance as a library
manager client.
I found a redbook that I've started working through, but thought I'd
see if anyone
On Mon, Apr 03, 2006 at 01:09:35PM -0400, Allen S. Rout wrote:
I'll allude to a bit of logical pedantry by suggesting a google of
'beg the question' :)
Darn, I /thought/ I got that right. From a Google search: If you're
not comfortable with formal terms of logic, it's best to stay away
from
I went through this about a year ago. The only way I know to get the
inventory of tapes moved out of tsm2t and into tsmlm2 correctly is to:
1) check the tapes out of tsm2t
2) delete the library (and drives and paths) from tsm2t
3) define the library (and drives and paths) in tsmlm2, and as a
Back in the days of VM, my favorite automation tool for ADSM was Host
Management Facility. Unix cron is a poor substitute, but it's what we've
got to work with. I do a majority of my scheduling from within the TSM
server with administrative schedules that trigger TSM Scripts. This is a
rather poor
On Mon, 3 Apr 2006 15:32:22 -0500, Bill Kelly [EMAIL PROTECTED] said:
1) check the tapes out of tsm2t
2) delete the library (and drives and paths) from tsm2t
3) define the library (and drives and paths) in tsmlm2, and as a shared
library in tsm2t
4) check the tapes in to tsmlm2.
What he
On Mon, 3 Apr 2006 22:00:52 +0200, Jurjen Oskam [EMAIL PROTECTED] said:
Our TSM environment is too small to justify that niceness, since the
Perl-code keeps everything running virtually maintenance-free. But
yes, I think there are many installations where these off-the-shelf
products really
We have TSM version 5.2
I have changed the standard policy so that we now keep the 10 latest
versions of each file rather than 7.
I have also changed our del volhist to tod=today-10 where it was
previously 7.
I have been told that previously we had to keep the 7 latest copy tapes
and db tapes
23 matches
Mail list logo
