Removing NetBackup from UNIX and Linux servers and clients
Use this procedure to remove NetBackup from UNIX and Linux servers and clients. You may also need to reference other documents for procedures of specific tasks to remove NetBackup successfully.
Use the following guidelines when you remove NetBackup from UNIX and Linux servers and clients:
NetBackup relational database (NBDB) location | If you moved the NBDB files in /usr/openv/db/data from their default installation location, this procedure includes a step that describes how to remove these files. |
Clustered environments | Before you begin to remove NetBackup, you must remove NetBackup from the cluster application. Follow the instructions in your cluster documentation on how to remove a group, then you can remove NetBackup. The virtual host name security certificates are automatically removed from the shared drive of the cluster as a part of NetBackup server software removal. You must remove NetBackup from each node in the cluster. |
PBX | When you remove NetBackup, PBX is not removed. You must remove PBX manually. This procedure includes a step that describes how to perform this task. Warning: Do not remove PBX if your server uses other Cohesity software products that require PBX to run. |
NetBackup Administration Console | The NetBackup Administration Console must be closed when you remove NetBackup. Otherwise, NetBackup may cause a failure that forces you to restart the procedure. |
IT Analytics Data Collector install location | IT Analytics Data Collector is installed at |
Note:
Since the VRTSpddeu.rpm package is optional, you may not need to remove it.
To remove NetBackup from Linux servers
- Log on as the root user on the server or the client.
- (Conditional: servers only) Perform a catalog backup.
- If the NetBackup Administration Console is open, you must close it now.
- (Conditional: servers only) Save all important data from any add-on products that you have installed.
- Stop the NetBackup/Media Manager daemons with the following command:
/usr/openv/netbackup/bin/bp.kill_all
- Identify any installed add-on products by using the following command:
AIX
lslpp -L
Linux
rpm -qa
Solaris
pkginfo
Look for any of the seven add-on products listed:
VRTSfrnb (Applies only to servers) VRTSfrnbclt VRTSjanb (Applies only to servers) VRTSjanbclt VRTSzhnb (Applies only to servers) VRTSzhnbclt VRTSnbsds (Applies only to servers)
Remove any add-on products found.
- To unregister NetBackup from the VxUL primary configuration that is stored in the /etc/vx/vrtslog.conf file, run the following command:
/usr/openv/netbackup/bin/vxlogcfg -r -p 51216
The -p option specifies the product ID, which is 51216 for NetBackup.
- (Conditional: servers only) If BMR is supported and enabled on the server, remove the associated files with the following command:
/usr/openv/netbackup/bin/bmrsetupmaster -undo -f
- (Conditional: servers only) If you moved the NBDB files from their default installation location, you must delete these files manually as follows:
Navigate to the following directory where the NBDB files reside:
/usr/openv/db/data
Open the
vxdbms.conffile.This file contains a list of the database-related files and the path for each file.
Delete each of the database-related files.
- (Conditional: servers only) If NetBackup Fibre Transport is supported and enabled on the server, remove the associated files.
If NetBackup Fibre Transport is enabled with BSI driver on Red Hat 7.x, run the command shown:
/usr/openv/netbackup/bin/admincmd/nbftsrv_config -d
If NetBackup Fibre Transport is enabled with SCST driver, run the command shown:
/usr/openv/netbackup/bin/admincmd/nbftsrv_config -scst -uninstall
- (Conditional: servers only) To remove the NetBackup server libraries, run the command shown.
Note:
The virtual host name security certificates are automatically removed from the shared drive of the cluster as a part of NetBackup server software removal.
More information about this topic is available. Please refer to the information on retaining host ID-based certificates when reinstalling NetBackup in the NetBackup Security and Encryption Guide.
Linux: rpm -e VRTSnbslibs
- (Conditional: primary servers only) Remove the packages shown, in the order shown, with the listed command:
rpm -e VRTSnbweb
rpm -e VRTSnbmqbrkr
- (Conditional: servers only) To remove the NetBackup server package, run the commands shown.
Note:
The virtual host name security certificates are automatically removed from the shared drive of the cluster as a part of NetBackup server software removal.
More information about this topic is available. Please refer to the information on retaining host ID-based certificates when reinstalling NetBackup in the NetBackup Security and Encryption Guide.
Linux primary server:
rpm -e VRTSnbprimary
rpm -e VRTSnetbp
Linux media server:
rpm -e VRTSnetbp
- (Conditional: primary servers only) Remove the package shown with the command shown:
rpm -e VRTSpostgresql
- Remove the NetBackup configuration package with the appropriate command as follows:
AIX
installp -u VRTSnbcfg
Linux
rpm -e VRTSnbcfg
Solaris
pkgrm VRTSnbcfg
- For the clients that support PureDisk, remove all PureDisk files with the following command:
/opt/pdde/pddeuninstall.sh -forceclean
- (Conditional: servers only) For the clients that support MSDP, remove all MSDP files with the following command:
/opt/pdde/pddeuninstall.sh -basedir /usr/openv/pdde/ -ostdir /usr/openv/lib/ost-plugins/ -forceclean
Note:
Be aware the preceding command is a single command which takes three parameters (basedir, , ostdir, and forceclean), and two directory parameters take paths as input.
- Remove the NetBackup-Java Display Console by using the appropriate native command as follows:
AIX
installp -u VRTSnbjava
Linux
rpm -e VRTSnbjava
Solaris
pkgrm VRTSnbjava
- Remove the NetBackup Java Runtime Environment by using the appropriate native command as follows:
AIX
installp -u VRTSnbjre
Linux
rpm -e VRTSnbjre
Solaris
pkgrm VRTSnbjre
- Remove the NetBackup client libraries by using the appropriate native command as shown.
Note:
As part of the removal of the NetBackup server software, the security certificates are automatically deleted. If you want to retain the certificates, please save them before removing NetBackup.
More information about this topic is available. Please refer to the information on retaining host ID-based certificates when reinstalling NetBackup in the NetBackupSecurity and Encryption Guide.
AIX
installp -u VRTSnbclibs
Linux
rpm -e VRTSnbclibs
Solaris
pkgrm VRTSnbclibs
- Remove the NetBackup client by using the appropriate native command as shown.
Note:
As part of the removal of the NetBackup server software, the security certificates are automatically deleted. If you want to retain the certificates, please save them before removing NetBackup.
More information about this topic is available. Please refer to the information on retaining host ID-based certificates when reinstalling NetBackup in the NetBackupSecurity and Encryption Guide.
AIX
installp -u VRTSnbclt
Linux
rpm -e VRTSnbclt
Solaris
pkgrm VRTSnbclt
Note:
If there are running NetBackup processes and daemons, terminate them manually for a successful NetBackup removal.
- Remove the NetBackup DirectIO package.
Linux: rpm -e VRTSnbdirectio
- Remove PBX with the appropriate native command as follows:
Note:
Remember, you should not remove PBX if your server uses other Cohesity software products that require PBX to run.
AIX
installp -u VRTSpbx
Linux
rpm -e VRTSpbx
Solaris
pkgrm VRTSpbx
- Remove NetBackup Pre-Check package with the appropriate command as follows:
AIX
installp -u VRTSnbpck
Linux
rpm -e VRTSnbpck
Solaris
pkgrm VRTSnbpck
- Run the script that is shown to remove IT Analytics Data Collector on Linux.
/usr/openv/analyticscollector/UninstallerData/uninstall_dc.sh -r
Remove the symbolic link from
/usr/openv/analyticscollectorif it exists.If the
uninstall_dc.shscript is unavailable for any reason, complete the steps shown:1
Stop the IT Analytics Data Collector services:
/usr/openv/analyticscollector/mbs/bin/aptare_agent stop systemctl stop aptare_kafka.service systemctl stop aptare_zookeeper.service systemctl disable aptare_zookeeper.service systemctl disable aptare_kafka.service
2
Delete the files. If
/usr/openv/analyticscollector/is a symbolic link, follow the link and identify the actual install path:rm -rf /usr/openv/analyticscollector/
If
/usr/openv/analyticscollector/is symbolic link, be sure to delete the actual DC install path.rm -f /etc/systemd/system/aptare_kafka.service rm -f /etc/systemd/system/aptare_zookeeper.service systemctl daemon-reload rm -f /etc/init.d/aptare_agent
3
Remove the RC scripts if they exist:
rm -f /etc/rc3.d/K*aptare_agent rm -f /etc/rc3.d/S*aptare_agent rm -f /etc/rc5.d/K*aptare_agent rm -f /etc/rc5.d/S*aptare_agent
4
If any stale processes are active on the system, stop them with the kill -9 pid command.
ps -ef | grep aptare kill -9 pid
- Remove the /usr/openv directory.
Warning:
The rm commands used remove any add-on products that are installed on the computer where you perform this command.
Determine if /usr/openv is a symbolic link with the command shown. If /usr/openv is a symbolic link, make note of the actual path. The path is required for a later command.
file -h /usr/openv
/usr/openv: symbolic link to /opt/openv
If /usr/openv is a symbolic link, run the commands shown:
cd /usr/openv
This command changes you into the directory that symbolic link points to, such as /opt/openv.
ls
List the contents of the directory. Review this information to confirm what you are about to delete.
Warning:
Before you continue, make sure that you are at the correct location and verify that the subdirectories are what you expect them to be. To help prevent removing the wrong directories, the previous commands verify your current location and list the files in that directory. After you verify the directory location and its contents, remove the directory with the next commands.
cd /
Change to the root directory.
rm -rf directory
For the directory value, enter the information from the file command. This command deletes the directory that contains the NetBackup binaries.
Example: rm -rf /opt/openv
rm -f /usr/openv
Delete the symbolic link.
If /usr/openv is the actual directory, run the command shown:
rm -rf /usr/openv
Note:
Depending on your operating system, you may need to use the rmdir command to remove the
/usr/openvdirectory.rmdir /usr/openv
- For Linux systems only:
If you modified the startup and the shutdown scripts, run the following command:
/sbin/chkconfig --del netbackup
Depending on the distribution of Linux, the startup and the shutdown scripts may already be deleted.
- Remove the scripts shown. Depending on the operating system, the startup and the shutdown scripts may already be deleted.
On AIX systems:
/etc/rc.netbackup.aix
On Linux Debian systems:
/etc.init.d/netbackup /etc/rc0.d/K01netbackup /etc/rc1.d/K01netbackup /etc/rc2.d/S95netbackup
On Linux Red Hat systems:
/etc/rc.d/init.d/netbackup /etc/rc.d/rc0.d/K01netbackup /etc/rc.d/rc1.d/K01netbackup /etc/rc.d/rc2.d/S77netbackup /etc/rc.d/rc3.d/S77netbackup /etc/rc.d/rc5.d/S77netbackup /etc/rc.d/rc6.d/K01netbackup
The following startup scripts are only on servers and appear only if NetBackup Fiber Transport was enabled on the server:
/etc/rc.d/init.d/nbftserver /etc/rc.d/rc0.d/K03nbftserver /etc/rc.d/rc1.d/K03nbftserver /etc/rc.d/rc2.d/S21nbftserver /etc/rc.d/rc3.d/S21nbftserver /etc/rc.d/rc5.d/S21nbftserver /etc/rc.d/rc6.d/K03nbftserver
On Linux SUSE systems:
/etc/init.d/netbackup /etc/init.d/rc0.d/K01netbackup /etc/init.d/rc2.d/S77netbackup /etc/init.d/rc3.d/S77netbackup /etc/init.d/rc5.d/S77netbackup /etc/init.d/rc6.d/K01netbackup
The following startup scripts are only on servers and appear only if NetBackup Fiber Transport was enabled on the server:
/etc/init.d/nbftserver /etc/init.d/rc2.d/K01nbftserver /etc/init.d/rc2.d/S05nbftserver /etc/init.d/rc3.d/K01nbftserver /etc/init.d/rc3.d/S05nbftserver /etc/init.d/rc5.d/K01nbftserver /etc/init.d/rc5.d/S05nbftserver
On other servers and clients:
/etc/init.d/netbackup /etc/rc0.d/K01netbackup /etc/rc1.d/K01netbackup /etc/rc2.d/S77netbackup
The following startup scripts are only on servers and appear only if NetBackup Fiber Transport was enabled on the server:
/etc/init.d/nbftserver /etc/rc0.d/K03nbftserver /etc/rc1.d/K03nbftserver /etc/rc2.d/S21nbftserver
For AIX systems only:
In the /etc/inittab file, remove the following NetBackup entry:
/etc/rc.netbackup.aix
In the /etc/rc.shutdown file, remove the following line:
/etc/rc.netbackup.aix stop
Remove the LiveUpdate components as follows:
First, examine the following file to see if NetBackup is the only product that uses LiveUpdate:
/etc/Product.Catalog.JavaLiveUpdateIf NetBackup is the only product that currently uses LiveUpdate, run the following command:
/opt/Symantec/LiveUpdate/uninstall.sh -a
If LiveUpdate is the only product installed in the
/opt/Symantecdirectory, remove the following files:rm -f /etc/Symantec.conf
Note:
Before you remove the following product catalog file, make sure that it is empty. The empty file size is equal to 0 bytes. If the product catalog file is not empty, do not remove it because other products still require it.
rm -f /etc/Product.Catalog.JavaLiveUpdate
- To remove the NetBackup-Java application state data for the root account, run the appropriate command as follows:
Warning:
Do not insert a space between the slash character (/) and the period or the dot character (.) of /.veritas. A space between these characters removes all of your files from the root level and beyond.
To remove the NetBackup-Java application state data for the root account for all releases, run the following command:
/bin/rm -rf /.veritas
To remove the NetBackup-Java application state data for the root account for a specific release, run the following command:
/bin/rm -rf /.veritas/java/version
Where version is the six-digit NetBackup version number. For example, NetBackup version 8.0 with no upgrades applied would be entered as 800000.
- Inform NetBackup-Java users that they can remove their $HOME/.veritas directory.
The $HOME/.veritas and the $HOME/.veritas/java directories contain application state information, that is saved when the user exits NetBackup-Java applications. The saved information includes table column order and size. The process removes this directory for the root user only.
The
commonsubdirectory in $HOME/.veritas/java/.userPrefs/vrts can be removed. - If you enabled NetBackup Access Control, NetBackup placed several files on clients and servers. These files can be divided into the following categories:
NetBackup application temporary files
These files are removed with NetBackup.
Individual user (cache) files
These cache files reside in the
$HOME/.vxssdirectory. Inform all users that they can remove this directory.Files are generated in the
/.vxssdirectory by a Single Sign-On operation of the NetBackup Administration Console on the host where the console runs. The NetBackup Administration Console cleans these files when an exit function is performed, so the directory does not always contain temporary files. However, if a system crash were to occur, any files in the directory may be left behind. With the console shutdown , you can delete these files safely with no data loss.NetBackup also creates cached certificates for client and server NetBackup applications. These files reside within the
/.vxssdirectory. These files typically have a name that is consistent with a DNS entry for a network interface, as inmachine.company.com. Example directory entries are as follows:/usr/openv/var/vxss/credentials/machine.company.com/usr/openv/var/vxss/credentials/dhcpThese files are created with the command bpnbat -LoginMachine. If you plan to reinstall NetBackup on the same computer at a later date, do one of the following:
Preserve the certificates in the
vxss/credentialsdirectory.If you do not preserve the certificates, you must provide the computer identity password as originally set on the Root+AB broker. As an alternative, you can reset the password on the Root+AB broker when you reinstall.
For more information on Root+AB brokers, see the .NetBackup Security and Encryption Guide
For more information on NetBackup Access Control and how to remove it, see the NetBackup Security and Encryption Guide.