I once had a issue with upgraded Windows server but mostly it worked fine for me. NW 742 also worked pretty stable. Currently I am working at upgrading to 7.4.3. Let us see how that works.

Hi,
We are running networker 7.4SP2 and there are issues as such. But i would request you to go through the release note for 7.4.2 before upgrading, as there are a number of things that change from 7.3.3 to 7.4 SP2. You can download the release notes from powerlink.

Hi,
We are running networker 7.4SP2 and there are issues as such. But i would request you to go through the release note for 7.4.2 before upgrading, as there are a number of things that change from 7.3.3 to 7.4 SP2. You can download the release notes from powerlink.

I have implemented NW 7.4.2 in about half a dozen sites and the feedback from them is that this version is quite stable. There are some niggling problems most of which have been to do with the NMC gui. Operationally it seems to be pretty stable.

I would suggest, as already done by some of the others, that you look at the release notes to analyse if there are any potential problems with the software in respect to your environment.

7.4 SP3 recently came out (Sept 12th). Is anyone running it yet? Any issues?

Here are the release notes.

https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/km/live1/en_US/Offering_Technical/Technical_Documentation/300-005-511.pdf

I've recently upgraded to NW 7.4 SP3 on our Linux backupserver running RHEL 4.6. I discovered some issues with nsrclone. It seems like the "-J" switch introduced in 7.4.x do not work as expected anymore. We have multiple storagenodes, so this is quite an issue for our cloning scripts.
I had to use the "old" way of directing clone jobs by using read hostname on the jukebox resource. I opened a support case today on the issue.
Anyone else had any problems with this ?

Interesting, I am running 7.4.2 and the -J doesn't work in our nsrclone scripts either. I spoke to EMC about it and they recommended I try this (I haven't gotten around to it yet). Manually (via script) load the volume with the save set you are going to clone on the storage node you want to clone on. The engineer explained that due to the logic of how networker works, it should choose the storage node that has the tape loaded as the node to do the clone on.

The -J worked perfectly for me on 7.4.2 on Linux. The Clone storage node and recvover storage node attribute on both server, storage node and client was left blank. The -J made both the read and write operation run on the selected storage node.

In my eyes 7.4.x is more stable than 7.3.x so you can't go wrong.