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.

Best method of Export.

Discussion in 'Backup / Archive Discussion' started by Duddey, Aug 11, 2017.

  1. Duddey

    Duddey Newcomer

    Joined:
    Aug 9, 2017
    Messages:
    3
    Likes Received:
    0
    Management says "No More Tapes", so I am looking to get the data from our four data centers to our DR site across our WAN. We have a need to keep multiple versions, indefinitely, so replication does not appear to be the answer. Much of the data is SQL TDP, so I am looking to use exports.
    Here is my dilemma. The domain defs on each of our four TSM servers are identical, so it appears that the exports will want to put them all in the samt location on the target server, if I use the 'toserver' option. I want to keep the output from each of the exports segregated so that I don't have them all in the same directory on the target server. I have been able to accomplish this by using the UNC name of the target server for the directory in the devclass rather than using the 'toserver' parameter. Am I losing any capabilities by using the devc method rather than toserver.

    Thanks,
    Duddey
     
  2.  
  3. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,829
    Likes Received:
    358
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    You should not be loosing any data provided that you export all backups and archives.
     
  4. Duddey

    Duddey Newcomer

    Joined:
    Aug 9, 2017
    Messages:
    3
    Likes Received:
    0
    Thank you Moon-Buddy.
     
  5. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,564
    Likes Received:
    358
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    Might be too late now, but replication sends both active and inactive data.
     
  6. Duddey

    Duddey Newcomer

    Joined:
    Aug 9, 2017
    Messages:
    3
    Likes Received:
    0
    Marclant,
    That's very interesting. It has always been my impression that replication was concerned with the most recent 'active' version of the files.
    If a file on the source is deleted, or modified then it is also deleted or modified on the target. I need to keep point in time versions indefinitely, no matter what happens on the source. That is why I chose to go with exports, but it's never too late to change, if replication is a better method, then I am interested.
     
  7. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,564
    Likes Received:
    358
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    Replication is better in the sense that you can run it X number of hours every day until it has nothing left to replicate. Replication will automatically skip objects that already exist on the target as well. As long as your policies are the same on both sides, retention will be the same.

    Export is less efficient if you have to stop it and restart it because it doesn't track what's been previously exported like replication does.

    As far as data movement, both will give you the same end result.
     
  8. opeth

    opeth ADSM.ORG Member

    Joined:
    Feb 3, 2016
    Messages:
    81
    Likes Received:
    0
    don't mean to hijack a thread here, but I having to export a TON of data from one TSM server to another that is the new target for backup. I never considered replication as a possibly solution but it makes sense.
    What I did not know is "Export is less efficient if you have to stop it and restart it because it doesn't track what's been previously exported" I thought export node picked up where it left off when you restart it, if that's not the case im in a bit of a mess as I am having to stop it periodically because its killing my activity log.

    If I have already pointed backups to the new TSM server, and I flip on replication from the old to the new, it will start deleting data on the new because it doesn't exist on the old (source) server during expiration right? To complicate this more all this data is in permanent retention

    Am I understanding this correctly?
     
  9. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,564
    Likes Received:
    358
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    It's not entirely true. If the export runs to completion, but you have to rerun it again because new backups were made to the old server, it will inspect everything, the replication would not. If you cancel the export, you can restart it. More info here:
    source: https://www.ibm.com/support/knowled...0/srv.reference/r_cmd_node_othsvr_export.html

    Replication only moves data from the source to the target, it doesn't delete data on the target. Expiration on the target is what is responsible to remove data passed the retention.
     

Share This Page