Dear Anu,
First of all, many thanks to offer this community an entry point
for bringing up our inputs.
You maybe know about me as author of Networker Reporting Utility Freeware
(http://users.skynet.be/networker_reporter), amply used by this
commuity's members. I am, for my part, working with (and enjoy working with)
former Legato Networker (and its Digital Equipment's DECNSR OEM
version) since version 3.x, years '94.
Since that time, I do consider 2 majors things to be missing from
media database :
1) Which drive did write SSIS chunck (being complete, head, medium
or tail part) on used media.
Since years, admins are workarounding missing info thru internal scripting.
This neglect increases difficultly when tracking medium errors, no
reliable information about used drive can be tracked back.
This has a lot of indirect consequences, preventing admins for brainy
resource management in DDS environment, keeping nsrd's main job overloaded
in unnecessary resource lookup/sharing, nor possible nor reliable resource
usage tracking resulting in exceeding resource usage from configuration
settings and longer recovery time (more medium to process for complete
SSID recovery). Last versions did workaround last one by introducing
limitative device target sessions on top of load-balancing device target
session settings.
I do not think adding media datbase a table, containing device name
and it's resource id, and linking it up with per SSID record
and per SSID used Media record(s)/index(es) to be an hard work.
2) From lot of administrator's eyes, media database is also lacking
of time clone copy operation did complete :
There are NO way at all (nor via daemon.raw, nor via GUI,...)
to track when a SSID has been cloned and/or staged.
Version 7.4 and above did change/introduce clone operation start time
but no clone opration completion time. Relying on SSID SSACCESS field
from media db (although theoretically being last SSID read/write access
operation time is not always accurate, ex up datedby a recover).
This prevents better resource usage and datazone tuning, device resources
not always used as best they can be.
Warm regards,
Thierry.
PS : Adding a vote for new auth method removal (or turning back
oldauth as default authentication method, keeping new one as an
option)
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Anu Yamunan
Sent: vendredi 13 août 2010 20:26
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Future of Networker
Hello,
I did not want this question go un-answered.
NetWorker continues to have a very strong roadmap and significant
engineering investment. We have a major new release coming in the next few
months that will include Data Domain integration, scheduled cloning and
checkpoint restart.
It would be great to get people's input on other desired features or
enhancements. Product management will gather that input to inform upcoming
releases.
If you are not comfortable responding to the list, please email me directly
at yamunan_anupama AT emc DOT com or NetWorker_Product_Management AT emc DOT com
Regards,
Anu Yamunan
Senior Product Manager
EMC Backup Recovery Systems
2841 Mission College Blvd Santa Clara, CA 95054
--- On Thu, 8/12/10, Kinnison <networker-forum AT BACKUPCENTRAL DOT COM> wrote:
From: Kinnison <networker-forum AT BACKUPCENTRAL DOT COM>
Subject: [Networker] Future of Networker
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thursday, August 12, 2010, 8:11 AM
Now that EMC has been selling Avamar for a few years, it seems that
Networker has been more and more pushed into the background. Do you see any
future for this product? What features or improvements would you like to
have added if you think there is a future for Networker? For example, it
makes sense that revamping the nwrecover command would seem to apparent.
+----------------------------------------------------------------------
|This was sent by paul.gilles AT navteq 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
|
