Well, sadly, it looks like updatevv updates the VV_WWN which is super annoying and will in fact change the device path.
--Brett
| HPE Storage Users Group https://3parug.net/ |
|
| updatevv and Solaris MPxIO https://3parug.net/viewtopic.php?f=18&t=99 |
Page 1 of 1 |
| Author: | brett [ Wed Nov 30, 2011 4:49 pm ] |
| Post subject: | updatevv and Solaris MPxIO |
Hey all, This is probably a dumb question but if I use the updatevv command to refresh a snapshot, does the Solaris MPxIO device name changes or will it stay the same? Thanks --Brett |
|
| Author: | brett [ Thu Dec 01, 2011 6:04 am ] |
| Post subject: | Re: updatevv and Solaris MPxIO |
Well, sadly, it looks like updatevv updates the VV_WWN which is super annoying and will in fact change the device path. --Brett |
|
| Author: | tool [ Tue Jun 12, 2012 3:35 pm ] |
| Post subject: | Re: updatevv and Solaris MPxIO |
If you're still around... I only update sets of VVs, so I use this command in a ksh script: updatevv -ro -f set:${VVSET} My WWNs and device paths get preserved on Solaris 10 using MPxIO. Some of the help sections specify that when you create the initial snapshots, you should specify a high-number VV ID. Looks like the array uses the lowest free ID number when anyone creates new volumes/snaps. Combine that with the idea that refeshing snaps temporarily removes the snap VV. Sounds like you don't want those two things happening at the same time. |
|
| Page 1 of 1 | All times are UTC - 5 hours |
| Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |
|