Filesystem creation during GSI restoration?

[Ken O'Neil]

Problem:
After creating a new logical volume (LV09), extending another (LV04), and installing Oracle 9.2i on an 11.11 system, I created a new GSI of it and updated the impacts statements in the /var/opt/ignite/data config file, using archive_impact tools to generate the impact statements.

During restoration of that GSI, the new LV (lv09:/home/oracle) was missing on the restored system and the newly extended LV (lv04:/tmp 500mb) was restored with its orignal value (200mb). The GSI actually restored completely, but it did not create LV09 and just increased LV08:/home to accept the /home/oracle directory.

Here is what the clause in my INDEX file looks like:
cfg "HP-UX B.11.11 Oracle.92010" {
description "Golden System Image Oracle"
"/opt/ignite/data/Rel_B.11.11/config"
"/var/opt/ignite/data/Rel_B.11.11.Oracle.92010/config"
"/var/opt/ignite/config.local"
}

Questions:
1. Where is the configuration that Ignite uses to re-create the LVs and filesystems. Is it using the defualt in /opt/ignite/data/Rel_B.11.11/config?

2. How does a GSI with a different filesystem layout get restored properly?

3. Where does the updated filesystem layout need to be configured/stored?

Thanks in advance!
-Ken

[Steven E. Protter]

GSI=Golden System Image?

If so, changes in configuration can be done by manually intervening in Ignite install interface. There is a point in the interactive Golden Image or Tape Restore when you can intervent and make changes to the setup from the image you are booting off of.

I commonly keep an image without oracle in it so I add that part during the interactive stage of the install.

If you intend for ORacle data to be moved via Golden Image the image must be taken with make_sys_image with the database down.

SEP

[Ken O'Neil]

Yep, GSI=Golden System Image

Your answer might work, but I'm trying to configure this so it runs unattended.

What do you think about saving a configuration in /var/opt/ignite/saved_cfgs and adding that to the configuration setup in the INDEX file?

[Ken O'Neil]

I tried that but it seems that the /var/opt/ignite/clients/LLA/config.full file takes precedence over the config in /var/opt/ignite/saved_cfgs.

Does anyone know the ranking of of the various configuration files and the order in which Ingite reads them?

-Ken

[Bernhard Mueller]

Ken,

see man manage_index
i.e. you have INDEX/CINDEX files which include statements for config files, and basically I would _assume_ that they are read sequentially and upon igniting a system the config.full is generated.
So I guess your Oracle.9201/config got overwritten by config.local

Verify them (plus the config.full) to see if that's what happened.

Maybe this extract from the manual also helps:

To make configuration file additions to all recovery configurations for a
given client, create a new Ignite-UX configuration file called:
/var/opt/ignite/clients/0x{LLA}/recovery/config.local
For local tapes the file is located in:
/var/opt/ignite/recovery/config.local
This config.local file will automatically be included into your recovery
configuration for this client each time you run make_net_recovery.
(make_net_recovery is run for you when you use Ignite-UX for network
recovery).
If you already have recovery configurations for this client and would like
them to include the config.local file, edit the
/var/opt/ignite/clients/0xLLA/CINDEX file to include a reference to
"recovery/config.local" in all of the configuration clauses.

HTH
Regards,
Bernhard

[Ken O'Neil]

"...they are read sequentially and upon igniting a system the config.full is generated. So I guess your Oracle.9201/config got overwritten by config.local"

Yes, but there are no filesystem layout statements in my config.local (which only contains a timezone, network and a default password that is common to all GSI archives), so it shouldn't effect what Ignite reads in the archive config.

"Verify them (plus the config.full) to see if that's what happened."
config.full is a strange one because it doesn't seem to be used by the client when the volumes and filesystem are created. If I remove the client directory in /var/opt/ignite/clients and start a new restore of a client using bootsys -a, there is no config.full created, but Ignite does create it towards the end of the installation. It seems to be more of a results file (perhaps for use by "Repeat Install") than for an initial installation.

"Maybe this extract from the manual also helps:
To make configuration file additions to all recovery configurations for a
given client, create a new Ignite-UX configuration file called:
/var/opt/ignite/clients/0x{LLA}/recovery/config.local
For local tapes the file is located in:
/var/opt/ignite/recovery/config.local
This config.local file will automatically be included into your recovery
configuration for this client each time you run make_net_recovery.
(make_net_recovery is run for you when you use Ignite-UX for network
recovery).
If you already have recovery configurations for this client and would like
them to include the config.local file, edit the
/var/opt/ignite/clients/0xLLA/CINDEX file to include a reference to
"recovery/config.local" in all of the configuration clauses."

The recovery configuration files you mention pertain to using Network Recovery Archives, however in the scenario I described I'm working with Golden System Images which use a different set of config files.

-Ken