The following sections list the issues that may occur during an NAS agent job cancellation.
Job state is marked as
Failure when the job is cancelled due to an unresponsive session.
When the NAS agent detects an unresponsive job, it triggers a cancellation request for that particular session. Once the cancellation is acknowledged and the session is successfully terminated, the NAS agent proceeds with its cancellation workflow for that session. Since the session was terminated due to a system-initiated cancellation rather than a user action, the entire task is designated as a failure.
When there are both user-initiated job cancellations and system-initiated job cancellations, the user-initiated job cancellation takes precedence.
Also when a user initiates a job cancellation, and later some sessions become unresponsive, the system initiates the cancellation of the unresponsive jobs. The final status of the job is marked as
Cancelled.
Job cancellation due to unresponsive state
If the NAS REST server or NAS Agent becomes unresponsive after initiation of the cancel request, or if the cancel request is not completed within a specific time period, the NAS protection engine force terminates the session.
After receiving the cancellation request from the
PowerProtect Data Manager, the NAS agent sends a maximum of 50 cancellation requests with 5 s intervals. There is a waiting time of 25 minutes for the completion of the cancellation requests. Once this waiting time threshold exceeds, the
PowerProtect Data Manager assumes that the session is unresponsive and initiates a forced job termination. The job is marked as
unknown.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\