Because FLAR is not part of the Volume Manager/Storage Foundation stack I have to emphasize that Oracle would be the best source for information regarding concerns over FLAR image generation.
Regarding root disk encapsulation and how this might impact FLAR image generation, the make considerations that need to be made are as follows:
1. System disk has been modified to have two additional partitions, one with tag 15, indicating a VM private region database, and a second with tag 14 which should span the complete disk.
If FLAR stores disk partition information this will impact the image.
2. Encapsulation modifies the /etc/vfstab table, pointing the root, opt, var, and other system partitions (if separate from the root partition) towards Volume Manager volumes, rather than underlying slices. The FLAR image will most likely store this modified vfstab file, and as a result modification will be necessary on target systems.
3. Encapsulation also modifies the /etc/system file, including two entries which load and establish the root volume image for use during boot-time. This need to be considered as well when generating a FLAR from an encapsulated system.
Your best option for determine specific steps necessary for your environment would be to request clarification from specialists with FLAR imaging in regards to the above considerations for optimal results.
- Nathan Buck
