Basics – Workflow for adding a new client

A question I get asked from time to time is “How do I do X in NetWorker?”, and by how, I mean what’s the order of steps, rather than a general description.

To me, the configuration steps in NetWorker are often quite minimal compared to the operational and organisational processes that typically should be followed to ensure an appropriately maintained system. Configuring a new client is a perfect example of this, so below is the procedure I normally recommend following:

1. Determine if there are any databases or applications on the host that require module-based backups.
2. Determine if there is anything on the host that should be excluded from backup.
3. Determine any special retention requirements (vs ‘default’ retention requirements used in the business).
4. Determine if any SLAs require integration between backup and other data protection processes (e.g., with snapshots, replication targets, etc.)
5. Check OS and application versions against the compatibility guide if they’re not standard/already known versions.
6. Ensure the backup system has sufficient capacity for bringing the client on-board.
7. Determine what tests are to be applied to this client to confirm it’s successfully brought on-board.
8. Determine whether any backup software to be installed will require an OS or application restart – for example:
   • NMM with GLR might require reboots (and if .Net needs to be installed, 2 reboots may be required).
   • Oracle and other databases may require restarting for library linking.
9. Determine if any firewalls will need to be adjusted to allow for backup traffic.
10. Confirm forward/reverse lookups between all appropriate hosts – for example:
    • New client and backup server
    • New client and storage node(s)
    • New client and IP backup storage (e.g., Data Domains)
11. Confirm network connectivity between all appropriate hosts.
12. File change requests or work plans as appropriate within the organisation, supplying appropriate installation/back-out plans, peripheral configuration activity (e.g., changing firewalls, etc.)
13. Confirm change approval and schedule.
14. Install filesystem client.
15. Install database module (if required).
16. Configure filesystem backups in NetWorker.
17. Test filesystem backups in NetWorker and remediate.
18. Configure database backups.
19. Test database backups and remediate.
20. Integrate client instances with appropriate retention policies and schedules.
21. Confirm successful next-day operation of automated backups.
22. Add client into any custom reporting (should fold automatically into standard reporting).
23. Close off change as required.

Depending on your environment, those processes may change a bit – or they may even be less formal, but cutting corners in data protection can easily lead to a mishap, so if you’re looking for a procedure for adding a client, you could do a lot worse than the one above.