Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

NetBackup file cleanup - client and media servers

Created: 23 Jan 2013 | 4 comments

This question is particularly for unix hosts!

 

When you install Netbackup, it loads files into the install directory.

When you patch or update, it makes a tar file of the old files and installs new ones.

Is there a process to remove/cleanup those old files?

 

On media servers it creates pack direcories for each version - is there an easy way to remove these files?

On clients, there are files in the java directory for old versions  - are these required for backwards compatability?

If not, is there an easy way to clean them up?

 

 

Comments 4 CommentsJump to latest comment

Will Restore's picture

Stuart Green addressed old pack files in this thread
https://www-secure.symantec.com/connect/forums/out...

Will Restore -- where there is a Will there is a way

Genericus's picture

I understand manually removing old pack files, I guess I was asking about if there was a process/command to do this - i.e. packremove, similar to committing a package.

Something that would read your current version and remove older pack files automatically.

 

Also, on CLIENTS, that have seen multiple upgrades, I see files here:

# ls -1 /usr/openv/java
allFSA_60.jar
allFSA_65.jar
allHSM_60.jar
allHSM_65.jar
allNB.jar
allNB_60.jar
allNB_65.jar
allNB_70.jar
allNB_71.jar
antlr-2.7.2.2.2.jar
antlr-2.7.2.jar
auth.conf
auth.conf.template
avalon-framework-4.1.5.2.2.jar
avalon-framework-4.1.5.jar
backport-util-concurrent.jar
cloudstorejava.conf
concurrent-1.3.2.jar
crimson.jar
dbext.jar
dbext_60.jar
dbext_65.jar
dbext_70.jar
dbext_71.jar
emmidl.jar
emmidl_65.jar
emmidl_70.jar
emmidl_71.jar
get_trace
jacorb.jar
jacorb2.2.jar
jbpSA
jcchart.jar
jcfield401K.jar
jdom.jar
jnbSA
jre
logkit-1.2.jar
logkit-1.2_2.2.jar
mcharts.jar
migrate_Preferences.sh
nbCommon.jar
nbCommon_60.jar
nbCommon_65.jar
nbCommon_70.jar
nbCommon_71.jar
nbj.conf
nbj.conf.bak
nbjP_60.jar
nonroot_admin_nbjava
pbxiop.jar
pbxiop2.jar
pvxDates.jar
pvxSpin.jar
servicelayer.jar
servicelayer_60.jar
servicelayer_65.jar
servicelayer_70.jar
servicelayer_71.jar
tpc_Client.txt
tpc_Console.txt
vrts
vxrep-v2.20.jar
vxssiop.jar
vxssiop2.jar
 

All the 60.jar, 65.jar 70.jar 71.jar - what are those and can I remove them?

 

NetBackup 7.5.0.3 on Solaris 10
EMC Data Domain 990 VTL via FC
acsls 8.3.0
SL8500 LTO5

CRZ's picture

All the 60.jar, 65.jar 70.jar 71.jar - what are those and can I remove them?

I DID find my 2011 answer to THIS question, at least.  ;-)

From https://www-secure.symantec.com/connect/forums/netbackup-71-java-administration-console-server-running-655#comment-5385721

We always include some backrev GUI environments (libraries and whatnot) for you to use via the -r command switch with jnbSA; however, that's UNIX/Linux only.  It doesn't exist on Windows.

For example, on my Solaris box running 7.1:
jnbSA -r 7.1 is kinda pointless, because it will do the same thing that a plain ol' jnbSA would do...bring up a 7.1 GUI.  But you can do it if you want!  :)
jnbSA -r 7.0 brings up a 7.0.1 Java console, on the other hand.  (But my display said "7.0.1RC4" - ?  Hmmm...)
jnbSA -r 6.5 will bring up a 6.5.6 console
Finally, jnbSA -r 6.0 will totally throw you back with a 6.0 MP7 console (and a really cool spinning V!!!)

So to answer YOUR question: yes, if you don't have any backrev servers you would ever need to try monitoring, you can go ahead and remove all the backrev stuff.  (Keep in mind, we may try to reinstall them when you upgrade to NetBackup 7.6!)

As for the old pack directories, Will's answer of "manual delete" is the correct one, in my opinion.


bit.ly/76LBN | APPLBN | 75LBN

Will Restore's picture

No automatic process, just manual delete.

 

If you are on 7.5 you should be fine to delete 60 65 70 files. 

I would keep one level back (71) just because. :)

 

Will Restore -- where there is a Will there is a way