The Kubernetes backup from snapshot job fails with the error 'system error occurred (130)'

Problem

The Kubernetes backup from snapshot job fails with the error 'system error occurred (130)'. The error occurs due to etcd server request timeout.

Error Message

NetBackup Activity Monitor logs:

Aug 19, 2025 5:33:49 PM - Error bpbrm (pid=3477259) bpcd on https://<kubernetes-cluster-ip-or-hostname>:6443 exited with status 130: system error occurred
Aug 19, 2025 5:36:48 PM - Error nbpem (pid=2661886) duplicate exited with status 130 (system error occurred)
Aug 19, 2025 5:36:48 PM - end writing
Aug 19, 2025 5:36:50 PM - Info bpbkar (pid=0) done. status: 130: system error occurred
system error occurred(130)

NOTE: This error appears in Activity Monitor on NBU versions earlier than 11.1.


NetBackup Kubernetes Operator logs :
2025-08-19T12:03:15Z    ERROR   controllers.NbConfigSetting     failed to get configmap {"nbconfigsetting": 
"netbackup/nbsetconfig-0b6e01c8-7cee-xxxx-xxxx-xxxxxxx-xxxxxxxx", "Namespace:": "netbackup", "Name:": 
"datamover-configmap-0b6e01c8-7cee-xxxx-xxxx-xxxxxxxx", "error": "the server was unable to return a response in the time allotted, but may still be 
processing the request (get configmaps datamover-configmap-0b6e01c8-7cee-11f0-a2a3-48aeb610965a)"}

Cause

There could be multiple concurrent requests to etcd, either from kubernetes API server operations or from other cluster components. These requests may overloaded etcd leading to increased latency and, eventually, request timeouts error occurs.

As a result, the backup from snapshot job fails with the error 'system error occurred (130)' because the required response, from etcd, is not received within the expected timeframe.

Solution

To resolve the Kubernetes API server request timeout, please refer to the official Kubernetes documentation for the API server.