Nicely put, Gianluca! I agree that LTO is (nearly) a no-brainer here.
The part about using HSM or not -- depends on your customer's perspective
(and wallet). I've been working with a couple clients who have similar (or
worse!) retention needs for some of their data; we've about resolved to
BUT WAIT... have you not seen 4.2.2 and 5.1.x -- both have broken summary
table info, specifically the BYTES column is (mostly, not always) ZERO! I
am still researching the other columns, they may be FUBAR'ed also; I am
told there is an APAR open for this -- IC33455 -- anyone know when it will
Hello,
I see no answer to this on the list. So get one
TSM utilizes transactions, in other words it groups files until they
reach some limit and processes the whole bunch at once. Limits are size of
transaction in kB (controlled by TXNBytelimit option in UNIX dsm.sys or
Windows dsm.opt) and
Hi,
If I take a full backup on Friday ADSM will the other days on backup the
files that were modified since that day afterwards (if copy mode is set to
modified). Now assuming that this data will expire after 7 days will ADSM
take a backup of the whole data again afterwards?
Regards,
We just went up to 4.2.2.2 and it's still broke. Actually that BROKE it for
us. We were at 4.1.2.5 before that. I have a PMR open and the tech said Per
my research, this problem matches APAR IC31132 for AIX, and IC31296 for
Windows. Per the README file for TSM 4.2.2, these apars
were supposed to
Hello all,
I think I should share my experience and ask for experience and opinions.
The environment (we are installing for a customer):
IBM 3583 with 3 drives + SAN Data Gateway Module connected to IBM 2109
(i.e. Brocade) switch
TSM server v4.2.1.15 (or may become 4.2.2) on Windows 2000 (its a
There is a limit on the number of bytes you can put for a PARM= in the JCL.
Try putting the filenames in a sequential dataset in the order you want. One
DSN per line. Then in the PARM field use the DD: specification instead of
listing all the dsnames. I don't have access to the mainframe right
Only the EXTRA versions will be expired after 7-days, if that's your
management class retention. TSM wil never-ever-EVER expire the ACTIVE
version of a file The RETEXTRA parameter of your management class tells
TSM how long to keep the INACTIVE or EXTRA copies of a file...not ALL copies
of a
Petur
No quiet. I need to know for all my nodename the permission access I
gave for another nodename to restore from.
The command is: set access backup * nodename
to check the permission i run on each nodename the command: q access
I figure if is it a global command to do it for all my
Hi TSM-ers,
in the near future I'll have to compare Legato's Networker with TSM.
* Has anyone written a comparison of both current products?
* If not, is anyone interested in such a comparison?
* If yes, I would write it in english otherwise in german.
Do you think
Please call your Tivoli support rep back and ask about the status of APAR
IC33455. This is the correct APAR for this problem. I have included the
text below.
ERROR DESCRIPTION:
Found on TSM Version 4.2.2.0
Other Versions Affected TSM Server V5.1
OSs Effected All (recreated on WIN, AIX,
Can you be sure that since you've set it up nothing has changed. It would
be interesting to see current dsm.opt of local cluster node. Also the
way how schedules are started may sched some light. Also check file backup
dates on those unnecessary filespaces - maybe someone manually invoked
dsmc
Hi,
Last friday I created a large file enable journaled file system on AIX 4.3.3
and put a
10 gb single file on it. It was my backup disk pool volume. But I recieved
following messages on
TSM and AIX. Any idea?
Actlong from TSM 4.2.2.0
24-05-2002 21:22:38 ANRD dsrtrv.c(538):
13 matches
Mail list logo
