how can I restore the VG ?

[Nail Wang]

a server rp8400,and have 2 disk 18G,and now we want to enlarge to 36G ,and used make_recovery,but it only can recovery the VG00,the system have 2VG,/VG00, /oradata ,the 2 disk in /oradata on the EMC used for Oracle,and now how can I restore the VG /oradata ?

[Trond Haugen]

You would like to look into vgexport and vgimport with a mapfile. And make a note of the HW path to the disks.

Regards,
Trond

[Michael Tully]

If you create your make_tape_recovery tape it will also have the LVM information for your other volume groups.
All you would need to do, is create the OS on the new disks from the the make_recovery tape and the rest will be automatic.
This is the best way to do this.

Create the tape: make 2 tapes
# make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn (make sure you use the no-rewind device)

Change the disks, restart your system and boot off your tape.
Once the system has rebooted the rest of your system should be available including the oracle VG.
Keep the old disks just in case until after the whole system has been proved ready.

[Michael Tully]

All this is assuming the disks you are replacing are the internal disks for the operating system and nothing else. As a precaution, and as suggested, do a vgexport in preview mode just in case. Keep the file on another system.

e.g.
# vgexport -m vg00.mapfile -p -v /dev/vg00

[Nail Wang]

the VG /oradata maked by ORACLE engineer ,used oracle command ,and maked in Character Device,I warry about the data on EMC ,can not fit the vg used vgexport.

[James R. Ferguson]

Hi:

If I understand correctly, you are going to use Ignite's make_tape_recovery to reinstall your current 18GB vg00 onto a 36GB physical volume. That's a very sound decision.

In this case, 'vgexport'/'vgimport' mapfiles will automatically be contructed for your non-vg00 volume groups; i.e. those holding your Oracle data as a separate volume group with physical disk in an EMC2 SAN.

When the Ignite recovery process runs, it will automatically 'vgimport' the non-vg00 volume groups using the map files it originally created. Your non-vg00 volume groups will thus "reappear" with all their data intact without you doing anything, unless the hardware paths to the EMC2 SAN changed as a result of the "cold-installation". In that case, you need only to invoke a commandline 'vgimport' with the mapfiles ('/etc/lvmconf/vgMM.mapfile') Ignite created and the correct pv_paths. See the man pages for more information.

Regards!

...JRF...

[John Meissner]

Here is a solution:

http://bizforums.itrc.hp.com/cm/QuestionAnswer/1,,0xb1235bd3782dd711abdc0090277a778c,00.html

I've tested this script at leaset a dozen times and it works like a charm. it only requires a VERY small ammount of work after it runs.....

[Nail Wang]

Summary:
Disk at hardware path 1/0/8/0/0.1.19.0.0.0.0 : Software configuration
error


Description of Error:

The device was unsuccessful in processing the current request message
because the message contained an invalid field in the command data block.
The request was not processed.

Probable Cause / Recommended Action:

The error most likely indicates that the device is not fully supported by
the current driver. This may or may not cause a problem in the operation
of the device.






here is the error,after do the vgimport