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.

same file being used by 2 different processes

Discussion in 'Backup / Archive Discussion' started by pcoviello, Sep 6, 2007.

  1. pcoviello

    pcoviello New Member

    Joined:
    Oct 9, 2002
    Messages:
    1
    Likes Received:
    0
    Location:
    NH
    I have the same file coming off disk and going two different tape drives. one is migration and the other is the backup storage pool to offsite... this is a 300+gb sql db file on dlt8000 tapes. so which one should I cancel or can both be left going... the only caveat is at some point if the backup doesn't finish the morning jobs don't kick off...

    tsm 5.3.4.0

    any thoughts?
    thanks
    Paul
     
  2.  
  3. sgabriel62

    sgabriel62 Senior Member

    Joined:
    Apr 7, 2005
    Messages:
    1,359
    Likes Received:
    5
    Occupation:
    Principal of SGSolutions Inc.; Systems Architect &
    Location:
    Michigan
    Paul
    Ya know both of these jobs are TSM Admin schedules. You dont want to cancel either of them. Migration is going to be used to keep your diskpool at a certain value - pushing data to tape once it meets a certain threshold level. The backup storage pool jobs sends your data offsite.

    I am curious to know where your sql db data is going - to which storage pool - disk or tape? I am assuming you are going to disk first. Or not.?

    Adjust your backup storage pool admin routine earlier on in the evening - give yourself enough time to nightlies to run as before your tape handlers prepare for offsite media movement. Your migration thresholds are at your discretion.

    Let us know
     
  4. BBB

    BBB Moderator

    Joined:
    Feb 13, 2007
    Messages:
    2,076
    Likes Received:
    20
    Location:
    Brisbane, Australia
    How do you know its the same "file" getting a "backup stgpool" and a migration at the same time? Or do you mean same stgpool?

    Anyway, usually its better to let backup stgpools from disk-> tape complete first, then let migrations run after that. This way the backup stgpool can copy from disk to tape rather than having to do tape->tape. You might want to reorganise your admin schedules if you can. Generally your housekeeping will go faster this way.
     

Share This Page