Installed mine today!  KLX250 dual sport.. I'll see how long I can go before I get pulled over by the locals.. :-)  Would also look good sitting on most desks.  Make sure you reply and let us know what you think and get your address to networkercommunity@emc.com to receive your plate...

glamour shot

NetWorker 8 equals to speed, which is greatly needed as the number of backup sources and amount of data is continously increasing. But not just in terms of data transfer thanks to the enhanced ddboost support, but also the administrative interface that improves visibility and manageability. Built for the future, not just today. Great work!

Not upgrading yet...probably would wait for SP1

Would be great if there is a white paper or best practices about Multi Tenancy

As much as I would love to install NW 8.0 I will not until it has been GA for at least 6 months.  I cannot afford to spend countless hours with EMC support to get issues resolved.  Our shop is just too big for that kind of downtime.

I am however going to upgrade to the NW 8.0 SN and DSN in at least one of my environments. 

I would like to see a document stating how much CPU/RAM is required by the new NetWorker 8 server on a per client basis. 

If I have 100 clients I need X GB of RAM and Y number of CPUs.

If I have 1000 clients I need X  GB of RAM and Y number of CPUs.

If I have 10,000 clients I need X  GB of RAM and Y number of CPUs.

This would help us to properly size the networker server(s) in the environment.

We are now entering into a backup world where we have PB of data.  We need not only faster backups but faster recovery options.

Hello...didn't get any gifts...

Did you send your mailing information (including phone number, pls.) to NetWorkerCommunity@emc.com?  When you do - voila! 

I think it looks very promising, I posted on the mailing list about a couple of challenges I had with it, but so far I'm a happy camper.

I especially like the improved handling of AFTD's.

/tony

Hi !

We will -in short i hope- be using the option to perform direct backups from individual clients to DD using DD Boost. It'll shrink our backup window because these last months it has become unmanageable !!! Data never stops growing !!!!

Josu.

NetWorker 8 has some very good features. After going through NetWorker 8, I was impressed with some of the new features and enhancements:

1)     NMM Client configuration wizards for SQL, Exchange and HyperV : this is something that most of the customers were looking for. It was not easy to go on each and every client and run nsrsnap_vss_save.exe to get the list of savesets. This will definitely make one’s life easier. Atleast somewhat!

2)     If you start a session from command line, there was no way of stopping it unless you kill the process. This new feature was added in NW 8 which does define the term “centralized management”.

3)     Editing multiple “common” resources attributes was really required from NW 7.x. Good to see it appear in NW 8. However, I am not sure if multiple sorting option is still available.

4)     History of previously ran groups! Good feature.

However there are few usability enhancements which can be implemented easily. They are:

1)     When creating a media pool, you have the ability to restrict that particular pool to use specific devices from a PTL/VTL or all devices. Maybe a tree like structure can be implemented, where the user selects either the whole VTL or certain devices from that particular VTL/PTL. Now, we need to know which device belongs to which VTL/PTL and it becomes very difficult once there are multiple VTLs and PTLs defined in NetWorker

2)     Maybe having a separate log file for each group / backup would help reduce the overload of going through the daemon.raw file and make life easy for the user to find out the problem

3)     Sorting multiple columns would certainly help the user in organizing their backups

4)     Creating a new client with default values in NetWorker when the client/storage node is installed would be an easy task (nsradmin command?!?)

NetWorker 8 has some very good features. After going through NetWorker 8, I was impressed with some of the new features and enhancements: 1)     NMM Client configuration wizards for SQL, Exchange and HyperV : this is something that most of the customers were looking for. It was not easy to go on each and every client and run nsrsnap_vss_save.exe to get the list of savesets. This will definitely make one’s life easier. Atleast somewhat! 2)     If you start a session from command line, there was no way of stopping it unless you kill the process. This new feature was added in NW 8 which does define the term “centralized management”. 3)     Editing multiple “common” resources attributes was really required from NW 7.x. Good to see it appear in NW 8. However, I am not sure if multiple sorting option is still available. 4)     History of previously ran groups! Good feature.  However there are few usability enhancements which can be implemented easily. They are: 1)     When creating a media pool, you have the ability to restrict that particular pool to use specific devices from a PTL/VTL or all devices. Maybe a tree like structure can be implemented, where the user selects either the whole VTL or certain devices from that particular VTL/PTL. Now, we need to know which device belongs to which VTL/PTL and it becomes very difficult once there are multiple VTLs and PTLs defined in NetWorker 2)     Maybe having a separate log file for each group / backup would help reduce the overload of going through the daemon.raw file and make life easy for the user to find out the problem 3)     Sorting multiple columns would certainly help the user in organizing their backups 4)     Creating a new client with default values in NetWorker when the client/storage node is installed would be an easy task (nsradmin command?!?)

NetWorker 8 has some very good features. After going through NetWorker 8, I was impressed with some of the new features and enhancements: 1)     NMM Client configuration wizards for SQL, Exchange and HyperV : this is something that most of the customers were looking for. It was not easy to go on each and every client and run nsrsnap_vss_save.exe to get the list of savesets. This will definitely make one’s life easier. Atleast somewhat! 2)     If you start a session from command line, there was no way of stopping it unless you kill the process. This new feature was added in NW 8 which does define the term “centralized management”. 3)     Editing multiple “common” resources attributes was really required from NW 7.x. Good to see it appear in NW 8. However, I am not sure if multiple sorting option is still available. 4)     History of previously ran groups! Good feature.  However there are few usability enhancements which can be implemented easily. They are: 1)     When creating a media pool, you have the ability to restrict that particular pool to use specific devices from a PTL/VTL or all devices. Maybe a tree like structure can be implemented, where the user selects either the whole VTL or certain devices from that particular VTL/PTL. Now, we need to know which device belongs to which VTL/PTL and it becomes very difficult once there are multiple VTLs and PTLs defined in NetWorker 2)     Maybe having a separate log file for each group / backup would help reduce the overload of going through the daemon.raw file and make life easy for the user to find out the problem 3)     Sorting multiple columns would certainly help the user in organizing their backups 4)     Creating a new client with default values in NetWorker when the client/storage node is installed would be an easy task (nsradmin command?!?)

CONTINUE THE CELEBRATION!  Join in the fun, take a break, and watch a quick YouTube video taken from the NetWorker 8 Launch Event at Mercedes-Benz World in London on July 10!  http://bit.ly/RunLgh

Have you noted that we've announced our first Service Pack update to NetWorker 8.0?  It's prime time now, if you haven't done so yet, to download NetWorker 8 and give it a go.  When you do, it's not too late to get a gift for your comments HERE regarding your thoughts and/or experiences with the New NetWorker.

Don't forget to also send a separate email message to NetWorkerCommunity@emc.com with your name, address, and phone number (for shipping purposes only) so we can get your gift directly to you! 

Hi

I have gone through the Networker 8.0 SP1 release notes and   confirmed our infrastructure  badly need Networker 8.0 SP1 upgrade to fix Auto Media Management issues and some other operational issues.

Below are my understandings about Networker 8.0 SP1

Some of the new Features available in 8.0 SP1

(a) Optimized disk reading – Dynamic block size value based on intelligent algorithm can help to improve backup performance.

(b) Device Management changes – New daemon nsrsnmd to manage device operations ,will reduce load of nsrd in networker server.

(c) DDBoost device read-write functionality --- Removes legacy read only mirror devices and this can help us in reducing number of devices.

(d) DDBoost support to multiple interfaces and network identities

(e) Client Direct Feature – Can help us in reducing number of storage node requirements and new DDBoost DSP component can make efficient deduplication.

(f) Stopping Sessions from NMC – This option is very much needed if we are using any external scheduler to start the backup job

(g) NDMP saveset browsing enhancements: Browsing NDMP mount points in saveset selection

Some of points need to be taken care when upgrading to 8.0 SP1

(a) NNM 2.3 is not supported with Networker 8. , need to update NNM2.4 before updating Networker Server

(b) DPA 6.0 not supported with NMC

(c) VM backup not supported for clients is suspended state

(d) It is recommended that number of clone jobs running concurrently not exceeded 35.

Please share with us if there anything else need to be taken care to upgrade 8.0 SP1 from 7.6.3

Sincere Regards,

Aneesh Mohan