Why is NetWorker 7.6.2 on Restricted Access?

Well, I must say it seems strange to me to download the RA code from the same special place that distributes the beta code. Then it seems strange to me to change the way the code is distributed at the same time distributing the older code in the old fashioned way.

Then I've read on the listserv about people waiting for the Networker 7.6.2 stop being RA and become GA so they can start use it.

It's a good thing for EMC to clear this misunderstanding up then!

Regards,

Johannes

How does one get into these Restricted Access programs? Is there a website to apply for it? Thanks!

There is a document over on Powerlink that describes the process and has the link to Feedback central.  Here's the link.

Allan

Thanks Allan, going to check it out.

We have been waiting on 7.6.2 to go to general availability for weeks now.  I really can't undserstand why the code is "released" and two months later it is still being treated as "Beta".

This story about "we want to know how people are using it" is very thin.  If it's not ready for prime time then don't say you are releasing it, keep it under lock and key, and then make the announcement when it is available for real instead of having us jump through hoops to get to it.

Just my 2 cents worth.

I have mixed feelings about RA.  Overall I believe it is better than before, but it gets time to get used to it.  RA access is nothing new really when it comes to different vendors, but usually it has been not applied that much to products like backup applications.  From PM PoV, I can see the benefit and how does this ease overall release process, but it will take time for customer base to get used to it.  Adanac, there is nothing stopping you from getting 7.6SP2 today and start your test cycle.  I do have policy not to apply early releases thus no matter how I would like to move to a new DR model of Windows boxes, I do not plan to make any tests until early fall at least.

Yeah, I'm also riding 7.5.3.5.  I have to say that 7.4.4.x I had before was great and the only reason I went to 7.5.3.5 was due to end of support.  Same will happen with 7.6.x (I plan to use 7.6.1.x code).  I wouldn't say that 7.0 has same issues as 6.0, but yes, you can see regression quite often - way more often than in Legato days.  I believe some work is required on that code thingy.  The way I see it, they freeze code at certain point and spawn new code tree to implement new features... these two run in parallel, but focus on new code is feature and fixing as much about those features while parant code gets fixed on normal basis.  Once released, it still contains those bugs and this is exactly the point which engineering should address better.  I usually do not mind those much as for me new versions are mostly acceptable as client side software implementation and you do not see much of issues reflecting client itself (this is not to say there are not any), but even those should be included in new releases.  Not sure what NW8 will be or will they continue with SP releases until really new NW is out as there is much to be done with product when you look at it.  I planned to (and still plan) to write an article about my feeling on backup strategy after EMC World this year, but still didn't get time (at least I will get some time to sort few ideas and thoughts).

I agree with you that other vendors use this but this is getting silly.  I understand the risks involved.  I also know that  releasing code that is not ready is not a good thing.

I have never installed  the .0 or .1 versions of networker because I have found them to be too bug-ridden to use.

Generally by the time we see .2 released it is womewhat stable.

Somewhere in the mix EMC has to stop re-using buggy code and start with the latest stable version.  e.g. NW 7.0 had the same bugs as NW 6.0, why were they in the 7.0 release?  Because someone is not paying attention?  because no one cares? Just the way it is?

I still have version 7.5.x in our environment because I am waiting for a stable version of 7.6 to be released. Will it happen before NW v 8.0 is released?  Well my crystal ball is not working today so I can't tell you.

It is not motorcycle jumping over Disk arrays that sells products.  Let's stop the Novell-like or the Microsoft-like antics and get working products out into the hands of the end users.  Let get products that work properly, that are user friendly, that don't change the GUI look and feel just because someone had chocolate for breakfast or whatever.

It's all about working smarter not harder.

Although i will not be able to change EMC's general policy/politics, i do not like restrictions in general (as most of us). Let everybody play and learn about new features and benefits whenever he wants. IMHO free access will encourage people to use things - restrictions will defenitively not do that.

What really concerns me is the way EMC names product (revisions). Right now, the "NW 7.6.2 Refresh Build" version is avalable which turns out to be 7.6.2.1 after installation. I just wonder what comes next - probably the "Even Fresher Build". Sorry, this is marketing .... rather often, their words do not make sense - at least not for 'straight' thinking techies.

I addition, nobody at EMC ever seems to log in as a vistitor on Powerlink. Otherwise one would notice that some issues (especially docs) are just missing. But does it make sense to download software without the docs?

Hi Bingo,

On the Powerlink downloads topic  (Also working on your other questions).  I gave it a try as a "customer".  Yes, the doc and downloads are in two different areas.  I guess the thought here is people might need more access to the docs so grouping them is easier?  Here's what I see.  Is your view the same?  If you notice docs are missing- let us know and I can check on them to see where in the Powerlink maze they are located.

Top view- Doc under one section, Downloads another:

Screenshot for doc section- NMDA example:

Screenshot for downloads section- NetWorker:

Hello Evilensky - I am a member of the NetWorker Product Management team.

First, I saw your recent post to temple listserv. As a personal policy I choose not to engage in discussions on listserv. I know I could have reduced some frustration by replying there for a wider customer audience, but I'm a believer that we unintentionally change the things that we observe. My active participation would create the impression in some minds that EMC uses Listserv as an extended marketing tool. I'm not asking you to agree with my policy, I'm only asking that you understand that my highest priority is to maintain integrity of the forum.

Second, EMC has not articulated the goals or benefits of this new release process to our customers. And I offer my apologies to you and the others who have posted here for creating needless confusion and frustration. 

Third, a simple translation of release labels makes everything easier to understand. What used to be beta is still in fact beta, and that is code that has not completed qualification and is not allowed into production environments. (Note: NetWorker 7.6 SP2 completed the beta program in March) What used to be GA is now called RA. In each case - old process and new - the code has completed a full and formal EMC qualification process and is subsequently released for customer use in production environments. There is no difference in product quality. And what used to be called Service Pack 1 is now called GA, essentially a release vehicle that allows EMC to get fixes for the early life bugs out to customers who have preferred to postpone adoption of a new release until the arbitrary goal of 'stabilization' has been reached. This is the very same translation that I have shared with EMC account teams and technical sales.

The benefits of this new release process can be easily summarized. By asking our inital adopters to 'register' for access to the code we are able to qualify the intended use of our customers (which wasn't occurring with the old process), track the identity of customer/EMC internal downloads (not trackable via PowerLink downloads), immediately notify our initial adopters if a severe problem was discovered (which couldn't be tracked with the old process) and allows us to develop qualitative mterics for stability, measuring time-in-use against reported problems. If you have ever asked the Listserv community "How many of you are using release x.x and have you seen any problems?" then you understand our goal.

BTW, the name 'Restricted Access' is misleading. To date, we have restricted the access to NetWorker 7.6 SP2 code to only 550+ customers. It would be better to consider this new release milestone as 'Registered Access'. If you can agree to think about RA as 'Registered Access', then EMC can agree to never let our engineers do marketing again.

Finally, the refresh build has already been downloaded by more than 300 of those initial adopters. Again, without this release process there would be no way for EMC to reach out to the affected user community so quickly and so directly. Had this been an actual emergency, the new process would have allowed us to alert users that the equivlaent to a 'consoldiated hotfix' package is available for download. In this particular test of the NetWorker emergency broadcast system the refresh build only adds support for last minute qualifications of DD Archiver and support for another platform (I can't recall at the moment). I'm not aware of any major bug fixes that have been discovered during RA program so far, although there may be minor bug fixes included in the refresh build. The RA program manager will have the details and can be contacted through Feedback Central.

On behalf of the NetWorker team, our apoligies for the unneccessary confusion. I hope you can see that RA is not intended to be a really well marketed beta program, but is instead a program designed to drive NetWorker to new levels of quality.

Best regards,

NetWorkerPM