3par dynamic optimization manual
LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF
File Name:3par dynamic optimization manual.pdf
Size: 3722 KB
Type: PDF, ePub, eBook
Category: Book
Uploaded: 15 May 2019, 13:38 PM
Rating: 4.6/5 from 833 votes.
Status: AVAILABLE
Last checked: 17 Minutes ago!
In order to read or download 3par dynamic optimization manual ebook, you need to create a FREE account.
eBook includes PDF, ePub and Kindle version
✔ Register a free 1 month Trial Account.
✔ Download as many books as you like (Personal use)
✔ Cancel the membership at any time if not satisfied.
✔ Join Over 80000 Happy Readers
3par dynamic optimization manualHow do you get the data from your old array onto the 3PAR StoreServ. Well if you have vSphere no problem you could use Storage vMotion or if you are performing a data migration good old robocopy would do the trick. This is where Peer Motion comes in strutting it’s stuff. These physical disks and then placed into an enclosure (cage) and are sub divided into Chunklets. Chunklets are used to breakdown each physical disk into 1GB portions. So a 146GB hard drive get’s broken down into 146 Chunklets. The Logical Disk is created from Chunklet’s from different physical disks. The Logical Disks are then pooled together to create a Common Provisioning Group (CPG). It’s at the CPG level where you set your RAID type which is either: The other choice is High Availability Enclosure which strips the chunklets across enclosures, so that you are protected from enclosure failure, in the same way as StoreVirtual Replicated RAID 10. An example of this, was when I was building a StoreServ 7200 config, which had the following requirements: There are three types of tunesys which are. A few things to note with tunesys Well what it does is pretty straight forward really. First of all tunesys calculates the percentage utilization for each disk type per node. It that checks the average utilization across all nodes. If any of the nodes are more than 3 out (default) then each Virtual Volumes is checked to see if it is well balanced across nodes. If it isn’t then tunesys does it’s magic and rebalances. The policies can be used to sample performance during the working day and then then data movement can be scheduled out of hours. Using DO, we have the ability to change the class of service seamlessley you want to move from RAID 6 on 10K SAS to RAID 5 on 15K SAS not a problem. This means we can move an application from a higher class of service to a lower class of service or vice versa on the fly.http://sudeoksa.com/userfiles/20200823163408.xml
- Tags:
- 3par dynamic optimization guide, 3par adaptive optimization guide, 3par dynamic optimization user guide, 3par dynamic optimization manual, 3par dynamic optimization manual pdf, 3par dynamic optimization manual download, 3par dynamic optimization manual software, 3par dynamic optimization manual free.
Sheldon Smith a HP Technology Consultant has confirmed that the limit has been removed when tuning a Virtual Volume using Dynamic Optimization, Well the following is the recommended practice: It’s the ability to take a fat volume and turn it into a thin volume or vice versa! So I won’t repeat myself. So no more sdelete! It was pretty complex and it always took me a couple of attempts to get it working. One of the really cool things with 3PAR OS 3.1.2 is that it’s been built in! Yes that’s right you need to have a four node system to benefit from this. However, a couple of things to note: Meaning you will loose all previous performance metrics. However, I do appreciate that some businesses such as cloud providers have no other alternative. However with 3PAR OS 3.1.2 when you issue the command If you answer yes then any active tasks are stopped and the node is rebooted. I haven’t been able to test this yet, however my understanding is that some tasks will automatically resume after the node has been rebooted. It allows for backup products to directly make snapshots of virtual volumes reducing the impact of backups on VM’s. Perhaps more importantly it allows for entire VM’s to be recovered more quickly rather than relying on instant restore mechanisms which run the backup from the backup target which ultimately results in performance degradation. Veeam have announced support for this integration for Q1 2013 A copy volume is then created which could be on lower tier of disks. You should keep this in mind. IT is a short living business. This information might be outdated. HP 3PAR Adaptive Optimization (AO) enables autonomic storage tiering on HP 3PAR storage arrays. With this feature the HP 3PAR storage system analyzes IO and then migrates regions of 128 MB between different storage tiers. Frequently accessed regions of volumes are moved to higher tiers, less frequently accessed regions are shifted to lower tiers.http://landingoa.com/propertiespulse/fckeditorimages/4-speed-manual-transmission-muncie.xml I often talk with customers about AO and I know that this feature is sometimes misunderstood and misconfigured. This blog post is a summary of in my opinion important topics. Basis about CPGs, LDs, VVs A physical disks is divided into 1 GB portions, so called chunklets. A Common Provisioning Group (CPG) creates a pool of logical disks (LD) and therefore a pool of storage, that can be used to create virtual volumes (VV). These properties are used to create LD. A LD is a collection of chunklets arranged in RAID sets. The size of a LD is determined by the number of data chunklets in the RAID set. A VV allocates space in size of 128 MB regions (user and snapshot space) or 32 MB (admin space). Each region is on another LD, so a VV is striped across LDs and therefore across physical disks. I hope this drawing makes it easier to understand. Thin Reclamation can reclaim space from VVs in 16 KB increments, but free VV space is only returned in 128 MB increments to a CPG. A defragment process goes over the LDs and consolidates smaller pages to bigger contiguous regions. With time the LDs can become less efficient in space usage. Due a process called “compacting”, mapped regions of VVs can consolidated to fewer, more utilized LDs. This may free disk space and increases the efficency of space usage. VVs can allocate space from free space on LD, or if no or not enough contiguous free space is available, new LDs are created. Different VV can share the same LD. Context between Adaptive Optimization and CPG An Adaptive Optimization (AO) configuration consists, in simple terms, of CPGs, a mode configuration and optional a schedule. An AO config must have configured at least two tiers and can have up to three tiers (tier 0, tier 1 and tier 2). It’s important to understand, that tier 1 should meet the performance requirements of your applications. It’s not a good idea to use a “slow” tier 1 and let AO move all data to tier 0, because your workload heat up chunklets.http://www.drupalitalia.org/node/67585 So everytime you create a VV, this should be associated with your tier 1 CPG. Mode configuration The tiering analysis algorithm considers three different things: available space in tiers average latency average tier access rate densities If allocated space in a tier (a CPG) exceed the tier size (or the CPG warning limit), AO will try to move data to other tiers. Busy regions will be moved to faster tiers, more idle regions will be moved to lower tiers. If your tier 0 exceeds the limit, but there’s space left in tier 1, AO will try to move more idle regions from tier 0 to tier 1. If all tiers exceeds their limits, AO will do nothing. If a higher tier gets to busy, the latency for this tier can become higher than for lower tiers. To prevent this, a region will not be moved to a faster tier, if the latency for the destination tier is higher than for the current tier. An exception is made, if the IOPS load on the destination tier is lower than an internal threshold. Then the region will be moved to the faster tier. The last point is the hardest and most complex. The average tier access rate densities is considered, if the system is not limited by tier latencies or tier space. It describes how busy the regions in a tier are on average and it’s measured in units of IOPS per gigabyte per minute. Thre results are compared to individual regions. Depending of the result of this comparison, a region is moved to a lower (it’s less busier than other regions) or higher tier (more busy than other regions). The mode configuration parameter has three different options: Performance Cost Balanced If it’s set to “Performance” more data is moved to faster tiers. In contrast to this, the “Cost” mode moves more data to lower tiers. The “Balanced” mode balances between performance and costs. This should be the default setting. Tier configuration You need to configure at least two tiers. Best practice is to configure three tiers.http://apartmangyula.com/images/3n1-pjt-manual.pdfNo VV should be associated directly with the tier 0 and tier 2 CPG. You should also ensure, that all CPGs that are used in an AO config have the same availability level (Cage, Magazine or Port). If tier 0 and tier 1 have cage availability and tier 2 only magazine availability, the VV will effectively have only magazine availability. Schedule You can configure a schedule or you can run AO immediately. If you have multiple AO configs, schedule them all to the same start time. They will run sequential, but the calculation which regions have be moved, is done at the same time. If you check the schedule on the CLI, you will notice another interesting fact. Lab-3PAR-7200 cli showschedThis is done as part of AO. Compacting moves regions of less efficient LDs to fewer, higher utilized LDs. You don’t have to run the run AO every hour. It’s sufficient to run it once a day. Run it at periods with low IO. You can exclude the weekend, if your company or customer isn’t working at the weekend. Other things to consider If you use AO, you should avoid using automated techniques, that move data between different storage tiers. Yes, if you think of VMware SDRS, that would be such a technique. But only if you use it in fully-automated mode. You can use it in manual mode and apply recommendations if necessary. Final Words I don’t say that these are the best practices, but with these topics in mind, it should be easy for you to discuss the requirements of your customer and impacts of different AO settings with your customer. If you take a look into the HP 3PAR StoreServ Storage best practices guide, you will recognize some of the above mentioned practices. But always keep in mind: Even the best practice can miss the customers requirements. So don’t just apply “best practices” without reflecting the impact to the customers requirements.He is a fan of Lean Management and agile methods, and practices continuous improvement whereever it is possible. Follow me Latest posts by Patrick Terlisten ( see all ) Virtually reseated: Reset blade in a HPE C7000 enclosure - July 19, 2020 Update Manager fails with unknown error during host remediation - July 19, 2020 Access to on-premise hosted Public Folders using Exchange Online mailboxes - July 18, 2020. This entry was posted in Storage and tagged 3par, hp, storage on May 29, 2014 by Patrick Terlisten. Post navigation Support me Badges Tags 3par automation azure backup blog bug certification citrix cloud datacore data protector esxi exam exchange exchange 2013 homelab horizon view hp hpe hyper-v industrialization job linux microsoft netscaler networking office 365 operations management power cli powershell proliant security server software storage storeonce troubleshooting vcap vdi veeam vExpert virtualization vmware vsphere windows. If you are from an EMC background AO is comparable to FAST VP, if you are from a NetApp background welcome to the brave new world of tiering. You can think of this as being a gold, silver and bronze level in terms of performance. Your SSD’s forming your high performing gold layer, 10 or 15K SAS disks operating as your silver layer and NL disks operating in bronze. Below the different tiers of disk are shown diagrammatically along with some example of blocks of data tiering both up and down. AO is a licenced feature that is enabled through the creatively named Adaptive Optimization software option and is available across all the hybrid models. It is not available on the all flash models for obvious reasons. So you may expect to see all your VV’s (Virtual Volumes) that are demanding the most IOPs end up in your tier 0 SSD’s, this however is not the case as AO is a sub-lun tiering system, i.e. it does not need to move entire volumes just the hot parts. This granular level of analysis and movement ensures that the capacity of expensive SSD disks is utilised to its fullest, by moving only the very hottest regions as opposed to entire VVs. To give an example if you have a 100GB VV and only 2 regions are getting hit hard only 256MB of data need to be migrated to SSD, a massive saving in space compared to moving the entire volume. Regional IO density is measured in terms of IOPs per GB per minute. The regional IO density stats are then used by AO to select those regions that have an above average regional IO density and marking them for movement to a higher tier. How aggressive AO is in moving data is dependent on the performance mode selected. AO is controlled through an AO config. In an AO config you define your tiers of disk through the selection of CPG’s and then choose an operational mode optimised for cost, performance or a balance between the two. Once you have setup your AO config you then need to schedule a task to run AO. When scheduling you will need to choose the analysis period during which regional IO density will be analysed and the times during which AO will actually perform the data moves. An example of AO config is shown in the table below. It is not recommended to have a 2 tier system that only contains NL and SSD disks as the performance differential would be too great. Some example tiers would be: At least start out with a single AO policy containing ALL your tiers of disk and allow ALL data to move freely. If for example you choose what you believe are your busiest VV’s and lock them to an SSD CPG you may find only a small proportion of data is hot, and be robbing yourself of space. Conversely if you choose to lock a VV into a lower tier of CPG on NL disks it may become busy and have nowhere to move up to, hammering the disks it’s placed on and affecting all the volumes hosted from there. So if you do go down the route of having multiple AO policies you must have a separate CPG to represent each tier of disks in each different AO policy. Additional CPG’s create additional management overhead in terms of reporting etc. For a reminder on what CPGs are about go here. So on a 7400 with 4 nodes, AO would occur across the cages attached to nodes 0, 1 and across those attached to nodes 2, 3. The key design principle here is to keep drives and drive cages balanced across nodes so performance in turn remains balanced Remember space in your higher tiers is at a premium, by second guessing and placing the wrong data in your tier 0 you are short changing yourself. I made this change for a customer recently moving from an AO config that only allowed business critical apps access to the SSDs, to allowing all data to move freely across all tiers.This way any new writes aren’t hitting slow disk, but also aren’t taking up valuable space in your top tier. By allowing AO complete control of your top tier and not provisioning any volumes from it you can allow AO to take capacity utilisation up to 100. The traditional days of storage and having to calculate the number disks and RAID type to allocate to a LUN are gone. Just provision your VVs from the CPG representing the central tier, allow the volumes access to all the disks and let the system decide which RAID and disk type is appropriate at a sub-lun level. Don’t try and second guess where data would be best placed, the machine will outsmart you. Start again by keeping things simple, monitor during your core business hours and be careful to not include things like backups in your monitoring period which could throw the results off. If you find you have certain servers with very specific access patterns adjust the timing to monitor during these periods. Schedule AO to run out of hours if possible as it will put additional overhead on the system. You can set a max runtime on AO to make sure that it is not running during business hours. At first make the max run period as long as you can outside of business hours to give AO every opportunity to run. If you do run multiple AO policies set them to start at the same time, this will minimise the chance of you running into space problems Which one you choose will depend on if your aim leans towards achieving optimum cost or performance. I would suggest selecting balanced to start with then monitoring and adjusting accordingly Having a mix of availability levels will mean that data is protected at the lowest availability level in the AO config. For example if you FC CPG has an availability level of cage and your NL CPG has magazine the net result will be an availability of magazine level. If the access pattern of your data is truly random each day Adaptive Flash Cache may help to soak up some of the hits and can be used conjunction with AO. It would be good if HP could learn the storage characteristic and then adapt for a time period for example lets say you had a workload that ran weekly which was IO intensive. My understanding from today’s version of AO is as follows: You make a good point that not every work load will be suitable for AO. For AO to be a good fit the regional IO density needs to be high i.e. a high proportion of your IOPs comes from a small proportion of capacity and the workload must have some kind of repeatable pattern to it. If the pattern is truly random like in your example then a different approach would have to be sought. However if the pattern repeated each week e.g. each Monday is an intensive day you could create a schedule which looked at the appropriate period from the previous week, although this would start to take you away from the model of simplicity. And HP do have adaptive flash cache. You can also now filter by volume, so you can have different schedules for specific VV’s within the same CPG and config. Then perhaps another DO job to move it back to the CPG with AO, once the workload drops. But I think there would be a couple of challenges with this approach. First of all DO operations take time, so if it was a larger volume you could be waiting several days for it to migrate to SSD’s and then several days back again. Of course while it was migrating there would be some impact on performance. Secondly remember AO works on regional IO density and so is able to move just the hottest regions to your smaller more expensive high performance tiers. By moving an entire volume you may find that it was only certain regions that truly required the SSD’s and but pushing the rest of the volume also to SSD’s you are effectively wasting space on them. I was mostly thinking about something that would fit completely into SSD, which would imply a small amount of data. I would think that if a 75GB database lun runs super hot one day a week on a schedule, the plan would work. A 10TB one? Not so much. However If you try to force movement based on your own bias, rather than the arrays recorded heuristics then you’ll likely be disappointed ?? As with most things in life its best kept simple Although the AO config is not replicated, so you may find if you fail over to another site it would take a while for AO to optimise the layout of the regions. We have used the default balanced configuration on our 3Par for adaptive optimization on our virtual volumes. We’ve got several volumes now using this config. What would happen if I decided to change the RAID levels on the various Tiers. What would be the impact on the existing volumes in doing this, or can it be done without destroying the data on the volumes. Would I instead have to create a new volume with a new AO config as I want it and then move the date from one volume to another? Existing data on the CPG will remain in the old format. You can try to get all data laid out in the new RAID style by running a tunesys afterwards. I would however say it would be cleaner to create a new CPG, and then to use dynamic optimization to move the volumes over. Then when its the original CPG is empty you would be able to delete it. Dynamic optimization is when you manually choose to move an entire virtual volume between tiers. After running happily for a while I added further SSD disk into my P1000 array which is of a larger size to the original SSD. On the systems screen It shows the SSD as 2 different entries and massively favours the original smaller disk, in fact, when I select an SSD cpg it shows only a small amount of available space left when I know the newer SSD has loads of space. I have’t allocated anything from SSD, it is purely for AO. Any idea how I can make the array view both sizes of SSD as 1 big pool and use accordingly, they are both 150k and the SSD cpg is set to default speed? Cheers. Are you using any filters on CPG? I create CPG on 64 disk SSD and schdule AO 2 tier SSD and FC. Now I am very worry disk SSD 100GB alocate 98. I supended AO. whether I start AO do system occur problem? It is intelligent enough to not move more blocks than there is space available. Specifically, I expect these LUNs to be large (e.g. 4 x 4TB each) so really and truly I can only provision from my Tier 2 initially to accomodate the LUN size I want. I’m wondering whether this is possible and whether there are any issues to doing so as all the recommendations I’ve read so far (including the above) seem to suggest that provisioning should always happen from the middle tier in a 3 tier system (which is not possible in my case). I’ve got no problem with the lun initially being a little slow and then gradually improving over time (as stuff moves up the tiers). As NL disks are often used in tier 2 many companies cannot tolerate the hit of new writes initially going to slow disk. As in your case your new writes will be going direct to 10K disk I would have thought this would be. In summary there is no technical reason not to do this, it’s just if you can accept the slower speed from new writes to 10K disks. Also, the default AO config shows SSD with R1.When you hit this level AO will not move any more data to those disks. DO NOT set a CPG space limit though this is a hard stop and will stop any data being written AO is enabled and is in Performance Mode.Currently this vv is in all the 3 tier’s as per the AO calculation. Are there negative affects to this? Thank you Initial binding was done from NL as it has the most capacity comparing to others. Now the NL utilization is 99, could you confirm if there is any impact?i mean like the VV’s goes to RO as there is no capacity or It will move the data to other tiers?Also I could see the data movement is not happening as like FAST. Is there a possibility to prioritize the data movement? But I would free space or buy more disks ASAP to resolve this issue. If you need it to be more aggressive you can change the mode to performance Learn how your comment data is processed. An alert window appears confirming that Adaptive An alert window appears confirming that the Adaptive Optimization has been changed. An alert window appears confirming that the Adaptive Optimization has been removed. If you want to remove a tier, you should first make sure that there is no VV data on the tier. To do so, set the space limit for that tier to 0. Adaptive Optimization will, over time (it may require multiple iterations), move the data to the other tiers. Once that CPG has no used space, you can then safely remove or change that CPG. The first two charts (. Je pritom snadne propadnout pocitu, ze cloveku nekde ujizdi vlak. V zaplave novych technologii neni jednoduche najit ty podstatne. Prinasime realisticky pohled na to, jake technicke inovace budou v letosnim roce nejvice relevantni z pohledu ceskych spolecnosti. IT trendy a technologie nejen pro pristi rok, ale i nasledujici leta. Prihlasky je mozne podavat pouze do 13. rijna. Zucastnete se i vy! K dispozici je on-line, tistena i elektronicky.Softwarova reseni, urcena pro zajisteni informacnich potreb podniku. vice Vsechny prihlasene pripadove studie najdete ve specialni priloze zarijoveho cisla, ktere lze objednat rovnez v digitalni podobe. vice Znate elegantni sloupove pristroje nebo treba ventilator na USB? Pomuze aplikace VMcom. Changes The material in this document is for information only and is subject to change without notice. Trademarks 3PAR, InServ, InForm, InSpire and Serving Information are registered trademarks of 3PAR Inc. Microsoft, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. All other trademarks and registered trademarks are owned by their respective owners. Federal Communications Commission Radio F requency Interference Statement WARNING: Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment. This device complies with Part 15 of FFC Rules. Operation is subjected to the following two conditions (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. This guide also contains a revision history describing the major changes for each version. 1.4 Organization 3PAR Confidential 3PAR MPIO 1.0.23 Users Guide 1.5 Typographical Conventions This guide employs the following typographical conventions: Typeface Meaning Example ABCDabcd Used for dialog elements When prompted, click Finish to such as titles, button labels, complete the installation.ABCDabcd Used for paths, filenames, Open the file and screen output. \ gui \ wi ndows\ setup. setup. exe 1.6 Advisories To avoid injury to people or damage to data and equipment, be sure to observe the cautions and warnings in this guide. NOTE: Notes are reminders, tips, or suggestions that supplement the procedures included in this guide. CAUTION: Cautions alert you to actions that can cause damage to equipment, software, or data. REQUIRED: Requirements signify procedures that must be followed as directed in order to achieve a functional and supported implementation based on testing at 3PAR. WARNING: Warnings alert you to actions that can cause injury to people or irreversible damage to data or the operating system. MPIO is enabled through third-party storage solutions providers such as 3PAR and supported by Windows 2003. The introduction of Microsoft MPIO has delivered a standard and interoperable path for communication between storage products and the Windows 2003 Server. MPIO is a technology that enables the use of more than one physical path to access a storage device. That is, a single Microsoft Windows host initiator can now see multiple InServ Storage Server host ports when connecting over a SAN environment. If the active path fails, then one of the standby paths is used. This is the default setting. NOTE: Round Robin is the only supported load balancing policy for a quorum disk device within a Microsoft Cluster environment. ? Round Robin with a subset of paths - In this type of load balancing, a set of paths are configured as active, and a set of paths are configured as standby. If all of the active paths fail, one of the standby path is used. If the path with the lowest weight fails, the path with the next lowest weight is used. NOTE: The path with the least weight is the only active path to the device drive. However, the Windows Disk Manager may not be capable of handling such a large number of disks at once. Therefore, it is recommended that you close the Windows Disk Manager application until the Windows Device Manager can see all disk devices. This issue has been addressed in 3PAR MPIO for Microsoft Windows, version 1.0.10. However, for all versions prior to version 1.0.10 of the 3PAR MPIO software, you al l. However, if MPIO is being installed on a system with mirrored disks, the disks appear as failed redundancy. This happens only if disk management applications (that use the dmadmin service) are running at the time of MPIO installation. It is strongly advised that all disk management applications (including but not limited to, di s kmgmt.To prevent the mirrored disks from showing up as failed redundancy please ensure that the dmadmi n service is not running at the time of MPIO installation Special Considerations 3PAR Confidential 2.7 3PAR MPIO 1.0.23 Users Guide 2.8 Special Considerations 3PAR Confidential 3PAR MPIO 1.0.23 Users Guide 3 Installation, Deinstallation and Upgrade In this chapter 3.1 Overview 3.2 3.2 Installing 3PAR MPIO for Microsoft Windows Windows 3.2 3.3 Additional Instructions for Remote Booting 3.9 3.4 Upgrading 3.10 3.5 Deinstalling 3.11 3.6 3PAR MPIO and MSCS Environments 3.13 Installation, Deinstallation and Upgrade 3PAR Confidential 3.1 3PAR MPIO 1.0.23 Users Guide 3.