1 Rookie
•
19 Posts
0
828
March 9th, 2023 11:00
starting troubleshooting
Hi,
I am just looking for basic troubleshooting steps in Networker...
here is a real life example... I check the log. What are further troubleshooting steps for failed save sets?
suppressed 3022338 bytes of output.
0 1678255493 1 5 0 13260 7284 0 SERVER_NAME nsrclone NSR notice 5 %s %s 2 0 24 03/08/23 01:04:53.848284 0 511 Total save set list: : 1275440590, 1795517094, 1812294301, 1829071506, 2282056269, 2349165123, 2416273979, 1896180343, 2433051195, 2500160054, 2550474608, 2567251824, 4127532695, 4261750412, 4278527627, 184885131, 352657249, 470097688, 1275361851, 1292139058, 1308916254, 1325693470, 1376019439, 1493446762, 1510223958, 1527001169, 1543778365, 1560555576, 1577332782, 1594109983, 16
0887189, 1627664390, 1644441586, 1661218772, 1677995962, 1694773148, 1711550339, 1728327541, 1778659048, 1812213434, 1828990620,
2023-03-08 1:04:53 AM 03/08/23 01:04:53.848284 Failed save set list: : 1275361851, 1292139058, 1308916254, 1325693470, 4009955446, 4043509859, 4110618599
0 1678255493 1 5 0 13260 7284 0 SERVER_NAME nsrclone NSR notice 5 %s %s 2 0 24 03/08/23 01:04:53.848284 0 511 Cloned save set list:: 1275440590, 1795517094, 1812294301, 1829071506, 2282056269, 2349165123, 2416273979, 1896180343, 2433051195, 2500160054, 2550474608, 2567251824, 4127532695, 4261750412, 4278527627, 184885131, 352657249, 470097688, 1376019439, 1493446762, 1510223958, 1527001169, 1543778365, 1560555576, 1577332782, 1594109983, 1610887189, 1627664390, 1644441586, 1661218772, 16
7995962, 1694773148, 1711550339, 1728327541, 1778659048, 1812213434, 1828990620, 1745104680, 1795436226, 1761881889, 1845767806,
2023-03-08 1:04:53 AM Action clone 'Clone-Mensuel' with job id 65935 is exiting with status 'failed', exit code 1
2023-03-08 1:04:53 AM NSRCLONE failed for one or more savesets.
barry_beckers
393 Posts
0
March 13th, 2023 08:00
As said, start with the mentioned documentation as there it states how to approach a clone failure as that is what you are dealing with here. This however assumes you have a login to access these resources, which normally should be the case when having a support contract.
I also get the idea that there are also no work instructions of what to do or look into wrg to clone or backup failures?
But to be honest getting to know things is not solely doing and finding things out on your own, as without the appropriate context, you would not know why something might be setup the way it is... this would require some kind of input either through design and implementation documents or actual colleagues.
There should be a minimum of guidance if you did not attend any formal training of how to deal with NW. It would be a waste of anyone's time to not use the resources that are available or re-inventing the wheel wrg to an approach. Even getting served bits and pieces from your colleagues might be enough to get you going.
You can and should have a look at the savesets in question to look at their status on the original backup medium as well to see if they also have a copy on other media and looking at their status to see if they are even valid. If with check the servers you mean the clients whose data is supposed to be cloned, those are completely unrelated to any cloning failures as the data to be cloned would already be on backup media and to be read from there and to be copied to other backup media. Nothing really going on anymore wrg to the clients at that point... but that is only wrg to dealing with a clone failure. Wrg to backup failures there is also references of how to deal with those.
We all started from zero at one point in time, however how to get up to speed use all available resources and if you don't have that, try to get that arranged...
barry_beckers
393 Posts
0
March 9th, 2023 13:00
It would help you and others that might try to jump in to be clear what you are even looking at? This for example is related to cloning, not to backup.
Also based on the "%s" in the log output, you seem to be looking at a .raw NW logfile, which you should render correctly by using the nsr_render_log command so that those "%s" are actually shown what they are referring to. Also it will render the date and time in the local locale setting instead of using the unix epoch time (seconds since 1970).
So not mentioning what it is even about or the NW version involved, not rendering the logs in a proper way, not stating what any information about the ssid's (and if they might possibly already be cloned already but not in a valid state, which might prevent another clone copy to be written to the target pool). Tape? Datadomain?
So really try to think about what someone might need to have to be able to say anything meaningful really?
Also I hope you have an actual support contract, because when you do you'd also have a plethora of KB articles to sift through? So to start with looking at https://www.dell.com/support/home/en-us/product-support/product/networker/docs. Where you would find KB articles like:
How to troubleshoot NetWorker Scheduled Cloning failure https://www.dell.com/support/kbdoc/en-us/000040541
https://www.dell.com/support/kbdoc/en-us/000004080/networker-log-files-and-how-to-collect-for-analysis
NetWorker: How to Debug Backup Operations https://www.dell.com/support/kbdoc/en-us/000010035
How to use nsr_render_log to render .raw log files: https://www.dell.com/support/kbdoc/000022793/
How to render daemon.raw log file at runtime https://www.dell.com/support/kbdoc/000023670/
And please start by also looking at the actual manuals. Where up until NW19.6 all docs only were available as pdf's, from nw19.7 onwards they are also online https://www.dell.com/support/manuals/en-us/networker/nw_p_nwadmin/preface?guid=guid-cfbac7bf-962d-4cac-b0dc-53707fe31149&lang=en-us.
So before asking them strangers on the internet, always first have a look at the extensive available resources and get a bit acquainted with the product that way also as above links are just a starting point really...
pob579
1 Rookie
•
19 Posts
0
March 13th, 2023 07:00
Barry, thank you very much for your time for answering...
To prevent your frustration with such may be a dumb post I will tell you that I am just "added" to the backup team with a little function to become familiar with interface and backup/clone status of Networker of a small remote site with Networker one DD unit and Dell Library covering 10+ servers.
I really don't have any intention to become a Networker guru but my experience does allow to quickly understand and troubleshoot (at least do maximum for finding causes of alerts). Sure it is exciting to myself to read and listen (utube) tech infos. But I am involved to Networker with a small role (no need to explain the goal). So, why I asked the question in the form that makes you laugh or mad (sorry about that).
From the above log I see that there are save sets proceeded succsessfully, and some of them in RED failed.
Failed save set list: : 1275361851, 1292139058, 1308916254, 1325693470, 4009955446, 4043509859, 4110618599
So, my logic say next step should be to identify a server/s to which these save sets belongs. And then check the servers. Is it so illogical?
Yes I am trying to find a solution for a problem by myself without involving for now other team members.
pob579
1 Rookie
•
19 Posts
0
March 13th, 2023 10:00
Barry, you kind of watched what's going on ... agree with you 120%
And few hours ago I had a session with my collegue for some yesterdays failures check.
Many things become obvious for me having a conversation with somebody totally aware of environment.
I continue that way. Thank you very much. And excuse my initiatives