The process for rebuilding a destroyed utility node is the same regardless of the type of node being used as the target (new utility node or spare node).

The utility node replacement process is documented in the following technical notes (available through PowerLink or Support Center):

300-007-551 - AVAMAR UTILITY NODE REPLACEMENT PROCEDURE (Avamar v5.x and earlier)

300-012-538 - UTILITY NODE REPLACEMENT PROCEDURE (Avamar v6.0)

Edit: The most current procedures can now be found in SolVe Desktop.

I would strongly recommend engaging support if you lose a utility node. The rebuild process is non-trivial. I would block out an 8 hour window for the rebuild but an experienced support person can complete the process considerably faster.

I would personally recommend having a replacement utility node shipped out to the site rather than using the spare. Using a spare node as a utility node is supported but it is not a typical configuration on Gen2 or newer hardware. Sticking to a standard configuration wherever possible makes life easier for support which will, in turn, make life easier for you.

Hi Ian,

has there been any changes in replacing a utility node in version 7?

Is there a document for avamar customers, where there is described what happend if a utility node fails and what can be done if this happens.

For example if I have 2 grids, can I replicate the configuration to the a secound grid and restore the configuration and go on?

If there are hardware errors, can only the disks can be replacned in a new node, and then go on?

If there are in the worst case disk errors, so that the utility node don´t come up again, what is the process here?

I dont need any detailed technical solution for this, it is only to describe the customer this process.

The process is largely unchanged for version 7. The only document I'm aware of is the full replacement procedure but that covers all the technical detail.

I would not recommend trying to perform any kind of configuration replication except as described in the utility node replacement procedure (which you can now find in SolVe Desktop, the successor to the Avamar Procedure Generator).

There are two replacement procedures that can be used depending on the nature of the failure. Both can be found in SolVe desktop.

If the RAID set is intact, the utility node can be replaced using the disk transplant / chassis swap procedure. There are a few extra steps for utility nodes since the license is keyed on the utility node hardware and has to be regenerated. Naturally, you can only transplant the disks into a utility node chassis.

If the RAID set is destroyed or the file system is otherwise unusable, a full utility node rebuild is required. The general outline of the procedure is:

1. Save configuration files from old node if possible (particularly probe.xml and the network configuration files)
2. Remove the defective node
3. Rack and cable the replacement
4. Configure / restore networking configuration and probe file
5. Update SSH keys and passwords (if changed)
6. Install the Avamar software on the new utility node
7. Restore installer database
8. Re-initialize utility node services
9. Restore service databases (MCS, EMS, etc.)
10. Perform time sync
11. Update license
12. Configure DRAC / RMM

Hi Ian,

thanks for your answer.

One last question.

in case of a RAID set failure, would it be good to make a backup of the probe.xml files and network config to another system?

It couldn't hurt to tar up the probe.xml and networking files and stash them away somewhere safe.