NetWorker 8 roundup


It’s not everyday that a product like NetWorker gets a major version release. I had wanted to provide some insight in regards to this release and delve into the new features a little. Did I mention I live in Canada? Our summers are short and my weekends have been filled with beer, Bar B Que’s, weddings and some summer festival type things. Right now I’m on my deck with my wife who has just made some kind of fruity alcohol filled concoction. Anyway, it has been a great summer. Work has been a little to busy for research during business hours. Of course Storagezilla and Preston were way more productive thankfully. Preston got in the lab to play with the product a little. He identifies some major architectural changes such as concurrent read write access to AFTD’s and a new daemon nsrsnmd which is a storage node multiplexor manager. This will will results in fewer interuption to the nsrd process.

Storagezilla provides some great insight into some of the new features and how NetWorker 8 will integrate with Data Domain boost technologies and get it’s hooks into more applications and databases.




I’m looking forward to doing some more research and presenting a case to my clients to upgrade to NetWorker 8.

no comments


EMC and Data Protection Unification

A constant theme in all the Backup/Recovery sessions I have attended has been about the integration of Avamar, Data Domain, NetWorker, major applications and VM’s. I didn’t realize how much work EMC Backup has done in this area. I was pretty impressed to see the work that has been done in NetWorker to provide a single interface to manage the backup infrastructure in these products.  It’s interesting to hear this message from EMC and I think it is one that they should promote more. The single pane is very compelling to most customers. EMC has done a great job on positioning Avamar, NetWorker and Data Domain to provide specific benefits in data protection. Administration of these systems as well as application recoveries (including RMAN) can be completed via the NetWorker GUI.

I had not explored the virtualization monitoring area of NetWorker before, but I can see the huge value it adds after seeing it. The VM visualization screen shows the entire VM infrastructure and reports on how your virtual machines are backed up, but more importantly which systems aren’t.  The focus on best practices were on leveraging VADP and DD Boost for ever broadening application support.




1 comment


nsradmin is your friend

I have a confession to make. I like the GUI. Don’t hold it against me. I know most of us in Backup Recovery and the products we support have roots in UNIX. I am well aware of how superior the command line can be and generally is. That’s what this post is about.  I find sometimes  the NetWorker GUI can be finicky about what it will and wont let you do, even though there may be a menu option for it?  So this week I noticed some incorrect devices hanging around. I had taken a vacation a while ago and it looks like somebody was having some fun. Grrr!

Do you think I can right click and delete? Nope!  So I configure the device as stand alone, again I try to delete it. Nada! Denied! So what to do? Thanks to EMC support for showing me this sometime ago. To the nsradmin utility!

Use tab to move through the menu. First choose NSR device from the select menu, then use next to move through the device list.

When you find you device in question select delete.


Boom! Take that careless co-worker with no respect for others backup env!



no comments


NetWorker Command Line Restores

Typically, I launch client restores using the client NetWorker GUI on the source client. I think this is a best practice as the source restore client should by default have all the required access and permissions required to its own data. However a few weeks ago a received a restore request for a client that is firewalled. We initially attempted the restore from the client, but ran into the following error.

Recovering files of client ‘cwf###’ from server ‘cls###’ to client cwf###’.
Recovering 1 file from D:\downstream\backup\infosys_exp_tosite\ into C:\temp
Total estimated disk space needed for recover is 23 KB.
Requesting 1 file(s), this may take a while…
Requesting 1 recover session(s) from server.
53363:winworkr: Recover of rsid 993513722 failed: Error receiving files from NSR server `cls##’
73724:winworkr: One or more recover threads failed to exit successfully
73731:winworkr: Parent recover thread exited with errors
52973:winworkr: Didn’t recover requested file C:\temp\EM700299_7002_infosys.2769
Received 0 file(s) from NSR server `cls###’
Recover completion time: 2/7/2012 10:34:10 AM

I initially assumed this may be related to the firewall. I decided instead to perform a redirected restore to one of my NetWorker storage nodes and get the restore done. My plan was to later examine the firewall setting on NetWorker and see if there was a problem there.

But! The restore also failed with the same error on the redirected restore? As stated this is the first time I had attempted a redirect in this backup env, so what was the problem? Well that is still pending, but I wanted to outline what we did do with the help of EMC support to get the restore done.

First we identified via the winworker GUI if the files where there and what date they were backed up and get the saveset ID

[root@cls### ~]# mminfo -avot -q “client=cwf###,savetime>01/27/12” -r name,savetime,ssid,level | more
name date ssid lvl
VSS USER DATA:\ 01/27/2012 253990450 full
D:\ 01/27/2012 3861092125 6
C:\ 01/27/2012 3777206061 6
VSS OTHER:\ 01/27/2012 3340998683 full
VSS SYSTEM BOOT:\ 01/27/2012 3156449364 full

With the saveset ID in hand we ran the the following mminfo command to confirm the required tapes.

mminfo -av -q ssid=69700782 -r name,sumsize,level,ssflags,savetime,volume
 name                             size  lvl ssflags date   volume
D:\                              11 GB incr vF   01/30/2012 001756
D:\                              11 GB incr vF   01/30/2012 VT0605

When confirmed the tapes were on hand we launched the restore via the following.

C:\Program Files\Legato\nsr\logs>recover -vv -d c:\temp\dan -s cls### -S 38610921252 -a D:\downstream\backup\dailytrans\EA111299_dailytrans.2086
Recovering a subset of 166881 files within D:\ into C:\temp\dan
Requesting 1 recover session(s) from server.
recovering 166881 save set(s) on rsid 993552684
asm -r C:\temp\dan\downstream\backup\dailytrans\
asm -r C:\temp\dan\downstream\backup\
asm -r C:\temp\dan\downstream\
Received 3 matching file(s) from NSR server `cls213′
Recover completion time: 2/22/2012 2:57:58 PM


I was glad to get this restore done and have the opportunity to familiarize myself a little more with the NetWorker command line. I’m discovering, like NetBackup that the command line cannot be ignored when performing daily operations of this product.

no comments

     Next Entries »