export node XXXX toserver=XXXXX fails

[combato]

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

 

[inestler]

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.

 

[combato]

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

 

[saiful]

What is the result?

 

[marclant]

Hi,
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

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.

 

[Andrew21210]

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