Presentation on theme: "HP-UX LVM, OnlineJFS and Oracle ASM Basics*"— Presentation transcript:
1HP-UX LVM, OnlineJFS and Oracle ASM Basics* My humble attempt to summarise some best-known features.I used many resources and valuable comments by others.I cannot claim big credits for this presentation.Dusan BaljevicSydney, Australia
2Disk Partitioning Concepts – HP-UX Partitions can be configured using:The Whole Disk Approach (no volume manager).Logical Volume Manager (LVM).Veritas Volume Manager (VxVM).
3Whole Disk Partitioning Concepts The whole disk approach supports partitioning a disk in five different ways:SwapFile SystemSwap SpaceRaw SpaceBoot Area
4Whole Disk Partitioning - Pros Simple to use, almost no Unix knowledgerequired.No licensing.Supports any type of physical volume.
5Whole Disk Partitioning - Cons Partitions cannot span multiple disks.Each disk can contain at most one file systempartition.Partitions cannot be easily extended.
6Logical Volume Manager Concepts HP-UX LVM is much more flexible than the whole disk approach.Introduced in HP-UX 9.0:Partitions/volumes can span multiple disksMultiple partitions/volumes may be configured on a single diskPartitions/volumes can be easily extended and reduced as needs changeLVM is included in all current versions of HP-UXBaseLVM is included with the operating systemLVM MirrorDisk/UX is available for an extra charge or in higher OE releasesPhysical VolumePhysical VolumeVolume GroupLogical Volumes
7HP-UX File Systems and Volume Managers Logical Volume Manager (LVM)Base File System (VxFS-lite)MirrorDiskUX (MDUX)Cluster File System (CFS)File System SolutionsIncluded in Base OEIncluded in VSE, HA, and DCOEIncluded in VSE, HA, and DCOEMirrorDiskUX (MDUX)Volume Management SolutionsVeritas Volume Manager (VxVM)Cluster Volume Manager (CVM)
8HP-UX with Symantec Releases HP-UX OS VersionHP-UX 11.23HP-UX 11.31Symantec Release Version3.54.15.05.0.1 Sep 2009Base Products Base-VxFSIn BaseOSBase-VxFS-50Base-VxFS-5.0Base-VxVMBase-VxVM-50Base-VxVM-5.0Standalone ProductsOnline-JFSB3929DAB3929EAB3929FAB3929FBVxVM-FULLB9116AAB9116BAB9116CAB9116CB
9HP-UX 11i v3 (L2 Layout Limits) Update 3 enhancementScalability: LVMSupported maximumsHP-UX 11i v1/v2HP-UX 11i v3 (L2 Layout Limits)LVMCurrent L1 LimitsOn Disk L2 LimitsCode L2 LimitsArchImplTestedMax LV size(64TB) 16TB28416EB264256TBMax PV size241 (2TB)16TBMax Volume Groups (VG)256N/A224-12112304*Max Logical Volumes (LV)255232-1211-12047Max Physical Volumes (PV)232 -1Max number of mirrors325476Max Nodes for mirroring216Max number of Extents/VG216 (64K)225Max extent size (range)1MB – 256MB1MB – 4TB1MB–4TB1MB–4GB1MB –256MBMax stripe width28 way (255)way511Max Volume Groups (VG): Additive of L1 and L2 limits i.e = 2304
10LVM and VxVM Features SAN Boot Support Y Y3 RAID0 RAID1 MD/UX HP-UX 11.31LVM, MD/UXVxVM 4.1/5.0 1SAN Boot SupportYY3RAID0RAID1MD/UXFULL license4Mirrored Stripes (RAID1+0)FULL licenseStriped Mirrors (RAID 0+1)Max Volume Size16EB (256TB)232TBMax Vol/Volume Group2048 (511) 2UnlimitedMax Volume Groups2304 (768) 2RootabilityOnline Volume ReconfigurationSLVMFULL license5 + CVM5Fast ResyncFULL license + VVRCluster AwareY(SLVM)Y(CVM)Static Path Failover (A/P)Dynamic Path Load balancing (A/A)# Mirrors632Dynamic Root Disk (DRD)HP Storage Device SupportALLLimited63rd Party Storage Support1 – VxVM 4.1 available with 11.31, VxVM 5.0 on VxVM 5.0 only 6 – Validate device in question with HP or Symantec qualification list:available H2CY Root Mirroring part of BASE2 – supported limit 5 – For all features
11LVM and VxVM Features - continued HP-UX 11.31LVM, MD/UXVxVM 4.1/5.0Instant SnapshotsNFULL licensePortable Data ContainersFULL license1Multi-volume File System supportDynamic Storage Tiering supportDynamic LUN expansionYExtended Campus, Metrocluster, and Continental cluster integrationDisk group configuration from any nodeNumber Of Nodes164 – VxVM & CVM Base16/8 – FULL License VxVM/CVMStorage Distance Support (standard/Metrocluster)100 km /300 kmRolling UpgradeY3RAID 5FULL LicenseCluster lock supportY (disk, lun)Hot RelocationHeterogeneous platformsSame commands on AIX, LinuxAIX, Solaris, Linux, Windows1 – VxVM 5.0 Only 3 – As long as no functional or protocol changes (y within 3.x, n between 3.x = 4.x)2 – AIX and Solaris have similar cluster solution 4 – Not supported for all configurations
12Scalability: Expanded file system Supported maximumsN/A = Not architecturally limitedFile systemsHP-UX 11i v1HP-UX 11i v2HP-UX 11i v3VxFS Number of filesN/AVxFS5.0 - File size16TBVxFS File system size50TBVxFS # Access Control List entries1024VxFS Number of filesVxFS File size2TBVxFS File system size32TBVxFS number of filesVxFS File sizeVxFS File system sizeVxVM volume32 TBVxVM volumes2^23VxVM mirrors32
13Disk Space Management Tool Comparison Whole DiskLVMVxVM10.x,11.x,11i11iYessam, smhveaSimilarNoYes*Active/PassiveActive/Active*HP-UX versions supportedBoot disk support?GUI configuration tool available?Available on other platforms?Can partitions span disks?Online resizing supported?Online backups supported?Striping (RAID 0) supported?Mirroring (RAID 1) supported?RAID 0+1 and 1+0 supported?RAID 5 supported?Dynamic relayout support?Dynamic multi-pathing support?* Features indicated by an asterisk may require an extra license
14Benefits of HP-UX Native Multipathing Zero-Config. No initial setup or configuration needed. No license or add-on software installation needed.Free. Comes bundled with Core HP-UX. Is not an add-on product. No additional license fee for Native MP.Transport Aware Failover/Failback.Fibre Channel RSCN based failover/failback.Detection and failover of all paths leading to affected component (hba, target port, switch, inter-switch link).Fully parallel path failover/failback and path monitoring.Built into Storage Stack. More responsive and better performing.Exploits both server platform and storage characteristics.
15Benefits of HP-UX Native Multipathing - continued Tested as a core part of HP-UX. Engineered for scalability, reliability, performance, serviceability.Time to Market support for new technologies. Being a core part of HP-UX, new technologies are supported when released (ex : HPVM, VPARs, VSE, new transports like SAS, storage management products, etc).Simplifies Storage Management. Eliminates an entire layer in the IO Stack (add-on MP product) and reduces amount of management overhead for sysadmin. No more need to install, tune, update, monitor add-on MP product.Ideal for Oracle ASM. Oracle ASM provides its own volume management capability and Native MP is a good fit in that environment since the customer does not need to install VxVM solely for DMP capabilities.
16HP-UX Native Multipathing vs. Classic MP Classic MP Product (DMP)Add-on product layered above IO stack.Agnostic of low level SAN and SCSI events.Unaware of transport specific failures (HBA, switch, switch port offline).Discovers failures on IO errors.Needs to issue test IO on IO error.Path Failover initiated following IO error and Test IO failure.Each such path failure detected individually on IO error on each path.Need to ping each failed path to detect recovery.HP-UX 11iv3 Native MPNot an add-on product. Built into the IO stack and HBA drivers are multi-path aware.Aware of SAN and SCSI events and takes advantage of those.Transport Aware. (Knows scope of outage such as HBA, switch, switch port, tgt port).Can failover at the scope of outage. (All paths under HBA, All paths thru the switch, all paths thru the switch port, all paths to the tgt port).SAN Fabric Events signal recovery. Pinging is avoided.Fully parallel failover/failback.
17Product-use application Volume ManagementLogical Volume Manager (LVM) If you need:VxVM If you need:No-cost solutionBasic Volume Management-default Operating Environment installSimple operationSAN bootDisk-mirroring capability with MirrorDisk/UXAdvanced Volume Management solutionInstant SnapshotsCross-platform data sharingQoSS supportRaid 5Hot Relocate/UnrelocateCFS support
18Product-use application File SystemsVxFS Lite If you need:VxFS Full (OnlineJFS) If you need:Cluster File System (CFS) If you need:* Available 10/Basic file system functionalityA no cost solutionSimple operationFast file system recoveryDirect I/O performance*Online defragmentationOnline log and file system resizingOracle Database ManagementConcurrent I/O performance*File change logStorage CheckpointsFunctionality for a clustered environmentCluster Volume ManagerDynamic Storage TiersFlashsnap technology
19Oracle ASM vs. Classical Storage Layers Bill Bridge the original architect of Automatic Storage Management. In the Oracle Press title, Oracle ASM, Bill provides a forward where he discusses the problems with using vendor specific OS file systems to manage Oracle datafile placement:for arch logs & backups, OS vendors don't provide shared disk file system 2. logical volume managers hide the location of files making it difficult to manage disk I/O and provide good stats 3. existing LVMs don't work well with over 100 disks4. OS's and Oracle don't handle databases well that have 1000's of datafiles5. naming becomes difficult with large number of datafiles6. features, and filesystem limitations vary across different OSs7. users at the OS level can touch Oracle files with standard utilities, without Oracle knowingSo, he set out to solve these problems by building Oracle's own filesystem. His intention wasto provide these features:1. tightly integrated with Oracle, and work with clusters (then parallel server)2. new storage automatically used, managed as disk unit or disk group 3. thousands of disks supported 4. files won't have names, and will be hidden from the OS
20Oracle Traditional Options - Raw versus Cooked and With or Without an LVM Slide courtesy ofApril 6, 2017
22Oracle ASM BasicsAn ASM file system layer is implicitly created within a disk group. ASM provides a vertical integration of the file system and volume manager for Oracle database files.This file system is transparent to users and only accessible through ASM instance, interfacing databases, and ASM’s utilities. For example, database backups of ASM files can be performed only with RMAN.Does not completely bypass the O/S I/O stack. It uses the asyncdsk driver in order to perform asynchronous I/O. Without it, the logwriter and dbwriters would be doing direct, synchronous I/O and would not be able to perform acceptably in high IO workloads. The I/O requests also have to pass though the SCSI and FC layers.
23Oracle ASM Basics - continued The functionality of an ASM instance can besummarized as follows:Manages groups of disks, called disk groups.Protects the data within a disk group. *Provides near-optimal I/O balancing without any manual tuning.Enables the user to manage database objects such as tablespaces without needing to specify and track filenames.Supports large files. * Choices for disk group redundancy include:External: defers to hardware protectionNormal: 2-way mirroringHigh: 3-way mirroringIn addition, ASM failure groups can be created, providing a set of disks sharing a commonresource whose failure needs to be tolerated. Redundant copies of an extent are stored inseparate failure groups. ASM failure groups can be assigned by DBAs or automatically byASM.
24Oracle ASM Basics - continued One can use Oracle Enterprise Manager (EM) or the Database Configuration Assistant (DBCA) for a GUI interface to Automatic Storage Management that replaces the use of SQL or SQL*Plus for configuring and altering disk groups and their metadata.DBCA eases the configuring and creation of the database.EM provides an integrated approach for managing both the ASM instance and database instance.
25Oracle ASM Limits 63 disk groups in a storage system. 10,000 ASM disks in a storage system.4 Petabyte maximum storage for each ASM disk.40 Exabyte maximum storage for each storage system.140 Petabyte in external redundancy (no ASM mirroring).42 Petabyte in normal redundancy (2-way ASM mirroring).15 Petabyte in high-redundancy (3-way ASM mirroring).NOTE: Oracle database limits file sizes to 128 TB with big file tablespacesand 32k block size, which is considerably lower than the ASM limits.
26Oracle ASM LimitsASM disk group that is implemented with External Redundancy has a maximum file size of 35 TB.ASM Disk Group that is implemented with Normal Redundancy has a maximum file size of 5.8 TB.ASM Disk Group that is implemented with High Redundancy has a maximum file size of 3.9 TB.1 million files for each disk group.2.4 Terabyte maximum storage for each file.NOTE: Oracle database limits file sizes to 128 TB with big file tablespacesand 32k block size, which is considerably lower than the ASM limits.
28Oracle ASM - ProsASM provides some file system and volume management capabilities for Oracle database files only. These include DB control files, redo logs, archived redo logs, data files, spfiles and Oracle Recovery Manager (RMAN) backup files (see previous slide).File-level striping/mirroring.Ease of manageability. Instead of running LVM software, run an ASM instance, a new type of "instance" that largely consists of processes and memory and stores its information in the ASM disks it is managing.Attempts to identify the configuration errors. **1. A single disk with different mount points is presented to an ASM instance. This can be caused by multiple paths to a single disk. In this case, if the disk in question is part of a disk group, disk group mount fails. If the disk is being added to a disk group with ADD DISK or CREATE DISKGROUP, the command fails. To correct the error, restrict the disk string so that it does not include multiple paths to the same disk.2. Multiple ASM disks, with the same ASM label, passed to separate ASM instances as the same disk. In this case, disk group mount fails.3. Disks that were not intended to be ASM disks are passed to an ASM instance by the discovery function. ASM does not overwrite a disk if it recognizes the header as that of an Oracle object.
29Oracle ASM - ProsGives Oracle Corporation control over the storage system, which makes them happy, so they promote it heavily. *No large Unix-level administration needed.Provides a single point of support (Oracle) so there is no “finger-pointing”.Provides easy management of block devices (raw partitions).Automatically moves hot blocks to the outside of the disk.Vendor and operating system neutral.* Oracle Automatic Storage Management (ASM) was introduced with Oracle Database 10g.Free, and widely adopted.
30Oracle ASM - ProsIncluded in the Oracle license so no additional cost for the software or its support.Supports very large disk groups and datafiles.Database File System with performance of RAW I/O.Supports clustering (RAC) and single instance.Automatic data distribution.Memory requirements for an ASM instance are small. 100 MB of RAM is typically all that is required to run an ASM instance on a production server.
31Oracle ASM - ProsOn-line add/drop/resize disk with minimum data relocation.Automatic file management. *Flexible mirror protection.Inode locks not applicable to ASM.Ability to grow diskgroup capacity on the fly.Supports multiple database instances running on a single host, and does not have its own data dictionary.* ASM uses system generated filenames, otherwise referred to as fully qualified filenames foreach file that is under ASM control. This filename gets generated automatically at filecreation time. These are also referred to as Oracle Managed Files and will be automaticallydeleted when it is no longer needed.
32Oracle ASM – Pros (Oracle 11gr) Fast mirror resynchronization. *Preferred mirror read in a cluster. **Support for large ALU. ***Variable size extents. ****Rolling upgrade and patching.Table level migration wizard in EM.New ASMCMD commands.New SYSADM privilege – separate from the SYSDNA privilege.More flexible FORCE options to MOUNT or DROP disk groups.* Benefits:Fast recovery from transient failuresEnables pro-active maintenance** Allows local mirror read operations andeliminates network latencies in extended clusters*** ALUs can be set to 1/2/4/8/16/32/64 MB at disk group creation time.Higher performance for large seq I/O (DW)Better leverage of Hardware RAID read-aheadSet Oracle MAXIO = AU size**** Extent size = AU size up to 20,000 extentsExtent size = 8*AU up to 40,000 extentsExtent size = 64*AU beyond 40,001 extentsStripingCoarse Stripe size always = one AUFine Stripe size always = 128 KB
33Oracle ASM - ConsASM cannot be used for Oracle executables and non-database files.ASM files can only be managed through an Oracle application such as RMAN. This can be a weakness if you prefer third-party backup software or simple backup scripts. Cannot store CRS files or database software. Cannot manage ASM through standard Unix tools.Potentially disrupts the balance of power between the Unix Systems Administration groups, and the Database/DBA groups. Traditionally the former group manages disks, hardware, and the operating system level, leaving the DBAs to coordinate with them for new resources. This would change that balance, which could cause some resistance. ** ASM enable a DBA to manage storage directly – DBA now has to consider:How do I deal with disk failures? Data resilienceHow do I back up storage? Data protectionHow do I make the best use of the raw storage? Storage UtilizationHow do I make it run fast enough? Performance
34Oracle ASM - ConsASM does not have multi-pathing capability. It assumes the underlying O/S will provide this functionality. In HP-UX, multi-pathing is provided by a Volume Manager feature such as PVLinks in the HP-UX Logical Volume Manager (LVM), native multipathing in HP-UX 11.31, or DMP in Veritas Volume Manager from Symantec (VxVM), or by other third-party software such as Securepath or Powerpath.ASM is still in the enterprise computing, relatively new. There are a number of vendors whose core business has been in the logical volume manager/file system space for years. Often, maturity matters a lot when it comes to software systems, reliability, and proven success rates.New technology to get familiar with.
35Oracle ASM - ConsAutomatic Storage Management load balances file activity by uniformly distributing file extents across all disks in a disk group. For this technique to be effective it is important that the disks used in a disk group be of similar performance characteristics.There may be situations where it is acceptable to temporarily have disks of different sizes and performance co-existing in a disk group (for example, when migrating from an old set of disks to a new set of disks). The new disks would be added and the old disks dropped. As the old disks are dropped, their storage is migrated to the new disks while the disk group in online.
36Oracle ASM - ConsThere is no shared awareness of LUN use between ASM and LVM or VxVM. It means that the system administrator must be careful not to accidentally allocate a LUN already allocated for LVM or VxVM use to ASM use (or vice-versa).ASM is not an enterprise-class file system.ASM is a proprietary solution.The customer is dependant on the reliability of the new ASM code stack. *Does not offer network monitoring.Be careful about ASM hidden parameters.* An example of a long-running bug:Oracle ASM holds disk after removing it (Metalink ).Workaround is to restart instances, or if using Oracle versionapply patches and – they are required for ServiceGuardsupport too.
37Oracle ASM - ConsNot for high I/O environments (that is what some tests claim).Everything is single threaded through one process at a very low level. *If one uses Oracle ASM and CRS, they will still require a 3rd party clustering solution to support the non-Oracle data. They will then have to manage multiple clustering solutions.* I found this claim somewhere but cannot find its reference now.This needs to be verified!
38Oracle ASM - ConsDBAs must still watch and then perform the task of adding and removing disks to an ASM disk group when needed. This leads back to the problem of DBAs under allocating, and worse yet, over allocating disk storage, just to be safe, which recreates the problem of wasted space and leads to higher than needed storage costs.This is where thin provisioning comes into play. Thin provisioning will automatically allocate on a just-enough and just-in-time basis which relieves the DBA from both having to watch and then add or remove disk to a disk group. Oracle's ASM and thin provisioning could be combined to offer a complete, end-to-end, storage solution. Oracle's ASM feature would create, allocate, place, and rebalance data files for performance and thin provisioning would dedicate disk space on the fly and only when needed.
39Oracle ASM - ConsConfiguration details and performance metrics are exposed via V$ views. Other possibilities are the command line interface, asmcmd and the graphical interface of OEM.Metadata are however partially hidden to the end user. That is the mapping between physical storage, ASM allocation units, and database files is not completely exposed via V$ views. It was found that is possible to query such information via undocumented X$ tables. For example, it is possible to determine the exact physical location on disk of each extent (or mirror copies of extents) for each file allocated on ASM (and if needed access the data directly via the O/S). This can be used by Oracle DBAs wanting to extend their knowledge of the inner workings of the ASM or wanting to diagnose hotspots and ASM rebalancing issues.
40What about Non-Database Files? Since ASM supports only database data files and log files, the following storage management methods are required for non-database files if ASM is used:A) A local file system or Cluster File System for Oracle Clusterware binaries and configuration files and RAC binaries and configuration files.B) Shared storage for Oracle Clusterware data: voting disk and OCR files. This storage has to be configured either as shared raw devices, shared raw volumes, or files in the Cluster File System. Oracle Clusterware needs to be up and running before the ASM daemon can start. Therefore, ASM cannot be used for Oracle Clusterware data.
41Some of the Oracle Plans and Efforts * Elimination of Symantec by destroying Veritas Cluster as a viable product (replaced with CRS), and the same for Veritas File System (replaced by ASM).Elimination of Sun by adopting Linux as a low-cost alternative to Solaris (Sun has now been acquired by Oracle who has been primarily responsible for its downfall).Attempted elimination of Red Hat by “migrating” Red Hat Linux under Oracle Enterprise Linux (limited success so far).Challenge to EMC and NetApp in the area of storage using the Oracle Exadata Storage (version 1 was with HP and just-announced version 2 on Intel X86 and Linux).Changes in licensing structure.Acquisition of Sun Microsystems.This slide simply points out the facts that Oracle istrying to “run the show alone as much as possible”.
42Capability compare Business Benefit Vendor Product(s) HP Oracle Business BenefitVendorProduct(s)Oracle executable and non-database filesMulti-pathing capabilityStrong I/O fencingSingle-instance Database object storageRAC Database object storageNear raw database performanceHPOnlineJFS+LVM/MirrorDisk/UX (Single Instance only)YesnoOnlineJFS+VxVM/ODM Storage Management for Oracle (Single Instance only)Cluster file system(both RAC & Single Instance)yNo file system – raw volumesNoYES – it is raw volume(RAC ONLY)OracleAutomatic Storage Management (RAC & SI)No*(limited)
43Capability compare - continued Business BenefitVendorProduct(s)Ability to use standard UNIX commands to move or copy dataProven, time-tested quality and reliabilityAll disaster-recovery needs can be metEase of management (e.g., backup and database maintenance)HPOnlineJFS+LVM/MirrorDisk/UX (Single Instance only)YesyOnlineJFS+VxVM/ODM (Storage Management for Oracle)(Single Instance only)Cluster file system(both RAC & Single Instance)No file system – raw volumesn(RAC ONLY)OracleAutomatic Storage Management (RAC & SI)No
44Oracle ASM versus HP-UX SLVM ** • ASM lacks Multipathing: The ASM-over-SLVM configuration provides multipathing for ASM disk groups (using LVM PV Links or storage based multipathing). This is not an issue on HP-UX 11i v3 (native multipathing).ASM-over-SLVM enables the HP-UX devices used for disk group members to have the same names on all nodes, easing ASM configuration. Generally, when using raw disk devices with ASM, the device files are created under /dev/oracle, so they can be the same on all nodes.ASM-over-SLVM protects ASM data against inadvertent overwrites from nodes inside/outside the cluster. If the ASM disk group members are raw disks, there is no protection currently against these disks being setup in LVM or VxVM volume/disk groups. *There are some disadvantages too. *** LVM pvcreate(1M) recognises the ASM disks and does not destroy themunless the “-f” (force) flag is used.** Disadvantages:- Additional configuration and management tasks introduced by the extra layer of volume management (volume groups, logical volumes, and physical volumes); - Performance impact of extra layer of volume management.
45Oracle Discontinues Raw/Block Device Support In release 11.2, the Oracle Installer and DBCA(Database Configuration Assistant) will no longersupport raw/block devices for database files. Inaddition, there will no longer be raw/block devicesupport for storing the OCR and Voting Disks for newinstalls. Customers who create a new 11.2 databasewill need to store their database files in either ASM, afile system, or on an NFS filer. RAC database files mustbe stored on ASM, a certified clustered file system, or acertifed NFS filer.As stated in Metalink note , Oracle plans to fully desupport RAW/Block devicestorage effective with the next major release following At this time, customers will needto migrate any data files stored on RAW/Block devices to ASM, a cluster file system, or NFS.Thus, we recommend new databases not be deployed on RAW/Block devices. For moreinformation on migrating from RAW to ASM, please see :
46Oracle ASM on HP-UX – Some Experiences It was found Oracle ASM was a good choice to simplify Oracle related storage and volume managementHowever do not use ASM redundancy featuresThe HP-UX 11v3 MSS (Mass Storage Stack) and Oracle ASM were a “killer combo”.ASM works very well for Oracle data management, but a severe performance penalty gets incurred if the ASM redundancy features are used on top of the storage array redundancy features.
47One of HP-UX SolutionsHP-UX file systems can provide read/write performance 95-98% as fast as a raw-device setup.*OJFS 5.0.1: performance impact virtually eliminated.The manageability and reduced administration from a file system, with near-raw performance.*Currently, HP offers advanced file system performance from its Storage Management Suite bundles—which include Oracle’s Database Manager (ODM)After October, 2009 Direct I/O capability will be enabled in the base file system and Concurrent I/O will be enable in OnlineJFS (which is included in all but the Base OE).* Currently this is offered through the purchase of a Storage Management Suite bundle
48HP-UX 11iv3 Mass Storage Stack Transparent native multipathing to LUNs is useful and necessary – decreases work and rework.Load balancing increased performance“least command load” policy provided the best performance for this BI workload“round robin” policy, the default, provided slightly less performancePersistent LUN bindings and LUN DSF’s reduce design and maintenance efforts significantly for mid-range and high-end BI implementations containing large storage subsystems.Storage management is extremely important fro BI customer due to the large volume of storage consumed by the BI workload. MSS greatly simplifies this task.Large Enterprise Example: Due to the work involved with migrating FC HBA to new cabinet in the SD they declined to do so and missed a good opportunity to balance the IO across cabinets and achieve better IO distribution and performance. MSS and v3 would have made the task much easier to do, and more likely for the customer to do.
49Some Best Practices for Oracle ASM with HP StorageWorks As a result of testing, a set of best practices for using Oracle ASMwith HP StorageWorks on HP-UX servers is presented:• Configure ASM disk groups to use external redundancy.• When building a disk group or adding to an existing one, use disks of similar capacity and performance characteristics in the same disk group.• To leverage I/O distribution across as many resources as possible, it is best to present more than one LUN to a disk group (allowing ASM to do the striping).• Use HP Secure Path with ASM on HP-UX or MSS (Mass Storage Stack) on HP-UX because it complements the high availability and performance of the entire stack.
50Some Best Practices for Oracle ASM with HP StorageWorks - continued • Each device (LUN) should be managed either by Oracle ASM or by HP-UX LVM, but not both.• Care should be taken not to attempt inadvertently to manage an ASM disk by a traditional volume manager or vice versa.• Configure async I/O (Please consult the Oracle Administration Guide documentation).• Use "insf" instead of "insf -e" to create the devices associated with new hardware because "insf -e" will reset the ownership to user "bin“.