Unsolved
1 Message
0
2226
September 9th, 2021 01:00
when trying to back up a SQL server I get the following error.
suppressed 9524 bytes of output.
9/9/2021 8:59:46 AM Group SQLMC waiting for 1 jobs (0 awaiting restart) to complete.
166682 1631174412 2 5 0 6940 1308 0 svbnw001.bbic.ao savegrp NSR warning 65 Job %u with command '%s' for client %s exited with return code %d 4 5 6 704272 0 471 nsrsqlsv -LL -S 4 -s svbnw001.bbic.ao -g SQLMCPolicy/Workflow1/backup/SQLMC -a "*policy action jobid=704269" -a "*policy name=SQLMCPolicy" -a "*policy workflow name=Workflow1" -a "*policy action name=backup" -y "Fri Sep 10 23:59:59 GMT+0100 2021" -w "Fri Sep 10 23:59:59 GMT+0100 2021" -m SVSQL101MC.bbic.ao -a "*policy action jobid restart=Yes" -b
Data Domain Default" -o "\"REQUESTED_LEVEL:level=incr;\"" -l full -q -W 78 -N MSSQL$HADR:BackupTest MSSQL$HADR:BackupTest 12 18 SVSQL101MC.bbic.ao 1 3 160
9/9/2021 9:00:12 AM SVSQL101MC.bbic.ao:MSSQL$HADR:BackupTest unexpectedly exited.
9/9/2021 9:00:12 AM SQLMC:SVSQL101MC.bbic.ao:MSSQL$HADR:BackupTest See the file 'C:\Program Files\EMC NetWorker\nsr\logs\policy\SQLMCPolicy\Workflow1\backup_704269_logs\704272.log' for command output.
9/9/2021 9:00:12 AM Client 'SVSQL101MC.bbic.ao' is being skipped because no savesets of this client have been backed up as part of the backup action.
9/9/2021 9:00:12 AM The save job for the save set 'MSSQL$HADR:BackupTest' on the host 'SVSQL101MC.bbic.ao' has been completed.
9/9/2021 9:00:17 AM Action backup traditional 'backup' with job id 704269 is exiting with status 'failed', exit code 1
bingo.1
2.4K Posts
0
September 9th, 2021 02:00
Do not just look at the error but read it carefully ...
...
C:\Program Files\EMC NetWorker\nsr\logs\policy\SQLMCPolicy\Workflow1\backup_704269_logs\704272.log' for command output.
...
barry_beckers
393 Posts
0
September 19th, 2021 08:00
Also any nw .raw log file should be viewed using nsr_render_log(.exe) so that all %s variables are actually filled in, making for better readability.
And indeed look in ALL logfiles being mentioned in such logfiles.
Also log files on client end might show more info, but more and more information is also available on nw server end nowadays.
Let's hope that nw might somewhere in time actually make it possible to have logfiles available for longer than the default setting of 3 days as the nsrjob db is really not that scalable still after all these years.
Still looking into a good way to keep log files available for a longer time to be able to sift through for historic overview and problem solving, not requiring to use for example a syslog server or copying files yourself.
Redirecting towards a logfile from the workflow and backup action, is rather limited, while the contents of the nsrjob db is gone within 3 days (and should for performance reasons according to the performance and tuning guide not be increased beyond those 3 days).
Maybe that I might have newer nw features, but improvements on that end are very much looked forward to.
DPA reports of nw backup log info are not that great to sift through, or you'd have to redirect that to a files again to sift through.