Unsolved
1 Rookie
•
6 Posts
0
1036
November 14th, 2023 11:49
Backup failed
When trying to backup a SQL database already extracted from the main server I receive the following message: "is being skipped because no savesets of this client have been backed up as part of the backup action."This is the process log:
"14/11/2023 06:42:57 srvcidasc50.cidasc.sc.gov.br:E:\backup\SQLServer\Completo aborted.
14/11/2023 06:42:57 srvcidasc50.cidasc.sc.gov.br:pseudo_saveset aborted.
14/11/2023 06:42:57 Group FileServerDiarioTape (Aborted) waiting 180 seconds for 2 jobs to exit.
14/11/2023 06:42:57 srvcidasc50.cidasc.sc.gov.br:E:\backup\SQLServer\Completo Termination request was sent to job 5696094 as requested; Reason given: Aborted
14/11/2023 06:42:57 srvcidasc50.cidasc.sc.gov.br:pseudo_saveset Termination request was sent to job 5696078 as requested; Reason given: Aborted
14/11/2023 06:42:59 The save job for the save set 'E:\backup\SQLServer\Completo' on the host 'srvcidasc50.cidasc.sc.gov.br' has been completed.
14/11/2023 06:42:59 Job 5696094 for client srvcidasc50.cidasc.sc.gov.br exited with return code 1
14/11/2023 06:42:59 Job 5696094 host: srvcidasc50.cidasc.sc.gov.br savepoint: E:\backup\SQLServer\Completo had ERROR indication(s) at completion
14/11/2023 06:42:59 srvcidasc50.cidasc.sc.gov.br:E:\backup\SQLServer\Completo failed.
14/11/2023 06:43:03 Group FileServerDiarioTape waiting for 1 jobs (0 awaiting restart) to complete.
14/11/2023 06:43:30 The save job for the save set 'pseudo_saveset' on the host 'srvcidasc50.cidasc.sc.gov.br' has been completed.
14/11/2023 06:43:30 Job 5696078 with command 'save -LL -s srvcidasc90.cidasc.sc.gov.br -g FileServerDiarioTape/BackupDiarioTape/BackupDiario/FileServerDiarioTape -a "*policy action jobid=5696069" -a "*policy name=FileServerDiarioTape" -a "*policy workflow name=BackupDiarioTape" -a "*policy action name=BackupDiario" -y "1 Months" -w "1 Months" -m srvcidasc50.cidasc.sc.gov.br -b TapeDiario -o "\"RENAMED_DIRECTORIES:index_lookup=on;REQUESTED_LEVEL:level=incr;\"" -l incr -q -W 78 -N pseudo_saveset "E:\\backup\\SQLServer\\Completo"' for client srvcidasc50.cidasc.sc.gov.br exited with return code 1
14/11/2023 06:43:30 Job 5696078 host: srvcidasc50.cidasc.sc.gov.br savepoint: pseudo_saveset had ERROR indication(s) at completion
14/11/2023 06:43:30 srvcidasc50.cidasc.sc.gov.br:pseudo_saveset failed.
14/11/2023 06:43:30 FileServerDiarioTape:srvcidasc50.cidasc.sc.gov.br:pseudo_saveset See the file 'C:\Program Files\EMC NetWorker\nsr\logs\policy\FileServerDiarioTape\BackupDiarioTape\BackupDiario_5696069_logs\5696078.log' for command output.
14/11/2023 06:43:30 group FileServerDiarioTape aborted.
14/11/2023 06:43:30 Client 'srvcidasc50.cidasc.sc.gov.br' is being skipped because no savesets of this client have been backed up as part of the backup action.
14/11/2023 06:43:30 Client 'srvcidasc50.cidasc.sc.gov.br' is being skipped because no savesets of this client have been backed up as part of the backup action.
14/11/2023 06:43:35 11/14/23 06:43:35.983545 Skipping incomplete or aborted saveset: (ssid=3780325839)
14/11/2023 06:43:35 Action backup traditional 'BackupDiario' with job id 5696069 is exiting with status 'failed', exit code 1"
and RAW log:
"174898 1699905601 1 5 0 8492 8400 0 server savegrp NSR notice 78 Step (%d of %d): nsrjobd has made a request to start this savegrp with PID-%d. 3 1 1 1 1 1 5 1 4 8400151761 1699905601 1 5 0 8492 8400 0 server savegrp NSR notice 53 Action %s '%s' has initialized as '%s' with job id %u 4 0 18 backup traditional 0 5 Bkp50 0 17 backup action job 5 7 5696032133602 1699905601 2 5 0 8492 8400 0 server savegrp NSR warning 37 Unable to obtain action's group name. 0140644 1699905601 2 5 0 8492 8400 0 server savegrp NSR warning 40 No group is associated with workflow %s. 1 0 5 Bkp50148758 1699905606 1 5 0 8492 8400 0 server savegrp NSR notice 71 Action %s '%s' with job id %u is exiting with status '%s', exit code %d 5 0 18 backup traditional 0 5 Bkp50 5 7 5696032 0 6 failed 1 1 1"No Events found!



crazyrov
4 Operator
•
1.3K Posts
0
November 16th, 2023 08:22
@Redes CID , A bit more context would help.
- Is this is a new configuration?
- Has this worked before ?
- Is the FS backups working ?
- Is this standalone or a cluster?
- How was the client configured ? Manually or via the GUI.
And any other details that you feel is important.
Redes CID
1 Rookie
•
6 Posts
0
November 16th, 2023 13:08
@crazyrov
@Redes CID, a little more context would help. -
Is this a new configuration? - No -
Has this worked before? - Yes -
Are FS backups working? - Yes -
Is this independent or a cluster? - Independent
How was the client configured? Manually or through the GUI. - Manually
crazyrov
4 Operator
•
1.3K Posts
0
November 17th, 2023 13:11
Anything in
C:\Program Files\EMC NetWorker\nsr\logs\policy\FileServerDiarioTape\BackupDiarioTape\BackupDiario_5696069_logs\5696078.log ?bbeckers1
2 Intern
•
195 Posts
0
November 17th, 2023 13:23
when showing any logs in NW .raw log format, please have it properly rendered using nsr_render_log as all of them %s are otherwise meaningless? You can even make sure that the damon.raw on the NW server is also runtime rendered as a .log file, that one can directly look into without needing to parse it through nsr_render_log first. Makes for way easier analysis.
Do I understand correcty that this is intended to be a filesystem backup to made of a MSSQL DB dumped to disk? Is that what you mean with "extracted from the main server"? So a normal filesystem backup?
I see :
Termination request was sent to job 5696094 as requested; Reason given: Aborted14/11/2023 06:42:57 srvcidasc50.cidasc.sc.gov.br:pseudo_saveset Termination request was sent to job 5696078 as requested; Reason given: Aborted
So that seems to suggest someone stopped the backup by cancelling it possibly?
Did you look into the logs mentioned, for example:
FileServerDiarioTape:srvcidasc50.cidasc.sc.gov.br:pseudo_saveset See the file 'C:\Program Files\EMC NetWorker\nsr\logs\policy\FileServerDiarioTape\BackupDiarioTape\BackupDiario_5696069_logs\5696078.log' for command output.And most importantly from .raw log:
No group is associated with workflowwhich makes me wonder what the full messages actually say? As a workflow should have a protection group assigned to it, but other logs seem stil to suggest it intended to backup
srvcidasc50.cidasc.sc.gov.br:E:\backup\SQLServer\Completo?