NetWorker (indeed, any complex piece of software) is like a jigsaw puzzle. In order to use it properly, you have to learn how to put those pieces of the jigsaw puzzle together. Having just run another NetWorker training course, here’s some tips if you’re new to NetWorker:
- Have handy access to documentation about the command line tools. For Unix users, this means to make sure the man pages are installed on every client, and you use them. For Windows users, this means make sure you download and maintain access to the NetWorker Command Reference Guide.
- Get the basic nomenclature down pat. For instance, at bare minimum make sure you understand the following NetWorker terms:
- Tier terms:
- Client
- Server
- Storage Node
- Dedicated Storage Node
- Resource/Configuration terms:
- Client
- Group
- Pool
- Policy
- Schedule
- Level
- Notification
- Device
- Jukebox
- Backup/Recovery terms/concepts:
- Saveset
- Automated backup
- Manually initiated backup
- Recovery
- Directed Recovery
- Clone
- Stage
- How backups automatically start, how schedules and browse/retention policies are applied, and how pools are selected
- Operational terms:
- Label
- Relabel
- Mount
- Unmount
- Deposit
- Withdraw
- Inventory
- Reset
- Database terms:
- Client file index
- Media database
- Saveset ID
- Clone ID
- nsavetime
- Saveset dependencies and their relation to eligibility of a saveset or volume for recycling
- Tier terms:
- Unless you are 100% certain as to what you’re doing, don’t*:
- Run a command with an “auto answer yes” option set
- Touch nsradmin
- Ever commit to a relabel operation in a library without confirming slot ranges
- Make spur of the moment backup configuration changes
- Assume an untested backup process can be recovered from
- Please read the Disaster Recovery Documentation before you have a disaster! Keep in mind at least half of this document is devoted to what could loosely be termed as “Disaster Recovery Preparedness”.
- Don’t use the default pools – or rather, don’t trust any backup that media verification does not occur on. That means – if you backup but don’t clone (again, why?), make sure you have auto media verification (AMV) turned on. If you backup and clone everything, you can leave AMV off for the backup pool (since you’re cloning, you’re doing a very complete media verification anyway), but should turn it on for the clone pool.
- Check your savegroup completion reports. If you don’t want to check these, just assume all your backups have failed. (I.e., check them.)
- Zero error means fixing the error, not masking it. (In particular, be very careful about directives.)
- When it comes to directives – skip for files, null for directories. Yes, there’s always exceptions, but this should be the same as an “i before e” rule for you.
Over time I may come back to this and add bits and pieces as I think of them.
* Obviously over time as you become more used to NetWorker, these restrictions relax. For instance, there’s a lot of powerful stuff that you can do within nsradmin, the command line configuration administration tool – however, it will also readily allow you to shoot yourself in the foot if you get it wrong.
