Results 1 to 3 of 3
  1. #1
    Newcomer
    Join Date
    Mar 2012
    Location
    Gothenburg, SWE
    Posts
    30
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Default export node XXXX toserver=XXXXX fails

    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. #2
    Member
    Join Date
    Mar 2007
    Location
    switzerland
    Posts
    151
    Thanks
    0
    Thanked 7 Times in 7 Posts

    Default

    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.

  3. #3
    Newcomer
    Join Date
    Mar 2012
    Location
    Gothenburg, SWE
    Posts
    30
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Default

    Quote Originally Posted by inestler View Post
    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.

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

    /C

Similar Threads

  1. Replies: 5
    Last Post: 04-04-2012, 08:32 AM
  2. Export node toserver problem
    By vvmoti in forum TSM Operation
    Replies: 4
    Last Post: 12-19-2011, 10:29 AM
  3. export node
    By dwcasey in forum Backup / Archive Discussion
    Replies: 7
    Last Post: 06-02-2011, 05:27 PM
  4. Urgent - Restore SQL DB from Cluster Node to Stand Alone Node fails
    By kabousv in forum TDP/Application Layer Backup
    Replies: 0
    Last Post: 02-11-2005, 03:48 AM
  5. AIX Client Message : ANS3408W The volume /xxx/xxxx contains bad blocks
    By cbrjones in forum Backup / Archive Discussion
    Replies: 0
    Last Post: 06-04-2004, 05:18 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •