Hello TSM'ers, are there any recommendations/experiences concerning volume size/
maximum number of volumes on sequential disk storage pools?
On our largest TSM server, we currently have a 27T pool consisting of 10G
volumes = some 2700 volumes. I chose the 10 gig size a couple of years ago
after
Just was up on the download page.
Has the as/400 client gone the way of the dinosaur?
Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310
Gary -
See http://www-03.ibm.com/systems/i/support/brms/adsmclnt.html
\o/ more fuel for the car :)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Lee, Gary D.
Sent: donderdag 18 september 2008 13:51
To: ADSM-L@VM.MARIST.EDU
Subject: Tsm client for as/400
Just was up on the download page.
Has the as/400 client gone
I would think the best way to keep TSM from getting into trouble would
be to limit the number of mounts.
This will keep you from having too many 10G files going at any one time.
OR
Increase the file size so that you limit how many volumes you manage in
TSM to keep the db size down. 2700 really
Because of some network changes, I need to change the IP address of the
system that controls my tape robot in a shared library environment.
This system is also my configuration manager.
Do I just need to change the high level address that the server has for
itself (using update server) and then
I know of no TSM-based limit.
I personally have 1672 25037MB FILE-class volumes on 88 filesystems. The
volume size was chosen to entirely fill the filesystems. The filesystem
size was chosen to fit evenly within the LUNs. The LUN size was chosen
to exactly fill optimally-available arrays. The
There's no evaluation provided. List is USD1030.90 for 10 PVU of the
basic product with exchange brick-level and bare-metal. It's the former
FilesX product.
We're torn between implementing it and waiting for the native
brick-level exchange restores in TSM 6.
Every Thursday this month at 15:30
Since the TSM server is running on the node you want to restore on, why
not just let the server serve the backupset to its own client?
[EMAIL PROTECTED]
/home/tconwayruntsm q backupset flatus
IBM Tivoli Storage Manager
Command Line Administrative Interface - Version 5, Release 4, Level 0.2
(c)
The PASE environment is no longer supported. I think you can run it on
the 400 in a Linux partition.
Lee, Gary D. [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
09/18/2008 07:52 AM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To
Greetings,
We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients
are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so
the TSM server launches the schedule.
We see an occasional problem where a Windows client is set up wrong
in Active Directory (which feeds
The simplest solution is
upd node STLO-MPVADM HLA=10.52.27.204
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Schneider, John
Sent: Thursday, September 18, 2008 9:29 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM scheduler can't reach TSM
Honestly, the AS400 client couldn't be called a dinosaur... More a fried
scrambled dinosaur egg that somebody sculpted into the shape of a
dinosaur and expected it to get up and walk around.
Dozens of hours to back up a single small library is not useable. The
response from IBM is that
John -
The ANR8213W message is conspicuously deficient in not parenthetically
including the IP address along with the network name that it's
reporting, such that you don't know for certain what address the TSM
server is using in making the connection attempt. With DNS awry at
your location, it
Tim,
We have tried this, but it doesn't help. When you issue a 'q
node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address
cached for it:
...
TCP/IP Name: STLO-MPVADM
TCP/IP Address: 10.52.27.204 ..
So the TSM scheduler seems to still
No, the problem is that the node TSM is trying to reach is
stlo-mpvadm.company.com but the machine that's responding is
stlo-mpvadm.smrcy.com and TSM knows there's a difference. You MUST
correct the DNS problem because TSM uses it in some way to verify
authentication.
I've seen this a dozen or
Try DSNLOOKUP NO in the dsmserv.opt file. The default is YES.
Bill Boyer
Hang in there, retirement is only thirty years away! - ??
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Schneider, John
Sent: Thursday, September 18, 2008 1:49 PM
To:
Bill,
Never heard of this option. Won't this make us unable to reach
ANY clients then, unless we put them in the local /etc/hosts file? That
would be impractical, with 1600 clients in our environment.
Or will TSM use the cached copy it saved when the client first
connected in?
Richard
Thanks for your post. It seems odd to me too that it doesn't
spell out the IP address when it tries to connect, but when you issue a
'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct
address cached for it:
...
TCP/IP Name: STLO-MPVADM
John -
One last thought: A 10-net is in use there (private net - no
routing). As such fussy firewall rules may be in force, which with
the DNS happening may be a further impediment to reaching that TSM
client through the server. Some basic network tracing (Wireshark, et
al) in conjunction
I specify this on almost all my TSM servers and haven't seen any adverse
effects. Bypasses the DNS issues like what you have right now. It is a
documented option in the Admin Reference.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Schneider, John
TSM will populate field TCP_ADDRESS in table NODES with the numeric
address of the client when it connects, so not having name lookups
performed is really no loss in functionality... And now that I know
about that option, it's going in next restart, because it will cut
latency, which will matter
22 matches
Mail list logo
