1 Rookie
•
35 Posts
0
1747
December 2nd, 2021 11:00
NetWorker 9.2 - Status / Session does not show
NetWorker 9.2 hosted on Windows Server 2012 R2.
In the Monitoring tab, the All Sessions no longer display anything although backups are working fine.
In the Policies pane, the Status does not show, it is also Never run for all policies.
While all functions seem to work (backups and restores work, and I can browse the savesets) I can no longer see the job status or Show details of the jobs.
I tried to do a complete reinstall of NetWorker 9.2. I deleted C:\Program Files\EMC NetWorker, however even after reinstall it did not fix the issue.
Any ideas?
No Events found!
VictorGh
1 Rookie
•
35 Posts
0
January 24th, 2022 14:00
I found the solution:
bingo.1
2.4K Posts
1
December 2nd, 2021 12:00
My assumption is: you have a corrupt job database. Try the following:
- stop all NW activities (net stop nsrexecd)
- delete/rename the directory "C:\Program Files\EMC NetWorker\nsr\res\jobsdb"
- restart NW (net start nsrd & net start gstd)
Let's see what the outcome will be.
Next, you have two more things to do:
- Move NW away from your system drive! - It should not be installed here!
- Upgrade/update to a current version (19.5.0.2) as yours is already out of support.
VictorGh
1 Rookie
•
35 Posts
0
December 3rd, 2021 07:00
Hi Bingo, thanks for the quick suggestion.
I tried renaming the jobsdb folder, but it didn't help. As I mentioned this is a clean installation, I deleted the entire C:\Program Files\EMC NetWorker folder before reinstalling fresh and the problem persists. I also reinstalled Java.
It seems to be an issue related to the OS itself, I just don't know what.
It has worked in the past and it continues to work on numerous other production servers.
bingo.1
2.4K Posts
0
December 3rd, 2021 07:00
O.K. - maybe it is time to use the latest version. Since NW 18.0 (afair) there is a new software available, called NetWorker Runtime Environment (NRE) which replaces JRE (and does not need any java licensing to obey). Let's hope this will do the trick.
VictorGh
1 Rookie
•
35 Posts
0
December 5th, 2021 09:00
Can I use NRE with NetWorker 9.2 ?
PrinceAijaz
1 Rookie
•
38 Posts
0
December 24th, 2021 07:00
Yes you can use NRE with 9.2.2 .
Latest Version of NRE is compatible with
, 9.2.2, 18.1.18.2, 19.1, 19.1.1, 19.2, 19.2.1, 19.3, 19.4, 19.5
barry_beckers
393 Posts
0
December 24th, 2021 09:00
any specific reason to use a version out of support since around dec. 2019 (albeit some support was offered even after that)? and 9.2.1.4 at that and not the latest nw9.2.2.x? as there might also be some issues with sessions not showing or the opposite old sessions still showing in the nw nmc until NMC is restarted?
A later version in combination with NRE (nre 8.0.11 just released recently) makes having a working/supported java runtime much easier for both the nw server and for the the windows host running the nmc client (most likely combination).
When using a very recent nw19 version, you might wanna use nw19.5.0.4 just released the 20th as that updates log4j to 2.16 so that at least the RCE (remote code execution) issues is prevented, even though log4j 2.16 still would show to be vulnerable to cve-2021-45105.
supported nw versions 19.2 and 19.3 use log4j 1.x and are therefor not vulnerable to the log4j 2.x issues. Even though Dell states nw19.3 is vulnerable it does seem to be the case according to the log4j scan tool stated in the NW DSA which shows log4j 1.x being used by NW.
PrinceAijaz
1 Rookie
•
38 Posts
0
December 24th, 2021 21:00
Hey Barry
This was intended only for question Can I use NRE with NetWorker 9.2?
With reference to the log4j to mitigate the risk , DELLEMC has released NWR 19.5.0.4 CHF
barry_beckers
393 Posts
1
December 25th, 2021 04:00
Which still beckons the question of OP why to use that even if it is a new install? Then better use a more recent one, which might have a lot of issues fixed (I sound almost as if being from Dell, which I am not, but we get the "please upgrade to latest-and-greatest: all the time, however without the promise that it would solve any issue we'd have).
Only if there would be valid reasons to have an unsupported older version (functionality no longer supported, environment to be decommissioned still pending whatever reasons, etc). However not ever for something new, especially not if it is intended for production.
No support, no nothing...