NetWorker Blog

Commentary from a long term NetWorker consultant and Backup Theorist

  • This blog has moved!

    This blog has now moved to Please jump across to the new site for the latest articles (and all old archived articles).



  • Enterprise Systems Backup and Recovery

    If you find this blog interesting, and either have an interest in or work in data protection/backup and recovery environments, you should check out my book, Enterprise Systems Backup and Recovery: A Corporate Insurance Policy. Designed for system administrators and managers alike, it focuses on features, policies, procedures and the human element to ensuring that your company has a suitable and working backup system rather than just a bunch of copies made by unrelated software, hardware and processes.
  • Advertisements
  • This blog has moved!

    This blog has now moved to Please jump across to the new site for the latest articles (and all old archived articles).



  • Twitter

    Error: Twitter did not respond. Please wait a few minutes and refresh this page.

Picking the best backup server

Posted by Preston on 2009-02-09

I’ll start this by saying that I used to be an out-and-out Unix bigot, and would still classify myself as strongly preferring Unix over Windows.

So when I’m asked “what operating system should I deploy my NetWorker server on?”, I tend to have to bite my tongue to not immediately respond with say, Solaris*.

The truth is, there’s only one answer to this question: the most appropriate operating system to your environment. This may sound like I’m sitting on the fence, but that couldn’t be further from the truth. Your backup server should be based on your operational strengths. That means if you’re have a completely homogeneous environment comprising only of Windows machines, then clearly the choice should be a Windows NetWorker server. If you have a purely Unix shop, you should deploy a Unix NetWorker server.

But what if you’re a mixed shop?

Traditionally one of two things happen in a heterogeneous environment:

  1. In an “average” sized environment with Unix and Windows system administrators, usually one team will deploy workgroup style backup environments while another will deploy an enterprise package. I’m not sure why this happens, but it’s not often you see enterprise packages deployed by both groups. In this case, the NetWorker server should be consolidated to the current enterprise environment.
  2. In larger environments, there should be a storage and data protection team that includes both Unix and Windows system administrators. In this case, that team should evaluate the unique needs of the environment and pick the most appropriate OS for the backup server on the basis of the overall system administration strengths and compatibilities of the organisation.

I know this sounds like a wishy-washy answer, but the point I’m wanting to make is that the choice of operating system for the backup server shouldn’t make a difference, and for one important reason: NetWorker scales far beyond just using a single backup server. Thus, rather than getting hung up on choosing between Windows or Linux or Solaris or AIX or HPUX (etc.) for the backup server, be prepared to scale your environment to suit.

For instance, I periodically get told, “We don’t want to deploy Windows as the backup server because the environment will get really big.” My response to this is simple: in a really big environment, the backup server should be in an executive role only, simply coordinating backups and handling indices and media databases, with all backups being handled by storage nodes**.

So if you want to know what the best backup server is to run NetWorker on, it’s whatever suits your environment with the caveat – be prepared to scale beyond just a backup server and clients.

* Alas, I’m not able to respond Mac OS X. There’s not even a storage node for this platform.

** Yes, I know that the backup server must at least be able to do its own bootstrap backups – and for what it’s worth, I agree with this requirement.


Sorry, the comment form is closed at this time.

%d bloggers like this: