Unsolved
This post is more than 5 years old
1 Message
0
2249
Errors: "savegrp: klnbppteamsql:index index was never started" & "Cannot determine status of backup process"
What are these TWO errors mean?
Why in-turn wee see "All savefs klnbppteamsql: succeeded." if these werer reported as failed in earlier part of the message sent-out by backup server "BMHDCCU1"?
What are we saving - if we see failed messages, and succeded messages from the same server ?
Thanks again!
=====
Email: BMHDCCU1@manganese.tw.dzcs.bz
Subject: BMHDCCU1: SAVEGROUP_FAILED
NetWorker savegroup: (alert) Manganese File Share Daily aborted, Total 7 client(s), 7 Failed. Please see group completion details for more information.
Failed: klnbppteamsql, kmblnfile3.tw.dzcs.bz, kmgecoradev2, kmgecoradev3, kmalporaprod1, kmgecomsqlp2, kmgecomsqlp1
Start time: Tue May 10 09:36:44 2011
End time: Tue May 10 09:51:27 2011
--- Never Started Save Sets ---
(**Note: Error#1 **)
savegrp: klnbppteamsql:index index was never started
savegrp: kmgecoradev2:index index was never started
savegrp: kmalporaprod1.tw.dzcs.bz:index index was never started
savegrp: kmgecomsqlp2:index index was never started
(**Note: Error#2 **)
--- Unsuccessful Save Sets ---
* kmblnfile3.tw.dzcs.bz:H:\ Cannot determine status of backup process. Use mminfo to determine job status.
* kmblnfile3.tw.dzcs.bz:H:\ aborted
* : termination request was sent to job 448062 as requested; Reason given was 'Aborted'
--- Successful Save Sets ---
* klnbppteamsql:All savefs klnbppteamsql: succeeded.
* kmgecoradev2:All savefs kmgecoradev2: succeeded.
* kmgecoradev3:All savefs kmgecoradev3: succeeded.
* kmblnfile3.tw.dzcs.bz:All savefs kmblnfile3.tw.dzcs.bz: succeeded.
* kmalporaprod1:All savefs kmalporaprod1: succeeded.
* kmgecomsqlp2:All savefs kmgecomsqlp2: succeeded.
* kmgecomsqlp1:All savefs kmgecomsqlp1: succeeded.
AllanW1
334 Posts
0
May 13th, 2011 06:00
Hi Srichirav- Moving this over for additional help..
Thanks,
Allan
ble1
2 Intern
2 Intern
•
14.3K Posts
0
May 15th, 2011 09:00
Regarding Error #1
It looks as if group was aborted and index saveset for given clients was never started.
Regarding Error #2
Looks as if it was also aborted. It may say too that control session (which is alive since start till the end of saveset backup, but idle during that time) was killed and NW server does not know if this has completed or not thus the only way to figure that out is to check with mminfo flags for that saveset.
In both cases it looks as if abort signal was sent by either some operator or some event that might have emulated such action has happened (eg. crash of nsrjobdbd). You don't say much about platform (OS) and NW version you run so we can only speculate. It would be easier if you had attached daemon.raw (the part which covers the error) to your message...