Enclosure Based consistent naming, or OS Native?
Using VxVM 5.0 on Solaris. Intend to upgrade soon. Currently all our servers are using OS Native disk naming:
#> vxddladm get namingscheme NAMING_SCHEME PERSISTENCE LOWERCASE USE_AVID ============================================================ OS Native No Yes Yes
Despite this, the disk names we get are something like "emc0_1234", or "disk_12" depending on what array the server is attached to on the SAN. I assume this is because VxVM will not use the very long WWN disk names that the OS uses.
Problem is, sometimes the servers with the generic "disk_XX" Veritas disk names get all their disks renumbered due to disks being removed from VxVM and from the server. When this happens, the disk groups get all mixed up, and we have to rebuild them from backups. As much fun as it is to rebuild the disk groups, I should probably prevent this from happening again if I can. I think that using persistent enclosure based names will resolve this.
Any reason I should not run 'vxddladm set namingscheme=ebn' on all our servers?
If I remove a disk from a disk group, then remove it from VxVM and finally from the server, will the /etc/vx/disk.info file update?