Does anyone know where this number is stored or hidden inside Linux, Device Mapper mpio config, bindings, files?

Each virtual disk or LUN on a SAN is assigned an long unique number called a UID or WWID world wide ID.

Example 6006-0160-9A30-1B00-50D2-9BA6-1626-DF11

If I build a boot disk to this device everything works fine. If I restore or clone this disk to a new one during a backup recovery test the new lun is identical in every way except it has a brand new unique UID

Example: 6006-0160-9A30-1B00-50D2-1330-1555-DF11

Now Linux will boot to the new lun just fine as long as I disable MPIO or multipath by editing the fstab and pointing things back to being a single path device. However this is not acceptable.

I spoke with a number of collegues and many people are aware of this issue but do not know a solution. I'm tried to move/edit/change the multipath config and bindings file and nothing works.

Something about that new UID is throwing Device Mapper off. Since I cannot change that UID at the storage array hardware level I need to isolate what location inside the OS needs to be changed-updated.

Any ideas or help greatly appreciated.

DougStorage