It's evident that EMC lost their focus on NetWorker. late Exchange 2010
support and VADP support are some good examples on how EMC is neglecting
NetWorker customers. Actually EMC still talks about the Server 2008 DR
support and the VADP support as "new features", but those features should
had been out 18 months before it got released. Another example is the
security model as discussed in the NMM issue thread this week. And what
scares me the most with that issue, is that EMC does not consider it an
issue.

Can't the users of this community not unite in putting pressure on some
RFE's?

J.W.




2011/10/19 STANLEY R. HORWITZ <stan AT temple DOT edu>

> Paul,
>
> Have you contacted your local EMC account manager to ask to see a NetWorker
> roadmap?
>
> On Oct 18, 2011, at 3:38 PM, HackNDos wrote:
>
> > Most all of there efforts switched from Networker into their Avamar
> product.  This was evident with the Exchange 2010 Support.  Typically
> something that would get released 90 days after a product is released took
> them 1.5 years to release.  And if you noticed during this same period
> Avamar had Exchange 2010 support.  In fact our account rep tried to get us
> to switch from Networker to Avamar.
> >
> > I have been questioning where Networker has been heading since that all
> started and how much effort is EMC going to keep putting into Networker
> based on these actions.
> >
> > Someone said do we want a good vs bad product release, I think maybe
> something more transparent like a roadmap of what they have planned would
> make plenty of Networker customers happy.
> >
> > Just my thoughts....
> >
> > Thanks
> > Paul
> >
> > +----------------------------------------------------------------------
> > |This was sent by hackndos AT gmail DOT com via Backup Central.
> > |Forward SPAM to abuse AT backupcentral DOT com.
> > +----------------------------------------------------------------------
> >
> > To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> > via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type
> "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER