Data Archive backup failure due to offline subsystem

When a subsystem registers for backup, the subsystem must remain online during the next backup or else the backup will fail with the following error:

Backup start failed, Status: [16896] RPC Resolver offline for a subsystem to which the backup subsystem is communicating. Find -10733 error in message log to identify problematic RPC

Two messages will appear in the Data Archive message log with the -10733 error similar to the following:

E 19-Oct-09 13:54:57 pibackup (5059)
>> Callback failed for <pibatch> for the IDENTIFY event. Error [10733]
PINET: RPC Resolver is Off-Line.
E 19-Oct-09 13:54:57 pibackup (5061)
>> Error [10733] PINET: RPC Resolver is Off-Line., failed to send the IDENTIFY backup event to pibatch

To fix the problem, you can either start the subsystem that is not running, or you can do the following, if the subsystem was purposefully stopped:

1. Run the command piartool -backup -query and make note of the subsystems that are currently registered for backup.

2. Restart PI Backup Subsystem.

3. Wait for the previously registered subsystems to register for backup again, with the exception of the problematic subsystem. Subsystems may take up to 5 minutes to re-register for backup after the backup subsystem has been restarted.