Preventing MultipathingSuppress Devices from VxVMs View
This section describes how to exclude a device that is under VxVM or Dynamic Multipathing control. To prevent multipathing or suppress devices, enter the command 1. Select menu item 17 Prevent Multipathing Suppress devices from VxVM's view from the vxdiskadm main menu. VxVM INFO V-5-2-1239 This operation might lead to some devices being suppressed from VxVM's view or prevent them from being multipathed by vxdmp. This operation can be reversed using the vxdiskadm command . Do you want to...
VEA Windows Client Package Installation
To install the Windows Client Package, follow this procedure 1. Install the base English package for the VEA client VRTSobgui.msi a. If the CD-ROM drive is drive D , navigate to D Windows b. Double click on VRTSobgui.msi c. Follow the instructions from the installer 2. Install the multi language pack for the VEA Client VRTSmuobg.msi a. If the CD-ROM is drive D , and, for example, you want to install the Japanese version, navigate to D ja windows. b. Double click on VRTSmuobg.msi c. Follow the...
Upgrading VxVM and the Solaris Operating System from VxVM 35 Encapsulated Root
This section explains how to upgrade VxVM if any of the following are true You are upgrading from VxVM 3.2 or earlier and your root disk is encapsulated You are upgrading from VxVM 3.5 and your root disk is encapsulated You are upgrading from VxVM 3.2 or earlier and your root disk is not encapsulated. 1. If you have not already obtained and installed a VxVM 4.0 license key, do so now. See Product Licensing on page 5 for details. Note The directory opt must exist, be writable, and must not be a...
Moving Volumes To Disk Partitions
All volumes must be moved to disk partitions. Use one of the following procedures Back up the system fully onto tape and then recover from tape. Back up each file system individually and then recover them all after creating new file systems on disk partitions. Use VxVM to move volumes incrementally onto disk partitions. Use the following instructions 1. Evacuate disks using the vxdiskadm program, VEA, or the vxevac script. You should consider the amount of target disk space required for this...
Starting the Volume IO Daemon
The volume I O daemon vxiod provides extended I O operations without blocking calling processes. Several vxiod daemons are usually started at system boot time after initial installation, and they should be running at all times. The procedure below describes how to verify that the vxiod daemons are running, and how to start them if necessary. To verify that vxiod daemons are running, enter the following command Note The vxiod daemon is a kernel thread and is not visible using the ps command. If,...
VxVM Components
The VxVM product includes a number of packages see The Packages on page 26 for details . However, VxVM installation is by component. Install the following components, using the appropriate procedure for each component VxVM The VERITAS Volume Manager software. You have the choice of using the pkgadd command for installation or you can use the VERITAS Installation Menu or the installvm script from the command line. See Check that the upgrade was successful. See Completing the Upgrade on page 89....
VEA Installation
The graphical user interface to VxVM is the VERITAS Enterprise Administrator VEA , VEA server The VEA server must be installed on a Solaris machine running VxVM 4.0. The VEA server is never installed by itself. See Installing VxVM using pkgadd on page 28 for the installation procedure that includes the VEA server packages. VEA client The VEA client is installed on a Solaris or Microsoft Windows machine that supports the Java 1.1 Runtime Environment. The VEA client can be installed as a...
VxVM and Solaris Operating System Upgrade Paths Possible Upgrade Paths for VxVM
The following table shows possible VxVM Solaris upgrade paths. Note If you are upgrading from a release earlier than VxVM 3.2, you should upgrade to VxVM 3.5 before upgrading to VxVM 4.0. You can upgrade VxVM and Solaris versions VxVM 3.1, 3.1.1, 3.2, 3.5 amp Solaris 2.6, 7, S, 9 See Upgrading VxVM and the Solaris Operating System on page 77 Upgrading the Solaris Operating System Only on page 87 Note If the upgrade_start script fails for any reason, run the upgrade_finish script to undo any...
Installing the VEA Client on Windows
The VEA client runs on Windows NT, Windows XP, Windows 2000, Windows ME, Windows 98, and Windows 95 machines. If you plan to run VEA from a Windows machine, install the optional Windows package after you have installed the VEA server on a Solaris machine. Before you install VEA on a Windows machine, you must uninstall any existing VERITAS Volume Manager Storage Administrator VMSA packages and remove the old setup.exe from that machine. Only one VEA package can be installed on a Windows machine...
Including and Excluding Disks
Declare what will be managed by VxVM and what will not. 2. Identify controllers, disks and enclosures that are to be excluded from being configured as VxVM devices by the vxdiskadm utility. 3. To exclude devices from VxVM control, create the etc vx cntrls.exclude, etc vx disks.exclude and etc vx enclr.exclude files. You can exclude one or more disks from VxVM control. exclude all disks on certain controllers from VxVM control. exclude all disks in specific enclosures from VxVM control. Note The...
Convert Existing VxVM Disk Groups to Shared Disk Groups
If you are upgrading from VxVM 3.x to VxVM 4.0 and you want to convert existing disk groups to shared disk groups, configure the shared disks as follows 1. Start the cluster on at least one node. For a two-node cluster, start the cluster on one node for a four-node cluster, start the cluster on three nodes. 2. Configure the disk groups using the following procedure. To list all disk groups, use the following command To deport disk groups to be shared, use the following command To import disk...
VMSA and VEA Coexistence
If you do not plan to use VMSA to administer other pre-VxVM 4.0 machines, then you should uninstall VMSA before installing VEA. You can later do a client-only install if you want to run the VMSA client on your machine. Note The release of VEA that ships with VxVM 4.0 is not compatible with VMSA, the previous VERITAS Volume Manager GUI. You cannot run VMSA with VxVM version 4.0. If you do not remove VMSA, the following warning appears during a reboot VERITAS VM Storage Administrator Server...
Dirty Region Logging DRL Guidelines
Dirty Region Logging DRL can speed up recovery of mirrored volumes following a system crash. When DRL is enabled, VxVM keeps track of the regions within a volume that have changed as a result of writes to a plex. VxVM maintains a bitmap and stores this information in the DCO volume. DCO Volumes are defined for and added to a volume to provide DRL. DCO volumes are independent of plexes, are ignored by plex policies, and are only used to hold the DRL information. See the VERITAS Volume Manager...
Enabling Enclosurebased Naming
Note If you used the VERITAS Installation Menu or the installvm script, you do not need to carry out the instructions in this section. Licensing, configuration of enclosure based naming and creation of a default disk group are managed by the menu installer and the installvm script. Because you are no longer required to configure VxVM disks straightaway, vxinstall no longer invokes the vxdiskadm program, so it is much simpler than in previous versions, and will cover the following three...
Installing the VEA Client on the Solaris Operating System
To install the VEA client on the Solaris machine that hosts VxVM or on other Solaris machines that can access the VxVM host 2. Mount the VERITAS Volume Manager CD-ROM. 3. Before using pkgadd to install VxVM, you will need to use the gunzip command on the packages to uncompress them. When you have done that, install the package. 4. Use the pkgadd utility to install the Solaris VEA client package pkgadd -d cdrom CD_.MAME volume_manager pkgs VRTSobgui
Download Required Patches
If the patches shown in the required list are not already installed, go to http sunsolve.Sun.com to download the patches. You need to install the appropriate DISCLAIMER Patch version and information is determined at the time of product release. For the most current patch version and information, please contact your vendor. The SUNWscpu package should be shipped as part of the OS. Solaris patches are available from Sun Patch ID Number and Required Package Note that SUNWscpu is a package and...