VxVM 2.x -> 3.0 Upgrade Workshop

1. VxVM 2.x -> 3.0 Upgrade Workshop

2. Course Objectives • Provide hands on experience of the new features of Volume Manager 3.0 • Understand how rolling upgrade is supported through diskgroup versioning • Practice the use of the JAVA interface • Appreciate the changes to the CLI • Describe the advantages and workings of the Task Monitor • Understand how layered volumes work • Experience the Online Relayout of volumes

3. Course Roadmap • Module 1: Upgrade Procedure • Module 2: JAVA Interface - vmsa • Module 3: CLI changes and Task Monitor • Module 4: Layered Volumes • Module 5:Online Relayout of Volumes

4. Module 1 Upgrade of VxVM and Rolling Upgrade Support Through Diskgroup Versioning

5. Module Objectives • Describe how to upgrade to VxVM 3.0 • Describe how disk group versioning enables diskgroups to be moved between different versions of VxVM • Determine a diskgroup version by using vxdg command

6. Upgrade of VxVm only • Add VxVM 3.0 packagepkgadd -d pathname VRTSvxvm • Using pkgadd install any or all of VRTSvmsa, VRTSvmdocs, VRTSvmman, VRTSvmdev • Reboot -r to restart VxVM using correct version of vxconfigd

7. Upgrade of VxVm and Solaris • Follow the instructions in the Installation Guide: • Essentially: • Mount VxVM CD Run upgrade_start script • Reboot to Single User Mode • Remove VxVM package • Shutdown system • Upgrade OS • Reboot system • Mount VM VxCD and pkgadd VRTSvxvm • Run upgrade_finish script • Reboot to multi-user mode • Add any further packages required (e.g. VRTSvmsa, VRTSvmman etc)

8. With Rolling Upgrade • Even though 3.0 has been installed the 2.x version of the software is always valid Diskgroup Version 2.X Shared Disks VxVM upgrade from 2.x to 3.0 VxVM 2.X

9. Diskgroup Versioning • In pervious versions of VxVM: • Importing a disk group upgraded the diskgroup’s on disk structures to match the importing version of VxVM • Makes it impossible to reimport that diskgroup on a lower version of VxVM • In VxVM 3.0: • Diskgroup import and Diskgroup upgrade processes have been separated • Upgrading a diskgroup is now an explicit operation • vxvg upgrade command is used to alter a diskgroup version

10. Version • Version of a diskgroup determines which VxVM features are allowed to operate in that diskgroup • For Example: Only version 60 diskgroups (VxVM 3.0) are allowed to make layered volumes • If a non-supported operation is attempted on the diskgroup, a message will be printed, similar to: Disk group version doesn’t support feature; see the vxdg upgrade command

11. vxdg list Command • Determines a diskgroup’s version # vxdg list rootdg Group: rootdg dgid: 983546876.1025.stoli.veritas.com import-id: 0.1 flags: version: 60 copies: ncongid=default nlog=default config: seqno=0.1046 permlen=1456 freee=1454 templen=2 loglen=220 config disk c0t1d0s2 copy 1 len=1456 state=clean online log disk c0t1d0s2 copy 1 len=220

12. Module 2 Volume Manager Storage Administrator vmsa

13. Module Objectives • Introduce the new JAVA GUI - vmsa • Describe the installation and configuration of vmsa • Describe the basic navigation of vmsa • Provide hands-on experience of the use of vmsa

14. Pre-installation: Requirements • The following software must be installed and running : • VERITAS Volume Manager 2.5 or higher • Volume Manager must be installed and initialized (via vxinstall) before using the Storage Administrator • Solaris 2.5 or higher • Confirm minimum space requirements for each package • VRTSvmsa (Volume Manager Storage Administrator, server and client) • 21m • VRTSadoc (online documentation) • 3m • vmsa.zip (Volume Manager Storage Sdministrator client- Windows) • 11m

15. Pre-installation: Requirements • If used, remove any existing VRTSvmsa V1 package • pkgrm VRTSvmsa(This is because the names of the programs have changed and do not get overwritten by the installation of the new package)

16. Installing the Storage Administrator Server • Install the Volume Manager Storage Administrator • pkgadd -d path • Path: directory that contains the VRTSvmsa package, For example: #pkgadd -d /cdrom/cdrom0/pkg VRTSvmsa • Install the server by answering y(es) at the appropriate prompt • Indicate where the web server package should be installed (optional) • Set the VMSAHOME environment variable and update the PATH variable: #VMSAHOME=/opt/VRTSvmsa #export VMSAHOME #PATH=$PATH:$VMSAHOME/bin #export PATH

17. Install the Storage Administrator Client (Windows 95/NT) • Log on as administrator • Insert CD-ROM containing the software • Locate the file vmsa.zip in the win32 directory • Unzip vmsa.zip to a temporary directory • Use the setup.exe program to perform the installation

18. Setting Up Security (Optional) • By default : only root can run Volume Manager Storage Administrator • To set up a list of users with permissions to use the Storage Administrator: • Add a group named vrtsadm to the group file (/etc/group) or NIS group table • Include user name of any user including root for the Storage Administrator; for example: vrtsadm::999:root,joe,bill

19. Security: Monitoring Access • Monitor access to the Storage Administrator by reviewing contents of the access log file • By default, the access log file is: /var/opt/vmsa/logs/access • Example entries: Fri jan 23 10:22:17 PST 1998: user xyz login success Fri jan 23 10:59:52 PST 1998: user xyz login fail with error “user password invalid”

20. Starting the Storage Administrator Server • To start the server manually: • Log on as superuser (root) and start the server $VMSAHOME/bin/vmsa_server & • Check the server.log file for information. If the server started successfully the file will contain: rebound //host:1099/vrts.remote.vrtsserver • vmsa_server -q will report whether server is running

21. Starting the Storage Administrator: As an Application • Unix • Local UNIX machine, type: #DISPLAY=`uname -n`:0.0; export DISPLAY #xhost + `uname -n` #vxvm & • Remote UNIX machine, type: #vxvm machine_name • Make sure the session initialization dialog contains the appropriate server name • Windows NT/Windows 95 • To administer remote UNIX machine, choose: • Start > Programs > VERITAS Volume Manager Storage Administrator • Make sure the session initialization dialog contains the remote server name

22. Session Initiation Dialog

23. Running the Storage Administrator in Read-only Mode • Useful for monitoring or browsing purposes • Objects can be viewed without being modified • Enable the mode via the properties file: /Opt/VRTSvmsa/vxvm/properties • To start in read-only mode: Vrts.server.readonly = true • To restore to full operation mode: Vrts.server.readonly = false

24. VMSA Components Menu Bar Toolbar Grid Object Tree Status Area Command Launcher

25. Disk and Disk Group Information All disk groups on system All disks in a disk group All disks on system Disks in free disk space pool Disk not under VM control

26. Select Disk

27. Create New Disk Group

28. Disk Group Operations

29. Select Disk Group for Volume Or Command Launcher

30. Create Concatenated Volume

31. Put Volume on Specific Disk

32. Display Volume/Mirror Layout and Properties

33. Volume Layout with Mirror

34. Volume Properties

35. Module 3 CLI Changes and Task Monitor

36. Module Objectives • To outline changes to the CLI • Describe the functions of the Task Monitor • Describe the type of task information that is displayed • Explain how to use the vxtask keywords

37. vxdisk list • vxdisk [-g diskgroup] [-o alldgs] [-qs] list [disk…] • # vxdisk -o alldgs list • DEVICE TYPE DISK GROUP STATUS • c0t0d0s2 sliced rootdisk rootdg online • c1t1d0s2 sliced - (datadg) online • c1t2d0s2 sliced - (datadg) online • c1t3d0s2 sliced - (datadg) online • c1t4d0s2 sliced - (datadg) online • c1t5d0s2 sliced - (datadg) online • c1t6d0s2 sliced - (datadg) online • #

38. vxdg • vxdg destroy diskgroup • Removes a diskgroup from the system • Cannot be removed if any volumes in diskgroup are open • Only imported diskgroups can be destroyed • vxdg [-T version] init groupname [medianame =] accessname • -T option creates a diskgroup with specified version number (default is highest supported version number) • vxdg [-T version] upgrade diskgroup • upgrades a diskgroup to specified version number (default is the highest supported version number)

39. vxassist • New Keywords • remove - to remove volumes, mirrors, logs • snapabort - to remove a mirror snaphot • convert - to convert volume structure between layered and non-layered volumes (see later module) • relayout - to convert one volume structure to another (see later module) • New Options • -f option now available to force operations • -t tasktag option for specifying task identifying tag • Tag is passed to any other utilities called by vxassist • [-b] added to maxgrow and maxsize

40. vxassist • New attributes • mirror, nlog, nmirror, nraid5stripe, nstripenow take +/- parameter to indicate increase or decrease in number of stripes/mirrors for relayout operations • stripe=diskclass[,….]specifies that volumes should be striped across instances of a particular disk class(e.g. ctrl or target) • stripe-mirror-col-trigger-pt=sizestripe-mirror-col-split-trigger-pt=sizetmpsize=sizetmpalloc=storage-spec[ ,storage-spec…]used to control layered volume creation and relayout operations (see later modules)

41. vxassist • New layouts • mirror-concat • mirror-stripe • concat-mirror • stripe-mirror (see later module for details)

42. vxprint -rth • DG NAME NCONFIG NLOG MINORS GROUP-IDDM NAME DEVICE TYPE PRIVLEN PUBLEN STATEV NAME USETYPE KSTATE STATE LENGTH READPOL PREFPLEXPL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODESD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODESV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE • v vol01 fsgen ENABLED ACTIVE 3072000 SELECT vol01-03pl vol01-03 vol01 ENABLED ACTIVE 3072000 STRIPE 2/128 RWsv vol01-S01 vol01-03 vol01-L01 1 1536000 0/0 2/2 ENAv2 vol01-L01 fsgen ENABLED ACTIVE 1536000 SELECT -p2 vol01-P01 vol01-L01 ENABLED ACTIVE 1536000 CONCAT - RWs2 datadg05-02 vol01-P01 datadg05 0 1536000 0 c1t2d0 ENAp2 vol01-P02 vol01-L01 ENABLED ACTIVE 1536000 CONCAT - RWs2 datadg06-02 vol01-P02 datadg06 0 1536000 0 c1t4d0 ENAsv vol01-S02 vol01-03 vol01-L02 1 1536000 1/0 2/2 ENAv2 vol01-L02 fsgen ENABLED ACTIVE 1536000 SELECT -p2 vol01-P03 vol01-L02 ENABLED ACTIVE 1536000 CONCAT - RWs2 datadg03-02 vol01-P03 datadg03 0 1536000 0 c1t3d0 ENAp2 vol01-P04 vol01-L02 ENABLED ACTIVE 1536000 CONCAT - RWs2 datadg04-02 vol01-P04 datadg04 0 1536000 0 c1t5d0 ENA

43. Task Monitor • Ability to monitor volume recovery and restructuring operations • Allows full control of ongoing Volume Manager tasks • Lists tasks • Modifying state of tasks • pause, resume and aborting • Modifying the rate and progress of tasks (throttle)

44. Monitoring Tasks • vxtask list • vxtask Monitor • Lists all tasks running on the system in on-line summaries • All tasks are printed or if the taskid is specified, the output is limited to that taskid • Specifying -l causes a long list to be printed • Default is a short one-line list • After the task is completed the state is printed as EXITED

45. vxtask list • # vxtask list TASKID PTID TYPE/STATE PCT PROGRESS 190 RDWRBACK/R 83.22% 0/1536000/1278192 VOLSTART vol01-L01 • # • # vxtask -l list Task: 196 RUNNING (Tag: tasktest) Type: RDWRBACK Operation: VOLSTART Vol vol01-L02 Started: Tue 18 May 1999 04:44:13 PM BST Throttle: 0 Progress: 0.90% 13888 of 1536000 Blocks Work time: 1 second (01:49 remaining) • #

46. vxtask monitor • vxtask -l monitor tasktest Task: 190 RUNNING (Tag: tasktest)Type: RDWRBACKOperation: VOLSTART Vol vol01-L01Started: Tue 18 May 1999 04:41:47 PM BSTThrottle: 0Progress: 46.66% 716720 of 1536000 BlocksWork time: 1 minute, 5 seconds (01:14 remaining) Task: 190 RUNNING (Tag: tasktest)Type: RDWRBACKOperation: VOLSTART Vol vol01-L01Started: Tue 18 May 1999 04:41:47 PM BSTThrottle: 0Progress: 46.68% 716968 of 1536000 BlocksWork time: 1 minute, 5 seconds (01:14 remaining)

47. vxtask monitor • vxtask monitor tasktest 211 RDWRBACK/R 99.93% 0/1536000/1534872 VOLSTART vol01-L02 211 RDWRBACK/R 99.94% 0/1536000/1535120 VOLSTART vol01-L02 211 RDWRBACK/R 99.96% 0/1536000/1535368 VOLSTART vol01-L02 211 RDWRBACK/R 99.97% 0/1536000/1535616 VOLSTART vol01-L02 211 RDWRBACK/R 99.99% 0/1536000/1535864 VOLSTART vol01-L02 211 RDWRBACK/EXITED

48. Controlling Tasks • vxtask abort • Causes specified task to cease operation • vxtask pause • Puts a running task in the paused state, causing it to suspend operation • vxtask resume • Causes a paused task to continue operation

49. Controlling Tasks (cont) • vxtask set • Allows you to change modifiable parameters of a task • Currently only one modifiable parameter: • slow attribute • represents a throttle on the task progress • larger the slow value, slower the progress of a task • fewer system resources consumed

50. Example: Using vxtask • To trace all tasks in diskgroup foodg that are currently paused: vxtask -g foodg -p -i systart list • To list all tasks that are currently paused: vxtask -p list • To monitor all tasks with the tag myoperation: vxtask monitor myoperation • To cause all tasks tagged with recovall to exit: vxtask abort recovall