Skip to main content
Start a Conversation

Solved!

Go to Solution

Andrebomb

3 Posts

3685

November 10th, 2020 10:00

fails bkp files on fileserver

Hello everyone! First I apologize for the English (I translated it on google). I'm new to Networker and have little experience with the tool, but until I manage it well, but today I have a problem, and I would like to ask the community for help, as I can't solve it. I have a Backup of a fileServer, which every time it runs as "incremental", the process ends successfully.

But when I take the same process and change to "full" the backup fails with the logs below, which I will already post! To point out, I recently upgraded from version 18.2 to 19.3, no other process has failed, all backups of VMs are successfully completed, I have the problem only with file backup. below the two logs listed in the process:

Log 01:

11/10/20 13:54:02 Step (1 of 5): nsrjobd has made a request to start this savegrp with PID-8574. 11/10/20 13:54:02 Action backup traditional 'backup' has initialized as 'backup action job' with job id 3264014 11/10/20 13:54:02 Step (2 of 5): Querying the group or policy for the configured group of clients with the savegrp PID-8574. 11/10/20 13:54:03 SRVFILESfs01.ipem.sp:F:\Arquivos requested level=full 11/10/20 13:54:03 Step (3 of 5): The group or policy information has been successfully returned. 11/10/20 13:54:03 Action backup traditional will run up to 100 jobs in parallel 11/10/20 13:54:03 Step (4 of 5): Creating a savefs job for all the configured clients. 11/10/20 13:54:03 Creating a 'savefs' job on the host 'SRVFILESfs01.ipem.sp'. 11/10/20 13:54:03 Policy 'FILESERVER', workflow 'FILESERVER_UNID_F', action 'backup', group 'FILESERVER_FILESERVER_DIARIO'. 11/10/20 13:54:03 Starting action backup traditional 'backup', which has 1 clients. 11/10/20 13:54:03 Starting a session on the host 'SRVFILESfs01.ipem.sp' to execute the job 'SRVFILESfs01.ipem.sp:savefs', which scans the file system to determine the files for backup. 11/10/20 13:54:03 The job 'SRVFILESfs01.ipem.sp:savefs' has been started on the client 'SRVFILESfs01.ipem.sp'. 11/10/20 13:54:03 SRVFILESfs01.ipem.sp:savefs started 11/10/20 13:54:03 savefs -s SRVFILESnw01.ipem.sp -c SRVFILESfs01.ipem.sp -g FILESERVER_FILESERVER_DIARIO -p -o "\"PSS:timeout_mins=60;\"" -l full -R -v -F "F:\\Arquivos" 11/10/20 13:54:04 Group FILESERVER_FILESERVER_DIARIO waiting for 1 jobs (0 awaiting restart) to complete. 11/10/20 13:54:09 SRVFILESfs01.ipem.sp:F:\Arquivos 11/10/20 13:54:09 level=full, vers=pools, p=4 11/10/20 13:54:09 The job 'SRVFILESfs01.ipem.sp:savefs' on the host 'SRVFILESfs01.ipem.sp' has been completed. 11/10/20 13:54:09 SRVFILESfs01.ipem.sp:savefs succeeded. 11/10/20 13:54:09 SRVFILESfs01.ipem.sp:savefs The job has successfully scanned the file system on the host 'SRVFILESfs01.ipem.sp'. The main save will now be started. 11/10/20 13:54:09 FILESERVER_FILESERVER_DIARIO:SRVFILESfs01.ipem.sp:savefs See the file '/nsr/logs/policy/FILESERVER/FILESERVER_UNID_F/backup_3264014_logs/3264015.log' for command output. 11/10/20 13:54:09 Step (5 of 5): Creating a pseudo_saveset job for all the configured clients. 11/10/20 13:54:09 Creating a save job for the save set 'pseudo_saveset' on the host 'SRVFILESfs01.ipem.sp'. 11/10/20 13:54:09 Parallel save streams per save set option value '-M#4' is being applied to save set 'pseudo_saveset' 11/10/20 13:54:09 Constructing the save command for the save set 'pseudo_saveset' on the host 'SRVFILESfs01.ipem.sp': save -LL -s SRVFILESnw01.ipem.sp -g FILESERVER/FILESERVER_UNID_F/backup/FILESERVER_FILESERVER_DIARIO -a "*policy action jobid=3264014" -a "*policy name=FILESERVER" -a "*policy workflow name=FILESERVER_UNID_F" -a "*policy action name=backup" -y "Thu Dec 10 23:59:59 GMT-0300 2020" -w "Thu Dec 10 23:59:59 GMT-0300 2020" -f - -m SRVFILESfs01.ipem.sp -M #4 -a "device interface=data domain" -a "Data Domain interface=IP" -b FILESYSTEM_Diario -o "\"PSS:timeout_mins=60;RENAMED_DIRECTORIES:index_lookup=on;REQUESTED_LEVEL:level=full;\"" -l full -q -W 78 -N pseudo_saveset "F:\\Arquivos". 11/10/20 13:54:09 Executing a 'pseudo_saveset' job on the host 'SRVFILESfs01.ipem.sp'. This job is an anchor save set for the workflow, and will be completed at the end of the client's backup. 11/10/20 13:54:09 SRVFILESfs01.ipem.sp:pseudo_saveset started 11/10/20 13:54:09 save -LL -s SRVFILESnw01.ipem.sp -g FILESERVER/FILESERVER_UNID_F/backup/FILESERVER_FILESERVER_DIARIO -a "*policy action jobid=3264014" -a "*policy name=FILESERVER" -a "*policy workflow name=FILESERVER_UNID_F" -a "*policy action name=backup" -y "Thu Dec 10 23:59:59 GMT-0300 2020" -w "Thu Dec 10 23:59:59 GMT-0300 2020" -f - -m SRVFILESfs01.ipem.sp -M #4 -a "device interface=data domain" -a "Data Domain interface=IP" -b FILESYSTEM_Diario -o "\"PSS:timeout_mins=60;RENAMED_DIRECTORIES:index_lookup=on;REQUESTED_LEVEL:level=full;\"" -l full -q -W 78 -N pseudo_saveset "F:\\Arquivos" 11/10/20 13:56:17 Group FILESERVER_FILESERVER_DIARIO waiting for 2 jobs (0 awaiting restart) to complete. 11/10/20 14:54:39 Action backup traditional 'backup' group 'FILESERVER_FILESERVER_DIARIO' is being aborted. REASON Aborted. 11/10/20 14:54:39 SRVFILESfs01.ipem.sp:F:\Arquivos aborted. 11/10/20 14:54:39 SRVFILESfs01.ipem.sp:pseudo_saveset aborted. 11/10/20 14:54:39 Group FILESERVER_FILESERVER_DIARIO (Aborted) waiting 180 seconds for 2 jobs to exit. 11/10/20 14:54:39 SRVFILESfs01.ipem.sp:F:\Arquivos Termination request was sent to job 3264017 as requested; Reason given: Aborted 11/10/20 14:54:39 SRVFILESfs01.ipem.sp:pseudo_saveset Termination request was sent to job 3264016 as requested; Reason given: Aborted 11/10/20 14:54:49 The save job for the save set 'F:\Arquivos' on the host 'SRVFILESfs01.ipem.sp' has been completed. 11/10/20 14:54:49 Job 3264017 for client SRVFILESfs01.ipem.sp exited with return code -1 11/10/20 14:54:49 Job 3264017 host: SRVFILESfs01.ipem.sp savepoint: F:\Arquivos had ERROR indication(s) at completion 11/10/20 14:54:49 SRVFILESfs01.ipem.sp:F:\Arquivos failed. 11/10/20 14:54:50 Group FILESERVER_FILESERVER_DIARIO waiting for 1 jobs (0 awaiting restart) to complete. 11/10/20 14:55:39 Group FILESERVER_FILESERVER_DIARIO (Aborted) waiting 120 seconds for 1 jobs to exit. 11/10/20 14:55:44 All jobs did not end gracefully, multiple abort requests forcing exit now... 11/10/20 14:55:44 group FILESERVER_FILESERVER_DIARIO aborted. 11/10/20 14:55:49 Unprocessed/pending input work items exist. 11/10/20 14:55:49 Action backup traditional 'backup' with job id 3264014 is exiting with status 'failed', exit code 1

Log 02:

181407:save: Step (1 of 5) for PID-4116: Save has been started on the client 'ipemstafs01.ipem.sp'. 174412:save: Step (2 of 5) for PID-4116: Running the backup on the client 'ipemstafs01.ipem.sp' for the save set 'pseudo_saveset'. 133073:save: The 'PSS:timeout_mins=' option valid value 60 has been detected and will override the default value 25. 174424:save: Step (3 of 5) for PID-4116: Creating the snapshot for the selected save sets. 174426:save: Step (4 of 5) for PID-4116: Determining whether the backup level is either full or incremental. 186857:save: Performing Level 'Full' Backup for 'ipemstafs01.ipem.sp:F:\Arquivos' 174430:save: Backup level for ipemstafs01.ipem.sp:F:\Arquivos = full. 181407:save: Step (1 of 5) for PID-7652: Save has been started on the client 'ipemstafs01.ipem.sp'. 181407:save: Step (1 of 5) for PID-9736: Save has been started on the client 'ipemstafs01.ipem.sp'. 181407:save: Step (1 of 5) for PID-3616: Save has been started on the client 'ipemstafs01.ipem.sp'. 174412:save: Step (2 of 5) for PID-7652: Running the backup on the client 'ipemstafs01.ipem.sp' for the save set '<2>F:\Arquivos'. 174412:save: Step (2 of 5) for PID-3616: Running the backup on the client 'ipemstafs01.ipem.sp' for the save set '<3>F:\Arquivos'. 174412:save: Step (2 of 5) for PID-9736: Running the backup on the client 'ipemstafs01.ipem.sp' for the save set '<1>F:\Arquivos'. 133073:save: The 'PSS:timeout_mins=' option valid value 60 has been detected and will override the default value 25. 133073:save: The 'PSS:timeout_mins=' option valid value 60 has been detected and will override the default value 25. 133073:save: The 'PSS:timeout_mins=' option valid value 60 has been detected and will override the default value 25. 180569:save: Identified a save for the backup with PID-3616 on the client 'ipemstafs01.ipem.sp'. Updating the total number of steps from 5 to 7. 174920:save: Step (3 of 7) for PID-3616: Contacting the NetWorker server through the nsrd process to obtain a handle to the target media device through the nsrmmd process for the save set '<3>F:\Arquivos'. 174908:save:Saving the backup data in the pool 'FILESYSTEM_Diario'. 175019:save:Received the media management binding information on the host 'ipemstanw01.ipem.sp'. 174910:save:Connected to the nsrmmd process on the host 'ipemstanw01.ipem.sp'. 175295:save: Successfully connected to the Data Domain device. 129292:save:Successfully established Client direct save session for save-set ID '4222273075' (ipemstafs01.ipem.sp:<3>F:\Arquivos) with Data Domain volume 'FILESYSTEMDiario.001'. 174922:save: Step (4 of 7) for PID-3616: Successfully connected to the target media device through the nsrmmd process on the host 'ipemstanw01.ipem.sp' for the save set '<3>F:\Arquivos'. 174422:save: Step (5 of 7) for PID-3616: Reading the save sets and writing to the target device. 180569:save: Identified a save for the backup with PID-7652 on the client 'ipemstafs01.ipem.sp'. Updating the total number of steps from 5 to 7. 174920:save: Step (3 of 7) for PID-7652: Contacting the NetWorker server through the nsrd process to obtain a handle to the target media device through the nsrmmd process for the save set '<2>F:\Arquivos'. 174908:save:Saving the backup data in the pool 'FILESYSTEM_Diario'. 175019:save:Received the media management binding information on the host 'ipemstanw01.ipem.sp'. 174910:save:Connected to the nsrmmd process on the host 'ipemstanw01.ipem.sp'. 175295:save: Successfully connected to the Data Domain device. 129292:save:Successfully established Client direct save session for save-set ID '4205495861' (ipemstafs01.ipem.sp:<2>F:\Arquivos) with Data Domain volume 'FILESYSTEMDiario.001'. 174922:save: Step (4 of 7) for PID-7652: Successfully connected to the target media device through the nsrmmd process on the host 'ipemstanw01.ipem.sp' for the save set '<2>F:\Arquivos'. 174422:save: Step (5 of 7) for PID-7652: Reading the save sets and writing to the target device. 180569:save: Identified a save for the backup with PID-9736 on the client 'ipemstafs01.ipem.sp'. Updating the total number of steps from 5 to 7. 174920:save: Step (3 of 7) for PID-9736: Contacting the NetWorker server through the nsrd process to obtain a handle to the target media device through the nsrmmd process for the save set '<1>F:\Arquivos'. 174908:save:Saving the backup data in the pool 'FILESYSTEM_Diario'. 175019:save:Received the media management binding information on the host 'ipemstanw01.ipem.sp'. 174910:save:Connected to the nsrmmd process on the host 'ipemstanw01.ipem.sp'. 175295:save: Successfully connected to the Data Domain device. 129292:save:Successfully established Client direct save session for save-set ID '4188718647' (ipemstafs01.ipem.sp:<1>F:\Arquivos) with Data Domain volume 'FILESYSTEMDiario.001'. 174922:save: Step (4 of 7) for PID-9736: Successfully connected to the target media device through the nsrmmd process on the host 'ipemstanw01.ipem.sp' for the save set '<1>F:\Arquivos'. 174422:save: Step (5 of 7) for PID-9736: Reading the save sets and writing to the target device. 181407:save: Step (1 of 5) for PID-7216: Save has been started on the client 'ipemstafs01.ipem.sp'. 174412:save: Step (2 of 5) for PID-7216: Running the backup on the client 'ipemstafs01.ipem.sp' for the save set 'F:\Arquivos'. 133073:save: The 'PSS:timeout_mins=' option valid value 60 has been detected and will override the default value 25. 180569:save: Identified a save for the backup with PID-7216 on the client 'ipemstafs01.ipem.sp'. Updating the total number of steps from 5 to 7. 174920:save: Step (3 of 7) for PID-7216: Contacting the NetWorker server through the nsrd process to obtain a handle to the target media device through the nsrmmd process for the save set 'F:\Arquivos'. 174908:save:Saving the backup data in the pool 'FILESYSTEM_Diario'. 175019:save:Received the media management binding information on the host 'ipemstanw01.ipem.sp'. 174910:save:Connected to the nsrmmd process on the host 'ipemstanw01.ipem.sp'. 175295:save: Successfully connected to the Data Domain device. 129292:save:Successfully established Client direct save session for save-set ID '4171941435' (ipemstafs01.ipem.sp:F:\Arquivos) with Data Domain volume 'FILESYSTEMDiario.001'. 174922:save: Step (4 of 7) for PID-7216: Successfully connected to the target media device through the nsrmmd process on the host 'ipemstanw01.ipem.sp' for the save set 'F:\Arquivos'. 174422:save: Step (5 of 7) for PID-7216: Reading the save sets and writing to the target device. 181407:save: Step (1 of 5) for PID-5188: Save has been started on the client 'ipemstafs01.ipem.sp'. 174412:save: Step (2 of 5) for PID-5188: Running the backup on the client 'ipemstafs01.ipem.sp' for the save set 'null'. 133073:save: The 'PSS:timeout_mins=' option valid value 60 has been detected and will override the default value 25. Received a termination signal. Terminating the save operation. Terminated the backup. 133079:save: Backups have been interrupted and are being aborted within the next 180 seconds ... 125796:save: The DPSS backup has been cancelled. 11/10/20 15:03:11.374954 find_idle_emitter() (tid:1): ERROR: Could not get Emitter Do MBS: Unable to find an idle emitter. 125798:save: DPSS save point 'ipemstafs01.ipem.sp:F:\Arquivos' has encountered a critical error. Received a termination signal. Terminating the save operation. Received a termination signal. Terminating the save operation. Received a termination signal. Terminating the save operation. Received a termination signal. Terminating the save operation. Received a termination signal. Terminating the save operation. parallel save streams summary ipemstafs01.ipem.sp: F:\Arquivos level=full, 0 KB 00:58:33 0 files parallel save streams summary savetime=1605027898

Andrebomb

3 Posts

November 11th, 2020 10:00

Hello, my friend, I did it !!!!
I found the error, actually not an error, but a parameter possibly changed in the version upgradde, as I mentioned I migrated from version 18.2 to 19.3

This is the solution:

NMC> Server> Server Properties> configuration> Job inactivity timeout> change to "0"

It was marked "60"

Thanks for your help, with your answer, I was able to filter a little better and follow a more effective line of reasoning. Thanks.

bingo.1

2.4K Posts

November 10th, 2020 14:00

There are 2 things to consider:

  -  A full backup obviously takes longer than 1 hour

  -  You are using PSS (Parallel Save Set) Backups. Here you set the value PSS:timeout_mins to 60.

Did you notice (from log 1) that the backup is terminated after exactly 1 hour? - I think this is your problem.

To verify this, please modify the client resource to run a 'standard' full backup - without PSS - this should run without problems but will of course take significantly longer.

Unfortunately, I looked through the docs and the internet but I could not find an explanation where the "PSS:timeout_mins" parameter will appear. You may want to ask support how to correct/reset the value. Please share the result with the community.

 

Andrebomb

3 Posts

November 11th, 2020 08:00

Hi Germanium
Thanks for your help in this case, the parameter "PSS: timeout_mins = 60",
I had manually entered it in client Properties> Apps & Modules> Save Operations.

I saw in a post with a similar problem that it helped a person, and I auditioned.

The fact that the backup has been limiting for an hour, I still haven't found where I can change it.

I performed new tests removing "PSS: timeout_mins" and the problem continues to be stopped in 1 hour.

below last log.

I realized that this error also happens with VMs after 1hr.

Unfortunately, we no longer have an EMC support contract.

Log01:

181407:save: Step (1 of 5) for PID-7600: Save has been started on the client 'SRVFILESfs01.ipem.sp'.
174412:save: Step (2 of 5) for PID-7600: Running the backup on the client 'SRVFILESfs01.ipem.sp' for the save set 'pseudo_saveset'.
133073:save: The 'PSS:timeout_mins=' option valid value 0 has been detected and will override the default value 25.
133074:save: The 'PSS:timeout_mins=' option zero value has disabled client-side inactivity timeout monitoring.
174424:save: Step (3 of 5) for PID-7600: Creating the snapshot for the selected save sets.
174426:save: Step (4 of 5) for PID-7600: Determining whether the backup level is either full or incremental.
186857:save: Performing Level 'Full' Backup for 'SRVFILESfs01.ipem.sp:F:\Arquivos'
174430:save: Backup level for SRVFILESfs01.ipem.sp:F:\Arquivos = full.
181407:save: Step (1 of 5) for PID-1084: Save has been started on the client 'SRVFILESfs01.ipem.sp'.
181407:save: Step (1 of 5) for PID-6576: Save has been started on the client 'SRVFILESfs01.ipem.sp'.
181407:save: Step (1 of 5) for PID-6252: Save has been started on the client 'SRVFILESfs01.ipem.sp'.
174412:save: Step (2 of 5) for PID-1084: Running the backup on the client 'SRVFILESfs01.ipem.sp' for the save set '<3>F:\Arquivos'.
174412:save: Step (2 of 5) for PID-6576: Running the backup on the client 'SRVFILESfs01.ipem.sp' for the save set '<2>F:\Arquivos'.
174412:save: Step (2 of 5) for PID-6252: Running the backup on the client 'SRVFILESfs01.ipem.sp' for the save set '<1>F:\Arquivos'.
133073:save: The 'PSS:timeout_mins=' option valid value 0 has been detected and will override the default value 25.
133074:save: The 'PSS:timeout_mins=' option zero value has disabled client-side inactivity timeout monitoring.
133073:save: The 'PSS:timeout_mins=' option valid value 0 has been detected and will override the default value 25.
133074:save: The 'PSS:timeout_mins=' option zero value has disabled client-side inactivity timeout monitoring.
133073:save: The 'PSS:timeout_mins=' option valid value 0 has been detected and will override the default value 25.
133074:save: The 'PSS:timeout_mins=' option zero value has disabled client-side inactivity timeout monitoring.
180569:save: Identified a save for the backup with PID-1084 on the client 'SRVFILESfs01.ipem.sp'. Updating the total number of steps from 5 to 7.
174920:save: Step (3 of 7) for PID-1084: Contacting the NetWorker server through the nsrd process to obtain a handle to the target media device through the nsrmmd process for the save set '<3>F:\Arquivos'.
174908:save:Saving the backup data in the pool 'FILESYSTEM_Diario'.
175019:save:Received the media management binding information on the host 'SRVFILESnw01.ipem.sp'.
174910:save:Connected to the nsrmmd process on the host 'SRVFILESnw01.ipem.sp'.
175295:save: Successfully connected to the Data Domain device.
129292:save:Successfully established Client direct save session for save-set ID '732686946' (SRVFILESfs01.ipem.sp:<3>F:\Arquivos) with Data Domain volume 'FILESYSTEMDiario.001'.
174922:save: Step (4 of 7) for PID-1084: Successfully connected to the target media device through the nsrmmd process on the host 'SRVFILESnw01.ipem.sp' for the save set '<3>F:\Arquivos'.
174422:save: Step (5 of 7) for PID-1084: Reading the save sets and writing to the target device.
180569:save: Identified a save for the backup with PID-6576 on the client 'SRVFILESfs01.ipem.sp'. Updating the total number of steps from 5 to 7.
174920:save: Step (3 of 7) for PID-6576: Contacting the NetWorker server through the nsrd process to obtain a handle to the target media device through the nsrmmd process for the save set '<2>F:\Arquivos'.
174908:save:Saving the backup data in the pool 'FILESYSTEM_Diario'.
175019:save:Received the media management binding information on the host 'SRVFILESnw01.ipem.sp'.
174910:save:Connected to the nsrmmd process on the host 'SRVFILESnw01.ipem.sp'.
175295:save: Successfully connected to the Data Domain device.
129292:save:Successfully established Client direct save session for save-set ID '715909732' (SRVFILESfs01.ipem.sp:<2>F:\Arquivos) with Data Domain volume 'FILESYSTEMDiario.001'.
174922:save: Step (4 of 7) for PID-6576: Successfully connected to the target media device through the nsrmmd process on the host 'SRVFILESnw01.ipem.sp' for the save set '<2>F:\Arquivos'.
174422:save: Step (5 of 7) for PID-6576: Reading the save sets and writing to the target device.
180569:save: Identified a save for the backup with PID-6252 on the client 'SRVFILESfs01.ipem.sp'. Updating the total number of steps from 5 to 7.
174920:save: Step (3 of 7) for PID-6252: Contacting the NetWorker server through the nsrd process to obtain a handle to the target media device through the nsrmmd process for the save set '<1>F:\Arquivos'.
174908:save:Saving the backup data in the pool 'FILESYSTEM_Diario'.
175019:save:Received the media management binding information on the host 'SRVFILESnw01.ipem.sp'.
174910:save:Connected to the nsrmmd process on the host 'SRVFILESnw01.ipem.sp'.
175295:save: Successfully connected to the Data Domain device.
129292:save:Successfully established Client direct save session for save-set ID '699132518' (SRVFILESfs01.ipem.sp:<1>F:\Arquivos) with Data Domain volume 'FILESYSTEMDiario.001'.
174922:save: Step (4 of 7) for PID-6252: Successfully connected to the target media device through the nsrmmd process on the host 'SRVFILESnw01.ipem.sp' for the save set '<1>F:\Arquivos'.
174422:save: Step (5 of 7) for PID-6252: Reading the save sets and writing to the target device.
181407:save: Step (1 of 5) for PID-7592: Save has been started on the client 'SRVFILESfs01.ipem.sp'.
174412:save: Step (2 of 5) for PID-7592: Running the backup on the client 'SRVFILESfs01.ipem.sp' for the save set 'F:\Arquivos'.
133073:save: The 'PSS:timeout_mins=' option valid value 0 has been detected and will override the default value 25.
133074:save: The 'PSS:timeout_mins=' option zero value has disabled client-side inactivity timeout monitoring.
180569:save: Identified a save for the backup with PID-7592 on the client 'SRVFILESfs01.ipem.sp'. Updating the total number of steps from 5 to 7.
174920:save: Step (3 of 7) for PID-7592: Contacting the NetWorker server through the nsrd process to obtain a handle to the target media device through the nsrmmd process for the save set 'F:\Arquivos'.
174908:save:Saving the backup data in the pool 'FILESYSTEM_Diario'.
175019:save:Received the media management binding information on the host 'SRVFILESnw01.ipem.sp'.
174910:save:Connected to the nsrmmd process on the host 'SRVFILESnw01.ipem.sp'.
175295:save: Successfully connected to the Data Domain device.
129292:save:Successfully established Client direct save session for save-set ID '682355305' (SRVFILESfs01.ipem.sp:F:\Arquivos) with Data Domain volume 'FILESYSTEMDiario.001'.
174922:save: Step (4 of 7) for PID-7592: Successfully connected to the target media device through the nsrmmd process on the host 'SRVFILESnw01.ipem.sp' for the save set 'F:\Arquivos'.
174422:save: Step (5 of 7) for PID-7592: Reading the save sets and writing to the target device.
181407:save: Step (1 of 5) for PID-9244: Save has been started on the client 'SRVFILESfs01.ipem.sp'.
174412:save: Step (2 of 5) for PID-9244: Running the backup on the client 'SRVFILESfs01.ipem.sp' for the save set 'null'.
133073:save: The 'PSS:timeout_mins=' option valid value 0 has been detected and will override the default value 25.
133074:save: The 'PSS:timeout_mins=' option zero value has disabled client-side inactivity timeout monitoring.
Received a termination signal. Terminating the save operation.
Terminated the backup.
133079:save: Backups have been interrupted and are being aborted within the next 180 seconds ...
do_mbs(): DPSS save point 'SRVFILESfs01.ipem.sp:F:\Arquivos' detected Quit ... SD is aborting
125798:save: DPSS save point 'SRVFILESfs01.ipem.sp:F:\Arquivos' has encountered a critical error.
Received a termination signal. Terminating the save operation.
Received a termination signal. Terminating the save operation.
Received a termination signal. Terminating the save operation.
Received a termination signal. Terminating the save operation.
Received a termination signal. Terminating the save operation.
74209:save: Quit signal received.
142169:save: Save-set ID '682355305' (client 'SRVFILESfs01.ipem.sp': save-set 'F:\Arquivos') is aborted.
86711:save: Aborted save-set ID '682355305' (client 'SRVFILESfs01.ipem.sp': save-set 'F:\Arquivos') may not have been removed properly.
parallel save streams summary SRVFILESfs01.ipem.sp: F:\Arquivos level=full, 0 KB 00:59:03 0 files
parallel save streams summary savetime=1605102699

Log02:

11/11/20 10:41:26 Step (1 of 5): nsrjobd has made a request to start this savegrp with PID-18311.
11/11/20 10:41:26 Action backup traditional 'backup' has initialized as 'backup action job' with job id 3264442
11/11/20 10:41:26 Step (2 of 5): Querying the group or policy for the configured group of clients with the savegrp PID-18311.
11/11/20 10:41:26 SRVFILESfs01.ipem.sp:F:\Arquivos requested level=full
11/11/20 10:41:26 Step (3 of 5): The group or policy information has been successfully returned.
11/11/20 10:41:26 Action backup traditional will run up to 1000 jobs in parallel
11/11/20 10:41:26 Step (4 of 5): Creating a savefs job for all the configured clients.
11/11/20 10:41:26 Creating a 'savefs' job on the host 'SRVFILESfs01.ipem.sp'.
11/11/20 10:41:26 Policy 'FILESERVER', workflow 'FILESERVER_UNID_F', action 'backup', group 'FILESERVER_FILESERVER_DIARIO'.
11/11/20 10:41:26 Starting action backup traditional 'backup', which has 1 clients.
11/11/20 10:41:26 Starting a session on the host 'SRVFILESfs01.ipem.sp' to execute the job 'SRVFILESfs01.ipem.sp:savefs', which scans the file system to determine the files for backup.
11/11/20 10:41:26 The job 'SRVFILESfs01.ipem.sp:savefs' has been started on the client 'SRVFILESfs01.ipem.sp'.
11/11/20 10:41:26 SRVFILESfs01.ipem.sp:savefs started
11/11/20 10:41:26 savefs -s SRVFILESnw01.ipem.sp -c SRVFILESfs01.ipem.sp -g FILESERVER_FILESERVER_DIARIO -p -o "\"PSS:timeout_mins=0;\"" -l full -R -v -F "F:\\Arquivos"
11/11/20 10:41:27 Group FILESERVER_FILESERVER_DIARIO waiting for 1 jobs (0 awaiting restart) to complete.
11/11/20 10:41:45 SRVFILESfs01.ipem.sp:F:\Arquivos
11/11/20 10:41:45 level=full, vers=pools, p=4
11/11/20 10:41:45 The job 'SRVFILESfs01.ipem.sp:savefs' on the host 'SRVFILESfs01.ipem.sp' has been completed.
11/11/20 10:41:45 SRVFILESfs01.ipem.sp:savefs succeeded.
11/11/20 10:41:45 SRVFILESfs01.ipem.sp:savefs The job has successfully scanned the file system on the host 'SRVFILESfs01.ipem.sp'. The main save will now be started.
11/11/20 10:41:45 FILESERVER_FILESERVER_DIARIO:SRVFILESfs01.ipem.sp:savefs See the file '/nsr/logs/policy/FILESERVER/FILESERVER_UNID_F/backup_3264442_logs/3264443.log' for command output.
11/11/20 10:41:45 Step (5 of 5): Creating a pseudo_saveset job for all the configured clients.
11/11/20 10:41:45 Creating a save job for the save set 'pseudo_saveset' on the host 'SRVFILESfs01.ipem.sp'.
11/11/20 10:41:45 Parallel save streams per save set option value '-M#4' is being applied to save set 'pseudo_saveset'
11/11/20 10:41:45 Constructing the save command for the save set 'pseudo_saveset' on the host 'SRVFILESfs01.ipem.sp': save -LL -s SRVFILESnw01.ipem.sp -g FILESERVER/FILESERVER_UNID_F/backup/FILESERVER_FILESERVER_DIARIO -a "*policy action jobid=3264442" -a "*policy name=FILESERVER" -a "*policy workflow name=FILESERVER_UNID_F" -a "*policy action name=backup" -y "Sat Nov 11 23:59:59 GMT-0300 2023" -w "Sat Nov 11 23:59:59 GMT-0300 2023" -f - -m SRVFILESfs01.ipem.sp -M #4 -a "device interface=data domain" -a "Data Domain interface=IP" -b FILESYSTEM_Diario -o "\"PSS:timeout_mins=0;REQUESTED_LEVEL:level=full;\"" -l full -q -W 78 -N pseudo_saveset "F:\\Arquivos".
11/11/20 10:41:45 Executing a 'pseudo_saveset' job on the host 'SRVFILESfs01.ipem.sp'. This job is an anchor save set for the workflow, and will be completed at the end of the client's backup.
11/11/20 10:41:45 SRVFILESfs01.ipem.sp:pseudo_saveset started
11/11/20 10:41:45 save -LL -s SRVFILESnw01.ipem.sp -g FILESERVER/FILESERVER_UNID_F/backup/FILESERVER_FILESERVER_DIARIO -a "*policy action jobid=3264442" -a "*policy name=FILESERVER" -a "*policy workflow name=FILESERVER_UNID_F" -a "*policy action name=backup" -y "Sat Nov 11 23:59:59 GMT-0300 2023" -w "Sat Nov 11 23:59:59 GMT-0300 2023" -f - -m SRVFILESfs01.ipem.sp -M #4 -a "device interface=data domain" -a "Data Domain interface=IP" -b FILESYSTEM_Diario -o "\"PSS:timeout_mins=0;REQUESTED_LEVEL:level=full;\"" -l full -q -W 78 -N pseudo_saveset "F:\\Arquivos"
11/11/20 10:42:56 Group FILESERVER_FILESERVER_DIARIO waiting for 2 jobs (0 awaiting restart) to complete.
11/11/20 11:41:39 Action backup traditional 'backup' group 'FILESERVER_FILESERVER_DIARIO' is being aborted. REASON Aborted.
11/11/20 11:41:39 SRVFILESfs01.ipem.sp:F:\Arquivos aborted.
11/11/20 11:41:39 SRVFILESfs01.ipem.sp:pseudo_saveset aborted.
11/11/20 11:41:39 Group FILESERVER_FILESERVER_DIARIO (Aborted) waiting 180 seconds for 2 jobs to exit.
11/11/20 11:41:39 SRVFILESfs01.ipem.sp:F:\Arquivos Termination request was sent to job 3264447 as requested; Reason given: Aborted
11/11/20 11:41:39 SRVFILESfs01.ipem.sp:pseudo_saveset Termination request was sent to job 3264444 as requested; Reason given: Aborted
11/11/20 11:41:56 SRVFILESfs01.ipem.sp:F:\Arquivos: already cancelled
11/11/20 11:41:57 The save job for the save set 'F:\Arquivos' on the host 'SRVFILESfs01.ipem.sp' has been completed.
11/11/20 11:41:58 SRVFILESfs01.ipem.sp:F:\Arquivos: already cancelled
11/11/20 11:41:58 Job 3264447 for client SRVFILESfs01.ipem.sp exited with return code -1
11/11/20 11:41:58 Job 3264447 host: SRVFILESfs01.ipem.sp savepoint: F:\Arquivos had ERROR indication(s) at completion
11/11/20 11:41:58 SRVFILESfs01.ipem.sp:F:\Arquivos failed.
11/11/20 11:41:59 Group FILESERVER_FILESERVER_DIARIO waiting for 1 jobs (0 awaiting restart) to complete.
11/11/20 11:42:39 Group FILESERVER_FILESERVER_DIARIO (Aborted) waiting 120 seconds for 1 jobs to exit.
11/11/20 11:42:44 All jobs did not end gracefully, multiple abort requests forcing exit now...
11/11/20 11:42:44 group FILESERVER_FILESERVER_DIARIO aborted.
11/11/20 11:42:49 Unprocessed/pending input work items exist.
11/11/20 11:42:49 Action backup traditional 'backup' with job id 3264442 is exiting with status 'failed', exit code 1

 

bingo.1

2.4K Posts

November 11th, 2020 14:00

Good that you found the result and solved the issue. Of course I remember several NW timeout settings but I was only looking for the PSS timeout attribute.

 

So I am still struggling with the "pss" parameter. It is obviously undocumented. According to the log information it is an attribute that you apply to the save command using the option "-o save_operations_parameter". And this seems to be correct as yo stated yourself:

      " I had manually entered it in client Properties> Apps & Modules> Save Operations."

If you have done this, you will easily find it stored within the resource database. As this is a 'text based db' you can easily search for the string. For example in Windows you will use the findstr command to verify that a string exists:

      E:\nsr\res\nsrdb>findstr /S /I /C:"pss" *.*

The result will show you the resource file name where the string is stored. In this case it will be a client resource.

-------------------------------------------------------------

I wonder where you got the info to use this attribute at all. I have verified that it neither exists in the NW 18.x nor in the NW 19.x Command Line Reference, which is considered to be the holy book of NW core operations.

Another undocumented feature ... well done Dell/EMC.

 

    

Durga Mukhia

1 Rookie

 • 

26 Posts

June 14th, 2024 07:10

Hi, 

I am having issues backing up the filesystem in RHEL server:

181407:save: Step (1 of 7) for PID-1696539: Save has been started on the client 'nppf-db-srv2-dc.nppf.org.bt'.
174412:save: Step (2 of 7) for PID-1696539: Running the backup on the client 'nppf-db-srv2-dc.nppf.org.bt' for the save set '/backup/test-2024'.
180569:save: Identified a save for the backup with PID-1696539 on the client 'nppf-db-srv2-dc.nppf.org.bt'. Updating the total number of steps from 7 to 6.
174920:save: Step (3 of 6) for PID-1696539: Contacting the NetWorker server through the nsrd process to obtain a handle to the target media device through the nsrmmd process for the save set '/backup/test-2024'.
175297:save: Unable to set up the direct save with server 'nppf-networker-srv1-dc.nppf.local': Client 'nppf-db-srv2-dc.nppf.org.bt' is not properly configured on the NetWorker Server..
175024:save: Cannot open a save session with NetWorker server 'nppf-networker-srv1-dc.nppf.local': Client 'nppf-db-srv2-dc.nppf.org.bt' is not properly configured on the NetWorker Server..
174921:save: Step (4 of 6) for PID-1696539: Unable to connect to the target media device through the nsrmmd process for the save set '/backup/test-2024'.

Please help me with the  issue?

Thanks,

Durga Mukhia

Was this post helpful?

View All

No Events found!

Top