NetWorker: backup fails with "pseudo_saveset aborted, inactivity timeout has been reached"

Some NetWorker backups are failing during psuedo_saveset creation, reporting inactivity timeout issues:

savegrp NSR warning Aborting inactive job (JOBID) CLIENT_NAME:pseudo_saveset. It has been inactive from 'DAY MONTH DATE HH:mm:SS YYYY'(EPOCH_TIMESTAMP) to 'DAY MONTH DATE HH:mm:SS YYYY'(EPOCH_TIMESTAMP) for 1817 seconds.
savegrp NSR info CLIENT_NAME:pseudo_saveset aborted, inactivity timeout has been reached.

pseudo_saveset is a metadata anchor save set used to register important parameters concerning the workflow of client jobs and is important for features such as immediate cloning of individual save sets; it is automatically generated at the start of the backup as an indicator of the list of save sets configured to start for the client.

The backup action contains an Inactivity Timeout that the default value is 30 minutes. pseudo_saveset enumeration of large data structures can take long enough that the pseudo_saveset appears inactive and is closed by the inactivity timeout.

Perform one of the following if these backup failures are persistent for one or more clients.

Option One (Client Parallelism):

Client parallelism defines the number of data streams that a client can use simultaneously during backup. Data streams include backup data streams, savefs processes, and probe jobs.

The default value is different for the NetWorker server than it is for all other client resources:

• For the NetWorker server client resource, the default value is 12. This higher default value enables the server to complete a larger number of index backups during a Server backup action.
• For all other clients, the default value is 4.

To define client parallelism, use the Parallelism attribute of the Client resource. You can find the parallelism attribute on the Globals(1 of 2) tab of the Client properties. A higher client parallelism results in multiple save streams attempting to access the client's disks simultaneously. Depending on the client's system configuration and use-case/load, this can lead to disk contention. 

For more information, see the NetWorker Administration Guide, available through: Support for NetWorker | Manuals & Documents 

Option Two (Inactivity Timeout):

Disable or extend the Inactivity Timeout of the backup action.

Open the backup action properties and modify the Inactivity Timeout in the Advanced Options window. The Inactivity Timeout is shown in minutes (default 30). To disable the Inactivity timeout, set the value to 0. Consider the following. Leave the Inactivity Timeout disabled until several backups have been completed. After you determine the average job duration, set an Inactivity Timeout that allows the job to finish. Include additional overhead when choosing this value. For example, if a backup takes four hours (on average) to complete, set the inactivity timeout for five hours (or more).

NetWorker: Azure VM Backup Workflow Fails at the End of the Backup on Pseudo_saveset