Dear All,
I have just installed TSM Extended Edition 5.2.2.
Taken a backup and even restored it.
While I am trying to Query the contents of a storage pool volume I am
getting this error
ANR2020E QUERY CONTENT: Invalid parameter - NAMETYPE
ANR2020E QUERY CONTENT: Invalid parameter - CODETYPE
Hmm, and what's that (server 5.2):
tsm: TSM1q n derma.tea* f=d
Node Name: DERMA.TEAFOR2
Platform: Linux86
Client OS Level: 2.4.18-27
Client Version: Version 5, Release 1, Level 5.0
...
Yup, we have
fsize = -1
cpu = -1
data = -1
rss = -1
stack = -1
nofiles = -1
for root, ulimit -a gives;
time(seconds)unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes)unlimited
memory(kbytes) unlimited
coredump(blocks)
Hi all
I am having a bit of an arm wrestle getting TSM to write to LTO2 drives in a
3582 library. Config as follows:
TSM 5.2.2.0 (also tried 5.2.0.0)
Solaris 5.9
Direct fibre attached to 2 drives.
Drive firmware 38D0 (latest on web)
IBMtape (latest on web dated 19 May)
Problem
Most Mac nodes(all client version 5.1.5.1, os lvls 10.2.8, 9.2.2, 10.3.2) have
blank IP addresses.
Some WinNT 4.00/5.1.6.0 don't have blank IP addresses, some do.
One Linux86 2.4.19-27/5.1.5.0 shows 127.0.0.1 .
Some nodes have a TCP/IP Name, but no TCP/IP Address.
It's mysterious ...
Gerhard
Most Mac nodes(all client version 5.1.5.1, os lvls 10.2.8, 9.2.2, 10.3.2)
have blank IP addresses.
Some WinNT 4.00/5.1.6.0 don't have blank IP addresses, some do.
One Linux86 2.4.19-27/5.1.5.0 shows 127.0.0.1 .
Some nodes have a TCP/IP Name, but no TCP/IP Address.
It's mysterious ...
Can you
I think I had that problem too. I am not remember exactly what I have
done there, but as far as I remember the policy was removed exidently
and files never expired. So I recreated policy with the same name and
let those files expire.
Sorry I can not give more clear answer, but nobody else
Why not make a select to see wich managementclasses the the files are binded to?
Does the managementclass not longer exist in the domain, the domains grace period will
take place. Read the manual under wich situation the grace period also will take place.
regards
joachim
-Ursprüngliche
Richard,
Here is an example:
tsm: TSM1q n gyn.echnaton f=d (some lines deleted)
Node Name: GYN.ECHNATON
Platform: WinNT
Client OS Level: 4.00
Client Version: Version 5, Release 1, Level 6.0
Policy Domain Name:
Just ideas...
If tar works and TSM doesn't, that could indicate your ELEMENT addresses are
wrong.
That is, TSM thinks /dev/rmtx is drive 1, so it mounts the tape in drive 1,
but AIX is looking for the tape on drive 0.
Do a Q DRIVE * F=D, make sure the element addresses are correct.
The other
Richard,
Here is an example:
...
TCP/IP Name: ECHNATON_GYN
TCP/IP Address:
...
Gerhard - Thanks much for taking the time to prepare the sample.
I'm not sure what to make of the empty TCP/IP Address field, which should
rightly contain the address of the client
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Prather, Wanda
If tar works and TSM doesn't, that could indicate your ELEMENT
addresses are wrong.
Another symptom of an element mismatch is if TSM will mount a tape but
be unable to use it and/or dismount it.
--
Mark
There is a 1 hour webinar on this subject Monday 07/26. I haven't seen
it but I have signed up for it. I see an avalanche of vendor offerings
lately. I hope this can straighten out things a little.
Matt
Topic: Disk Only Backup Strategies
This presentation will examine some possible disk
What are the pitfalls/gotchas/hazards/ROT/suggestions of changing a NODES
Policy Domain ?
I really need to move some nodes to different PD's so I can move their
management classes to use different, non-collocated storage pools ! I
can't move the whole PD/MC since there are some heavy-hitters I
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Zoltan Forray/AC/VCU
What are the pitfalls/gotchas/hazards/ROT/suggestions of
changing a NODES Policy Domain ?
You will lose any associated client schedules.
However, rather than create a whole new policy domain, just create
What are the pitfalls/gotchas/hazards/ROT/suggestions of changing a NODES
Policy Domain ?
If the node has centrally scheduled backups you will need to copy the
schedule to the new domain (unless a suitable schedule exists there
already) and execute a 'define association' command to associate
Thanks for the quick response.
I do not understand the scope of lose any associated client schedules ?
Do you mean for the node that I am moving to the new PD ?
I thought about the MC issue. However, wouldn't this cause issues with
everything already backed-up ? I assume it would automagically
If the OLD policy domain and the NEW policy domain don't have the same
management class NAMES, and the client has files bound to the OLD management
class names that don't exist in NEW, you will get some weird messages in the
activity log when expiration runs.
If you create the new PD by copying
There are some other faster restore solutions out there. With Virtual
Tape Libraries you get all the speed and reliability of D2D but with all
the functionality of tape. For example, I happen to work for a company
that provides a VTL solution which is certified by IBM-TSM. There is no
way to
You will have to def assoc to add them to a backup schedule in the new
domain. If you want to move the existing data to the new storagepool
structure, you will need to do move nodedata NODE from=OLDSTGPOOL
to=NEWSTGPOOL for the primary tape pool. Your normal backup stg
processing will create the
Just to close the loop with the rest of this list on this:
The doc that Melinda and Leif sent me both showed invalid verb received
messages, which suggested IC40841. The current APAR description isn't an
exact match, but from what I knew about the fix for that APAR, it seemed
worth a shot.
There
21 matches
Mail list logo
