joka2

updated

15 years ago

J

joka2

144 Posts

0

6382

May 23rd, 2011 04:00

Why is NetWorker 7.6.2 on Restricted Access?

Hi.

Why is NetWorker distributed under RA (restricted access) program?

Does that mean that it's really just að beta version that EMC wants it's customers to run in production?

Regards,

Johannes

  • AllanW1

    334 Posts

    842

    0

    Posted May 23rd, 2011 08:00

    Hi Johannes,

    Absolutely not.   Software released under Restricted Availability (RA) is fully-tested and production-ready.  The process simply allows us to track the software and documentation usage to ensure the roll out meets customer expectations.  After this initial monitoring, the software and documentation will be deemed Generally Available (GA) and moved in total to EMC Powerlink. The RA process also builds in some communication methods so feedback can be received easier than if just moved onto Powerlink for free download.  I recall you had questions about the RA process on the NMM2.3 post too.  Does the process make sense or is it that 7.6 SP2 does not have a GA stamp on it?

    Allan

  • joka2

    144 Posts

    842

    0

    Posted May 23rd, 2011 09:00

    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

  • unexpected1

    34 Posts

    842

    0

    Posted May 23rd, 2011 11:00

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

  • AllanW1

    334 Posts

    842

    0

    Posted May 23rd, 2011 12:00

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

    Allan

  • unexpected1

    34 Posts

    842

    0

    Posted May 24th, 2011 11:00

    Thanks Allan, going to check it out.

  • adanac1

    19 Posts

    842

    0

    Posted June 3rd, 2011 05:00

    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.

  • ble1

    6 Operator

    14354 Posts

    56186 Points

    842

    0

    Posted June 3rd, 2011 05:00

    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.

  • ble1

    6 Operator

    14354 Posts

    56186 Points

    840

    0

    Posted June 3rd, 2011 06:00

    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).

  • adanac1

    19 Posts

    840

    0

    Posted June 3rd, 2011 06:00

    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.

  • bingo.1

    1 Rookie

    2430 Posts

    1053

    0

    Posted June 18th, 2011 02:00

    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?