1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This message will disappear after you have made at least 12 posts. Thank you for your cooperation.

TSM Network Upgrade running slow

Discussion in 'TSM Server' started by Poohmanchoo, Sep 22, 2012.

Thread Status:
Not open for further replies.
  1. Poohmanchoo

    Poohmanchoo New Member

    Joined:
    Sep 22, 2011
    Messages:
    17
    Likes Received:
    0
    Occupation:
    TSM Administrator/ Avamar and Networker Admin.
    Location:
    New York
    I am currently attempting a network up grade, TSM 5.5.3 to 6.2.1, and the insertdb is slowing down.
    This is my second attempt as the last attempt slowed down to a xfer rate of 1.2GB/ hr and I had to cancel it.
    After 110+ hours I still 90+GB to transfer and had already been a week without backups while this was happening.
    I know there are other ways to do the upgrade that might take as long and that will be next attempt, but in the meanwhile,
    can anyone explain to me why theprocess is slowing down? The following is an excerpt from the insertDB.out file, of which i noticed my
    last attempt of data migratin was hovering at about 4.5-6 GB an hour until the ANR0478W started to appear after abuot 40 hours of
    data transfer, this showing that the ANR0478W started showing up even before the data transfer started. This didn't seem to have any negative affect at first, but now (last line) it has slowed tremendously and contiunes to do so. I also noticed that as the data rate slows, the reporting interval lengthens. In the beginning it was reporting every five minutes and now it reports every half hour?!?

    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR1336I INSERTDB: Ready for connections from the source server. Remaining
    time: 0:49:29
    ANR1336I INSERTDB: Ready for connections from the source server. Remaining
    time: 0:48:59
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR1336I INSERTDB: Ready for connections from the source server. Remaining
    time: 0:48:29
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR1336I INSERTDB: Ready for connections from the source server. Remaining
    time: 0:47:59
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR1336I INSERTDB: Ready for connections from the source server. Remaining
    time: 0:47:29
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0408I Session 104 started for server $UPGRADESOURCE$ (Windows) (Tcp/Ip) for
    V6 Database Upgrade.
    ANR1377I Analyst authority has been revoked for administrator id 108.
    ANR1337I A DBBACKUP trigger has been removed.
    ANR1337I A DBSPACE trigger has been removed.
    ANR1337I A LOGSPACE trigger has been removed.
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR1379I INSERTDB: Read 70,991,086 bytes and inserted 627,103 database entries
    in 0:00:00 (0.00 megabytes per hour).
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    .............
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR1379I INSERTDB: Read 583,544,287 bytes and inserted 5,533,841 database
    entries in 0:05:01 (6649.83 megabytes per hour).
    ANR0478W Session request refused. Server is running in standalone mode.
    .............
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR1379I INSERTDB: Read 1,262,478,212 bytes and inserted 11,518,861 database
    entries in 0:10:01 (7205.99 megabytes per hour).
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    .............
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR1379I INSERTDB: Read 29,503,297,397 bytes and inserted 211,109,384 database
    entries in 10:01:00 (2808.92 megabytes per hour).
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.
    ANR0478W Session request refused. Server is running in standalone mode.

    I had IBM look into it and one response was "That's how it works, nothing you can do about it, just let it run." A second response from
    a different tech was that it just takes a long time, but that I might be able to correct issue if I put
    ALLOWREORGTABLE NO
    ALLOWREORGINDEX NO
    into the dsmserv.opt file. and restarted the upgrade process. I didn't do this because I was in the middle of the upgrade. As I could not wait another 4 days for the rest of the data to transfer, last night I canceled the upgrade, made the changes as stated and then restarted the upgrade process. Not only didn't it work, it took less time for these warnings to start showing and for their effects to be felt on the processing.
    I saw that moon-buddy had somewhat addressed this in another post, totally different situation with the same error, and said to disable all sessions in the dsmserv.opt file. I don't know if that would apply here and if someone thinks it would help, let me know.
    Also is it just the same sytax as admin command line?
    Why would there be any sessions causing problems, should the servers be in an 'exclusive mode' as all sessions and weren't all sessions stopped prior to beginning of upgrade.

    If anybody has any suggestions, at this point I am willing to try anything, and this includes going over my bosses directives (he knows nothing about TSM, and insisted on this method) and taking moon-buddy's advice and setting new server up at same level as current and doing in-place upgrade. But that is a last resort considering the reprecussions.
     
  2.  
  3. moon-buddy

    moon-buddy Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,209
    Likes Received:
    279
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    I would do the update as I posted - less effort and worry, and there is a way to go back!
     
    Last edited: Sep 22, 2012
  4. Poohmanchoo

    Poohmanchoo New Member

    Joined:
    Sep 22, 2011
    Messages:
    17
    Likes Received:
    0
    Occupation:
    TSM Administrator/ Avamar and Networker Admin.
    Location:
    New York
    I knew you were going to say that.
    That appears it is pretty much my only real option right now.
    The data rate is down to 2GB an hour and still dropping.
    Thanks for your reply on the other post. Your wisdom is always helpful and appreciated.
     
Thread Status:
Not open for further replies.

Share This Page