著者：东方蜘蛛 专载请注明出处，不正之处请指出，谢谢！
Veritas Volume Manager 4.1的双机安装使用installvm安装，安装时必须保证双机都在线，双机互相关系正确，网络连接正常！在安装的过程中会对两台主机同时安装！
1. 安装、配置vxvm4.1软件
# cd /cdrom/cdrom/volume_manager
# ./installvm
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
Copyright (c) 2005 VERITAS Software Corporation. All rights reserved.
VERITAS, the VERITAS Logo and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation. VERITAS and the VERITAS Logo Reg. U.S. Pat. & Tm. Off. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies.
Enter the system names separated by spaces on which to install VxVM: server1 server2
Checking system communication:
Checking OS version on server1 ......................................... .................. SunOS 5.9
Checking VRTSvxvm package ............................................ ..... ................ not installed
Verifying communication with server2 ......... ..... ..... ........... ... ............... ping successful
Attempting rsh with server2....................... .. ............................................ rsh successful
Attempting rcp with server2 ...................................................................... rcp successful
Checking OS version on server2 .............................................................. SunOS 5.9
Checking VRTSvxvm package .................................................................... not installed
Creating log directory on server2 ............................................................. Done
Logs for installvm are being created in /var/tmp/installvm523153948.
Using /usr/bin/rsh and /usr/bin/rcp to communicate with remote systems.
Initial system check completed successfully.
Press [Return] to continue: [Enter]
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
VERITAS Infrastructure package installation:
Installing VERITAS Infrastructure packages on server1:
Checking VRTScpi package ........................................................................... not installed
Checking VRTSvlic package .......................................................................... not installed
Checking file system space ...................................................... required space is available
Installing VRTScpi 4.1.0.92 on server1 ................................................................. Done
Installing VRTSvlic 3.02.005k on server1 ............................................................. Done
Installing VERITAS Infrastructure packages on server2:
Checking VRTScpi package ........................................................................... not installed
Checking VRTSvlic package .......................................................................... not installed
Checking file system space ....................................................... required space is available
Copying VRTScpi package to server2 ................................................................... Done
Installing VRTScpi 4.1.0.92 on server2 .................................................................. Done
Copying VRTSvlic.tar.gz to server2 ....................................................................... Done
Installing VRTSvlic 3.02.005k on server2 ............................................................. Done
VERITAS Infrastructure packages installed successfully.
Press [Return] to continue: [Enter]
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
installvm can install the following optional VxVM packages:
VRTSobgui VERITAS Enterprise Administrator
VRTSvmman VERITAS Volume Manager Manual Pages
VRTSvmdoc VERITAS Volume Manager Documentation
VRTSvrw VERITAS Volume Replicator Web Console
VRTSvrdoc VERITAS Volume Replicator Documentation
VRTSap VERITAS Action Provider
VRTStep VERITAS Task Provider
1) Install all of the optional packages
2) Install none of the optional packages
3) View package descriptions and select optional packages
Select the optional packages to be installed on all systems? [1-3,q,?] (1) [Enter]
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
installvm will install the following VxVM packages:
VRTSperl VERITAS Perl 5.8.0 Redistribution
VRTSob VERITAS Enterprise Administrator Service
VRTSobgui VERITAS Enterprise Administrator
VRTSvxvm VERITAS Volume Manager Binaries
VRTSvmman VERITAS Volume Manager Manual Pages
VRTSvmdoc VERITAS Volume Manager Documentation
VRTSvmpro VERITAS Volume Manager Management Services Provider
VRTSfspro VERITAS File System Management Services Provider
VRTSalloc VERITAS Volume Manager Intelligent Storage Provisioning
VRTSddlpr VERITAS Device Discovery Layer Services Provider
VRTSvrpro VERITAS Volume Replicator Client Extension and Provider for
VERITAS Enterprise Administrator
VRTSvcsvr VERITAS Cluster Server Agents for VVR
VRTSjre VERITAS Java Runtime Environment Redistribution
VRTSweb VERITAS Java Web Server
VRTSvrw VERITAS Volume Replicator Web Console
VRTSvrdoc VERITAS Volume Replicator Documentation
VRTSap VERITAS Action Provider
VRTStep VERITAS Task Provider
Press [Return] to continue: [Enter]
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
Checking system installation requirements:
Checking VxVM installation requirements on server1:
Checking VRTSperl package .. .. ..................................................................... not installed
Checking VRTSob package ..................... ....................................................... not installed
Checking VRTSobgui package ........................................................................ not installed
Checking VRTSvxvm package ......................................................................... not installed
Checking VRTSvmman package ..................................................................... not installed
Checking VRTSvmdoc package ....................................................................... not installed
Checking VRTSvmpro package ....................................................................... not installed
Checking VRTSfspro package ......................................................................... not installed
Checking VRTSalloc package .......................................................................... not installed
Checking VRTSddlpr package ......................................................................... not installed
Checking VRTSvrpro package ......................................................................... not installed
Checking VRTSvcsvr package ......................................................................... not installed
Checking VRTSjre package ............................................................................. not installed
Checking VRTSweb package ........................................................................... not installed
Checking VRTSvrw package ............................................................................ not installed
Checking VRTSvrdoc package ........................................................................ not installed
Checking VRTSap package ............................................................................. not installed
Checking VRTStep package ............................................................................ not installed
Checking VERITAS patch 115209 .................................................................... not installed
Checking VERITAS patch 115210 .................................................................... not installed
Checking for any Solaris patch issues ........................................................................ None
Checking file system space ....................................................... required space is available
Checking for any AP driver issues .............................................................................. None
Stopping VVR processes on host server1 ............................................................... Done
Checking vxsvc process .................................................................................... not running
Checking VRTSweb process ............................................................................. not running
Checking VxVM installation requirements on server2:
Checking VRTSperl package ........................................................................... not installed
Checking VRTSob package ............................................................................. not installed
Checking VRTSobgui package ........................................................................ not installed
Checking VRTSvxvm package ......................................................................... not installed
Checking VRTSvmman package ..................................................................... not installed
Checking VRTSvmdoc package ...................................................................... not installed
Checking VRTSvmpro package ....................................................................... not installed
Checking VRTSfspro package ......................................................................... not installed
Checking VRTSalloc package .......................................................................... not installed
Checking VRTSddlpr package ......................................................................... not installed
Checking VRTSvrpro package ......................................................................... not installed
Checking VRTSvcsvr package ......................................................................... not installed
Checking VRTSjre package ............................................................................. not installed
Checking VRTSweb package ........................................................................... not installed
Checking VRTSvrw package ............................................................................ not installed
Checking VRTSvrdoc package ........................................................................ not installed
Checking VRTSap package ............................................................................. not installed
Checking VRTStep package ............................................................................ not installed
Checking VERITAS patch 115209 ................................................................... not installed
Checking VERITAS patch 115210 ................................................................... not installed
Checking for any Solaris patch issues ....................................................................... None
Checking file system space ...................................................... required space is available
Checking for any AP driver issues .............................................................................. None
Stopping VVR processes on host server2 ............................................................... Done
Checking vxsvc process .................................................................................... not running
Checking VRTSweb process ............................................................................. not running
Installation requirement checks completed successfully.
Press [Return] to continue: [Enter]
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
VxVM can be installed on systems consecutively or simultaneously. Installing on systems consecutively takes more time but allows for better error handling.
Would you like to install Volume Manager on all systems simultaneously? [y,n,q,?] (y) [Enter]
Installing Volume Manager 4.1 on all systems simultaneously:
Copying VRTSperl.tar.gz to server2 ................................................... Done 1 of 60 steps
Installing VRTSperl 4.0.12 on server1 ................................................ Done 2 of 60 steps
Installing VRTSperl 4.0.12 on server2 ................................................ Done 3 of 60 steps
Copying VRTSob.tar.gz to server2 .................................................... Done 4 of 60 steps
Installing VRTSob 3.2.514.0 on server1 ............................................ Done 5 of 60 steps
Adding patch 115209-16 on server1 .................................................. Done 6 of 60 steps
Installing VRTSob 3.2.514.0 on server2 ............................................ Done 7 of 60 steps
Copying 115209-16.tar.gz to server2 ................................................. Done 8 of 60 steps
Installing VRTSobgui 3.2.514.0 on server1 ........................................ Done 9 of 60 steps
Adding patch 115210-16 on server1 ................................................ Done 10 of 60 steps
Adding patch 115209-16 on server2 ................................................ Done 11 of 60 steps
Copying VRTSobgui.tar.gz to server2 .............................................. Done 12 of 60 steps
Installing VRTSobgui 3.2.514.0 on server2 ...................................... Done 13 of 60 steps
Copying 115210-16.tar.gz to server2 ............................................... Done 14 of 60 steps
Installing VRTSvxvm 4.1 on server1 ................................................ Done 15 of 60 steps
Installing VRTSvmman 4.1 on server1 ............................................. Done 16 of 60 steps
Installing VRTSvmdoc 4.1 on server1 .............................................. Done 17 of 60 steps
Installing VRTSvmpro 4.1 on server1 .............................................. Done 18 of 60 steps
Adding patch 115210-16 on server2 ................................................ Done 19 of 60 steps
Installing VRTSfspro 4.1 on server1 ................................................ Done 20 of 60 steps
Copying VRTSvxvm.tar.gz to server2 .............................................. Done 21 of 60 steps
Installing VRTSalloc 4.1 on server1 ................................................. Done 22 of 60 steps
Installing VRTSddlpr 4.1 on server1 ................................................ Done 23 of 60 steps
Installing VRTSvrpro 4.1 on server1 ................................................ Done 24 of 60 steps
Installing VRTSvcsvr 4.1 on server1 ................................................ Done 25 of 60 steps
Installing VRTSjre 1.4 on server1 .................................................... Done 26 of 60 steps
Installing VRTSweb 4.2 on server1 .................................................. Done 27 of 60 steps
Installing VRTSvrw 4.1 on server1 ................................................... Done 28 of 60 steps
Installing VRTSvrdoc 4.1 on server1 ................................................ Done 29 of 60 steps
Installing VRTSap 2.00.023 on server1 ........................................... Done 30 of 60 steps
Installing VRTStep 1.20.028 on server1 ........................................... Done 31 of 60 steps
Installing VRTSvxvm 4.1 on server2 ................................................ Done 32 of 60 steps
Copying VRTSvmman.tar.gz to server2 ........................................... Done 33 of 60 steps
Installing VRTSvmman 4.1 on server2 ............................................. Done 34 of 60 steps
Copying VRTSvmdoc.tar.gz to server2 ............................................ Done 35 of 60 steps
Installing VRTSvmdoc 4.1 on server2 .............................................. Done 36 of 60 steps
Copying VRTSvmpro.tar.gz to server2 ............................................ Done 37 of 60 steps
Installing VRTSvmpro 4.1 on server2 .............................................. Done 38 of 60 steps
Copying VRTSfspro.tar.gz to server2 .............................................. Done 39 of 60 steps
Installing VRTSfspro 4.1 on server2 ................................................ Done 40 of 60 steps
Copying VRTSalloc.tar.gz to server2 ............................................... Done 41 of 60 steps
Installing VRTSalloc 4.1 on server2 ................................................. Done 42 of 60 steps
Copying VRTSddlpr.tar.gz to server2 ............................................... Done 43 of 60 steps
Installing VRTSddlpr 4.1 on server2 ................................................ Done 44 of 60 steps
Copying VRTSvrpro.tar.gz to server2 .............................................. Done 45 of 60 steps
Installing VRTSvrpro 4.1 on server2 ................................................ Done 46 of 60 steps
Copying VRTSvcsvr.tar.gz to server2 .............................................. Done 47 of 60 steps
Installing VRTSvcsvr 4.1 on server2 ................................................ Done 48 of 60 steps
Copying VRTSjre.tar.gz to server2 .................................................. Done 49 of 60 steps
Installing VRTSjre 1.4 on server2 .................................................... Done 50 of 60 steps
Copying VRTSweb.tar.gz to server2 ................................................ Done 51 of 60 steps
Installing VRTSweb 4.2 on server2 .................................................. Done 52 of 60 steps
Copying VRTSvrw.tar.gz to server2 ................................................. Done 53 of 60 steps
Installing VRTSvrw 4.1 on server2 ................................................... Done 54 of 60 steps
Copying VRTSvrdoc.tar.gz to server2 .............................................. Done 55 of 60 steps
Installing VRTSvrdoc 4.1 on server2 ................................................ Done 56 of 60 steps
Copying VRTSap.tar.gz to server2 .................................................. Done 57 of 60 steps
Installing VRTSap 2.00.023 on server2 ........................................... Done 58 of 60 steps
Copying VRTStep.tar.gz to server2 .................................................. Done 59 of 60 steps
Installing VRTStep 1.20.028 on server2 ........................................... Done 60 of 60 steps
Volume Manager installation completed successfully.
Press [Return] to continue: [Enter]
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
Each system requires a VxVM product license before installation. License keys for additional product features should also be added at this time.
Some license keys are node locked and are unique per system. Other license keys, such as demo keys and site license keys, are registered on all systems and must be entered on the first system.
VxVM Licensing Verification:
Checking VxVM license key on server1 ....................................................... not licensed
Enter a VxVM license key for server1: [?] 8EPU-OPBU-NNBP-8O4O-4UPP-PCPZ-C6PN-P
Registering VERITAS Volume Manager DEMO key on server1
Do you want to enter another license key for server1? [y,n,q,?] (n) [Enter]
Registering 8EPU-OPBU-NNBP-8O4O-4UPP-PCPZ-C6PN-P on server2
Checking VxVM license key on server2 ..................................... Volume Manager Demo
Do you want to enter another license key for server2? [y,n,q,?] (n) y
Enter a VxVM license key for server2:8EPU-OPBU-NNBP-8O4O-4UPP-PCPZ-C6PN-P
Registering VERITAS Volume Manager DEMO key on server2 Duplicate License key detected
Do you want to enter another license key for server2? [y,n,q,?] (n) [Enter]
VxVM licensing completed successfully.
Press [Return] to continue: [Enter]
VERITAS VOLUME MANAGER 4.1 INSTALLATION PROGRAM
It is optional to configure VxVM now. If you choose to configure VxVM later, you can either do so manually or run the installvm -configure command.
Are you ready to configure VxVM? [y,n,q] (y) y
Installation of Volume Manager 4.1 has completed successfully.
The installation summary is saved at:
/opt/VRTS/install/logs/installvm523153948.summary
The installvm log is saved at:
/opt/VRTS/install/logs/installvm523153948.log
Volume Manager cannot be started without configuration.
Run installvm -configure when you are ready to configure VxVM.
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
Copyright (c) 2005 VERITAS Software Corporation. All rights reserved.
VERITAS, the VERITAS Logo and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation. VERITAS and the VERITAS Logo Reg. U.S. Pat. & Tm. Off. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies.
Enter the system names separated by spaces on which to configure VxVM: server1 server2
Checking system communication:
Checking OS version on server1 .................................................................... SunOS 5.9
Checking VRTSvxvm package ............................................................ version 4.1 installed
Verifying communication with server2 ..................................................... ping successful
Attempting rsh with server2 ..................................................................... rsh successful
Attempting rcp with server2 ...................................................................... rcp successful
Checking OS version on server2 .................................................................... SunOS 5.9
Checking VRTSvxvm package ............................................................ version 4.1 installed
Creating log directory on server2 ............................................................................ Done
Logs for installvm are being created in /var/tmp/installvm523164354.
Using /usr/bin/rsh and /usr/bin/rcp to communicate with remote systems.
Initial system check completed successfully.
Press [Return] to continue: [Enter]
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
Each system requires a VxVM product license before installation. License keys for additional product features should also be added at this time.
Some license keys are node locked and are unique per system. Other license keys, such as demo keys and site license keys, are registered on all systems and must be entered on the first system.
VxVM Licensing Verification:
Checking VxVM license key on server1 ..................................... Volume Manager Demo
Checking VxVM license key on server2 ..................................... Volume Manager Demo
VxVM licensing verified successfully.
Press [Return] to continue: [Enter]
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
The enclosure-based naming scheme is a feature of Volume Manager. It allows one to reference disks using a symbolic name that is more meaningful than the operating system's normal device access name. This symbolic name is typically derived from the array name.
Do you want to set up the enclosure-based naming scheme? [y,n,q,?] (n) [Enter]
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
Configuring Volume Manager:
Volume Manager configured successfully.
Press [Return] to continue: [Enter]
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
Note: The vxconfigd daemon will be started, which can take a while depending upon the hardware configuration.
Disabling enclosure-based naming on server1 ....................................................... Done
Starting vxconfigd for VxVM on server1 ............................................................... Started
Disabling enclosure-based naming on server2 ....................................................... Done
Starting vxconfigd for VxVM on server2 ............................................................... Started
Volume Manager default disk group configuration:
Many Volume Manager commands affect the contents or configuration of a disk group. Such commands require that the user specify a disk group. This is accomplished by using the -g option of a command or setting the VXVM_DEFAULTDG environment variable. An alternative to these two methods is to configure the default disk group of a system.
Do you want to set up the default disk group for each system? [y,n,q,?] (y) [Enter]
Will you specify one disk group name for all eligible systems? [y,n,q,?] (y) [Enter]
Specify a default disk group for all systems or type 'l' to display a listing of existing disk group(s). [?] y
You have decided to specify the default disk groups as follows:
Host: server1 .............................................................................................. Disk group: y
Host: server2 .............................................................................................. Disk group: y
Note: If 'nodg' is displayed, then the host will be configured to have no default disk group.
Is this correct? [y,n,q] (y) [Enter]
Volume Manager default disk group setup and daemon startup
Setting default disk group to y on server1 ............................................................... Done
Starting vxcached on server1 ............................................................................... Started
Setting default disk group to y on server2 ............................................................... Done
Starting vxcached on server2 ............................................................................... Started
Volume Manager was started successfully.
Press [Return] to continue: [Enter]
VERITAS VOLUME MANAGER 4.1 CONFIGURATION PROGRAM
Configuration of Volume Manager 4.1 has completed successfully.
The configuration summary is saved at:
/opt/VRTS/install/logs/installvm523164354.summary
The installvm log is saved at:
/opt/VRTS/install/logs/installvm523164354.log
2. 封装系统盘
用下面命令封装两个节点的系统盘，操作系统会自动连续重启两次，中间不要作任何操作，最后会启动到cluster下。
# scvxinstall -e
Disabling DMP.
scvxinstall: /dev/vx/dmp is not set up correctly.
scvxinstall: Warning: Unable to disable DMP, but installation will continue...
scvxinstall: /dev/vx/rdmp is not set up correctly.
scvxinstall: Warning: Unable to disable DMP, but installation will continue...
The Volume Manager package installation is already complete.
Discovered and using the predefined vxio number 286...
Volume Manager installation is complete.
Verifying encapsulation requirements.
The Volume Manager root disk encapsulation step will begin in 20 seconds.
Type Ctrl-C to abort ....................
Arranging for Volume Manager encapsulation of the root disk.
Reinitialized the volboot file...
The setup to encapsulate rootdisk is complete...
Updating /global/.devices entry in /etc/vfstab.
This node will be re-booted in 20 seconds.
Type Ctrl-C to abort ....................
用df -k以及more /etc/vfstab文件查看系统的所挂接的设备是否由cxtxdxsx 替换为volume。
3. 调整磁盘管理参数(所有节点都需安装)
操作系统已经实现DMP的功能，关闭Volume Manager中的此功能，否则可能会出问题。
以root用户登录，关闭Volume Manager中的DMP功能。
# vxdiskadm
下面是交互的安装过程，需要选择的参数如下：
Volume Manager Support Operations
Menu: VolumeManager/Disk
1 Add or initialize one or more disks
2 Encapsulate one or more disks
3 Remove a disk
4 Remove a disk for replacement
5 Replace a failed or removed disk
6 Mirror volumes on a disk
7 Move volumes from a disk
8 Enable access to (import) a disk group
9 Remove access to (deport) a disk group
10 Enable (online) a disk device
11 Disable (offline) a disk device
12 Mark a disk as a spare for a disk group
13 Turn off the spare flag on a disk
14 Unrelocate subdisks back to a disk
15 Exclude a disk from hot-relocation use
16 Make a disk available for hot-relocation use
17 Prevent multipathing/Suppress devices from VxVM's view
18 Allow multipathing/Unsuppress devices from VxVM's view
19 List currently suppressed/non-multipathed devices
20 Change the disk naming scheme
21 Get the newly connected/zoned disks in VxVM view
22 Change/Display the default disk layouts
23 Mark a disk as allocator-reserved for a disk group
24 Turn off the allocator-reserved flag on a disk
list List disk information
? Display help about menu
?? Display help about the menuing system
q Exit from menus
Select an operation to perform: 17
Exclude Devices
Menu: VolumeManager/Disk/ExcludeDevices
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 continue ? [y,n,q,?] (default: y) [Enter]
Volume Manager Device Operations
Menu: VolumeManager/Disk/ExcludeDevices
1 Suppress all paths through a controller from VxVM's view
2 Suppress a path from VxVM's view
3 Suppress disks from VxVM's view by specifying a VID:PID combination
4 Suppress all but one paths to a disk
5 Prevent multipathing of all disks on a controller by VxVM
6 Prevent multipathing of a disk by VxVM
7 Prevent multipathing of disks by specifying a VID:PID combination
8 List currently suppressed/non-multipathed devices
? Display help about menu
?? Display help about the menuing system
q Exit from menus
Select an operation to perform: 5
Exclude controllers from DMP
Menu: VolumeManager/Disk/ExcludeDevices/CTLR-DMP
Use this operation to exclude all disks on a controller from being multipathed by vxdmp.
As a result of this operation, all disks having a path through the specified controller will be claimed in the OTHER_DISKS category and hence, not multipathed by vxdmp. This operation can be reversed using the vxdiskadm command.
VxVM INFO V-5-2-1263
You can specify a controller name at the prompt. A controller name is of the form c#, example c3, c11 etc. Enter 'all' to exclude all paths on all the controllers on the host. To see the list of controllers on the system, type 'list'.
Enter a controller name [,all,list,list-exclude,q,?] all
VxVM INFO V-5-2-1182 No disk will be multipathed by vxdmp as a result of this operation !
Continue operation? [y,n,q,?] (default: n) y
VxVM NOTICE V-5-2-1241 This operation will take effect only after a reboot.
Hit RETURN to continue.
Volume Manager Device Operations
Menu: VolumeManager/Disk/ExcludeDevices
1 Suppress all paths through a controller from VxVM's view
2 Suppress a path from VxVM's view
3 Suppress disks from VxVM's view by specifying a VID:PID combination
4 Suppress all but one paths to a disk
5 Prevent multipathing of all disks on a controller by VxVM
6 Prevent multipathing of a disk by VxVM
7 Prevent multipathing of disks by specifying a VID:PID combination
8 List currently suppressed/non-multipathed devices
? Display help about menu
?? Display help about the menuing system
q Exit from menus
Select an operation to perform: q
Volume Manager Support Operations
Menu: VolumeManager/Disk
1 Add or initialize one or more disks
2 Encapsulate one or more disks
3 Remove a disk
4 Remove a disk for replacement
5 Replace a failed or removed disk
6 Mirror volumes on a disk
7 Move volumes from a disk
8 Enable access to (import) a disk group
9 Remove access to (deport) a disk group
10 Enable (online) a disk device
11 Disable (offline) a disk device
12 Mark a disk as a spare for a disk group
13 Turn off the spare flag on a disk
14 Unrelocate subdisks back to a disk
15 Exclude a disk from hot-relocation use
16 Make a disk available for hot-relocation use
17 Prevent multipathing/Suppress devices from VxVM's view
18 Allow multipathing/Unsuppress devices from VxVM's view
19 List currently suppressed/non-multipathed devices
20 Change the disk naming scheme
21 Get the newly connected/zoned disks in VxVM view
22 Change/Display the default disk layouts
23 Mark a disk as allocator-reserved for a disk group
24 Turn off the allocator-reserved flag on a disk
list List disk information
? Display help about menu
?? Display help about the menuing system
q Exit from menus
Select an operation to perform: q
VxVM vxdiskadm NOTICE V-5-2-1231
The system must be shut down and rebooted for the device suppression/
unsuppression operations you have performed to take effect. To shutdown your
system, cd to / and type
shutdown -g0 -y -i6
Do not attempt to use the device suppression/unsuppression operations
again before the system is rebooted.
重启系统，使修改的参数生效。
# sync
# sync
# shutdown -g0 -y -i6(分别重启)
4.修改vxvm磁盘默认类型，vxvm默认磁盘类型是cds，为了和rootdg中被封装的系统盘统一，可以将其修改为sliced,此步为可选。
1). Start the 'vxdiskadm' utility.
2). Select option 22 "Change/Display the default disk layouts."
3). Select option 1 "Change/View preferences for use when initializing new disks."
4). Select option 1 "Store preferred format when initializing new disks."
5). Enter the desired format [cdsdisk, sliced ,simple,q,?] sliced
5. 安装vxvm4.1的补丁(所有节点都需安装)
将EIS光盘放入光驱
# cd /cdrom/cdrom0/sun2/patch/veritas/volume_manager/4.1/9
# unpack-patches
Are you ready to unpack patches into /tmp/9? [y/n]: y
# cd /tmp/9; ./install_patches
装完后需要重启。
6.系统盘镜像
为了提高系统的可靠性，保证一旦操作系统所在磁盘出现故障时系统能够正常、连续运行，需要对系统盘进行镜像，两块本地硬盘互为镜像，下面给出系统盘镜像的方法。
说明：为了描述的方便，对系统盘和镜像盘进行如下约定：系统盘指在做镜像前安装操作系统的磁盘，镜像盘指对系统盘做镜像的磁盘。根据前面的规划，c1t0d0用来安装操作系统，c1t1d0用来作系统盘镜像。
初始化镜像盘c1t1d0。
# vxdctl enable
# vxdiskunsetup -C c1t1d0
执行该命令后系统可能会报错，不需处理。
# vxdisksetup -i c1t1d0
# vxdisk list
查看所有本地硬盘是否online。
把镜像盘加入rootdg。
# vxdg -g rootdg adddisk rootdg_1_mirror=c1t1d0
# vxmirror rootdg_1 rootdg_1_mirror &
上面命令操作完后，vxvm会对这个磁盘上的各卷分别做同步。
用下面命令对同步的进度做观察：
# vxtask list
如果想查看更详细的信息，请用如下命令查看：
# vxprint -ht
将会有如下显示：
Disk group: rootdg
DG NAME NCONFIG NLOG MINORS GROUP-ID
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME NVOLUME KSTATE STATE
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
dg rootdg default default 50 1148374300.9.qzguoku1
dm rootdg_1 c1t0d0s2 auto 40703 286657920 -
dm rootdg_1_mirror c1t1d0s2 auto 40703 286657920 -
v rootdg_16vol - ENABLED ACTIVE 2116608 ROUND - fsgen
pl rootdg_16vol-01 rootdg_16vol ENABLED ACTIVE 2116608 CONCAT - RW
sd rootdg_1-03 rootdg_16vol-01 rootdg_1 279331199 2116608 0 c1t0d0 ENA
pl rootdg_16vol-02 rootdg_16vol ENABLED ACTIVE 2116608 CONCAT - RW
sd rootdg_1_mirror-03 rootdg_16vol-02 rootdg_1_mirror 279331200 2116608 0 c1t1d0 ENA
v rootvol - ENABLED ACTIVE 245770752 ROUND - root
pl rootvol-01 rootvol ENABLED ACTIVE 245770752 CONCAT - RW
sd rootdg_1-02 rootvol-01 rootdg_1 33560447 245770752 0 c1t0d0 ENA
pl rootvol-02 rootvol ENABLED ACTIVE 245770752 CONCAT - RW
sd rootdg_1_mirror-02 rootvol-02 rootdg_1_mirror 33560448 245770752 0 c1t1d0 ENA
v swapvol - ENABLED ACTIVE 33560448 ROUND - swap
pl swapvol-01 swapvol ENABLED ACTIVE 33560448 CONCAT - RW
sd rootdg_1-B0 swapvol-01 rootdg_1 286657919 1 0 c1t0d0 ENA
sd rootdg_1-01 swapvol-01 rootdg_1 0 33560447 1 c1t0d0 ENA
pl swapvol-02 swapvol ENABLED ACTIVE 33560448 CONCAT - RW
sd rootdg_1_mirror-01 swapvol-02 rootdg_1_mirror 0 33560448 0 c1t1d0 ENA
如果有以上显示，则说明镜像成功。
另外一个节点的镜像操作同上。
阅读(4994) | 评论(0) | 转发(1) |
