1. Community Tip: Please Give Thanks to Those Sharing Their Knowledge.
    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.
  2. Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
    Click the link above 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 notice will disappear after you have made at least 3 posts.

Daily ops that change after moving to V6.2

Discussion in 'TSM Server' started by evilution, Jun 15, 2011.

  1. evilution

    evilution ADSM.ORG Member

    Joined:
    May 24, 2011
    Messages:
    81
    Likes Received:
    2
    Occupation:
    Storage Engineer
    Location:
    Madison, WI
    We are on the verge of moving our test environment to 6.2 from 5.5.5 and I'm curious if any of you changed your approach to daily QA or monitoring after moving to V6.

    I'm also interested if you discoverd any got-yas after the move. We have all of our procedures well documented in the event of a problem we simply read the page and do the step. I suspect some of these procedures will change with V6. For instance does the recovery process for the TSM DB change or are the steps the same except for the NEED of the devconfig and vol hist?
     
  2.  

Share This Page