Dynamic Root Disk October 2011 http://www.hp.com/go/DRD ©2011 Development Company, Company, L.P. L.P.
Agenda • DRD overview • DRD use models – Recovery – Maintenance – Provisioning/Rehosting – Update • DRD status & sync • Real-life examples • Wrap-up
DRD is supported on 11i v2 and v3; the orange lightning bolt on future slides indicates areas of increased feature support on 11i v3 DRD overview Mission/benefits Significantly reduce the downtime needed to perform HP-UX software maintenance Reduce the downtime required for recovery from administrative errors Perform software update work during normal business hours, or whenever convenient Provision systems quickly and efficiently Simplify testing 3
DRD use models
DRD use case Recovery clone Active 5 1. Original system image is active 2. Create a clone of the original system image (drd clone) 3. When clone completes, two copies of system image exist (drd status) 4.
DRD use case Maintenance (slide 1 of 3) clone Active 6 1. Original system image is active 2. Create a clone of the original system image (drd clone) 3.
DRD use case Maintenance (slide 2 of 3) Apply patches & products sync Active 7 1. Original system image is active 2. Create a clone of the original system image (drd clone) 3. When complete, two copies of system image exist (drd status) 4. Modify inactive image to reach desired state – install patches & products (drd runcmd swinstall) 5. When modification completes, have an unmodified original image and a modified clone 6.
DRD use case Maintenance (slide 3 of 3) Apply patches & products Modified clone Active 8 1. Original system image is active 2. Create a clone of the original system image (drd clone) 3. When complete, two copies of system image exist (drd status) 4. Modify inactive image to reach desired state – install patches & products (drd runcmd swinstall) 5. When modification completes, have an unmodified original image and a modified clone 6.
DRD use case High Availability with DRD and MirrorDisk/UX (slide 1 of 3) clone Active 9 1. Original mirrored system image is active 2. Create mirrored clone of the original system image (drd clone) 3.
DRD use case High Availability with DRD and MirrorDisk/UX (slide 2 of 3) Apply patches & products sync Active 10 Modified clone w/patches 1. Original mirrored system image is active 2. Create mirrored clone of the original system image (drd clone) 3. When complete, four copies of system image exist (drd status) 4. Patch inactive image (drd runcmd swinstall) 5. When modification completes, have an unmodified original image and a modified clone 6.
DRD use case High Availability with DRD and MirrorDisk/UX (slide 3 of 3) Modified clone w/patches Active 11 1. Original mirrored system image is active 2. Create mirrored clone of the original system image (drd clone) 3. When complete, four copies of system image exist (drd status) 4. Patch inactive image (drd runcmd swinstall) 5. When modification completes, have an unmodified original image and a modified clone 6.
DRD Customer use models High Availability with DRD and MirrorDisk/UX Requires 4 LUNs Requires a MirrorDisk/UX license Enables fast mirrored recovery Easy to implement drd clone –t/dev/dsk/c3t15d0 –x mirror_disk=/dev/dsk/c4t15d0 Provides protection against both hardware and software failures 12
DRD use case Updating from HP-UX 11i v3 0903 to HP-UX 11i v3 1103 (slide 1 of 3) HP-UX 11i v3 0903 HP-UX 11i v3 0903 clone Active 13 1. Original system image is active 2. Create a clone of the original system image (drd clone) 3.
DRD use case Updating from HP-UX 11i v3 0903 to HP-UX 11i v3 1103 (slide 2 of 3) 1. Original system image is active 2. Create a clone of the original system image (drd clone) 3. When complete, two copies of system image exist (drd status) 4. Update the inactive image to HP-UX 11i v3 March 2009 or later (1103 or March 2011 in this case) (drd runcmd update-ux) 5.
DRD use case Updating from HP-UX 11i v3 0903 to HP-UX 11i v3 1103 (slide 3 of 3) Patches 1. Original system image is active 2. Create a clone of the original system image (drd clone) 3. When complete, two copies of system image exist (drd status) 4. Update the inactive image to HP-UX 11i v3 March 2009 or later (1103 or March 2011 in this case) (drd runcmd update-ux) 5. When modification completes, have an original image with HP-UX 11i v3 0903, and a modified clone with HP-UX 11i v3 1103 6.
DRD use case Updating from HP-UX 11i v2 to HP-UX 11i v3 1103 (slide 1 of 4) HP-UX 11i v2 Active 16 HP-UX 11i v2 clone Modified clone 1. Create a clone of the original system image (drd clone) 2. Run update-ux in preview mode on the active disk (update-ux -p) 3. Adjust file system sizes on the clone as needed (www.hp.
DRD use case Updating from HP-UX 11i v2 to HP-UX 11i v3 1103 (slide 2 of 4) HP-UX 11i v3 1103 update HP-UX 11i v2 0712 HP-UX 11i v3 1103 Modified clone Active 17 1. Create a clone of the original system image (drd clone) 2. Run update-ux in preview mode on the active disk (update-ux -p) 3. Adjust file system sizes on the clone as needed (www.hp.com/go/drd-docs) 4. Activate the clone & boot when ready (drd activate) 5. Update the active image to HP-UX 11i v3 1103 (update-ux) 6.
DRD use case Updating from HP-UX 11i v2 to HP-UX 11i v3 1103 (slide 3 of 4) SWA Report 1. Create a clone of the original system image (drd clone) 2. Run update-ux in preview mode on the active disk (update-ux -p) 3. Adjust file system sizes on the clone as needed (www.hp.com/go/drd-docs) 4. Activate the clone & boot when ready (drd activate) 5. Update the active image to HP-UX 11i v3 1103 (update-ux) 6.
DRD use case Updating from HP-UX 11i v2 to HP-UX 11i v3 1103 (slide 4 of 4) Patches 1. Create a clone of the original system image (drd clone) 2. Run update-ux in preview mode on the active disk (update-ux -p) 3. Adjust file system sizes on the clone as needed (www.hp.com/go/drd-docs) 4. Activate the clone & boot when ready (drd activate) 5. Update the active image to HP-UX 11i v3 1103 (update-ux) 6.
DRD use case Rehosting – Provisioning (blade example, slide 1 of 2) Original system image is the active image 2. Create clone of the original system image (drd clone) 3. When clone completes, two copies of system image exist (drd status) 4. Rehost the clone to be BL6: 1. BL6 BL2 a. Create a system information file b. Copy the system info file to the EFI partition of the clone (drd rehost) sys_info_BL6 SYSINFO.
DRD use case Rehosting – Provisioning (blade example, slide 2 of 2) Original system image is the active image 2. Create clone of the original system image (drd clone) 3. When clone completes, two copies of system image exist (drd status) 4. Rehost the clone to be BL6: 1. BL6 BL2 a. Create a system information file b. Copy the system info file to the EFI partition of the clone (drd rehost) 5. 6. sys_info_BL6 SYSINFO.TXT 7.
Rehosting: Is • Provided by sysinfo file management: − • Ability to change hostname, IP @, network cfg Provided by 11i v3 storage agility: − Persistence of agile device files • • Provided by 11i v3 LVM − 22 E.g.
Rehosting: Is not • Additional software is not installed by “drd rehost”: − − • For 11iv2, do not get − − 23 Use “drd runcmd swinstall“ for all drivers needed for target before rehost Use “drd runcmd mk_kernel to configure all drivers needed for target into kernel Storage agility LVM Boot resiliency 23
Rehosting: Additional information Rehosting can be done between VMs, blades and even different systems on 11i v3 – similar systems will be more straightforward, and different systems will require more manual work • You may need to do kernel work on the target system for different systems, including different types of blades.
DRD use case Maintaining a mixed 11i v2/v3 VM environment (slide 1 of 2) Install VM Host, VM1 and VM2 via Ignite 2. VM3 needs to be added 3. On host, setup resources: 1. a. 11i v3 b. 4. 11i v2 On VM2, create and rehost the new boot disk: a. VM Host VM1 VM2 b. 11i v3 sys_info_vm3 clone VM3 11i v3 SYSINFO.TXT 25 Add disk to VM2 Create VM3 with just a network interface c. d.
DRD use case Maintaining a mixed 11i v2/v3 VM environment (slide 2 of 2) Install VM Host, VM1 and VM2 via Ignite 2. VM3 needs to be added 3. On host, setup resources: 1. a. 11i v3 b. 4. 11i v2 On VM2, create and rehost the new boot disk: a. VM Host VM1 VM2 b. 11i v3 sys_info_vm3 c. d. VM3 11i v3 26 5.
DRD Status & DRD Sync
DRD status ======= 9/23/11 22:09:00 MDT BEGIN Displaying DRD Clone Image Information (user=root) (jobid=drdtest10) * Clone Disk: /dev/disk/disk8 * Clone EFI Partition: AUTO file present, Boot loader present * Clone Rehost Status: SYSINFO.TXT not present * Clone Creation Date: 10/24/10 16:41:56 MDT * Last Sync Date: 10/25/10 14:26:16 MDT * Clone Mirror Disk: /dev/disk/disk10 * Mirror EFI Partition: AUTO file present, Boot loader present * Mirror Rehost Status: SYSINFO.
DRD sync Without DRD Sync 1. A system administrator creates a DRD clone on a Thursday 2. The administrator applies a collection of software changes to the clone on Friday using the drd runcmd command 3. On Friday, several log files are updated on the booted system 4.
File 1 File 1 File 2 File 2 File 3 File 3 File 4 File 4 File 4 File 4 File 4 File 4 File 5 File 5 File 5 File 5 File 5 File 5 File 1 File 1.2 File 2 File 2 File 3 File 3 File 4 File 4 File 4 File 4 File 5 File 5 File 5 File 5 Inactive Image Active Image DRD sync File 1.1 File 1.1 File 2 File 2 File 3.1 File 3.1 ♠ File 1.1 File 2 File 3.2 File 1.1 File 2 ♥ File 3.2 ♠ File 1.2 File 1.2 File 2 File 3.1 ♥ ♠ File 2 File 3.
DRD sync – algorithm • The list of files on the active system in the root group is the initial list of files to be synchronized Trimming the list of files to be synchronized The following locations are not synchronized: /var/adm/sw/, /var/tmp/, /var/opt/drd/tmp/, /stand/, /tmp, /etc/lvmconf, /etc/vx/, /etc/vxvmconf/, /dev/, plus files specified by adminstrator Files that have changed on the clone because of operations other than „drd sync‟ are not synchronized Nonvolatile files in the Software
DRD real-life examples
Scenario 1: Maintenance of an 11i v3 IA system • System setup − rx3600, 8 GB RAM − HP-UX 11i v3, initial release • Without DRD: − Quiesce the system − Load: Downtime • Quality Pack (QPK) • Hardware Enablement (HWE) • Feature11i • HP SIM, Software Assistant, MD5Checksum − Reboot system − Verify system • 33 Total downtime: 32:07 (min:sec) 33
Scenario 1: Maintenance of an 11i v3 IA system (Continued) • System setup − rx3600, 8 GB RAM − HP-UX 11i v3, initial release • With DRD: − Create clone − Load: • Quality Pack (QPK) • Hardware Enablement (HWE) • Feature11i • HP SIM, Software Assistant, MD5Checksum − Reboot system − Verify system • • 34 Downtime Total downtime: 13:29 (min:sec) Downtime reduction: ~58% 34
Scenario 2: Updating an HP-UX 11i v3 IA system • System setup − rx3600, 4 GB RAM − HP-UX 11i v3, March 2008 • Without DRD: • 35 Downtime − Quiesce the system − Update to HP-UX 11i v3, March 2009 − Reboot system − Verify system Total downtime: 1:14:49 (hrs:min:sec) 35
Scenario 2: Updating an HP-UX 11i v3 IA system (continued) • System setup − rx3600, 4 GB RAM − HP-UX 11i v3, March 2008 • With DRD: − Create clone − Update to HP-UX 11i v3, March 2009 − Reboot system Downtime − Verify system • Total downtime: 35:53 • Downtime reduction: ~52% 36 (min:sec) 36
DRD sample timeline I am interrupted by a call– I need to submit my trip report for HP Discover today or I won‟t get reimbursed… Now that I know I created the clone, I will install the QPK & a security patch. drd runcmd swinstall –s hostname:/depot_loc QPK1131 PHKL_12345 6.13.2011 @ 4:01 pm 6.13.2011 @ 4:00 pm I have just returned from HP Discover and have decided to use DRD when installing the latest QPK plus a security patch! I create a clone of my root volume.
Wrap-up
More information • Get the DRD Toolset! − DRD tools and documentation are available as a no-cost download: http://www.hp.com/go/drd http://www.hp.
THANK YOU
