About chriswilkes33

chriswilkes33

Netbackup 10.4 has a vulnerable version of tomcat running.I need to patch it (or throw the webserver in the trash since we dont use it anyway but that doesnt seem possible)I tried downloading the latest version of tomcat 9.0.88 and extracting and put...

chriswilkes33 · 05-01-2023

I have multiple libraries connected to my backup server. Each with multiple drives in them. One of my robots will only write to one drive leaving the other 3 always idle. I have just removed and readded all robots and dives (which seems to be requir...

chriswilkes33 · 03-14-2023

I am running Netbackup 10.1.1 on a RedHat 8 server. I recently did a catalog restore recovering from a hardware failure and I am having trouble connecting to two of our drives in a robot. There are still ghosts of the drive path, though the robot has...

chriswilkes33 · 11-02-2020

During an attempted upgrade from NetBackup 8.1.2 on RedHat Enterprise Linux 7.9 to Netbackup 8.3.0.1, the precheck critical checks fails the check for java_key_store fingerprints with the error:not_ok: java_key_store: [fingerprint_redacted] fingerpri...

chriswilkes33

Hi, I assumed there would be something like the nbcomponentupdate tool for the JRE.This particular vulnerability is found in CVE-2024-23672 and CVE-2024-24549. Unfortunately our auditors care more about vulnerability software flagging vulnerabilities...

chriswilkes33 · 05-02-2023

chriswilkes33 · 05-02-2023

That seems to have done it for me. There were stale allocations for the 3 drives of the 4 in that specific robot that needed to be cleared I guess.I suppose I will try to find a way to have this server notify when thos allocations hang like that. Tha...

chriswilkes33 · 03-20-2023

Appreciate the help. This did get me through whatever issue was keeping those drives stuck in that DB. Kind of frustrating to have to rebuild all of the magnetic drives across our small army of tape robots but it was successful. Thank you for the sug...

chriswilkes33 · 12-10-2020

So what this came down to was the fact that I use the NB Compnent Update utility to keep the JRE updated between releases. This caused the fingerprint to be messed up. I reinstalled the original 8.1.2 and then was able to immediately upgrade to 8.3.0...

VOX

User Statistics

User Activity

Upgrade tomcat instance

Only writing to 1 drive in a library

Invalid Drive Index when trying to delete drive

upgrade from 8.1.2 to 8.3.0.1 fails pre-check java_key_store fingerprint check

Re: Upgrade tomcat instance

Re: Only writing to 1 drive in a library

Re: Only writing to 1 drive in a library

Re: Invalid Drive Index when trying to delete drive

Re: upgrade from 8.1.2 to 8.3.0.1 fails pre-check java_key_store fingerprint check