Hi,
sometimes we have problem with backups times longer than normal.
For example backup of several files (600 MB) usualy takes 1 minute to
complete and when the problem occurs it takes for over 40 minutes. In
this situation a query session on the server shows that almost all
sessions are in Run state:
tsm: AMO>q se
Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name
Number Method State Time Sent Recvd Type
------- ------ ------ ------ ------- ------- ----- -------- -------------
1 Tcp/Ip IdleW 7 S 4.7 M 3.6 M Server HP-UX EON
38,369 Tcp/Ip IdleW 7 S 21.2 M 13.1 M Server HP-UX EON
470,633 Tcp/Ip SendW 0 S 1.8 M 108 Admin WinNT CONSOLE
475,213 Tcp/Ip IdleW 15.2 M 143.8 K 5.0 K Node WinNT MSSQLDBS
475,215 Tcp/Ip Run 0 S 1.4 K 35.6 G Node WinNT MSSQLDBS
475,222 Tcp/Ip IdleW 2.7 M 20.0 K 3.8 K Node HPUX LEAPW
475,223 Tcp/Ip IdleW 2.7 M 504.0 K 5.4 K Node HPUX LEAPW
475,228 Tcp/Ip Run 0 S 615.1 K 4.9 K Admin WinNT MILIEVA
475,321 Tcp/Ip IdleW 1.8 H 161.2 M 3.8 K Node HPUX OMNIX
475,552 Tcp/Ip IdleW 48.1 M 24.2 K 783 Node AIX NIM
475,553 Tcp/Ip Run 0 S 668 13.3 G Node AIX NIM
475,586 Tcp/Ip IdleW 36.7 M 66.7 K 581 Node HPUX EOS
475,588 Tcp/Ip Run 0 S 564 212.2 M Node HPUX EOS
475,605 Tcp/Ip IdleW 26.7 M 65.4 K 581 Node HPUX EOS
475,606 Tcp/Ip Run 0 S 503 122.0 M Node HPUX EOS
475,607 Tcp/Ip Run 0 S 499 107.7 M Node HPUX EOS
475,608 Tcp/Ip Run 0 S 499 119.7 M Node HPUX EOS
475,609 Tcp/Ip Run 0 S 499 108.2 M Node HPUX EOS
475,656 Tcp/Ip IdleW 21.7 M 20.4 K 738 Node HPUX LNGARCH
475,657 Tcp/Ip Run 0 S 468 69.2 M Node HPUX LNGARCH
475,658 Tcp/Ip Run 0 S 469 78.2 M Node HPUX LNGARCH
475,659 Tcp/Ip Run 0 S 464 68.5 M Node HPUX LNGARCH
475,660 Tcp/Ip Run 0 S 464 72.5 M Node HPUX LNGARCH
475,669 Tcp/Ip IdleW 16.7 M 65.6 K 581 Node HPUX EOS
475,670 Tcp/Ip Run 0 S 438 39.2 M Node HPUX EOS
475,671 Tcp/Ip Run 0 S 439 47.2 M Node HPUX EOS
475,672 Tcp/Ip Run 0 S 429 38.5 M Node HPUX EOS
475,673 Tcp/Ip Run 0 S 434 47.5 M Node HPUX EOS
475,674 Tcp/Ip Run 0 S 429 38.7 M Node HPUX EOS
475,710 Tcp/Ip IdleW 6.7 M 65.9 K 581 Node HPUX EOS
475,711 Tcp/Ip Run 0 S 389 16.0 M Node HPUX EOS
475,712 Tcp/Ip Run 0 S 374 13.2 M Node HPUX EOS
475,713 Tcp/Ip Run 0 S 374 15.5 M Node HPUX EOS
475,714 Tcp/Ip Run 0 S 374 13.2 M Node HPUX EOS
475,715 Tcp/Ip Run 0 S 374 15.5 M Node HPUX EOS
475,716 Tcp/Ip Run 0 S 374 13.0 M Node HPUX EOS
475,726 Tcp/Ip IdleW 2.6 M 43.8 K 422 Node HPUX LEAPW
475,727 Tcp/Ip RecvW 2.6 M 6.7 K 2.6 K Node HPUX LEAPW
475,733 Tcp/Ip IdleW 1.7 M 20.4 K 738 Node HPUX LNGARCH
475,734 Tcp/Ip Run 0 S 359 2.8 M Node HPUX LNGARCH
475,735 Tcp/Ip Run 0 S 349 3.2 M Node HPUX LNGARCH
475,736 Tcp/Ip Run 0 S 349 2.5 M Node HPUX LNGARCH
475,737 Tcp/Ip Run 0 S 349 3.0 M Node HPUX LNGARCH
475,738 Tcp/Ip Run 0 S 349 2.2 M Node HPUX LNGARCH
475,739 Tcp/Ip Run 0 S 349 2.7 M Node HPUX LNGARCH
475,740 Tcp/Ip Run 0 S 349 2.2 M Node HPUX LNGARCH
475,742 Tcp/Ip IdleW 45 S 16.1 K 1.2 K Node AIX NIM
475,743 Tcp/Ip Run 0 S 343 8.2 M Node AIX NIM
This behavior occurs in a random manner. It can occur twice per week,
once per month, sometimes there are no problems for about three or
four months.
Usually the problem dissapears for less than an hour without any intervention.
There is no network or server load at the time of the problem.
Anyone have ideas what can cause that behaviour?
Any help will be appreciated!
TSM Server 5.3.3.0 on AIX 5.3
TSM Clients 5.3 and higher
Best Regards,
Maria Ilieva
|
