Over the years I’ve been forced to come to one key conclusion about the NetWorker ‘tmp’ directory and NetWorker upgrades.

While it’s not stated in any upgrade documentation, and in theory it shouldn’t matter, anyone upgrading their NetWorker server software should, as a matter of course, delete the server’s NetWorker ‘tmp’ directory prior to starting the new version of the software.

If you’re not familiar with this, you’ll find it:

  • On Unix/Linux platforms as: /nsr/tmp
  • On Windows platforms in the NetWorker install directory, as “Legato\nsr\tmp”.

This directory contains a plethora of files, some relating to savegroups, some relating to operations – in general ‘tmp’ is almost a poor choice of nomenclature for it: I like to think of it as a ‘state’ directory instead.

Nine times out of ten, or perhaps even 49 times out of 50, if I do an upgrade of a NetWorker server and forget to delete the ‘tmp’ directory, what can only be described as weird stuff will happen within 72 hours. Groups may not finish. Media may not unload. Libraries may forget state. The mouse on your desk may spontaneously quantum ooze to the floor. You may hear the Twilight Zone theme music playing in the background when it should be entirely quiet – that sort of stuff.

So, if looking for a new rule to follow when upgrading NetWorker on your server, please make sure you delete the NetWorker ‘tmp’ directory. You’ll save yourself a lot of time and hassles.

(Note: Deleting the NetWorker server ‘tmp’ directory prevents any backup that previously failed or was stopped from being restarted after the failure – it will need to be started as a whole new operation.)

 

Released in December 2008, NetWorker 7.5 represents an incremental increase in NetWorker functionality mainly aimed at the following three things:

  • Virtualisation support – better VCBs, better awareness of virtual infrastructure, visualisation of virtual infrastructure, etc.;
  • Better integration with third party authority systems – e.g., LDAP, etc.;
  • Support for IPv6.

It’s the support for IPv6 that poses a particular challenge for Mac OS X clients. A bug currently exists with the NetWorker client for OS X that causes the startup and shutdown of the NetWorker daemons to take somewhere in the order of 5 minutes for the average machine. Given that IPv6 is enabled by default on Mac OS X, this means that a very high proportion of Mac OS X clients that are upgraded will experience this problem.

This doesn’t pose a problem in normal operations; this startup and shutdown normally occurs in the background for machine boot/reboot/shutdown, and thus doesn’t impact the time taken for a machine to start or shutdown – however, where it does pose an inconvenience is for an administrator working on the command line who needs to debug or test issues on a Mac OS X client. Indeed, the shutdown takes long enough that at least 50% of the time it times out and the nsrexecd processes need to be manually killed.

There are three options that administrators can choose to perform:

  • Delay deployment of NetWorker 7.5 on Mac OS X until the release of 7.5 SP1, where this issue is going to be fixed. (A 7.4.x client will communicate successfully with a 7.5 server.)
  • Accept the shutdown/startup delay for the time being and document it so that backup and system administrators are aware of the implications for the time being.
  • Disable IPv6 on affected clients until the release of NetWorker 7.5 SP1. This can be done using the command: ip6 -x  on the affected Mac OS X machines.

This isn’t a big inconvenience, but it’s one to be aware of.

© 2012 The NetWorker Blog Suffusion theme by Sayontan Sinha