- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- Re: Newly created AO policy is keeping space on Ti...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2019 08:32 AM - edited 03-25-2019 08:45 AM
03-25-2019 08:32 AM - edited 03-25-2019 08:45 AM
Hello everyone,
I have a newly created AO policy which is going to only be using FC and NL. I create the CPG's / AO and a single VLUN. It is set for Cost.
The creation of the VV was 6TB but checking the AO policy, it is keeping the space all on FC and has not moved it to NL, even though the VLUN has no active data on it. Also the AO policy is set to only use 500G of FC space. IOPS min is set for 50, is this why the fully provisioned 6TB VV is not being moved down to NL?
https://i.imgur.com/C39sWrc.png
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2019 08:52 AM
03-25-2019 08:52 AM
Solution
@MBLVS wrote:... the VLUN has no active data on it. ... IOPS min is set for 50, is this why the fully provisioned 6TB VV is not being moved down to NL?
Look at the task details after the scheduled AO job runs. You should see a message about the volume's average IOPS being low enough to preclude further data movement.
Question: If you want the bulk of the volume kept on NL, why not change the volume's CPGs to use NL and then use Dynamic Optimization to tune the volume to NL? After that, once there is activity, AO can move the "hot" parts up to FC.
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2019 09:21 AM - edited 03-25-2019 09:25 AM
03-25-2019 09:21 AM - edited 03-25-2019 09:25 AM
Re: Newly created AO policy is keeping space on Tier 2?
Forgot all about Tuning it!
I did a new schedule and just put the IOPS min to 0 and it appears it is moving data now, at 41G moved down to NL.
But tuning it may be a quicker option.
Recomendation I was told from HPE was to never create a new VV on a NL CPG, and always create it on FC?
I presume in this case, this would be an exception since we are trying to keep most data on NL anyways...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2019 09:57 AM
03-25-2019 09:57 AM
Re: Newly created AO policy is keeping space on Tier 2?
I haven't looked at the latest options for tuning via SSMC. With the tunevv command line, note the -src_cpg option to move just the parts of the volume still on FC. No reason to have it fiddle with the parts already moved to NL.
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company