Re: 3584 checkin/checkout

[Jurjen Oskam]

On Thu, May 04, 2006 at 02:10:09PM -0400, Jim Zajkowski wrote:

> People leave their IO doors open?

After exchanging tapes, it *did* happen once or twice here. When that
happens, people automatically get informed Really Quickly and come to
the library to close the door. Which is no problem, because those
people are in the room next to the library.

--
Jurjen Oskam

Savage's Law of Expediency:
You want it bad, you'll get it bad.

Re: 3584 checkin/checkout

[Jurjen Oskam]

On Thu, May 04, 2006 at 12:01:49PM -0500, John Monahan wrote:

> The whole point of using scripts is so you don't have any manual tasks
> *unless* something is wrong.  I would consider an open library door as
> something being wrong.

I meant that it probably would be wise to not use the WAITTIME=0 parameter
and use the REPLY mechanism. The REPLY would then only be sent when the
operator acknowledges (via a menu or something) that he closed the door.

The handling of the REPLY can be scripted of course, i.e.: the operator
doesn't need to be in dsmadmc and issue the REPLY himself.

> Automation scripts also won't work if someone powers off the library.
> Seriously, you can't expect a TSM admin to write automation scripts to
> cover every possible instance of human error.  Technology can't fix
> stupid.

True, but if you can foresee errors which are easy to make that have
large(ish) consequences, it's silly not to think about how to prevent
either the error or the consequences.

--
Jurjen Oskam

Savage's Law of Expediency:
You want it bad, you'll get it bad.

Re: Log pinning issue, not quite sure what's going on...

[Sung Y Lee]

Suggestion

Assuming that data(s) are being migrated from diskpool, I would also
examine if disks of primary diskpool are going bad or there are some bad
data written to disk.
I would look at /var log or error logs.  Maybe run some  diagnostics
commands top see if OS see all devices are fine on the TMS server.

Sung

"ADSM: Dist Stor Manager"  wrote on 05/04/2006
01:32:22 PM:

> Hello everyone,
>
> Earlier in the week I had an issue with the log being pinned by a
migration
> task.  I have thus experienced the issue again this morning and it
appears
> as if another migration task has it pinned again.  The weird thing is
that
> in all cases the migration task that has it pinned it the same drive each
> time.  It just seems to sit there and does not continue after a certain
> point in time.
>
> I have a TSM 5.2.1.7 server on AIX 5.2 which runs Gresham EDT 7.4.0.5
with
> ACSLS 7.1.0.24 and LTO2 tape drives.  We have had the drive replaced
today,
> but I am still seeing this bizarre issue happening with the migration
task
> and that particular drive.
>
> Does anyone have any suggestions/ideas?
>
> And also, I will be changing this recovery log to rollforward mode within
> the next day.  Thanks for the suggestion Richard!
>
>   Sess Comm.  Sess Wait   Bytes   Bytes Sess  Platform Client Name
>
> Number Method StateTimeSent   Recvd Type
> -- -- -- -- --- --- - 
> 
> 11 Tcp/Ip Run  0 S   10.9 K  30.7 G Node  WinNTHMCH1143
>
> 54 Tcp/Ip IdleW0 S4.6 K   4.8 K Node  WinNTHMCH1143
>
>  2,004 Tcp/Ip Run  0 S0  42 Admin WebCons  DCOPS
>
>ole
>
>  2,295 Tcp/Ip IdleW   32 S1.3 G   1.2 K Node  TDP  LNPITTA02
>
>Domino
>
>AIX
>
>  2,466 HTTP   Run  0 S0   0 Admin WebBrow  LIDZR8V
>
>ser
>
>
> Dirty page Lsn=5493127.198.1518, Last DB backup Lsn=5493128.7.1110,
> Transaction table Lsn=5491887.53.2214, Running DB backup Lsn=0.0.0, Log
> truncation Lsn=5491887.53.2214
>
> Lsn=5491887.53.2214, Owner=DB, Length=56
> Type=Update, Flags=82, Action=SetIcb, Page=5543936, Tsn=0:2734908799,
> PrevLsn=0.0.0, UndoNextLsn=0.0.0, UpdtLsn=0.0.0 ===> Bit Offset = 454
> (80) Generating SM Context Report:
> (80)  *** no sessions found ***
> (52) Generating SM Context Report:
> (52)  *** no sessions found ***
> (52)   procNum=9, status=Examined 2684470 objects, deleting 365892 backup
> objects, 99 archive objects, 0 DB backup volumes, 0 recovery plan files;
0
> errors encountered.
> , cancelInProgress=False
> (52)   descr=Expiration, name=EXPIRE INVENTORY, cancelled=False
> (36) Generating SM Context Report:
> (36)  *** no sessions found ***
> (62) Generating SM Context Report:
> (62)  *** no sessions found ***
> (62)   procNum=8, status=Disk Storage Pool WINDOWS, Moved Files: 12914,
> Moved Bytes: 9,273,446,400, Unreadable Files: 0, Unreadable Bytes: 0.
> Current Physical File (bytes): 12,546,048 Current output volume: T01486.
,
> cancelInProgress=False
> (62)   descr=Migration, name=MIGRATION, cancelled=False
> No session or process assoicated with this transaction can be located, or
> one or more session and process found.
>
>  Process Process Description  Status
>
>   Number
>  
> -
>8 MigrationDisk Storage Pool WINDOWS, Moved Files:
> 12914,
>Moved Bytes: 9,273,446,400, Unreadable
> Files: 0,
>Unreadable Bytes: 0. Current Physical File
>
>(bytes): 12,546,048 Current output volume:
>
>T01486.
>
>9 Expiration   Examined 2688075 objects, deleting 365892
> backup
>objects, 99 archive objects, 0 DB backup
>
>volumes, 0 recovery plan files; 0 errors
>
>encountered.
>
>
> 
> Joni Moyer
> Highmark
> Storage Systems, Senior Systems Programmer
> Phone Number: (717)302-9966
> Fax: (717) 302-9826
> [EMAIL PROTECTED]
> 

Re: 3584 checkin/checkout

[Kauffman, Tom]

What I was thinking, also.

In our shop, he who stuffs tapes into I/O port runs checkin -- and
whoever runs the checkout is responsible for stripping the tapes out of
the port, putting them in those neat little plastic boxes, and stuffing
same into the transport case.

Tom Kauffman

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Jim Zajkowski
Sent: Thursday, May 04, 2006 2:10 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: 3584 checkin/checkout

On Thu, 4 May 2006, Jurjen Oskam wrote:

> Yeah, but when you enter this command and the library door is NOT
> closed, all you library operations will hang until the door is
> closed.

People leave their IO doors open?

--Jim
CONFIDENTIALITY NOTICE:  This email and any attachments are for the 
exclusive and confidential use of the intended recipient.  If you are not
the intended recipient, please do not read, distribute or take action in 
reliance upon this message. If you have received this in error, please 
notify us immediately by return email and promptly delete this message 
and its attachments from your computer system. We do not waive  
attorney-client or work product privilege by the transmission of this
message.

Re: Log pinning issue, not quite sure what's going on...

[Joni Moyer]

Hey Everyone,

As an update, I have checked the firmware levels of the drives and they are
all the same and I have also checked the attributes on the drives and they
are the same as well.   Also, we have an SL8500 STK library housing the
LTO2 drives.  I am at a loss at this point in time as to what might be
causing this issue.

Gresham just allows me to share the library between our 2 TSM servers.  It
has the drive definitions in them, but they have not been modified, so that
shouldn't effect this issue.

If anyone has other suggestions I am open to listen to them.  This problem
has me stumped.

Thanks Richard for your suggestions on checking the drive firmware level
and the attributes!


Joni Moyer
Highmark
Storage Systems, Senior Systems Programmer
Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]




 "Richard Sims"
 <[EMAIL PROTECTED]>
To
 05/04/2006 01:49  "Joni Moyer"
 PM<[EMAIL PROTECTED]>
cc

   Subject
   Re: Log pinning issue, not quite
   sure what's going on...










Joni - I don't have your drive type or Gresham; but whereas it seems
like
a certain drive, I would compare its firmware level with that of
its companion drives and see if any difference.

Beyond that, I would inspect recent migration statistics and see if that
drive seems to be a lot slower than the others, for some reason.
Another thing I'd do, at least for my own curiosity, would be like
'lsattr -El rmt0' and see if all the drives exhibit the same attributes:
TSM should be setting them the same, but something might interfere that
I'm not familiar with (Gresham?).

 Richard Sims

On May 4, 2006, at 1:32 PM, Joni Moyer wrote:

> Hello everyone,
>
> Earlier in the week I had an issue with the log being pinned by a
> migration
> task.  I have thus experienced the issue again this morning and it
> appears
> as if another migration task has it pinned again.  The weird thing
> is that
> in all cases the migration task that has it pinned it the same
> drive each
> time.  It just seems to sit there and does not continue after a
> certain
> point in time.
>
> I have a TSM 5.2.1.7 server on AIX 5.2 which runs Gresham EDT
> 7.4.0.5 with
> ACSLS 7.1.0.24 and LTO2 tape drives.  We have had the drive
> replaced today,
> but I am still seeing this bizarre issue happening with the
> migration task
> and that particular drive.
>
> Does anyone have any suggestions/ideas?
>
> And also, I will be changing this recovery log to rollforward mode
> within
> the next day.  Thanks for the suggestion Richard!
>
>   Sess Comm.  Sess Wait   Bytes   Bytes Sess  Platform Client Name
>
> Number Method StateTimeSent   Recvd Type
> -- -- -- -- --- --- - 
> 
> 11 Tcp/Ip Run  0 S   10.9 K  30.7 G Node  WinNTHMCH1143
>
> 54 Tcp/Ip IdleW0 S4.6 K   4.8 K Node  WinNTHMCH1143
>
>  2,004 Tcp/Ip Run  0 S0  42 Admin WebCons  DCOPS
>
>ole
>
>  2,295 Tcp/Ip IdleW   32 S1.3 G   1.2 K Node  TDP  LNPITTA02
>
>Domino
>
>AIX
>
>  2,466 HTTP   Run  0 S0   0 Admin WebBrow  LIDZR8V
>
>ser
>
>
> Dirty page Lsn=5493127.198.1518, Last DB backup Lsn=5493128.7.1110,
> Transaction table Lsn=5491887.53.2214, Running DB backup Lsn=0.0.0,
> Log
> truncation Lsn=5491887.53.2214
>
> Lsn=5491887.53.2214, Owner=DB, Length=56
> Type=Update, Flags=82, Action=SetIcb, Page=5543936, Tsn=0:2734908799,
> PrevLsn=0.0.0, UndoNextLsn=0.0.0, UpdtLsn=0.0.0 ===> Bit Offset = 454
> (80) Generating SM Context Report:
> (80)  *** no sessions found ***
> (52) Generating SM Context Report:
> (52)  *** no sessions found ***
> (52)   procNum=9, status=Examined 2684470 objects, deleting 365892
> backup
> objects, 99 archive objects, 0 DB backup volumes, 0 recovery plan
> files; 0
> errors encountered.
> , cancelInProgress=False
> (52)   descr=Expiration, name=EXPIRE INVENTORY, cancelled=False
> (36) Generating SM Context Report:
> (36)  *** no sessions found ***
> (62) Generating SM Context Report:
> (62)  *** no sessions found ***
> (62)   procNum=8, status=Disk Storage Pool WINDOWS, Moved Files:
> 12914,
> Moved Bytes: 9,273,446,400, Unreadable Files: 0, Unreadable Bytes: 0.
> Current Physical File (bytes): 12,546,048 Current output volume:
> T01486. ,
> cancelInProgress=False
> (62)   descr=Migration, name=MIGRATION, cancelled=Fa

Re: Log pinning issue, not quite sure what's going on...

[Talafous, John]

Joni,
  Have a close look at Sessions 11 and 54 from Client Node HMCH1143.
Looks to be running a long time and the TSM Server has received over
30GB of data.
  My $0.02 says this is your culprit. What is this client doing and why?



John G. Talafous
Berbee Information Networks
http://www.berbee.com


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Thursday, May 04, 2006 1:32 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Log pinning issue, not quite sure what's going on...

Hello everyone,

Earlier in the week I had an issue with the log being pinned by a
migration task.  I have thus experienced the issue again this morning
and it appears as if another migration task has it pinned again.  The
weird thing is that in all cases the migration task that has it pinned
it the same drive each time.  It just seems to sit there and does not
continue after a certain point in time.

I have a TSM 5.2.1.7 server on AIX 5.2 which runs Gresham EDT 7.4.0.5
with ACSLS 7.1.0.24 and LTO2 tape drives.  We have had the drive
replaced today, but I am still seeing this bizarre issue happening with
the migration task and that particular drive.

Does anyone have any suggestions/ideas?

And also, I will be changing this recovery log to rollforward mode
within the next day.  Thanks for the suggestion Richard!

  Sess Comm.  Sess Wait   Bytes   Bytes Sess  Platform Client Name

Number Method StateTimeSent   Recvd Type
-- -- -- -- --- --- - 

11 Tcp/Ip Run  0 S   10.9 K  30.7 G Node  WinNTHMCH1143

54 Tcp/Ip IdleW0 S4.6 K   4.8 K Node  WinNTHMCH1143

 2,004 Tcp/Ip Run  0 S0  42 Admin WebCons  DCOPS

   ole

 2,295 Tcp/Ip IdleW   32 S1.3 G   1.2 K Node  TDP  LNPITTA02

   Domino

   AIX

 2,466 HTTP   Run  0 S0   0 Admin WebBrow  LIDZR8V

   ser


Dirty page Lsn=5493127.198.1518, Last DB backup Lsn=5493128.7.1110,
Transaction table Lsn=5491887.53.2214, Running DB backup Lsn=0.0.0, Log
truncation Lsn=5491887.53.2214

Lsn=5491887.53.2214, Owner=DB, Length=56 Type=Update, Flags=82,
Action=SetIcb, Page=5543936, Tsn=0:2734908799, PrevLsn=0.0.0,
UndoNextLsn=0.0.0, UpdtLsn=0.0.0 ===> Bit Offset = 454
(80) Generating SM Context Report:
(80)  *** no sessions found ***
(52) Generating SM Context Report:
(52)  *** no sessions found ***
(52)   procNum=9, status=Examined 2684470 objects, deleting 365892
backup
objects, 99 archive objects, 0 DB backup volumes, 0 recovery plan files;
0 errors encountered.
, cancelInProgress=False
(52)   descr=Expiration, name=EXPIRE INVENTORY, cancelled=False
(36) Generating SM Context Report:
(36)  *** no sessions found ***
(62) Generating SM Context Report:
(62)  *** no sessions found ***
(62)   procNum=8, status=Disk Storage Pool WINDOWS, Moved Files: 12914,
Moved Bytes: 9,273,446,400, Unreadable Files: 0, Unreadable Bytes: 0.
Current Physical File (bytes): 12,546,048 Current output volume: T01486.
, cancelInProgress=False
(62)   descr=Migration, name=MIGRATION, cancelled=False
No session or process assoicated with this transaction can be located,
or one or more session and process found.

 Process Process Description  Status

  Number
 
-
   8 MigrationDisk Storage Pool WINDOWS, Moved Files:
12914,
   Moved Bytes: 9,273,446,400, Unreadable
Files: 0,
   Unreadable Bytes: 0. Current Physical
File

   (bytes): 12,546,048 Current output
volume:

   T01486.

   9 Expiration   Examined 2688075 objects, deleting 365892
backup
   objects, 99 archive objects, 0 DB backup

   volumes, 0 recovery plan files; 0 errors

   encountered.



Joni Moyer
Highmark
Storage Systems, Senior Systems Programmer Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]

Re: 3584 checkin/checkout

[Jim Zajkowski]

On Thu, 4 May 2006, Jurjen Oskam wrote:


Yeah, but when you enter this command and the library door is NOT
closed, all you library operations will hang until the door is
closed.


People leave their IO doors open?

--Jim

Log pinning issue, not quite sure what's going on...

[Joni Moyer]

Hello everyone,

Earlier in the week I had an issue with the log being pinned by a migration
task.  I have thus experienced the issue again this morning and it appears
as if another migration task has it pinned again.  The weird thing is that
in all cases the migration task that has it pinned it the same drive each
time.  It just seems to sit there and does not continue after a certain
point in time.

I have a TSM 5.2.1.7 server on AIX 5.2 which runs Gresham EDT 7.4.0.5 with
ACSLS 7.1.0.24 and LTO2 tape drives.  We have had the drive replaced today,
but I am still seeing this bizarre issue happening with the migration task
and that particular drive.

Does anyone have any suggestions/ideas?

And also, I will be changing this recovery log to rollforward mode within
the next day.  Thanks for the suggestion Richard!

  Sess Comm.  Sess Wait   Bytes   Bytes Sess  Platform Client Name

Number Method StateTimeSent   Recvd Type
-- -- -- -- --- --- - 

11 Tcp/Ip Run  0 S   10.9 K  30.7 G Node  WinNTHMCH1143

54 Tcp/Ip IdleW0 S4.6 K   4.8 K Node  WinNTHMCH1143

 2,004 Tcp/Ip Run  0 S0  42 Admin WebCons  DCOPS

   ole

 2,295 Tcp/Ip IdleW   32 S1.3 G   1.2 K Node  TDP  LNPITTA02

   Domino

   AIX

 2,466 HTTP   Run  0 S0   0 Admin WebBrow  LIDZR8V

   ser


Dirty page Lsn=5493127.198.1518, Last DB backup Lsn=5493128.7.1110,
Transaction table Lsn=5491887.53.2214, Running DB backup Lsn=0.0.0, Log
truncation Lsn=5491887.53.2214

Lsn=5491887.53.2214, Owner=DB, Length=56
Type=Update, Flags=82, Action=SetIcb, Page=5543936, Tsn=0:2734908799,
PrevLsn=0.0.0, UndoNextLsn=0.0.0, UpdtLsn=0.0.0 ===> Bit Offset = 454
(80) Generating SM Context Report:
(80)  *** no sessions found ***
(52) Generating SM Context Report:
(52)  *** no sessions found ***
(52)   procNum=9, status=Examined 2684470 objects, deleting 365892 backup
objects, 99 archive objects, 0 DB backup volumes, 0 recovery plan files; 0
errors encountered.
, cancelInProgress=False
(52)   descr=Expiration, name=EXPIRE INVENTORY, cancelled=False
(36) Generating SM Context Report:
(36)  *** no sessions found ***
(62) Generating SM Context Report:
(62)  *** no sessions found ***
(62)   procNum=8, status=Disk Storage Pool WINDOWS, Moved Files: 12914,
Moved Bytes: 9,273,446,400, Unreadable Files: 0, Unreadable Bytes: 0.
Current Physical File (bytes): 12,546,048 Current output volume: T01486. ,
cancelInProgress=False
(62)   descr=Migration, name=MIGRATION, cancelled=False
No session or process assoicated with this transaction can be located, or
one or more session and process found.

 Process Process Description  Status

  Number
 
-
   8 MigrationDisk Storage Pool WINDOWS, Moved Files:
12914,
   Moved Bytes: 9,273,446,400, Unreadable
Files: 0,
   Unreadable Bytes: 0. Current Physical File

   (bytes): 12,546,048 Current output volume:

   T01486.

   9 Expiration   Examined 2688075 objects, deleting 365892
backup
   objects, 99 archive objects, 0 DB backup

   volumes, 0 recovery plan files; 0 errors

   encountered.



Joni Moyer
Highmark
Storage Systems, Senior Systems Programmer
Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]

Re: 3584 checkin/checkout

[John Monahan]

 "ADSM: Dist Stor Manager"  wrote on 05/04/2006
11:24:56 AM:

> On Thu, May 04, 2006 at 10:24:14AM -0400, Jim Zajkowski wrote:
>
>[scsi library]
> > In 5.3, you can say checkin libv waitt=0 and it will not bother to
> > generate a prompt, it will just do it.  Handy.
>
> Yeah, but when you enter this command and the library door is NOT
> closed, all you library operations will hang until the door is
> closed. So you might want to require a manual action when kicking
> off this command.
>
> (The way I solved this is to check for the "library requires manual
> attention" error. If it occurs, scream loudly. :) )
>
> --

The whole point of using scripts is so you don't have any manual tasks
*unless* something is wrong.  I would consider an open library door as
something being wrong.

Automation scripts also won't work if someone powers off the library.
Seriously, you can't expect a TSM admin to write automation scripts to
cover every possible instance of human error.  Technology can't fix
stupid.

Re: 3584 checkin/checkout

[Jurjen Oskam]

On Thu, May 04, 2006 at 10:24:14AM -0400, Jim Zajkowski wrote:

[scsi library]
> In 5.3, you can say checkin libv waitt=0 and it will not bother to
> generate a prompt, it will just do it.  Handy.

Yeah, but when you enter this command and the library door is NOT
closed, all you library operations will hang until the door is
closed. So you might want to require a manual action when kicking
off this command.

(The way I solved this is to check for the "library requires manual
attention" error. If it occurs, scream loudly. :) )

--
Jurjen Oskam

Savage's Law of Expediency:
You want it bad, you'll get it bad.

Re: Auditing Tools

[Doug Fox]

Awesome thanks!

I'll have plenty of things to look at now :)

On 5/4/06, Mark Stapleton <[EMAIL PROTECTED]> wrote:


"ADSM: Dist Stor Manager"  wrote on 05/04/2006
09:07:45 AM:
> Would there be easy ways to get the following informaiton?
>
> Query a storage pool to see what schedules are defaulted to it.

There is no one-to-one relationship between a storage pool and client
schedules. Client schedules are defined within a domain, and a storage
pool is not. The QUERY ASSOCIATION will tell you what client schedules are
linked with what nodes.

> Query a storage pool to see when it migrates during the day/week.

The TSM OR tool by default has a handy graph that will tell you when
migrations go on. Message ANR1000I in the server activity log will tell
you when a given storage pool's migration has started, but the the
analogous message for a migration's completion (ANR1001I) doesn't mention
how much data was moved; the accompanying (generic) message ANR0986I tells
you a migration is complete, and its size, but not the storage pools that
were involved.

> Query the library to find out the size of the last backup for x node(s).
> This to my knowledge you can only check client side, but does the server
> track the size of backups?

On an AIX TSM server, the /usr/tivoli/tsm/server/bin/dsmaccnt.log is a
comma-delimited file that breaks down client activity by node and
date/time.

--
Mark Stapleton ([EMAIL PROTECTED])
MR Backup and Recovery Management
262.790.3190

--
Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by electronic communications privacy
laws, and is also confidential and proprietary in nature. If you are not the
intended recipient, please be advised that you are legally prohibited from
retaining, using, copying, distributing, or otherwise disclosing this
information in any manner. Instead, please reply to the sender that you have
received this communication in error, and then immediately delete it. Thank
you in advance for your cooperation.

==

Re: Auditing Tools

[Mark Stapleton]

"ADSM: Dist Stor Manager"  wrote on 05/04/2006
09:07:45 AM:
> Would there be easy ways to get the following informaiton?
>
> Query a storage pool to see what schedules are defaulted to it.

There is no one-to-one relationship between a storage pool and client
schedules. Client schedules are defined within a domain, and a storage
pool is not. The QUERY ASSOCIATION will tell you what client schedules are
linked with what nodes.

> Query a storage pool to see when it migrates during the day/week.

The TSM OR tool by default has a handy graph that will tell you when
migrations go on. Message ANR1000I in the server activity log will tell
you when a given storage pool's migration has started, but the the
analogous message for a migration's completion (ANR1001I) doesn't mention
how much data was moved; the accompanying (generic) message ANR0986I tells
you a migration is complete, and its size, but not the storage pools that
were involved.

> Query the library to find out the size of the last backup for x node(s).
> This to my knowledge you can only check client side, but does the server
> track the size of backups?

On an AIX TSM server, the /usr/tivoli/tsm/server/bin/dsmaccnt.log is a
comma-delimited file that breaks down client activity by node and
date/time.

--
Mark Stapleton ([EMAIL PROTECTED])
MR Backup and Recovery Management
262.790.3190
--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==

Re: Auditing Tools

[Doug Fox]

Sorry for lack of information.

TSM is on AIX 5.3

We do have the TSM operational reporter. I will have to spend some time with
that. There any sites that would have custom scripts or are all of the
things I'm looking for pretty much built in?

Thanks again for your help :)

On 5/4/06, Bos, Karel <[EMAIL PROTECTED]> wrote:


Q system?

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Doug Fox
Sent: donderdag 4 mei 2006 16:08
To: ADSM-L@VM.MARIST.EDU
Subject: Auditing Tools

Hello,

I was put in charge of a large TSM system and I would like to perform an
audit. I am looking for the following types of information and I was
wondering if there's an easy or automated way of having this generated
for me. I would like to use a minimal amount of commands to get results
from the entire system. In other words, I don' t want to have to go to
every node and research them. I'd like to map out both my schedules and
my pools with the nodes.

Would there be easy ways to get the following informaiton?

Query a storage pool to see what schedules are defaulted to it.

Query a storage pool to see when it migrates during the day/week.

Query a storage pool to see how much data is backed up to it
daily/weekly.

Query the library to find out the size of the last backup for x node(s).
This to my knowledge you can only check client side, but does the server
track the size of backups? (ex. server 1 backs up 125GB on a full
backup) does the server keep track of this at all or do I have to check
client log files for this info?

I've heard that using TSM Reporter can get most of this information. Are
there any user-made scripts that I can look for, since I'm not familiar
with complex SQL Scripts. ANY information you could toss my way would be
greatly appreciated. We're in the midst of transferring ownership and I
would like to know when things are being backed up, where, and how big
they are etc. I think any TSM admin woudl want this ;)

Thanks in advance, I realize this is a large request and I apologize.

-Doug Fox

Re: 3584 checkin/checkout

[Jim Zajkowski]

On Thu, 4 May 2006, Kauffman, Tom wrote:


The checkin script runs a 'checkin libv  search=bulk
checklabel=barcode stat=pri', does a 'reply' to the tsm-generated
prompt, and updates each volume as it is checked in to an access of
'readw'. We fill the I/O port and run the script; if there are more than
32 tapes to process, we do it a second time.


In 5.3, you can say checkin libv waitt=0 and it will not bother to
generate a prompt, it will just do it.  Handy.

--Jim

Re: Auditing Tools

[Bos, Karel]

Q system?

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Doug Fox
Sent: donderdag 4 mei 2006 16:08
To: ADSM-L@VM.MARIST.EDU
Subject: Auditing Tools

Hello,

I was put in charge of a large TSM system and I would like to perform an
audit. I am looking for the following types of information and I was
wondering if there's an easy or automated way of having this generated
for me. I would like to use a minimal amount of commands to get results
from the entire system. In other words, I don' t want to have to go to
every node and research them. I'd like to map out both my schedules and
my pools with the nodes.

Would there be easy ways to get the following informaiton?

Query a storage pool to see what schedules are defaulted to it.

Query a storage pool to see when it migrates during the day/week.

Query a storage pool to see how much data is backed up to it
daily/weekly.

Query the library to find out the size of the last backup for x node(s).
This to my knowledge you can only check client side, but does the server
track the size of backups? (ex. server 1 backs up 125GB on a full
backup) does the server keep track of this at all or do I have to check
client log files for this info?

I've heard that using TSM Reporter can get most of this information. Are
there any user-made scripts that I can look for, since I'm not familiar
with complex SQL Scripts. ANY information you could toss my way would be
greatly appreciated. We're in the midst of transferring ownership and I
would like to know when things are being backed up, where, and how big
they are etc. I think any TSM admin woudl want this ;)

Thanks in advance, I realize this is a large request and I apologize.

-Doug Fox

Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel
bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd,
verzoeken wij u dit onmiddellijk aan ons te melden en het bericht te
vernietigen.
Aangezien de integriteit van het bericht niet veilig gesteld is middels
verzending via internet, kan Atos Origin niet aansprakelijk worden gehouden
voor de inhoud daarvan.
Hoewel wij ons inspannen een virusvrij netwerk te hanteren, geven
wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden wij
enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit
bericht.
 
Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten waaronder
Atos Origin goederen en/of diensten levert zijn met uitsluiting van alle
andere voorwaarden de Leveringsvoorwaarden van Atos Origin van toepassing.
Deze worden u op aanvraag direct kosteloos toegezonden.
 
This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail
in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender
does not warrant that this transmission is virus-free and will not be
liable for any damages resulting from any virus transmitted.
 
On all offers and agreements under which Atos Origin supplies goods and/or
services of whatever nature, the Terms of Delivery from Atos Origin
exclusively apply. 
The Terms of Delivery shall be promptly submitted to you on your request.

Re: 3584 checkin/checkout

[Smith, I (Ian)]

 
If you set up the snmp alerting from the library- it will send a trap
when the bulk IO loader is full.

_
Ian Smith



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bill Kelly
Sent: 04 May 2006 13:34
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] 3584 checkin/checkout

Both of these processes require scripting in order to automate things to
the point that the 3584 appears more 3494-ish.  We use a perl script to
kick off the 'move drm' command (or 'checkout libv' command, take your
pick) and monitor the TSM server messages via a dsmadmc -consolemode
session.  If the script sees a message indicating that the I/O bin is
full, we issue a message to the operator running the script and wait for
them to indicate that it's okay to proceed.

On the checkin side, I don't think you can have the 3584 automagically
move tapes from the I/O bin to empty slots (and if you could, I don't
think the library would tell TSM where they are...and how would either
the library or TSM know whether the tapes are private or scratch?).
Again, we script this, having the script do 'move drm' commands for
specific volumes to be checked in, issuing a 'checkin libv' command and
monitoring the server log for success/failure messages.

With SCSI-type tape libraries, there's a lot more work to be done by
people and/or scripts than there is with a 3494.

Regards,
Bill

Bill Kelly
Auburn University OIT
334-844-9917

>>> "Gill, Geoffrey L." <[EMAIL PROTECTED]> 05/03/06 11:32 PM
>>>
I'm wondering if I'm missing anything in our setup of the 3584 as it
relates to incoming and outgoing tapes. Currently the mainframe sends
alerts to the operators when the I/O port is full on the 3494 and needs
emptying.
Once
empty the checkout of tapes can continues. I was wondering how others
manage that on a 3584. Is there a way to send alerts when the port is
full?
I'd
hate to come in and find all the tapes were not ejected because the job
could not continue.



Second question relates to checking in tapes. On the 3494 you can insert
tapes to the I/O port and it automatically empties it and put tapes into
empty slots. I don't see this available with a 3584, but easily could
have missed it, so I'm wondering if there is a way to change a setting
on the library or automate this.



Thanks,



Geoff Gill

TSM Administrator

PeopleSoft Sr. Systems Administrator

SAIC M/S-G1b

(858)826-4062

Email:   [EMAIL PROTECTED]
_

This email (including any attachments to it) is confidential, legally 
privileged, subject to copyright and is sent for the personal attention of the 
intended recipient only. If you have received this email in error, please 
advise us immediately and delete it. You are notified that disclosing, copying, 
distributing or taking any action in reliance on the contents of this 
information is strictly prohibited. Although we have taken reasonable 
precautions to ensure no viruses are present in this email, we cannot accept 
responsibility for any loss or damage arising from the viruses in this email or 
attachments. We exclude any liability for the content of this email, or for the 
consequences of any actions taken on the basis of the information provided in 
this email or its attachments, unless that information is subsequently 
confirmed in writing. If this email contains an offer, that should be 
considered as an invitation to treat.
_

Re: AIX Client Restore question

[Bos, Karel]

TESTFLAGDISABLENQR ??

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: donderdag 4 mei 2006 16:06
To: ADSM-L@VM.MARIST.EDU
Subject: Re: AIX Client Restore question

Interesting situation, David.

I have not encountered any client controls for Restartable Restore
(supported or otherwise): it is implicit, and always in effect (for
NQR).

One way to address the issue is to reduce your server RESTOREINTERVAL
value. This is the simplest solution.

Another is for you or your AIX admin to render the restore interface
command more sophisticated...to have the dsmc run as a child of a
control process which intercepts Ctrl-C (SIGINT) to then cancel the
restore (which is non-trivial, given the client interface to this task).

On the server side, you might have a cron job check for lingering RRs
before the backups window, to dispose of them.

Richard Sims

On May 4, 2006, at 9:26 AM, David Browne wrote:

> My AIX admin has created a script for some of our users on our AIX 
> clients to run a restore command.
>  One of the users canceled the restore leaving a pending restartable 
> restore. This caused the backup to fail last night.
> Is there a parm for the Unix client to say restartable restore=no?

Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel
bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd,
verzoeken wij u dit onmiddellijk aan ons te melden en het bericht te
vernietigen.
Aangezien de integriteit van het bericht niet veilig gesteld is middels
verzending via internet, kan Atos Origin niet aansprakelijk worden gehouden
voor de inhoud daarvan.
Hoewel wij ons inspannen een virusvrij netwerk te hanteren, geven
wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden wij
enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit
bericht.
 
Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten waaronder
Atos Origin goederen en/of diensten levert zijn met uitsluiting van alle
andere voorwaarden de Leveringsvoorwaarden van Atos Origin van toepassing.
Deze worden u op aanvraag direct kosteloos toegezonden.
 
This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail
in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender
does not warrant that this transmission is virus-free and will not be
liable for any damages resulting from any virus transmitted.
 
On all offers and agreements under which Atos Origin supplies goods and/or
services of whatever nature, the Terms of Delivery from Atos Origin
exclusively apply. 
The Terms of Delivery shall be promptly submitted to you on your request.

Auditing Tools

[Doug Fox]

Hello,

I was put in charge of a large TSM system and I would like to perform an
audit. I am looking for the following types of information and I was
wondering if there's an easy or automated way of having this generated for
me. I would like to use a minimal amount of commands to get results from the
entire system. In other words, I don' t want to have to go to every node and
research them. I'd like to map out both my schedules and my pools with the
nodes.

Would there be easy ways to get the following informaiton?

Query a storage pool to see what schedules are defaulted to it.

Query a storage pool to see when it migrates during the day/week.

Query a storage pool to see how much data is backed up to it daily/weekly.

Query the library to find out the size of the last backup for x node(s).
This to my knowledge you can only check client side, but does the server
track the size of backups? (ex. server 1 backs up 125GB on a full backup)
does the server keep track of this at all or do I have to check client log
files for this info?

I've heard that using TSM Reporter can get most of this information. Are
there any user-made scripts that I can look for, since I'm not familiar with
complex SQL Scripts. ANY information you could toss my way would be greatly
appreciated. We're in the midst of transferring ownership and I would like
to know when things are being backed up, where, and how big they are etc. I
think any TSM admin woudl want this ;)

Thanks in advance, I realize this is a large request and I apologize.

-Doug Fox

Re: AIX Client Restore question

[Richard Sims]

Interesting situation, David.

I have not encountered any client controls for Restartable Restore
(supported or otherwise): it is implicit, and always in effect (for
NQR).

One way to address the issue is to reduce your server RESTOREINTERVAL
value. This is the simplest solution.

Another is for you or your AIX admin to render the restore interface
command more sophisticated...to have the dsmc run as a child of a
control process which intercepts Ctrl-C (SIGINT) to then cancel the
restore (which is non-trivial, given the client interface to this task).

On the server side, you might have a cron job check for lingering RRs
before the backups window, to dispose of them.

   Richard Sims

On May 4, 2006, at 9:26 AM, David Browne wrote:


My AIX admin has created a script for some of our users on our AIX
clients
to run a restore command.
 One of the users canceled the restore leaving a pending restartable
restore. This caused the backup to fail last night.
Is there a parm for the Unix client to say restartable restore=no?

Scripting the Halt Command

[Barnes, Kenny]

Anyone have a script for halting TSM from Cron?  I want to scheduler TSM
starts. 
TSM 5.3 running on Solaris 9
 
Kenny Barnes
Enterprise Storage Team
GMAC Insurance
336-770-8280
[EMAIL PROTECTED]
 

--
Note:  The information contained in this message may be privileged and 
confidential
and protected from disclosure.  If the reader of this message is not the 
intended recipient,
or an employee or agent responsible for delivering this message to the intended 
recipient,
you are hereby notified that any dissemination, distribution or copying of this 
communication
is strictly prohibited.  If you have received this communication in error, 
please notify us 
immediately by replying to the message and deleting it from your computer.  
Thank you.
--

Constant / new errors with Netware 6.0 servers and 5.2.4.x client

[Zoltan Forray/AC/VCU]

We are having constant problems with Netware 6.0 server backups, since 
installing the latest supported clients (5.2.4.10) on these systems.  The 
errors/problems were not seen before with the older clients.  We also 
moved these systems to a newer TSM server (Linux 5.3.2 vs z/OS 5.2).

We are constantly getting message like:

VCUL-NW1.ULS.VCU.EDU : ANE4005E Error processing 'USERDATA:/My 
Guidarelli/mguidare/Application Data/Microsoft/Office/Recent/Com g?y qu- 
ch-a Hu- Quang.ppt.LNK': file not found(SESSION: 51910)
VCUL-NW1.ULS.VCU.EDU : 

These I realize are probably files using a different language or have 
funky characters.  How do you handle these ?

But this other one is driving me crazy.  We get this on almost *EVERY* 
file it tries to backup.   It also seems to ignore my EXCLUDE statements 
since I get these errors for directories/files I have completely excluded 
(both by file name and EXCLUDE.DIR).

DEN1A.VCU.EDU : ANE4007E Error processing 'SYS:/6sp2/nw6sp2/TOOLS.TXT': 
access to the object is denied (SESSION: 60035) 

I have checked all rights of the NDS userid configured for this (and other 
systems) and they have the proper/full rights. Tried reinstalling numerous 
times (always doing the DSMC Q TSA and TSA NDS which both say they are 
happy).  Still no success.

Also getting lots of "stream" error messages in the error logs.

The TSANDS/TSA600 files are the most up to date, available !

What gives ?

Fw: 3584 checkin/checkout

[Nicholas Cassimatis]

What about using the "remove=untileefull" parameter on the "move drm"
command?  Fills the IO slots, then stops.  After the IO door is cleared,
you can rerun the command to continue ejecting tapes.

Nick Cassimatis
email: [EMAIL PROTECTED]

AIX Client Restore question

[David Browne]

My AIX admin has created a script for some of our users on our AIX clients
to run a restore command.
 One of the users canceled the restore leaving a pending restartable
restore. This caused the backup to fail last night.
Is there a parm for the Unix client to say restartable restore=no?


The information transmitted is intended only for the person or entity to which 
it is addressed and may contain CONFIDENTIAL material.  If you receive this 
material/information in error, please contact the sender and delete or destroy 
the material/information.

Re: 3584 checkin/checkout

[Kauffman, Tom]

The 3584 is pretty much an automatic tape mounter with bulk storage and
no real 'smarts'. If you want it to do something, you need to tell it.

I've got two perl scripts I use for checkout and checkin. The checkout
script finds all copy pool tapes with data on them and checks them out
(we don't use drm), updating the access to 'offsite' as it goes. It
pauses and waits for an 'enter' if there are more than 32 tapes to come
out -- we have the second I/O port -- and the assumption is that we
check out tapes just prior to taking them off-site.

The checkin script runs a 'checkin libv  search=bulk
checklabel=barcode stat=pri', does a 'reply' to the tsm-generated
prompt, and updates each volume as it is checked in to an access of
'readw'. We fill the I/O port and run the script; if there are more than
32 tapes to process, we do it a second time.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Gill, Geoffrey L.
Sent: Thursday, May 04, 2006 12:32 AM
To: ADSM-L@VM.MARIST.EDU
Subject: 3584 checkin/checkout

I'm wondering if I'm missing anything in our setup of the 3584 as it
relates
to incoming and outgoing tapes. Currently the mainframe sends alerts to
the
operators when the I/O port is full on the 3494 and needs emptying. Once
empty the checkout of tapes can continues. I was wondering how others
manage
that on a 3584. Is there a way to send alerts when the port is full? I'd
hate to come in and find all the tapes were not ejected because the job
could not continue.



Second question relates to checking in tapes. On the 3494 you can insert
tapes to the I/O port and it automatically empties it and put tapes into
empty slots. I don't see this available with a 3584, but easily could
have
missed it, so I'm wondering if there is a way to change a setting on the
library or automate this.



Thanks,



Geoff Gill

TSM Administrator

PeopleSoft Sr. Systems Administrator

SAIC M/S-G1b

(858)826-4062

Email:   [EMAIL PROTECTED]
CONFIDENTIALITY NOTICE:  This email and any attachments are for the 
exclusive and confidential use of the intended recipient.  If you are not
the intended recipient, please do not read, distribute or take action in 
reliance upon this message. If you have received this in error, please 
notify us immediately by return email and promptly delete this message 
and its attachments from your computer system. We do not waive  
attorney-client or work product privilege by the transmission of this
message.

Re: 3584 checkin/checkout

[Bill Kelly]

Both of these processes require scripting in order to automate things to
the point that the 3584 appears more 3494-ish.  We use a perl script to
kick off the 'move drm' command (or 'checkout libv' command, take your
pick) and monitor the TSM server messages via a dsmadmc -consolemode
session.  If the script sees a message indicating that the I/O bin is
full, we issue a message to the operator running the script and wait for
them to indicate that it's okay to proceed.

On the checkin side, I don't think you can have the 3584 automagically
move tapes from the I/O bin to empty slots (and if you could, I don't
think the library would tell TSM where they are...and how would either
the library or TSM know whether the tapes are private or scratch?).
Again, we script this, having the script do 'move drm' commands for
specific volumes to be checked in, issuing a 'checkin libv' command and
monitoring the server log for success/failure messages.

With SCSI-type tape libraries, there's a lot more work to be done by
people and/or scripts than there is with a 3494.

Regards,
Bill

Bill Kelly
Auburn University OIT
334-844-9917

>>> "Gill, Geoffrey L." <[EMAIL PROTECTED]> 05/03/06 11:32 PM
>>>
I'm wondering if I'm missing anything in our setup of the 3584 as it
relates
to incoming and outgoing tapes. Currently the mainframe sends alerts to
the
operators when the I/O port is full on the 3494 and needs emptying.
Once
empty the checkout of tapes can continues. I was wondering how others
manage
that on a 3584. Is there a way to send alerts when the port is full?
I'd
hate to come in and find all the tapes were not ejected because the
job
could not continue.



Second question relates to checking in tapes. On the 3494 you can
insert
tapes to the I/O port and it automatically empties it and put tapes
into
empty slots. I don't see this available with a 3584, but easily could
have
missed it, so I'm wondering if there is a way to change a setting on
the
library or automate this.



Thanks,



Geoff Gill

TSM Administrator

PeopleSoft Sr. Systems Administrator

SAIC M/S-G1b

(858)826-4062

Email:   [EMAIL PROTECTED]

TSM and SNMP agent

[Bernaldo de Quiros, Iban 1]

Hi World,

Did anyone know where to find the following information about TSM and the SNMP 
agent ¿?

-installation
-tune up
-others

Thanks in advance.

regards,

Ibán Bernaldo de Quirós Márquez 
Technical Specialist 
cell: + 34 659 01 91 12 
Sun Microsystems Iberia

Re: Client restores for NFS server backups

[Dirk Kastens]

Hi,


Question: if user smith logs on to nfsclient1, is there a way for
him to restore his own /home/smith files without knowing nfssrv1's
TSM password?


We have the same problem. Users have to call us to get their /home files
restored, because they don't have access to the backup server. The only
solution that I see is to write a restore script that hides the TSM
password from the users.

--
Regards,

Dirk Kastens
Universitaet Osnabrueck, Rechenzentrum (Computer Center)
Albrechtstr. 28, 49069 Osnabrueck, Germany
Tel.: +49-541-969-2347, FAX: -2470