Tacking/Tracing SAN LUN WWID's to Xen Vritual Disks
Greetings,
Problem: Managing SAN luns once they are used by Xen. There does not appear to be an easy way to locate the SAN wwid once it gets handed over to the PVGuest (/dev/xvdc) from the guest side. This becomes a problem when multiple guests and LUN's are created and presented.
Setup: OVM 3.2.1 with 2 Node cluster + Clusterware
2x OEL6.4 -- Para Virtualized Guests
2x OVServers -- Oracle VM server release 3.2.4
For example, I have two PVGuests in a Cluster that share an asm disk, but only PVGuest1 is being presented a separate back-up lun from the SAN :
PVGuest 1
/dev/xvda - local_storage
Problem: Managing SAN luns once they are used by Xen. There does not appear to be an easy way to locate the SAN wwid once it gets handed over to the PVGuest (/dev/xvdc) from the guest side. This becomes a problem when multiple guests and LUN's are created and presented.
Setup: OVM 3.2.1 with 2 Node cluster + Clusterware
2x OEL6.4 -- Para Virtualized Guests
2x OVServers -- Oracle VM server release 3.2.4
For example, I have two PVGuests in a Cluster that share an asm disk, but only PVGuest1 is being presented a separate back-up lun from the SAN :
PVGuest 1
/dev/xvda - local_storage
Tagged:
0