It’s that time of the year where I sit back for a moment and look at what articles have attracted the most readers over the year, and it’s a fairly eclectic bunch. Interestingly, for the first time since forever, the article about fixing NSR Peer Information issues didn’t come first – we have some new winners.

10 – New Micromanual – LinuxVTL and NetWorker

The second micromanual was a step-by-step guide for configuring the open source LinuxVTL system with NetWorker. I had hoped when I started writing micromanuals that I’d get them more frequently delivered, but various factors get in the way of this. Maybe in 2012 I’ll be able to get a couple more out and available.

9 – Killing scheduled cloning operations

When NetWorker’s scheduled clone option was introduced, there were a few bugs relating to stopping a scheduled clone operation from the GUI. Sometimes you could, and sometimes you couldn’t. However, you could always kill a scheduled clone job from the command line, which is what this post explained.

8 – NetWorker Firewall Configuration on Windows

Very early in the year I was doing a lot of work with NetWorker on Windows 2008 R2, and I was noticing a few gaps in the installation process when it came to the process of automated configuration of the Windows Firewall to work with NetWorker daemons. This post explained the lessons I learnt.

7 – Carry a jukebox with you (if you’re using Linux)

This article was my first post about configuring the open source LinuxVTL system with NetWorker. Since then LinuxVTL has evolved quite a lot, and I’ll likely even need to update that micromanual early in the new year as a consequence.

6 – Why I’d choose NetWorker over NetBackup Every Time

Despite the fact that the article was titled “Why I’d choose…”, I had a rather indignant response to this post insisting I was being a jerk by writing it. I stand by every word in that post. I would not, personally, elect to choose NetBackup over NetWorker on the basis that NetBackup only has true image recovery as an option, and that NetBackup doesn’t support dependency chains for backup images. I see both of these factors as critical to a true enterprise backup product, and NetBackup only half supports one of them. That doesn’t make me a jerk, it makes me someone who gives a damn about your data.

5 – Using NetWorker Client with Opensolaris

A guest article written by Ronny Egner, this post covered off getting the NetWorker client working with the OpenSolaris version of Solaris.

4 – Basics – Fixing “NSR peer information” errors

A persistent challenge in NetWorker is when the NSR peer information gets out of whack; usually this can happen when a significant change happens on a client, and the server must have this information reset. I’d still love to see this article become irrelevant by seeing an option appear in NMC to handle it, but until then, this will remain a fairly popular article.

3 – This is wrong

Earlier this year, an Australian hosting service lost thousands of hosted domains and websites due to a “hack attack”. Supposedly the clever hackers destroyed not only the production data, but also all the backups.

What really went wrong was that the company in question had designed a very poor and inadequate backup solution. Rumours were abounding at the time that backups were just simply replicated snapshots. Snapshots may be able to act as backups, but not indefinitely, and not if they’re the only thing configured. (Backups and snapshots are effectively ‘sister’ activities in ILP.)

2 – micromanual: NetWorker Power User Guide to nsradmin

The original micromanual – “NetWorker power user guide to nsradmin” was and remains extremely popular. There’s been thousands of downloads of it since its release, including quite a number from EMC themselves, so it’s clearly a handy resource. If you’ve not downloaded it yourself but you want to boost your NetWorker productivity, it’s a must read.

1 – NetWorker 7.6 SP1

When NetWorker 7.6 SP1 came out, it was a huge release. In my opinion, it should have been numbered NetWorker 7.7 at least; it wasn’t a minor set of changes or a round of bug fixes, it included significant functionality updates (including one of my favourites – support for Boost). As the number one read article of the year, it’s been a big resource for people looking at the functionality of newer releases of NetWorker.

And that, they say, is that

This year has personally been a huge year for me. My partner and I moved state/city in June, going from a regional area just outside of Sydney to the inner west of Melbourne. We also celebrated our 15th anniversary together, surrounded by many of our new friends (who are like family to us) and a few of our old friends. We were even invited to get on the radio to talk about that, not only from the longevity of the relationship and having run the anniversary party up against the monthly Melbourne Den night. (There’s a podcast coming…) It was also the year when I sorted a lot of stuff out, and to boil all this down: it was the year that I spent a lot of time focusing on my personal life and not so much on the blog.

There may still be one or two posts left for 2011, but I’m also starting to get my head around changes and new material for 2012, and I believe 2012 will be a big year for NetWorker users.

 

After an 8+ hour outage on my domain this week, with no explanation from my hosting provider, I’ve finally had enough!

So, over the coming weeks, as I get things setup in the background, there may be brief outages on this blog as I transfer across to a new, better and more stable hosting provider.

Apologies, in advance, for any disruption.

Cheers,

Preston

 

My employer, IDATA Australia, is expanding, and we’re looking for subject matter experts around EMC products, with a strong focus on backup and archiving skills. Regardless of whether you’re located in Australia or the other side of the world, we may have a position for you. The roles will cover both support and services, so you need to have great communication skills and a strong customer focus.

Specifically, we’re looking for people who are comfortable working in a combined support and services team – i.e., the role would involve both deployments and training on customer sites, as well as customer remote support. If you’ve got experience in one or the other rather than both, that’s not a problem so long as you’re eager to learn.

The Australasian market is a region of high growth, so working for IDATA will keep you challenged to stay in top technical form.

If you’re interested in working for IDATA Australia, contact me.

(Please note, IDATA does not accept solicitations from recruitment agencies.)

 

In March this year, I ran a NetWorker Usage Survey to gauge the lay of the land in terms of how and on what NetWorker is deployed within the user community. As a result of that, hundreds of people downloaded the March 2010 NetWorker Usage Survey Report.

It’s time to revisit that survey; I’ve adjusted the questions a little based on some of the responses from the previous survey results, and I’m keen for as many answers as possible to make this a worthwhile report. (Don’t forget, the report will be free to download.)

I’ll be aiming to keep the survey running until the end of November, and publish the results early in December. So please, fill out the survey below and have your say!

~

The survey has now closed. The report will be posted soon.

 

Amazon are currently selling Enterprise Systems Backup and Recovery: A Corporate Insurance Policy at a reduced price.

If you’ve been wanting to buy it, but the price has previously put you off, this may be a good excuse to go back and revisit Amazon for it.

Remember if you do read it that reviews are always welcome!

 

Having spent the last several days of my holiday clearing lantana from my property, I needed to take a break from yard work and spent the day writing a new micromanual.

Titled “Configuring LinuxVTL on CentOS for NetWorker”, this micromanual focuses on providing a start-to-finish description of the process required to install and configure the LinuxVTL software and then subsequently get it configured with NetWorker – in this case, NetWorker 7.6 SP1.

If you’re interested in using the LinuxVTL for lab/testing purposes, but needed a more comprehensive guide on getting it set up and running, this micromanual should get you over the line.

To download, go to the micromanuals page and fill out the registration form.

 

When something is going wrong in a NetWorker environment, the first thing you need to do is be able to run up some basic tests. If the issue has anything to do with NetWorker clients, you’ll want to be able to initiate a series of network, probe and index based tests. If you’ve got nothing scripted, ‘check-clients’ from IDATA Tools may very well be what you’re looking for.

As a command line tool, ‘check-clients’ can power through a suite of different tests and data gathering activities against your clients, all with very minimum effort on your part. Let’s look at the tests that are currently available:

[root@nox bin]# check-clients -l
Test Name           Test Description
------------------- ------------------------------------------------------
client_ids          Returns client ID for each configured client
empty               Report clients with empty indices
index               Perform nsrck -L3 on each client
index_rebuild       Perform nsrck -L6 on each client
info                Retrieve client information
list_active         List all configured clients in active groups
list_all            List all clients currently configured
performance         Check backup performance via bigasm
ping                Ping each client
probe               Savgroup probe for each client
resolution          Test/confirm name resolution
rpcinfo             Test rpcinfo/portmapper access
used_space          Calculates used space for backups

Now technically, not all of the above are actually tests as such – for instance, the used_space option was one recently requested by a customer to report on all backups currently held by a backup server for a client. Running it on one of my lab machines, the output looks like the following:

[root@nox bin]# check-clients -g all_active -t used_space
============================================================
Running test: used_space (Calculates used space for backups)
============================================================
        Client                         Used Space (GB)
        ----------------------------   --------------------
        archon                                    362.60783
        faero                                       0.00000
        luyten                                      0.00000
        nox                                       544.40887
        ----------------------------   --------------------
                 Total for 4 clients              907.01669
        ----------------------------   --------------------

To me, that’s a combo test/information gathering option; specifically the customer was after this particular test so that they could spot any newly added clients that hadn’t been backing up (i.e., by having a “Used Space” of 0 GB).

Equally, there’s use in periodically running the “client_ids” test – running and keeping the output of this test will give you help in any sticky situation where you suddenly need access to a previous clients’ host ID:

[root@nox bin]# check-clients -a -t client_ids
=======================================================================
Running test: client_ids (Returns client ID for each configured client)
=======================================================================
        aralathan = 65100d33-00000004-464fcacc-464fcacb-00050000-c0a86404
        archon = 3f33ca7b-00000004-43a4837c-43a484d7-00030000-c0a80006
        asgard = 00b151ed-00000004-43a4837b-43a4837a-00010000-c0a80006
        djwmp = 5560bbf6-00000004-4910cd4b-4910cd4a-01961a00-3d2a4f4b
        faero = 76c06b0a-00000004-453e8e44-453e8e43-00310000-c0a86406
        loki = d3f277da-00000004-4857452f-4857452e-00020000-c0a86404
        luyten = 93166424-00000004-4a2f8cde-4a2f8cdd-01041a00-3d2a4f4b
        nimrod = d6454919-00000004-496aaadc-496aaadb-006f1a00-3d2a4f4b
        nox = 85acae6f-00000004-464fbdd1-464fbdd0-00010000-c0a86404
        valhalla = 61d3ca1e-00000004-495525db-4955299a-00051500-98e71c17

Moving on into actual test territory, multiple tests can be teamed up to do a chunk of information gathering in one command. For instance, combining a ping test and a name resolution test against all active clients is as simple as:

[root@nox bin]# check-clients -g all_active -t ping,resolution
=====================================
Running test: ping (Ping each client)
=====================================
	archon  (0 responses, expected 4)
	faero  (0 responses, expected 4)
	luyten  (4 responses)
	nox.pmdg.lab  (4 responses)

=======================================================
Running test: resolution (Test/confirm name resolution)
=======================================================

	archon
		Name: archon (archon.pmdg.lab) (192.168.100.1) 
		Name: archon.pmdg.lab (archon.pmdg.lab) (192.168.100.1) 
		Addr: 192.168.100.1 (archon.pmdg.lab) 

	faero
		Name: faero (faero.pmdg.lab) (192.168.100.10) 
		Name: faero.pmdg.lab (faero.pmdg.lab) (192.168.100.10) 
		Addr: 192.168.100.10 (faero.pmdg.lab) 

	luyten
		Name: luyten (luyten.pmdg.lab) (192.168.100.18) 
		Name: luyten.pmdg.lab (luyten.pmdg.lab) (192.168.100.18) 
		Addr: 192.168.100.18 (luyten.pmdg.lab) 

	nox.pmdg.lab
		Name: nox.pmdg.lab (nox.pmdg.lab) (192.168.100.4) 
		Name: nox (nox.pmdg.lab) (192.168.100.4) 
		Addr: 192.168.100.4 (balrog.pmdg.lab (unknown))

None of this is re-inventing the wheel of course, but being able to just run a single command that cycles through and tests every active client (or even all clients) is particularly useful.

Even performance testing is catered for with check-clients; reaching out to the clients, the utility can run bigasm tests automatically – a great way for easily testing where performance hits are happening on the network. For example, a quick/basic demo of this option is below:

[root@nox bin]# check-clients -c luyten,nox.anywebdb.com -b Staging -S 50 -t performance
===============================================================
Running test: performance (Check backup performance via bigasm)
===============================================================
        luyten (Solaris/UNIX style test)
                Backup 50 MB to Staging
                50 MB took 12 seconds (4.17 MB/s)
        nox.pmdg.lab (Linux/UNIX style test)
                Backup 50 MB to Staging
                50 MB took 3 seconds (16.67 MB/s)

If you are looking around for a test kit option for NetWorker – and want access to a heap of other goodies at the same time – then ‘check-clients’ out of the IDATA Tools suite may very well be what you need.

 

Today my site hosting service suffered an outage of over 12 hours.

While this was the first major outage for the NetWorker Blog, I have two sites hosted with the service, and have suffered several maddening and unexplained outages on the other site. Each time I’ve requested assistance regarding the other site my support inquiries have taken over 24 hours to be answered, by which time the site has been available again for hours and I get a drones’ response: “Your website appears to be working.”

As a consequence I’ll be starting to look for a hosting provider that actually has a real 24×7 support team and communicates well with its customers. If anyone out there has recommendations for hosting services, preferably Unix/Linux/Mac based that support WordPress, PHP with custom scripts and decent bandwidth/storage limits, I’d be grateful in hearing from you.

 

A couple of weeks ago now I decided to take a break from writing on the blog due to personal reasons. Being a bit of a geek, it’s fair to say that I have a lot of IT-related personal projects on the boil at any given time. Or rather, I used to.

However, I found that it had reached the point where I was focusing so much on the blog that I wasn’t giving myself any time to work on other projects that also happen to give me a great deal of personal satisfaction. So I wanted to pull back from the blog for a little while to evaluate where I was going, and what I was doing.

In its own way, this has been both a challenge and also very rewarding. Rewarding because I actually managed to achieve several things that I’d been putting off for ages, and challenging because it made me realise how much I’ve been using this blog as a measure of personal satisfaction.

On top of all that, last Friday marked my partner’s 40th birthday, and I would have been remiss if I’d not spent serious time on preparations for that*.

So, where does this leave nsrd.info?

I’m back, the hiatus is over, but having had some time for reflection, there’ll be a few changes so that I can ensure I don’t let the blog take over my personal life again. Here’s what those changes are going to be:


  • I’m going to wherever possible limit myself to two articles a week. Some weeks there may only be one.
  • I’d be very pleased to have additional contributors. A while ago Ronny Egner contributed a great article about installing the NetWorker client on OpenSolaris, and I’d be pleased to hear from others who have information they’d like to contribute.
  • Before the hiatus, I cutover to using Mail Chimp for notices about new articles. I’m going to continue to use Mail Chimp, but, I’ll be only using Mail Chimp for those one or two articles a week. What does that mean? See the next point…
  • While I’ll only be aiming to publish one or two articles a week, I’ll be starting a new “Tidbit” category and if minor items come to mind during the week (e.g., I spot an article I’d recommend you read), I’ll post it under the Tidbit category. With that in mind, you may very well wish to subscribe to the site’s RSS feed. These won’t be long articles, more like extended tweets.
  • My previous plan for micromanuals will probably slow down quite a bit. At this point I’ll be aiming to provide a micromanual for configuring LinuxVTL with NetWorker by the end of June, and after that I’ll evaluate when the next one will come out, and what it will be about.

In short, I’m hoping that by taking a more structured approach to the blog I’ll get a more balanced personal life :-)

In keeping with the strategy of actually finishing some personal projects, this week I’m going to be focusing on completing the Nomenclature page rather than completing new articles.

Thanks for your patience!


* On that front, here’s a tip for a 40th birthday present: an iPad. Well, that was part of it. The other tip is – if you’re going to have a party – organise in advance a photo book of everyone attending, and get them to sign and leave a message in the book on the night. It seems you can’t go wrong with that, as I was pleased to discover.

 

I’ve now opened forums on the primary nsrd.info site. While I’d initially planned to try to setup an alternate style of forums to others that are out there, it’s clear from discussions I’ve been having with various people that a good old traditional forum approach is actually the best way – particularly since the number of visitors that arrive to the blog daily come on the back of questions about NetWorker!

I’d encourage as many people as possible to jump across to the forums. Obviously being brand new, there may be some bugs in the system that we’ll need to work out, but let me know if you strike some issue that we need to address. (Over time I’ll be looking for some additional forum moderators.)

While I’ve not quite decided how to do it yet, over time as questions get answered on forums I’d like to have a repository of “known solutions” available, so please, if you use the forums to ask a question and someone gives you a great solution, return and make a note of it so that over time we can build up a really useful system.

You can access the forums at nsrd.info/forum.

© 2012 The NetWorker Blog Suffusion theme by Sayontan Sinha