How to Recover an Ibrix Logical Volume (ILV)

another example used at Discover e-Legal is as follows:
pvcreate --restorefile /etc/lvm/backup/ivg22 --uuid OfVkK7-RsRj-hXdr-rx8j-VTD5-
wHH7-Is8AYk /dev/emcpowerz -ff
You will be asked:
Really INITIALIZE physical volume "/dev/mpath/mpath2" of volume group
"ivg2" [y/n]? y
Where the --uuid # above comes from the backup ivg#.date_file under the PV
section which is the first of the 3 ids in the file
here is the line to grab the --uuid# from
i.e.
pv0 {
id = "r0JdHv-9o4A-YZar-zL7e-m3to-urgf-pu41L2"
device = "/dev/mapper/ibrixpath01" # This is a Hint Only!!
Trouble Note: If the pvcreate --restorefile bombs out for some reason i.e. the pv 0
uuid is persistantly invalid because raid was reformated, then you just do the
following and then execute the mkibfs and ibrestitch the name space:
#/usr/sbin/pvcreate -ff --uuid r0JdHv-9o4A-YZar-zL7e-m3to-urgf-pu41L2
/dev/emcpowerz
#/usr/sbin/vgcreate ivg22 /dev/emcpowerz
#/usr/sbn/vgdisplay ivg22
[take note of the PE and PE total size number and use it in lvcreate -l <PE#>
below]
#/usr/sbin/lvcreate -l 56789 --name ilv22 ivg22
*now skip right to running mkibfs in procedure below*
When pvcreate --restore file works without error you now run:
#/usr/sbin/vgcfgrestore -f "path_to_filename" -n ivg# ivg#
NOTE: make sure lvm now sees the /vg/lv in lvmdiskscan, vgscan and lvscan
*You will be mkibfs-ing and doing an ibrestitch at this point if the above steps did
not recover the ilv metadata
Running mkibfs and restitching your namespace:
While the FS is UNMOUNTED; From the FM use ibrix_umount –f fsname to
unmount the fs from servers and clients