I have been fighting these issues, myself.

It seems that EXPORT/IMPORT is very, very fragile and V6 is worse than V5.


If the data the export needs is on a tape and all tape drives are busy, it
just up-and-dies with these errors.  It does not wait for a tape drive to
become available.

This has been causing me grief for the past 3-weeks.  I have been trying
to move nodes between servers (v5.5.3 --> V6.1) and if in the middle of
the "import" to the target server, it requires a tape mount on the source
"export" server, and all tape drives are busy, you get these failures.

This has caused me to have to bounce my V5.5 ("export") server, twice in
the last week.  The "import" on the V6.1 server dies but the "export" on
the v5.5 is still running/hung.  Attempts to cancel the export fail and
the process goes into a never-ending "cancel pending", thus pinning my
logs.  Only choice has been to restart the V5.5 server.



From:
Mario Behring <mariobehring AT YAHOO DOT COM>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
02/09/2010 05:49 AM
Subject:
[ADSM-L] Export errors
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



Hi list,


I am getting the following errors during an EXPORT operation:

02/08/10   22:59:04      ANR0670W EXPORT NODE: Transaction failed -
storage media
                          inaccessible. (SESSION: 33, PROCESS: 3)
02/08/10   22:59:06      ANR0794E EXPORT NODE: Processing terminated
abnormally -
                          error accessing data storage. (SESSION: 33,
PROCESS: 3)
02/08/10   22:59:06      ANR9999D Thread<312>  0x0000000000ba91a7
                          PrintExportStats+0x0x77  (SESSION: 33, PROCESS:
3)
02/08/10   22:59:06      ANR9999D Thread<312>  0x0000000000baa564
XiExport+0x0x9f4
                          (SESSION: 33, PROCESS: 3)


Everything looks normal....the library works fine....all other operations
ok.....

Any ideas?

Mario