1752402 Members
5581 Online
108788 Solutions
New Discussion юеВ

Re: Ignite tape recovery

 
Hofman P A
Occasional Advisor

Ignite tape recovery

Hello,

I restored a Ignite tape which was made with :
/opt/ignite/bin/make_tape_recovery \
-x inc_entire=vg00 \
-P s -I -v -a /dev/rmt/0mn

without any problem.

But, I also want to execute a post command script, when a system was restored.
This script should setup again my mirror.
This /var/opt/ignite/recovery/config.local script was not executed after installation.

What is going wrong?
Where can I find the logfiles?

Thanks in advance.
5 REPLIES 5
Steven E. Protter
Exalted Contributor

Re: Ignite tape recovery

Shalom,

The error is in the normal ignite log files in /var/opt/ignite

If your mirror configuration is correct before you backup ignite and the paths are the same.

You don't need on Ignite 5 and Ignite 6 to do anything special to restore mirroring.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Hofman P A
Occasional Advisor

Re: Ignite tape recovery

Hi Steven,

On the system I just restored,I switch to directory :/var/opt/ignite

/var/opt/ignite -> find .
.
./local
./local/config
./local/hw.info
./local/host.info
./local/manifest
./local/manifest/manifest
./local/manifest/manifest.info
./local/manifest/manifest.oinfo
./local/manifest/manifest.orig
./local/manifest/manifest.seed
./local/manifest/template.def
./local/install.log
./clients
./INDEX
./config.local
./data
./data/Rel_B.11.11
./server
./server/ignite.defs
./server/preferences
./logs
./scripts
./saved_cfgs
./recovery
./recovery/config.local
./recovery/mnr_lockfile
./recovery/latest
./recovery/client_status
./recovery/previews
./recovery/2007-02-07,13:22
./recovery/2007-02-07,13:22/recovery.log
./recovery/2007-02-07,13:22/archive_content
./recovery/2007-02-07,13:22/system_cfg
./recovery/2007-02-07,13:22/control_cfg
./recovery/2007-02-07,13:22/flist
./recovery/2007-02-07,13:22/archive_cfg
./recovery/2007-02-07,13:22/tape
./recovery/2007-02-07,13:31
./recovery/2007-02-07,13:31/recovery.log
./recovery/2007-02-07,13:31/archive_content
./recovery/2007-02-07,13:31/system_cfg
./recovery/2007-02-07,13:31/control_cfg
./recovery/2007-02-07,13:31/flist
./recovery/2007-02-07,08:47
./recovery/2007-02-07,08:47/recovery.log
./recovery/2007-02-07,08:47/archive_content
./recovery/2007-02-07,08:47/system_cfg
./recovery/2007-02-07,08:47/control_cfg
./recovery/2007-02-07,08:47/flist
./recovery/2007-02-07,08:47/archive_cfg
./recovery/2007-02-07,08:47/tape
./recovery/2007-02-07,09:08
./recovery/2007-02-07,09:08/recovery.log
./recovery/2007-02-07,09:08/archive_content
./recovery/2007-02-07,09:08/system_cfg
./recovery/2007-02-07,09:08/control_cfg
./recovery/2007-02-07,09:08/flist
./recovery/2007-02-07,09:08/archive_cfg
./recovery/2007-02-07,09:08/tape
./recovery/2007-02-07,09:08/manifest

No logfile discovered ... of my restored session.

After setting up :config.local

I ran ,

/opt/ignite/binpa/instl_adm -T -f /var/opt/ignite/recovery/config.local

to make sure it was syntax error free.

And I Uncomment the set -x line to enable debug in this script.
Hofman P A
Occasional Advisor

Re: Ignite tape recovery

Steven,sorry.

Found the log.

* Running in recovery mode (os_arch_post_c).
* Executing user specified commands.
vgimport: Physical volume "/dev/dsk/c5t2d1" is not a block special file.
Beginning the import process on Volume Group "/dev/vg02".
vgchange: Volume group "/dev/vg02" does not exist in the "/etc/lvmtab" file.
vgimport: Physical volume "/dev/dsk/c5t2d0" is not a block special file.
Beginning the import process on Volume Group "/dev/vg01".
vgchange: Volume group "/dev/vg01" does not exist in the "/etc/lvmtab" file.
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
vgcfgbackup: Couldn't access the list of physical volumes for volume group "/dev/vg02".
vgcfgbackup: Couldn't access the list of physical volumes for volume group "/dev/vg01".
ERROR: Executing the commands "
/usr/sbin/vgimport -v -m /etc/lvmconf/vg02.mapfile /dev/vg02 \
/dev/dsk/c5t2d1
/usr/sbin/vgchange -a r vg02

/usr/sbin/vgimport -v -m /etc/lvmconf/vg01.mapfile /dev/vg01 \
/dev/dsk/c5t2d0
/usr/sbin/vgchange -a r vg01

test -d /dev/vg00 && /usr/sbin/vgcfgbackup /dev/vg00
test -d /dev/vg02 && /usr/sbin/vgcfgbackup /dev/vg02
test -d /dev/vg01 && /usr/sbin/vgcfgbackup /dev/vg01
" produced a failure.


* Run_Postconfigure_Scripts: Error

After this the system reboots and came Online.

Regards.
Paul
Joelmel Roche
Valued Contributor

Re: Ignite tape recovery

Hi,

You have problem regarding VG import failure.

try this..

Edit the control_cfg file and set the following option to "FALSE":

init _IMPORT_VG = "FALSE"

The recovery ran correctly without failures after this was corrected.
Hofman P A
Occasional Advisor

Re: Ignite tape recovery

Hi Joelmel,

init _IMPORT_VG = "FALSE" works fine !!! Thanks.

I reran Ignite & re-stored this tape.

Run_Postconfigure_Scripts: give now a Warning ....?


* Boot_From_Client_Disk: Complete
* Run_SD_Configure_Scripts: Begin
* Run_SD_Configure_Scripts: Complete
* Run_Postconfigure_Scripts: Begin
* Applying the networking information.
* Running scripts from /sbin/ch_hostname.d
* Applying the timezone: MET-1METDST.
* Applying the root password.
WARNING: The secure root passwd entry already has a password. Will replace.
WARNING: The instance number request for 0/0/1/0 (usb) has a conflicting class
with 0/0/1/0 (ext_bus) - ignored.
WARNING: The instance number request for 0/0/1/1 (usb) has a conflicting class
with 0/0/1/1 (ext_bus) - ignored.
WARNING: The instance number request for 0/0/2/0 (sideba) has a conflicting
class with 0/0/2/0 (ext_bus) - ignored.
* Run all specified post-configure scripts.
* Executing:
"/var/adm/sw/products/EMS-KRMonitor/KRMON-RUN/iux_postconfig".
* Executing user specified script:
"/opt/ignite/data/scripts/os_arch_post_c".
* Running in recovery mode (os_arch_post_c).


* Run_Postconfigure_Scripts: Warning


======= 02/08/07 15:09:10 MET Installation complete: Successful