Forum Discussion

cimo's avatar
cimo
Level 4
11 years ago
Solved

AIR with DataDomain, replication job 191

Hello!

I'm using the feature AIR with my DataDomain since few days. Everything is running well, but the replication jobs are failing only for a specific client, that is a Windows Server 2003 Standard edition x86, with Lotus Notes.

This is the filtered bpdm log :


13:37:55.025 [1059] <16> 3345718:bptm:1059:michelangelo: [423:100A5D210] ddpi_remote_fileop() failed operation: 1, Err: 5004-nfs remote file op failed (nfs: No such file or directory)
13:37:55.025 [1059] <16> 3345718:bptm:1059:michelangelo: /usr/openv/lib/ost-plugins/libstspiDataDomain.so:stspi_async_wait_v11 STS_EPLUGIN filecopy status failed [DDErrNo = 5004 (nothing matched)] for source dd2500-vi-110:lsuAIR-dd2500-vi-110/iglnotes1.sesto.mil_1396333800_C1_IM target iglnotes1.sesto.mil_1396333800_C1_IM
13:37:55.044 [1059] <16> rpl_copy_image_set: wait failed: error 174
13:37:55.045 [1059] <16> rpl_copy_cancel: <async> cancel failed: error 2060001:
13:37:55.045 [1059] <16> rpl_copy_image_set: copy cancel failed: error 174
 

Do you know this error?

Thank you very much!

 

 

 

  • The EMC support is very quick!!

    I modified the datadomain configuration by executing this command:

     

    # priv set se

    # reg set system.NFS_FILECOPY_TIMEOUT = 600000

    # filesys restart

    all the replication jobs are running well.

5 Replies

Replies have been turned off for this discussion
  • I think you need to open a support case with Data Domain - it looks like a BOOST issues of some sort.

     /usr/openv/lib/ost-plugins/libstspiDataDomain.so:stspi_async_wait_v11 STS_EPLUGIN filecopy status failed DDErrNo = 5004

  • Ok , support case opened in EMC. I hope that they will find a solution.

  • The EMC support is very quick!!

    I modified the datadomain configuration by executing this command:

     

    # priv set se

    # reg set system.NFS_FILECOPY_TIMEOUT = 600000

    # filesys restart

    all the replication jobs are running well.

  • Cool  - good to see a follow-up post with the response from EMC support.