UNIX for Dummies Questions & Answers
Veritas commands??
can someone tell me where I can go look for information of commands to check up on veritas volume manager and veritas file system if an alert is received about there being a disk problem??
I need information on what commands to use to perform diagnostic checkups.
this is quite important so any straight forward answers is greatly appreciated. By the way, am using a SunOS 5.8 system
If you have some problem in the Veritas disk, the
system will log this problem in the /var/adm/messages.
I haven’t the latest Veritas Version (I have VM 3.1 and FS 3.3.3),
in thats versions, the volume manager don’t log by default, you must change the script vxvm-startup2 to add the -x Flags, see man vxconfigd (export MANPATH=$MANPATH:/opt/VRTSvxvm/man/)
When the Volume manager log information, the default file
is:
To query the status of Veritas Objetcs, you can use:
vxprint -Aq
In other machine (HP-UX), I use a script to check errors,
you must to modify at your convenience and correct
the paths to the commands.
added code tags for readability —oombera
vxdisk list will list all the disks and quick status
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t4d0s2 sliced — — error
c0t5d0s2 sliced crash-p rootdg online
c1t0d0s2 sliced data00p datadg online
c1t1d0s2 sliced data01p datadg online
Note «error» on c0t4d0s2, that drive is not actually controlled by Veritas but by DiskSuite. You may see the same on a different drive if you have drives not controlled by Veritas.
vxprint -th will list all the disks, groups, plexes. more detailed listing AND is one you are suppose to do to help with recovery. It should be saved, printed, put into a D/R book.
# vxprint -th
Disk group: rootdg
DG NAME NCONFIG NLOG MINORS GROUP-ID
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
V NAME USETYPE KSTATE STATE LENGTH READPOL PREFPLEX
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
dg rootdg default default 0 926539269.1025.isybase
dm crash-p c0t5d0s2 sliced 3590 17678493 —
dm crash-s c4t1d0s2 sliced 3590 17678493 —
v vol01 fsgen ENABLED ACTIVE 21356672 SELECT —
pl vol01-01 vol01 ENABLED ACTIVE 21359268 CONCAT — RW
sd crash-p-01 vol01-01 crash-p 0 17678493 0 c0t5d0 ENA
sd crash-s-01 vol01-01 crash-s 0 3680775 17678493 c4t1d0 ENA
Disk group: datadg
DG NAME NCONFIG NLOG MINORS GROUP-ID
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
V NAME USETYPE KSTATE STATE LENGTH READPOL PREFPLEX
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
dg datadg default default 50000 926546267.1194.isybase
dm data00p c1t0d0s2 sliced 2159 8378640 —
dm data00s c5t0d0s2 sliced 2159 8378640 —
dm data01p c1t1d0s2 sliced 2159 8378640 —
dm data01s c5t1d0s2 sliced 2159 8378640 —
dm data02p c1t2d0s2 sliced 2159 8378640 —
Источник
Command line option to get client NetBackup version, OS, and hardware type
Description
Command line option to get client NetBackup version, operating system (OS), and hardware type.
To get client information, run the following command from the Master server:
Note: Where is the host for which you want to get configuration information.
UNIX/Linux: /usr/openv/netbackup/bin/admincmd/
Windows: install_path\Veritas\NetBackup\bin\admincmd\
Add the -L and -A options (when using -g or -s) to get the NetBackup patch level.
Example, Linux master:
bpgetconfig -g nbmaster2 -L
Client/Master = Master
NetBackup Client Platform = Linux, RedHat2.6.32
NetBackup Client Protocol Level = 8.3.0
Product = NetBackup
Version Name = 8.3
Version Number = 830000
NetBackup Installation Path = /usr/openv/netbackup/bin
Client OS/Release = Linux, 3.10.0-693.el7.x86_64
Example, Windows client:
bpgetconfig -g nbclient1 -L
Client/Master = Client
NetBackup Client Platform = PC-x64, WindowsXP
NetBackup Client Protocol Level = 8.3.0
Product = NetBackup
Version Name = 8.3
Version Number = 830000
NetBackup Installation Path = C:\Program Files\Veritas\NetBackup\bin
Client OS/Release = Windows2016 10
For more information, please consult the Commands Reference Guide specific to your NetBackup version.
Источник
Veritas NetBackup™ Installation Guide
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.
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.
HP-UX Service Guard Clusters
If NetBackup has been configured to run as a clustered package, you must also delete the following directory:
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.
Do not remove PBX if your server uses other Veritas 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.
To remove NetBackup from UNIX 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:
Identify any installed add-on products by using the following command:
Seven add-on products can be installed on servers and clients. They are:
Remove any add-on products found.
(Conditional: servers only) For Solaris systems only, run the following command:
To unregister NetBackup from the VxUL master 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
To unregister all NetBackup products with LiveUpdate, enter the following command:
(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:
Open the vxdbms.conf file.
This file contains a list of the database-related files and the path for each file.
Delete each of the database-related files.
Remove the NetBackup configuration package with the appropriate command as follows:
installp -u VRTSnbcfg
rpm -e VRTSnbcfg
(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
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.
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 Veritas NetBackupSecurity and Encryption Guide.
installp -u VRTSnetbp
rpm -e VRTSnetbp
When the script asks if you want to remove the installed package VRTSnetbp , enter y and press Enter .
When the script asks if you want to continue with the package removal using superuser permission, enter y and press Enter .
installp -u VRTSnbjava
rpm -e VRTSnbjava
installp -u VRTSnbjre
rpm -e VRTSnbjre
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.
installp -u VRTSnbclt
rpm -e VRTSnbclt
If there are running NetBackup processes and daemons, terminate them manually for a successful NetBackup removal.
Remember, you should not remove PBX if your server uses other Veritas software products that require PBX to run.
installp -u VRTSpbx
installp -u VRTSnbpck
rpm -e VRTSnbpck
The rm -f /usr/openv command also removes any add-on products that are installed on the computer where you perform this command.
If /usr/openv is the actual directory, run the following command:
If /usr/openv is a symbolic link to that directory, run the following commands:
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.
Depending on your operating system, you may need to use the rmdir command to remove the /usr/openv directory.
If you modified the startup and the shutdown scripts, run the following command:
/sbin/chkconfig —del netbackup
Remove the following startup scripts:
On HP-UX systems:
On Linux Debian systems:
On Linux Red Hat systems:
The following startup scripts are only on servers and appear only if NetBackup Fiber Transport was enabled on the server:
On Linux SUSE systems:
The following startup scripts are only on servers and appear only if NetBackup Fiber Transport was enabled on the server:
On other servers and clients:
The following startup scripts are only on servers and appear only if NetBackup Fiber Transport was enabled on the server:
For AIX systems only:
In the /etc/inittab file, remove the following NetBackup entry:
In the /etc/rc.shutdown file, remove the following line:
Remove the LiveUpdate components as follows:
First, examine the following file to see if NetBackup is the only product that uses LiveUpdate:
If NetBackup is the only product that currently uses LiveUpdate, run the following command:
If LiveUpdate is the only product installed in the /opt/Symantec directory, remove the following files:
rm -f /etc/Symantec.conf
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
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.
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 common subdirectory 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/.vxss directory. Inform all users that they can remove this directory.
Files are generated in the /.vxss directory 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 /.vxss directory. These files typically have a name that is consistent with a DNS entry for a network interface, as in machine.company.com . Example directory entries are as follows:
These 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/credentials directory.
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.
Источник
