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.

export node XXXX toserver=XXXXX fails

Discussion in 'TSM Operation' started by combato, Nov 13, 2012.

  1. combato

    combato New Member

    Joined:
    Mar 22, 2012
    Messages:
    65
    Likes Received:
    0
    Occupation:
    A reliable employee
    Location:
    Sweden
    Hi,

    I've tried to export some nodes from serverA to serverB. "export node node1 filedata=all toserver=serverB"
    The process starts but after some hours the process died with this error:

    ANR0670W EXPORT NODE: Transaction failed - storage media
    inaccessible. (SESSION: 117066, PROCESS: 1551)
    ANR0794E EXPORT NODE: Processing terminated abnormally -
    error accessing data storage. (SESSION: 117066, PROCESS:
    1551)

    I've tried to restart the export with the "restart export export_node_1454" command but if gives the same error.
    I have three questions:

    1. Can I somehow find what volumes that is the problem and maybe repair the volume (or skip it) and continue the export?

    2. If I choose to skip the rest of the export and leave it as it is, and now turn on my node backups to the serverB will the node fill out the missing filespaces that was not exported? (I know I will loose retention data of some filespaces that was not exported correctly from the failing export node command...)

    3. Or is it better to delete the node1 (and partly exported filespaces) on serverB and register the node1 on serverB from scratch instead and start backing up the node1 from scratch?

    /C
     
  2.  
  3. inestler

    inestler Member

    Joined:
    Mar 12, 2007
    Messages:
    151
    Likes Received:
    7
    Location:
    switzerland
    1. yes -
    User response: Use the QUERY ACTLOG command to examine messages prior to
    this error to determine the cause of the data storage failure. If the
    import or export operation involves a session with another server, run
    the QUERY ACTLOG command to examine messages on the other server as
    well. Messages on the other server can help you troubleshoot the error
    on the local server. If you find and resolve the error, retry the export
    or import operation. If you cannot find the error, contact your service
    representative for assistance in resolving the problem.

    2 . yes but better is 3.
     
  4. combato

    combato New Member

    Joined:
    Mar 22, 2012
    Messages:
    65
    Likes Received:
    0
    Occupation:
    A reliable employee
    Location:
    Sweden

    OK, thanks! I wil go for number three then. :)

    /C
     
  5. saiful

    saiful New Member

    Joined:
    Sep 23, 2010
    Messages:
    1
    Likes Received:
    0
    What is the result?
     
  6. marclant

    marclant Senior Member

    Joined:
    Jun 16, 2006
    Messages:
    861
    Likes Received:
    106
    Occupation:
    TSM Accelerated Value Specialist
    Location:
    Canada
    For 3, you don't need to delete the node and partially exported filespaces. The next incremental backup will skip active objects that were already imported if they have not changed.

    What's best really depends on your requirements. If you need to keep the old data, then an export is needed. If you don't need to keep the old data, then you can just start backing up at the new server.
     
  7. Andrew21210

    Andrew21210 New Member

    Joined:
    Apr 10, 2008
    Messages:
    35
    Likes Received:
    0
    Or you could do:

    EXPORT NODE XXXX FILEDATA=NONE TOSERVER=XXXX
    then, back the node up on the new server and do
    EXPORT NODE XXXX FILEDATA=ALL MERGE=YES TOSERVER=XXXX
     

Share This Page