Hi Harold,
Everything depending on your hardware.
But I got everything from 300 nodes up to approx. 500 nodes and every TSM
Server are running on Wintel.
Best Regards
Christian Svensson
Cell: +46-70-325 1577
E-mail: christian.svens...@cristie.se
Säkra återläsningar.
-Ursprungligt meddela
IMHO,
It's not about the nodes, it's about the number of managed objects and the I/O
throughput in TB per day (and the size of the DB, if you are still on V5).
Have had 2 different customers where ONE node (an imaging app, naturally)
occupied > 50% of the TSM DB. Really.
I usually don't see mo
We have two TSM servers, one with 137 nodes and one with 50. The number
of nodes doesn't make so much difference as the data rate and metadata
rate (number of files) though.
-- Skylar Thompson (skyl...@u.washington.edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (
We have a Mac agent that is hanging after it scans about 400K files. Has
anyone seen this before?
Mac 10.6.7
Agent 6.2.4.0
TSM 6.2.3.0
Andy Huebner
This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
r
There are all kinds of measures involved in setting up a TSM server; processor,
RAM, disk I/O, stg pool design, reclamation, migration, all the bits and pieces.
But, I'm curious about how many nodes some of you have on your TSM servers?
I'm in a Windows environment, and have been tasked with "co
In a library sharing environment, I think this will flag volumes that
are associated with a different TSM server as orphaned. This is the
script I've been using:
tsm: TIBUR>q scr find_orphan_vols f=r
SELECT lv.volume_name from libvolumes lv -
LEFT OUTER JOIN volumes v ON lv.volume_name=v.
Here is a script that I got at a Share conference years ago that lists tapes
that are marked Private but are not being used:
tsm: ULTSM>q script q_lost_tapes f=l
Name Line Command
Number
-- --
Q_LOST_TA-
