1. Please help support our sponsors by considering their products and services.
    Our sponsors enable us to maintain high-speed Internet connection and fast webservers.
    They support this free information and knowledge exchange forum service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions

TSM disaster recovery with protectier vtl

Discussion in 'TSM Server' started by Houssam, Dec 20, 2016.

  1. Houssam

    Houssam ADSM.ORG Member

    Joined:
    Aug 19, 2016
    Messages:
    12
    Likes Received:
    1
    hello,
    i have 2 sites with vtl replication (ts7620), in the site n°1 i have a tsm server 7.x.

    i want to know how vtl replication and tsm work together in order to have a disaster recovery plan, i think that we have to choose between tsm replication and vtl replication, and not both.
     
  2.  
  3. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,679
    Likes Received:
    374
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    Correct.

    If you do VTL replication, you would need HADR to replicate the DB changes to the DR server. Or have an offline DR server that you would restore the DB too.

    Or use TSM replication and deduplication, but your storage would need to be disk, not VTL.
     
  4. Houssam

    Houssam ADSM.ORG Member

    Joined:
    Aug 19, 2016
    Messages:
    12
    Likes Received:
    1
    dear marclant,

    i do have an offline server to restore a db make a copy of volhist and devconf.
    my question is :
    if i have a vtl on primary site named ts3500-prim with 10 cartridges labaled primsite001 ... primsite010, and i have a vtl ont secondary site named ts3500-sec with 10 cartriges.
    do i have to configure cartriges with the same label on the secondary site ? if so, do vtl replicate cartridge primsite001 of primary site with primsite001 cartridge of secondary site ?
    how tsm knows about replicated backups
     
  5. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,679
    Likes Received:
    374
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    They have to be the same name, TSM will look for known tapes labels (real or virtual).
    I would assume so.
    It doesn't. It knows about all the volumes it has used, if those volumes are replicated, the DR server can access those volumes in the DR VTL. TSM has no clue if these are the original volumes or replicated volumes.
     
  6. chavdar.cholev

    chavdar.cholev ADSM.ORG Member

    Joined:
    Apr 17, 2007
    Messages:
    15
    Likes Received:
    0
    If possible,
    I would define second VTL on protecTIER @site2 and present to site 1 and do the db backups there ....
    Also if servers are lunux/unix ... NFS from site 2 , export NFS and mount to TSM in site1 and do the db backups, volhist and devconfig files ...
     
  7. marcinek

    marcinek ADSM.ORG Member

    Joined:
    Sep 14, 2004
    Messages:
    48
    Likes Received:
    0
    Occupation:
    TSM & AIX Consultant
    Location:
    Warsaw, Poland
    Hi,
    First, since this thread is quite stale I wonder how your solution looks now.
    I'm working on similiar architecture right now, it's still not ready, but here is what I've found regarding PT and TSM.
    HADR seems to work fine... but:
    - additionally you need to replicate a lot of encryption related files located in "instance" directory. Otherwise "resurected" instance will not be able to autheticate virtually anything.
    - turn on LOGINDEXBUILD on db2's. Even with that enabled, it can take long time to faliover.
    - PT replicates cartridges. No need to create any on DR side.
    - Replicas can appear in your DR site in two ways: on the shelf, shared between all defined VTLs, or in io slots of selected VTL. It depends on "visibility" setting of replication policy.
    - Visibility is important - With "on" it triggers replication once the cartridge is ejected on the source library. And it appears in io slot of the target library. It makes you life easier with testing. Or is ecellent if you want to have offsite copy pool. With "visibility" off, PT replicates your cartridges more or less instantly, but they are not available in DR site untill you put it in "DR mode". Then you can find them on the shelf.
    And here goes my doubts:
    - If primary site goes down, both TSM and PT, on DR site I have my tapes, but the library is completly different. I'm working on clean solution of redefinig the library under the storage pool, and checking in the tapes back.
    - I want to make it as automatic as possible, because I have 64 drives available lanfree to 10 hosts... That makes 705 paths to update, including TSM :-\
    I'd appreciate any sugestions how to design and automate such solution.
     

Share This Page