Hi Ronald,

This looks like an issue that has been reported, but there hasn't been a fix developed yet.  When you open your support case, ask the support person to compare your issue to ongoing escalations NW135930 & NW136514.

-Bobby

Thanks Bobby,

Got the reply frmo EMC, a bit dissappointed as if they know what the problem is...

Anyway, I've got a workaround in place whereby if the device unmounts, it will kill the nsrmmd and restart it :-)

Cheers,

R

Hi all, sorry for my poor English

Now i'm trying integrate DD630 with Networker 7.6 sp3 in my lab,

go through Device Conf Wizard all steps, but at the final step got error:

Connecting to 'DD' failed ([5004] nothing matched).

What should I do?

EMC Engineering have now resolved this and the hot fix is included in the latest Cumulative Build for 7.6.3 which will become GA next week.  If you already have an open SR the software should be available to you now.  The Cumulative details are 7.6.3.2, or 7.6.3 Build 860, it will be available for download from: -

ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes/7.6

next week.

Hi Bill,

How are things.

I am running the latest build

@(#) Release:      7.6.3.2

@(#) Build number: 860

@(#) Build arch.:  linux86w

But still seeing nothing matched on my devices, it's random... It gets unmounted automatically and then I get nothing matched

Thanks,

Ronald

Bill,

This is VERY useful information, better than being told to DOWNGRADE alltogether. You can understand this is not an option in our environment now after having upgraded 7.6.3 (30 storage nodes, 2 sites and 20TB a night).

Extremely useful, thanks will use the older library as I need to clone data betwen sites and a few particular devices are always giving nothing matched and never mount on 7.6.3.

Cheers!

R

Ronald,

Thanks for the comments. One thing I forgot to mention in the previous post was that the NMC software also contains this library. To be completely in sync I would also replace the library under NMC path also just to ensure there is no strange behaviour. I have not been able to get confirmation internally as yet if this is required but do not see if causing any adverse effects and if you use GUI for creating etc it is probably best to have both the same. You can use the same file from NetWorker 7.6.2 - you do not have to download/extract NMC separately.

I'll post the new solution reference as soon as I have it completed.

Regards,

Bill Mason

Hi Ronald

I am in the process of writing another Support Solution which details this error and some others which can be received when using 7.6.3.x software. Our engineers are in the process of making code changes (which are currently being tested), however as a workaround you can replace the libDDBoost library (.dll for windows, usually .so suffix for Unix) with the version from NetWorker 7.6.2. The latest software has v2.4 of the library and the older one v2.3 works with all versions of NetWorker so there is no compatibility issues with other binaries/executables.

The hot fix should be available very shortly if you need would like the hot fix in preference to the workaround above then please raise and SR quoting NW137528 Engineering reference. If you do not have an older version of the software its available from Powerlink.

Regards,

Bill Mason

Ronald,

There are a few different ways these error messages can be reported therefore I think its best to Consult Support Solution esg127727 going forward it will be available on Powerlink very shortly and replacement of the library file considered "normal procedure/recommendation". There are several things going forward which will be affected if the older library is put in place with the newer software. Of course if there is any doubt you can raise an SR and contact EMC Support.

Regards,

Bill Mason

Fellows,

I have tested integration DD with NW 7.6.2 build 638 at different OS's Solaris 10 Sparc 64, Windows 2008 R2, and still getting the same error:

Connecting to 'DD' failed ([5004] nothing matched).

I do not understand whether is hotfix availble or not?

d1v3r,

This message can be output for a valid reason within the environment.

What are you trying to do? Are you attempting to label the volume on the DDBoost device? Mount it?

Is volume set to Automatic recycle?

Regards,

Bill Mason

I recieved this error in version 8.  I found it to be the DD Boost service on the Data Domain.  Once I disabled and enabled the service the error went away.

Herschel Boyd

Wow, that worked for me Herschel! Thank you for your post.

+1 Herschel - We just experienced this issue and stopping/starting DDBoost on the DD640 did the trick.  Thank you!

Steve Galbincea