For those of you that are ServerGraph customers. Could you send Lindsay
lmorris AT servergraph DOT com <mailto:lmorris AT servergraph DOT com> some
sample
activity logs where you update the path information on a drive. He is
trying to solve a problem and provide a capability for its customers. After
getting blasted, I suspect he is a little gun shy to ask for this
information. The thread of discussion here may also be interesting. Folks
may not realize that drive/path definitions can be changed while the drive
is online/active.
He has come to Share in the past and done an excellent non-sales
presentation on Servergraph techniques. These techniques have helped TSM
users.
Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180
-----Original Message-----
From: Mr. Lindsay Morris [mailto:lmorris AT servergraph DOT com]
Sent: Thursday, October 17, 2002 11:04 PM
To: Seay, Paul
Subject: RE: Wisdom re paths?
Not so nasty - the program that needs this is the one that's reading all the
activity log messages anyway, and it's already got the smarts to make sense
out of them.
All we need is real-world sample activity log messages where somebody is
updating drives' devices.
If you know of likely candidates, tell them to call me, would you?
And thanks.
---------------------------------
Mr. Lindsay Morris
Lead Architect, Servergraph
www.servergraph.com <http://www.servergraph.com/>
859-253-8000 ofc
425-988-8478 fax
-----Original Message-----
From: Seay, Paul [mailto:seay_pd AT naptheon DOT com]
Sent: Thursday, October 17, 2002 10:58 PM
To: 'lmorris AT servergraph DOT com'
Subject: RE: Wisdom re paths?
It has to be an overt command that would show up in the activity log. The
quickest way I could think of is start running an SNMP trap of the Update
Command message or a simple select against the activity log:
select originator, message from actlog where msgno=2017 and upper(message)
like '%UPDATE %DRIVE %'
Then you will have to parse that message and check to see if it was
successful by selecting all the instances that go with the session.
Which would work on 4.2, but under 5.1 I would guess it would be UPDATE
PATH.
NASTY.
Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180
-----Original Message-----
From: Mr. Lindsay Morris [mailto:lmorris AT servergraph DOT com]
Sent: Thursday, October 17, 2002 10:47 PM
To: Seay, Paul
Subject: RE: Wisdom re paths?
I attach the 5.1 schema - no drivemaps table...
How could the drive's device change on us?
a. Someone changes it manually - then maybe we can detect the activity log
message about that and repair our internal tables.
b. Some SAN hardware reboot magic takes place - would we still see an
activity log message about that?
c. other...?
You know what I really need? Somebody running 5.1 with enough SAN hardware
to exercise this stuff, who would let us have a login to their Servergraph
(not TSM) machine. Might that be you, in the not-too-distant future? We
offer test site discounts, if you're intereseted. Or maybe you know
somebody like that.
Where's a good place to read about this drive mapping stuff? I guess the 5.1
Admin Guide?
---------------------------------
Mr. Lindsay Morris
Lead Architect, Servergraph
www.servergraph.com <http://www.servergraph.com/>
859-253-8000 ofc
425-988-8478 fax
-----Original Message-----
From: Seay, Paul [mailto:seay_pd AT naptheon DOT com]
Sent: Thursday, October 17, 2002 8:10 PM
To: 'lmorris AT servergraph DOT com'
Subject: RE: Wisdom re paths?
Yes it can happen with TSM up and running.
I am not running 5.1 yet, but I am aware of the issue you are talking about.
Actually, they do some hokie stuff in 4.2 where the device is really not in
the drives table. You have to select the device_type field at the same time
as the device field or the device field does not show. The implementation
was already there in 4.2, but were insulated from it until the finished the
job in 5.1.
You can actually update the device in 4.2, it was going to the path table
then. There really is not a change between 4.2 and 5.1 on the issue you
bring up. You are just concerned about it now because the device does not
show up in the select anymore.
A drive does not have to be offline to update the path information.
If you think about it, now it is consistent for all maps to a drive
regardless of who the path is for (server or storage agent). This is
actually a good thing.
However, I can see the quagmire that places you in. You have to report
drive usage and at any time some one could just change it on you and the now
the ServerGraph information is no good. This does suck because now we have
no idea if the table information matches.
Does the DRIVEMAPS table exist in 5.1?
Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180
-----Original Message-----
From: Mr. Lindsay Morris [mailto:lmorris AT servergraph DOT com]
Sent: Thursday, October 17, 2002 5:49 PM
To: Paul Seay
Subject: Wisdom re paths?
Hi, Paul.
TSM 5.1 no longer has a device-name in the DRIVES table.
They took it out and put it in the PATHS table.
We need to find out what device a drive is using, because some activity log
messages about mounts/dismounts don't HAVE a drive name explicitly - they
only have a device name. So we have to use device name to figure out the
drive name.
Now, I can join the tables to match up the device name with the drive name
(see below), but my question is this:
when is this mapping liable to change?
I mean, might DRIVE-01 suddenly switch from using /dev/rmt1 to using
/dev/rmt2?
Can that happen while TSM is still up and running?
Thanks for any light you can shed....
---------------------------------
Mr. Lindsay Morris
Lead Architect, Servergraph
www.servergraph.com <http://www.servergraph.com/>
859-253-8000 ofc
425-988-8478 fax
select drives.library_name, drives.drive_name, paths.device from drives,
paths \
where drives.library_name=paths.library_name\
and drives.drive_name=paths.destination_name\
group by drives.library_name, drives.drive_name, paths.device
|
