Hi John,
First let me comment on yr first question/observation: "I am seeing times that a
TSM server has more tapes mounted than would be necessary for Administrative
tasks like migration and backup of storage pools." answer----> TSM (without
migration settings, client schedules, admin schedules, etc.) does not initiate
any jobs that will require mounting tapes and copying data etc. everything is
controlled by the configuration layout.
You might have a few issues in yr installation:
a) Looks like that your environment lacks of sufficient scheduling.
1) You need to start from your requirements, then evaluate your
existing resources (libraries, drives, tapes, network, etc.),
2) then prioritize the activities,
3) then create the schedules that have been designed on your
environment,
4) then run them for 1 to 3 weeks and monitor your server very
closely,
5) then go back and make any necessary adjustments to your scheduling
strategy,
(you might have to repeat steps 3 to 5 a couple times, until you get
the best fit setting.
b) Do you control the migration processes with administrative schedules or not ?
looks like that you don't...
What you can do is: create admin schedules that set the migration thresholds to
higher numbers like 89, 90, etc. and when you four tape drives are not busy,
then you set another set of admin schedules that will set the migration
threshold to zero and will start the migration processes.
c) Prioritization. You need to make the decision what activities have higher
priority, and use the scheduling time in conjunction with TSM's priorities
levels to accomplish your goal.
d) In a normal/standard TSM environment TSM operations need to occur in a
sequence that will satisfy yr customized requirements. Below is a basic sequence
of events that works...
1) Run your backups (Incr/Arch/TDPs/etc/). From 4:00-7:00 pm to something
like 1:00-3:00 am.
(You can also have TDP Databases' archive logs, and backups running
through out the whole day, but if you can control and influence... try to have
and set a recovery timeline or next day cutover point, especially if you are
using DRM and have offisite requirements and DR tests... "the works"... ).
2) Activate your migration processes and empty yr disk pools. From 2:00-3:00
am to 4:00-5:00 am.
3) Make copies (backup) of your tape storage pools (onsite/offsite). From
4:00-06:00 am to 07:00-10:00 am.
4) Make a database backup (offsite copy). Around 10:00 am.
5) Run your Disaster Recovery stuff (DRM)... if applicable.
6) Eject the DRM offsite tapes. Around 11:00 am.
7) Make another database backup (snapshot) to keep on site... if applicable.
Around 12:00 pm.
8) Expire inventory. Around 01:00 pm.
9) Start your "controlled" reclamation processes. Around 02:00 pm. If you
have two many storage pools, and you think that 3 to 5 hours is not enough for
your whole reclamation process, you might want to group yr storage pools and
spread them across the week ( 1 group on Mondays, 1 group on Tuesdays, etc.)
This last step will bring you to the 4:00 to 6:00 pm time frame, where you
nightly backups start, go back to step 1.
The above times are imaginary, but they work fine in most of our TSM
installations, again the scheduling times depend on your local customized backup
and restore requirements.
e) Limited resources. At the end of the day... you might realize that you don't
have enough resources to accommodate your requirements, then you have two
options: 1) either go back and modify or rethink yr business requirements, or 2)
add some extra $$$ on next year's budget and add more tape drives to your
library. Since, now you are getting 2 more tape drives... and you will have a
total of 6 tape drives, is a good opportunity to take some time and redesign
your TSM internal scheduling scheme. I always like to have an odd number of tape
drives: like 5 or 7 or 9 etc... because the backup storage pools processes
occupy 2 drives per process, so if you run 2 or 3 processes it will occupy all
your drives (2x2=4, 3x2=6,)... and you will not have any drives available for
any other TSM activities or restore requests... just a thought.
f) Network. The network is another great variable on your scheduling
environment, because if you have the best TSM structure and you have a poor
network then you will still have problems. I hope that you have dealt with the
network issue.
g) TSM and Operating System tuning. From what I see from the NT sessions some
ran for a long time, and is hard to identified by only the below report, but you
might have some tuning issues in your environment, provided that your network is
fast enough.
Finally, I don't think that there are classes that deal with customized
requirements and scheduling issues, however you might find consulting firms that
they can come in for a day or so and help you out.
Cheers.
Othonas
"Talafous, John G." wrote:
> This is more a TSM internal logic question than anything else. I am seeing
> times that a TSM server has more tapes mounted than would be necessary for
> Administrative tasks like migration and backup of storage pools. When and
> how does this happen?
>
> The details.... Looking at system queries for this particular instance, I
> can see that there is one migration task with an output tape volume in use
> and a backup stgpool task waiting for a mount point in devclass 3590-E1A.
> (Devclass 3590-E1A has a mount limit of DRIVES, which we have four (4).) So,
> I am thinking that three (3) client tasks are, in fact, utilizing physical
> tape drives. Notice also that there are twenty-three (23) client tasks with
> MediaW as the session state. We have not begun sending client data direct to
> tape because of the limited number of tape drives available. To date, this
> performance enhancement has not been an issue.
>
> What is TSM doing? How can I better understand and provide the best services
> with the resources I have? Are there TSM classes that deal with this type of
> concept?
>
> Environment is TSM 3.7.2 server on a 3466-C00 (AIX 4.3.2) with a 3494
> library containing four (4) 3590-E1A drives. (Soon to be increased by 2 more
> 3590-E1A drives and 144GB of SSA disk.)
>
> Here I include the results of four commands. Query STG, Q PRocesses, Q
> Mounts, Q SEsssions F=D.
>
> Thanks in advance for reviewing this long post...
>
> Tivoli Storage Manager
> Command Line Administrative Interface - Version 4, Release 1, Level 2.0
> (C) Copyright IBM Corporation, 1990, 1999, All Rights Reserved.
>
> Session established with server FSPHNSM1: AIX-RS/6000
> Server Version 3, Release 7, Level 2.0
> Server date/time: 03/04/2001 01:00:24 Last access: 03/04/2001 00:30:01
>
> Storage Device Estimated Pct Pct High
> Low Next Stora-
> Pool Name Class Name Capacity Util Migr Mig
> Mig ge Pool
> (MB) Pct
> Pct
> ----------- ---------- ---------- ----- ----- ----
> --- -----------
> ARCHIVE DISK 81,370.0 48.8 48.3 74
> 50 ARCHIVE_TA-
>
> PE
> ARCHIVE_CO- 3590-E1A 18,071,904 39.7
>
> PY .7
>
> ARCHIVE_TA- 3590-E1A 17,506,379 40.9 47.0 90
> 70
> PE .0
>
> DIR DISK 9,908.0 21.3 21.3 90
> 70 DIR_TAPE
> DIR_COPY 3590-E1A 200,000.0 0.7
>
> DIR_TAPE 3590-E1A 0.0 0.0 0.0 90
> 70
> DISKPOOL DISK 0.0 0.0 0.0 90
> 70
> SERVER DISK 250,777.0 80.6 79.8 74
> 50 SERVER_TAPE
> SERVER_COPY 3590-E1A 23,524,586 34.7
>
> .7
>
> SERVER_TAPE 3590-E1A 24,022,339 34.0 57.0 90
> 70
> .9
>
> WORKSTN DISK 9,231.0 60.5 60.5 90
> 50 WORKSTN_TA-
>
> PE
> WORKSTN_TA- 3590-E1A 1,290,919. 2.2 4.0 90
> 70
> PE 3
>
> Process Process Description Status
>
> Number
> -------- --------------------
> -------------------------------------------------
> 255 Migration Disk Storage Pool SERVER, Moved Files:
> 241, Moved
> Bytes: 141,957,177,344, Unreadable
> Files: 0,
> Unreadable Bytes: 0. Current Physical
> File
> (bytes): 4,570,263,552
>
> Current output volume: K20181.
>
> 257 Backup Storage Pool Primary Pool SERVER, Copy Pool
> SERVER_COPY, Files
> Backed Up: 0, Bytes Backed Up: 0,
> Unreadable
> Files: 0, Unreadable Bytes: 0.
> Current Physical
> File (bytes): 24,576
>
> Waiting for mount point in device
> class 3590-E1A
> (13 seconds).
>
> ANR8330I 3590 volume K20020 is mounted R/W in drive 3590DRIVE4 (/dev/rmt4),
> status: IN USE.
> ANR8330I 3590 volume K20181 is mounted R/W in drive 3590DRIVE2 (/dev/rmt2),
> status: IN USE.
> ANR8330I 3590 volume K20065 is mounted R/W in drive 3590DRIVE1 (/dev/rmt1),
> status: IN USE.
> ANR8330I 3590 volume K20314 is mounted R/W in drive 3590DRIVE3 (/dev/rmt3),
> status: IN USE.
> ANR8334I 4 volumes found.
>
> Sess Comm. Sess Wait Bytes Bytes Sess
> Platform Client Name Media Access Status
> User Name Date/Time First Data Sent
> Number Method State Time Sent Recvd Type
>
> ------ ------ ------ ------ ------- ------- -----
> -------- --------------------
> ---------------------------------------- --------------------
> ----------------------------------------
> 15,523 Tcp/Ip IdleW 8 S 142.7 K 4.3 M Node
> WinNT GNWHPAR02
>
> 16,143 Tcp/Ip RecvW 0 S 17.2 K 27.8 G Node
> WinNT GNWHPAR02
> 03/03/2001 10:30:22
> 16,369 Tcp/Ip IdleW 17.3 M 54.7 M 6.5 K Node
> AIX CTNHPM01
>
> 16,379 Tcp/Ip MediaW 17.3 M 2.1 K 9.7 G Node
> AIX CTNHPM01 Waiting for mount point in device
> class 03/03/2001 21:01:26
>
> 3590-E1A (1040 seconds).
>
> 16,389 Tcp/Ip IdleW 4.0 H 1.2 K 298 Node
> WinNT CTNHCTST
>
> 16,396 Tcp/Ip IdleW 4.1 M 24.2 M 2.3 K Node
> WinNT CTNHCTST
>
> 16,404 Tcp/Ip RecvW 0 S 2.8 K 74.4 G Node
> WinNT CTNHCTST
> 03/03/2001 21:04:11
> 16,445 Tcp/Ip IdleW 14 S 10.9 K 185.5 K Node
> WinNT GNWHPAR04
>
> 16,446 Tcp/Ip RecvW 0 S 3.1 K 3.4 G Node
> WinNT GNWHPAR04
> 03/03/2001 22:59:11
> 16,452 Tcp/Ip RecvW 0 S 32.3 K 31.3 G Node
> TDP MSE- CTNHEMAIL07_EXCH Current output volume: K20065.
> 03/03/2001 23:39:27
>
> xchg NT
>
> 16,513 Tcp/Ip IdleW 33.6 M 24.5 M 964 Node
> WinNT RHNT03
>
> 16,518 Tcp/Ip IdleW 35.0 M 3.8 M 811 Node
> WinNT RHNT01
>
> 16,533 Tcp/Ip IdleW 13.5 M 44.4 M 1.2 K Node
> WinNT RHNT03
>
> 16,565 Tcp/Ip IdleW 3 S 22.8 M 918 Node
> WinNT RHNT01
>
> 16,641 Tcp/Ip IdleW 32.0 M 32.0 M 2.6 K Node
> AIX CTNHCAD12
>
> 16,644 Tcp/Ip IdleW 17.6 M 542 31.5 M Node
> AIX CTNHCAD12 Current output volume: K20314.
> 03/04/2001 00:04:52
> 16,650 Tcp/Ip IdleW 10 S 115.6 M 10.7 K Node
> AIX CTNHCAD15
>
> 16,654 Tcp/Ip IdleW 23 S 1,016 23.0 M Node
> AIX CTNHCAD15
> 03/04/2001 00:05:41
> 16,692 Tcp/Ip IdleW 45.7 M 2.9 M 785 Node
> WinNT CTNHECSTAGE1
>
> 16,701 Tcp/Ip IdleW 32.8 M 37.8 M 981 Node
> WinNT CTNHECSTAGE1
>
> 16,720 Tcp/Ip IdleW 44.7 M 2.8 M 614 Node
> WinNT BONHNT04
>
> 16,724 Tcp/Ip IdleW 19 S 23.3 M 985 Node
> WinNT BONHNT04
>
> 16,726 Tcp/Ip MediaW 33.4 M 726 40.1 M Node
> WinNT RHNT03 Waiting for mount point in device
> class 03/04/2001 00:08:59
>
> 3590-E1A (2004 seconds).
>
> 16,739 Tcp/Ip IdleW 19.0 M 15.1 M 1.1 K Node
> WinNT CTNHCISNA01
>
> 16,742 Tcp/Ip IdleW 43.8 M 3.0 M 622 Node
> WinNT BONHNT03
>
> 16,745 Tcp/Ip IdleW 19.1 M 24.4 M 758 Node
> WinNT CTNHCISNA01
>
> 16,758 Tcp/Ip IdleW 34.0 M 5.3 M 728 Node
> WinNT CTNHIISDEV
>
> 16,768 Tcp/Ip IdleW 17.2 M 9.9 M 1.0 K Node
> WinNT CTNHGRAPHICS1
>
> 16,774 Tcp/Ip IdleW 1 S 19.6 M 974 Node
> WinNT CTNHGRAPHICS1
>
> 16,790 Tcp/Ip MediaW 33.3 M 385 981.3 K Node
> WinNT RHNT03 Waiting for mount point in device
> class 03/04/2001 00:12:20
>
> 3590-E1A (2000 seconds).
>
> 16,822 Tcp/Ip MediaW 32.8 M 457 782.9 K Node
> WinNT CTNHECSTAGE1 Waiting for mount point in device
> class 03/04/2001 00:13:47
>
> 3590-E1A (1967 seconds).
>
> 16,834 Tcp/Ip MediaW 21.1 M 1.8 K 1.4 M Node
> WinNT BONHNT04 Waiting for mount point in device
> class 03/04/2001 00:14:49
>
> 3590-E1A (1263 seconds).
>
> 16,864 Tcp/Ip MediaW 25.2 M 1.4 K 17.6 M Node
> WinNT BONHNT03 Waiting for mount point in device
> class 03/04/2001 00:16:57
>
> 3590-E1A (1514 seconds).
>
> 16,874 Tcp/Ip IdleW 34.2 M 8.6 M 271.4 K Node
> HPUX CTNHUG02
>
> 16,876 Tcp/Ip IdleW 19.1 M 85.5 M 5.1 K Node
> HPUX CTNHUG01
>
> 16,878 Tcp/Ip MediaW 29.1 M 1.1 K 14.3 M Node
> WinNT CTNHGRAPHICS1 Waiting for mount point in device
> class 03/04/2001 00:17:36
>
> 3590-E1A (1743 seconds).
>
> 16,879 Tcp/Ip MediaW 31.4 M 483 91.9 M Node
> HPUX CTNHUG01 Waiting for mount point in device
> class 03/04/2001 00:17:39
>
> 3590-E1A (1882 seconds).
>
> 16,885 Tcp/Ip MediaW 26.9 M 610 34.9 M Node
> WinNT CTNHIISDEV Waiting for mount point in device
> class 03/04/2001 00:18:12
>
> 3590-E1A (1616 seconds).
>
> 16,888 Tcp/Ip IdleW 35.0 M 3.9 M 672 Node
> WinNT CTNHPROXY1
>
> 16,891 Tcp/Ip MediaW 34.2 M 428 7.5 M Node
> HPUX CTNHUG02 Waiting for mount point in device
> class 03/04/2001 00:18:38
>
> 3590-E1A (2052 seconds).
>
> 16,892 Tcp/Ip IdleW 4.1 M 286.7 K 2.2 K Node
> WinNT CTNHPROXY1
>
> 16,893 Tcp/Ip MediaW 30.0 M 979 1.8 M Node
> WinNT CTNHCISNA01 Waiting for mount point in device
> class 03/04/2001 00:30:26
>
> 3590-E1A (1798 seconds).
>
> 16,895 Tcp/Ip IdleW 2 S 2.9 K 6.9 M Node
> WinNT CTNHPROXY1
> 03/04/2001 00:18:59
> 16,905 Tcp/Ip IdleW 16.8 M 9.9 M 921 Node
> WinNT CTNHCORSTR01
>
> 16,909 Tcp/Ip IdleW 35.1 M 3.8 M 680 Node
> WinNT CTNHCORIIS07
>
> 16,910 Tcp/Ip IdleW 34.0 M 6.0 M 720 Node
> WinNT CTNHCORIIS06
>
> 16,915 Tcp/Ip IdleW 6 S 57.6 M 2.1 K Node
> WinNT CTNHCORIIS06
>
> 16,916 Tcp/Ip IdleW 23.1 M 33.2 M 973 Node
> WinNT CTNHCORIIS07
>
> 16,917 Tcp/Ip IdleW 9.0 M 9.8 M 884 Node
> WinNT CTNHCORSTR01
>
> 16,920 Tcp/Ip MediaW 34.9 M 370 639.0 K Node
> WinNT RHNT01 Waiting for mount point in device
> class 03/04/2001 00:19:26
>
> 3590-E1A (2093 seconds).
>
> 16,943 Tcp/Ip MediaW 28.8 M 439 7.7 M Node
> WinNT CTNHCORSTR01 Waiting for mount point in device
> class 03/04/2001 00:21:50
>
> 3590-E1A (1727 seconds).
>
> 16,960 Tcp/Ip Run 0 S 356 3.1 M Node
> WinNT CTNHCORIIS07 Current output volume: K20020.
> 03/04/2001 00:25:06
> 16,964 Tcp/Ip MediaW 33.8 M 363 153.1 K Node
> WinNT CTNHCORIIS06 Waiting for mount point in device
> class 03/04/2001 00:26:33
>
> 3590-E1A (2030 seconds).
>
> 16,967 Tcp/Ip MediaW 33.2 M 314.0 K 566 Node
> HPUX BONHI2 Waiting for mount point in device
> class 03/04/2001 00:27:13
>
> 3590-E1A (1991 seconds).
>
> 16,968 Tcp/Ip MediaW 32.4 M 356 91.5 M Node
> WinNT CTNHECSTAGE1 Waiting for mount point in device
> class 03/04/2001 00:27:49
>
> 3590-E1A (1945 seconds).
>
> 16,978 Tcp/Ip MediaW 27.6 M 351 292.3 K Node
> WinNT CTNHGRAPHICS1 Waiting for mount point in device
> class 03/04/2001 00:32:50
>
> 3590-E1A (1654 seconds).
>
> 16,979 Tcp/Ip MediaW 25.8 M 2.0 K 122.4 K Node
> WinNT CTNHIISDEV Waiting for mount point in device
> class 03/04/2001 00:33:00
>
> 3590-E1A (1550 seconds).
>
> 16,980 Tcp/Ip MediaW 26.7 M 357 4.0 M Node
> WinNT CTNHCORIIS07 Waiting for mount point in device
> class 03/04/2001 00:33:39
>
> 3590-E1A (1603 seconds).
>
> 16,981 Tcp/Ip MediaW 25.8 M 369 191.6 K Node
> WinNT CTNHCISNA01 Waiting for mount point in device
> class 03/04/2001 00:34:31
>
> 3590-E1A (1545 seconds).
>
> 16,988 Tcp/Ip MediaW 22.2 M 357 496.9 K Node
> WinNT CTNHCORSTR01 Waiting for mount point in device
> class 03/04/2001 00:38:09
>
> 3590-E1A (1334 seconds).
>
> 16,995 Tcp/Ip IdleW 18.9 M 369 2.7 K Node
> WinNT CTNHCORIIS06
> 03/04/2001 00:41:29
> 17,000 Tcp/Ip MediaW 9.1 M 351 179.4 K Node
> WinNT BONHNT04 Waiting for mount point in device
> class 03/04/2001 00:49:50
>
> 3590-E1A (543 seconds).
>
> 17,005 Tcp/Ip MediaW 6.4 M 322.7 K 574 Node
> HPUX LATHSAPD Waiting for mount point in device
> class 03/04/2001 00:54:01
>
> 3590-E1A (384 seconds).
>
> 17,012 Tcp/Ip Run 0 S 127 163 Admin
> WinNT ODBC
>
> ANS8002I Highest return code was 0.
>
> Thanks in advance,
> John G. Talafous IS Technical Principal
> The Timken Company Global Software Support
> P.O. Box 6927 Data Management
> 1835 Dueber Ave. S.W. Phone: (330)-471-3390
> Canton, Ohio USA 44706-0927 Fax : (330)-471-4034
> [EMAIL PROTECTED] http://www.timken.com
