370 likes | 380 Views
VERITAS Storage Foundations For HP: Operational Efficiencies. Kelly Floyd HPUX Platform Specialist Aug 2005. Case study. Customer: Sprint, SBC and AG Edwards Problem statement Rapid growth Large complex environments High availability is paramount Multi-platform environments
E N D
VERITAS Storage Foundations For HP:Operational Efficiencies Kelly Floyd HPUX Platform Specialist Aug 2005
Case study • Customer: Sprint, SBC and AG Edwards • Problem statement • Rapid growth • Large complex environments • High availability is paramount • Multi-platform environments • Budget dollars are hard to come by • Revenue represented • Aprox.5 million in recent revenue on the HP platform
The Value proposition * Creating Operational Efficiencies • Manage more systems and storage in less time and with less resources • Reduce your maintenance windows • Repurpose older storage • Manage multiple tiers of storage more effectively while maintain current SLA’s • Reduce the amount of storage needed in your environment
Applications Applications Applications Applications Applications DBMS DBMS DBMS DBMS DBMS Cluster Management Cluster Management Cluster Management Cluster Management Cluster Management Cluster Management Data Replication Data Replication Data Replication Data Replication Data Replication Clustering Clustering Clustering Clustering Clustering Backup & Restore Backup & Restore Backup & Restore Backup & Restore Backup & Restore Volume Management Volume Management Volume Management Volume Management Volume Management File System File System File System File System File System SAN Management SAN Management SAN Management SAN Management SAN Management SAN Management VERITAS Interoperability across Platforms Data Availability Software HP-UX AIX NT4 / W2K Linux Solaris Complete Storage Devices and SAN Fabrics Planned EMC IBM HDS Sun Compaq NetApp Non VERITAS Brocade McDATA InRange QLogic CISCO
HPUX 11iv1 (PARISC) (aka 11.11) JFS/Online JFS 3.5 VM Lite/Full 3.5 Foundation Suite 3.5 Database Edition 3.5 Database Edition/AC 3.5 Sanpoint Foundation Suite 3.5 VCS 3.5 HA versions VVR and Flashsnap options HPUX 11iv2 (Itanium, PARISC) (aka 11.23) JFS/Online JFS 4.1 VM Lite/Full 4.1 Storage Foundation 4.1 (Standard and Enterprise) Storage Foundation for Oracle 4.1 (Standard and Enterprise) Storage Foundation Clustered File System 4.1 Storage Foundation for Oracle RAC 4.1 HA versions VVR Option Product Availability on HPUX 11iv1 and 11iv2
What’s new with HP and Veritas/Symantec? • In December 2004, HP named Veritas as its preferred supplier of storage virtualization for highly available HP-UX 11i environments • Single instance file-based • Clustered file-based • Single instance Oracle • Clustered Oracle • Joint effort integrates key products with Serviceguard: • Veritas Storage Foundation (SF), SF for Oracle, SF Cluster File System (SFCFS), and Storage Foundation for Oracle RAC • New offerings replace HP’s plans to bring TruCluster technology and Advanced File System to HP-UX 11i v3 • Joint investment in successful migration of Tru64 customers • Symantec reaffirms commitment to HP platforms, including Itanium
HP and Symantec Joint Support Agreement Integrated Support and Services Agreement (ISSA) Customer Bi-direction, Worldwide, Co-operative Support • Direct Access 7*24*365 • Escalation Procedures • Executive Relationship HP is single point of contact for: • HP software and hardware support • VERITAS storage software support • Support for 3rd party Operating systems Support for Mission Critical Environmentsacross products/operating systems
Symantec HP-UX Roadmap • Storage Foundations 4.1 for HP-UX 11iv2 PI • Quality of Storage Service • Intelligent Storage Provisioning • Portable Data Containers • New DMP policies • Instant Snapshots (Flashsnap) • SF/HPSg Integration • Storage Foundations Solutions with Serviceguard • HxRT 4.1MP1 • Oracle 10gRACR1 support • HxRT 4.1MP2 • Oracle 10gRACR2 support • Bug Fixes • 5.0 Train (Target Q2’06) • Synchronous release July 2005 Sept 2005 Oct 2005 Dec 2005 Q2 2006 8 VERITAS Confidential 8 VERITAS Confidential
Information Infrastructure INFORMATION Customers (internal and external)….Suppliers…..Partners…. DATA Solaris HP-UX server HP-UX NT HP-UX server Site A - U.S. FC Switch Disk Array Site C - APAC Tape Libraries Site B - Europe
Problems with LVM • PE_SIZE is set at VG creation. (Default 4MB) • Cannot be changed after creation. • MAX_PE is set at VG creation. (Default 1016 or #PEs on largest disk) • Cannot be changed after creation. • Cannot add larger disk to VG and use all available space on disk. • MAX_PV is set at VG creation. (Default 16) • Cannot be changed after creation. • Must know MAX_PV value when VG is created. • Since these values are fixed at VG creation, the PE-LE map size is fixed also. • To change any of these values, the HP administrator must back up the data, destroy the existing VG, recreate the VG with new values, then restore the data.
Consumer Consumer Consumer Storage Virtualization Application Aspects of Storage Physical Aspects of Storage Storage Resources
--- Volume groups --- VG Name /dev/vg00 VG Write Access read/write VG Status available Max LV 255 Cur LV 9 Open LV 9 Max PV 16 Cur PV 1 Act PV 1 Max PE per PV 4350 VGDA 2 PE Size (Mbytes) 4 Total PE 4340 Alloc PE 3766 Free PE 574 --- Logical volumes --- LV Name /dev/vg00/lvol1 LV Status available/syncd LV Size (Mbytes) 500 Current LE 125 Allocated PE 125 Used PV 1 LV Name /dev/vg00/lvol2 LV Status available/syncd LV Size (Mbytes) 1024 Current LE 256 Allocated PE 256 Used PV 1 LV Name /dev/vg00/lvol3 LV Status available/syncd Typical LVM “vgdisplay” output
Typical LVM “pvdisplay” output --- Distribution of physical volume --- LV Name LE of LV PE for LV /dev/vg00/lvol1 125 125 /dev/vg00/lvol2 256 256 /dev/vg00/lvol3 125 125 /dev/vg00/lvol4 5 5 /dev/vg00/lvol5 1000 1000 /dev/vg00/lvol6 250 250 --- Physical extents --- PE Status LV LE 0000 current /dev/vg00/lvol1 0000 0001 current /dev/vg00/lvol1 0001 0002 current /dev/vg00/lvol1 0002 0003 current /dev/vg00/lvol1 0003 --- Physical volumes --- PV Name /dev/dsk/c1t15d0 VG Name /dev/vg00 PV Status available Allocatable yes VGDA 2 Cur LV 9 PE Size (Mbytes) 4 Total PE 4340 Free PE 574 Allocated PE 3766 Stale PE 0
Key Application Offline Online -8hr -16hr 1 TB 1 TB 1 TB 1 TB EMC EMC
Key Application Offline Online -8hr -16hr 1 TB 1 TB 1 TB 1 TB Clariion EMC
Key Oracle application (assuming 20% change) Offline Online -8hr -16hr 200 GB 200 GB 1 TB 1 TB EMC EMC
Storage Foundation 4.1 (Q3 ‘05) Major New Themes • Share Data Across Platforms • Make it Easier to Allocate Storage • Move Data to the Most Appropriate Storage Device • Improve Performance and Manageability of DMP
Share Data Across Platforms Portable Data Containers Linux Solaris HP-UX AIX • Solaris records the incoming data • HP-UX batch processes the data • AIX loads the data onto a data warehouse • Linux backs up the data Simplifies Serial Processing Enables Easy Data Migration Reduces Vendor Lock-in Eliminates “Double Storage”
Intelligent Storage ProvisioningStorage provisioning can be challenging Storage provisioning without ISP • Mission Critical • High-end storage • 4 column stripe • 3 mirrors (2 offsite) Disk Group • Takes too long • Risk of errors • Inconsistent • Virtually impossible to create storage service levels
New in 4.x Mission Critical Business Priority Snapshot • StorageWorks XP12000 • 3 Mirrors • One Mirror in BLDG A • Two Mirrors in BLDG B • Virtual Array 7410 • 2 Mirrors • One Mirror in BLDG A • One Mirror in BLDG B • Virtual Array 7410 • RAID-5 Intelligent Storage ProvisioningTemplates reduce cost and risk Storage Provisioning Templates • Provisions storage faster • Eliminates configuration errors • Creates company-wide consistency • Simplifies implementation of storage service levels
Quality of Storage Service Storage Today: Problem = All data created “equal” • One class of storage • When storage is consumed: • Delete files • Archive files to tape • Buy more storage 1997 EmployeeReviews CurrentHR Files 2004 Holiday Party Pictures HR DepartmentEVA3000
New in 4.x Quality of Storage ServicePolicy-based tiered storage QoSS Overview • Multiple classes of storage available from one file system • Policy-based, automatic relocation • Transparent to applications VERITAS File System 2004 Holiday Party Pictures CurrentHR Files 1997 EmployeeReviews EVA3000 DS 2120
Quality of Storage ServiceSimple implementation How it Works • Create two or more volumes • Group volumes into a volume set • Create a file system on top of the volume set • Applications and users create files • Set and run relocation policies VERITAS File System EVA3000 DS 2120 No Application Changes Necessary
MENU DMP Management Enhancements • Can Set Policies for Load Balancing • Now Fully Managed from GUI • Detailed Stats • Can Now Specify Which Paths to Scan • Automatically Recognizes Changes in Server Partitions
MENU DMP Performance Enhancements • Several New Load Balancing Algorithms • Balanced path • Round-robin • Minimum queue length • Priority-Based • Adaptive Priority • Concurrent A/P • A/P-C, A/PG-C
MENU Storage Expert • Scans Configuration for Common Errors • Makes Recommendations for Improvement Poor Fault Tolerance Improper Layout Slow Relayout (Configuration Changes) Poor Recovery Time Poor Utilization of Storage Too Many Volumes to be Checked by Hand Configuration Degradation
MENU Major FlashSnap Enhancements • Incremental Volume Level Checkpoints • Similar to File System Checkpoints • Split Mirror Before it is Synchronized • Unlimited Number of Snapshots • Integrated with NetBackup • Can Take and Mount Checkpoints from VEA • Restore an Entire File System to a Point In Time • Create Storage CheckPoints Faster
MENU Instant Snapshots Instant Split of 3rd Mirror Makes Mirror Available BEFORE It Sync’s
& QUESTIONS ANSWERS
VxVM: Physical Allocation VM Disk private region subdisk public region VxVM utilizes variable sized allocation units called subdisks. These structures are defined by an offset into the public region and a length for flexibility in space allocation.
PVRA VGRA The Real View Two views of an LVM disk PVRA/VGRA physical extents HP’s View So why do we care about this?
The LVM ‘Bermuda Triangle’ (1-65535) MAX_PE (Max # of PEs on single PV) (Resolution size of LV) (Max # PVs in VG) PE_SIZE (1-256 MB) MAX_PV (1-255) This is what every HP system administrator must think about when creating a new volume group.