Preparing to Install the VERITAS Software
Note
You must ensure that you have made backups of all data that you want to preserve. In particular, you will need the information in files such as /etc/fstab. You should also run the vxlicrep, vxdisk list, and vxprint -ht commands, and record the output from these. You may need this information to reconfigure your system after the upgrade.
If you are upgrading an HA cluster, follow the guidelines given in the VERITAS Cluster Server (VCS) Installation Guide for information on preserving your VCS configuration across the upgrade procedure. In particular, you should take care to make backups of configuration files, such as main.cf and types.cf, in the /etc/VRTSvcs/conf/config directory. Additional configuration files, such as Oracletypes.cf, may also be present in this directory if you have installed any VCS agents. You should also back up these files.
To prepare for the VERITAS software upgrade
-
Log in as superuser.
-
Perform any necessary preinstallation checks and configuration. See Preinstallation Instructions for more information.
-
Use the vxlicrep command to make a record of the currently installed VERITAS licenses. Print the output or save it on a different system.
-
If the systems are running as a cluster, take all service groups offline, and shut down VCS prior to launching the uninstallsf script:
# /opt/VRTSvcs/bin/hastop -all
Note
Do not use the -force option when executing hastop. This will leave all service groups online and shut down VCS, causing undesired results during uninstallation of the packages.
-
Use the following command to check if any VxFS file systems or Storage Checkpoints are mounted:
# df -F vxfs
-
Unmount all Storage Checkpoints and VxFS file systems:
# umount /checkpoint_name
# umount /filesystem
-
Verify that all file systems have been cleanly unmounted:
# echo "8192B.p S" | fsdb -F vxfs filesystem | grep clean
flags 0 mod 0 clean clean_value
A clean_value value of 0x5a indicates the file system is clean, 0x3c incidates the file system is dirty, and 0x69 indicates the file system is dusty. A dusty file system has pending extended operations.
- If a file system is not clean, enter the following commands for that file system:
# fsck -F vxfs filesystem
# mount -F vxfs filesystem mountpoint
# umount mountpoint
This should complete any extended operations that were outstanding on the file system and unmount the file system cleanly.
There may be a pending large fileset clone removal extended operation if the umount command fails with the following error:
file system device busy
You know for certain that an extended operation is pending if the following message is generated on the console:
Storage Checkpoint asynchronous operation on file_system file
system still in progress.
- If an extended operation is pending, you must leave the file system mounted for a longer time to allow the operation to complete. Removing a very large fileset clone can take several hours.
- Repeat step 7 to verify that the unclean file system is now clean.
-
Stop activity to all VxVM volumes. For example, stop any applications such as databases that access the volumes, and unmount any file systems that have been created on the volumes.
-
Stop all the volumes by entering the following command for each disk group:
# vxvol -g diskgroup stopall
To verify that no volumes remain open, use the following command:
# vxprint -Aht -e v_open
-
Make a record of the mount points for VxFS file systems and VxVM volumes that are defined in the /etc/fstab file. You will need to recreate these entries in the /etc/fstab file on the freshly installed system.
-
Reboot the system.
|
