I have read all the documentation I could find on Shared Storage Pools and I thought it would be awesome to replace NFS mounts with this VIOS feature. However, when I put together a test case for two different LPARs, they were not able to identify when the other LPAR made changes (add/delete files). Additional research found a one-liner that indicated additional software was needed on the client LPARs to perform file management.
I think I am missing the point of this feature!
From my SAN I can already attach a single disk to any number of VIO servers. Is there a future direction to add functionality that will keep the disk in-sync across multiple LPARs?
Pinned topic Shared Storage Pools in VIOS 18.104.22.168 What's the point?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-10-07T10:18:20Z at 2012-10-07T10:18:20Z by SystemAdmin
gcorneau 0100003X4E8 Posts
Re: Shared Storage Pools in VIOS 22.214.171.124 What's the point?2012-10-04T16:03:29ZThis is the accepted answer. This is the accepted answer.The capability you need is met not with Shared Storage Pools, but with GPFS.
To my knowledge, GPFS hasn't been tested with SSP disks yet. It certainly works with shared SAN disks (either via dedicated FC, vSCSI or NPIV).
IBM Power Systems Advanced Technical Skills
Dan_Casale 100000G1QV2 Posts
Re: Shared Storage Pools in VIOS 126.96.36.199 What's the point?2012-10-04T18:29:53ZThis is the accepted answer. This is the accepted answer.Yes, that is what I discovered. I am still looking for the advantage of doing shared storage pools over direct connect.
SystemAdmin 110000D4XK1743 Posts
Re: Shared Storage Pools in VIOS 188.8.131.52 What's the point?2012-10-07T10:18:20ZThis is the accepted answer. This is the accepted answer.
- Dan_Casale 100000G1QV
You're still looking for the advantage of SSP, here is my opinion :
- LPM, Live Partition Mobility is working "out of the box" without the need of your SAN team.
- Snapshot and rollback all backing devices on the Shared Storage Pool, for example I'm using it on rootvg backing device before updating an host.
- Pre zone/mask lun on the SSP an reduce time needed to setup an lpar.
- In the future with VIOS 184.108.40.206 or 220.127.116.11 some nice feature will be added :
- 16 VIO Servers can participate in a shared storage pool.
- Live Storage Mobility : move backing devices between SSP (VMotion Storage like).
You can check my blog post if your are interested in :