vxvm:vxprint error when doing Ignite make_recovery

[Robert Milne]

Hello all,

When creating an Ignite-UX recovery tape using make_recovery (or more correctly make_tape_recovery on 11.11) I get the following error a few times during the process:
vxvm:vxprint ERROR: IPC failure: Configuration daemon is not accessible.
Even though the error appears, the recovery tape does appear to get created OK. I have not actually tried to do a system recovery from it, but before I do I would like to understand the message just in case I get half way through the recovery process and the whole thing turns to jelly; because of something wrong on the tape.
Does anyone know what causes this error and how serious it is in this process ?

Thanks, any help appreciated.
Rob.

[harry d brown jr]

run check_recovery against your tape

live free or die
harry

[Robert Milne]

Harry, thanks.

I did try running check_recovery, which doesn't work if you have used (I did) the newer, suggested option in 11i called make_tape_recovery. Interestingly there is no -C option in this to create a recovery status file; so I don't know what HP suggest here. So I went back to do the older make_recovery with the -C.
This is what the system says when running make_recovery:
make_recovery(103): The make_recovery command will be replaced by make_tape_recovery. Both commands are supported in this release (Ignite-UX Revision 3.2). Please read the man page make_tape_recovery(1M) for usage of the new command. In a future release, make_recovery will be replaced by a script that calls make_tape_recovery.

So make_recovery runs, I still do get the same error as before at:
*** Previewing only ***
vxvm:vxprint: ERROR: IPC failure: Configuration daemon is not accessible
vxvm:vxprint: ERROR: IPC failure: Configuration daemon is not accessible
vxvm:vxprint: ERROR: IPC failure: Configuration daemon is not accessible
etc.

However process does get to the end OK and I got a "System Recovery Tape successfully created" so I assume it is OK.
I then ran the check_recovery that says:
"No system changes that would require the creation of a new
System Recovery Image were detected." which is true, but this only checks the system against the recovery status file for config. changes, not against the tape. So I guess you can't actually verify the tape ?!

Rob.

[T G Manikandan]

Hello,
The HPUX11i uses Base VERITAS Volume Manager 3.1 which is now the default volume manager
Execution of Multiple VxVM Commands Failure
Multiple simultaneous invocations of VxVM commands (for example,vxprint) may result in the following error message and produce no output:vxvm:vxprint: ERROR: IPC failure: Configuration daemon is not accessible
This is due to the command getting a Connection Refused (Error code
ECONNREFUSED) error when attempting to connect to the volume daemon
while performing the requested transaction.
Retrying the command works in most cases. If the error persists, make sure
that the volume daemon is actually running with a "vxdctl mode" command.

#vxdctl mode
to see the status of the operating system mode whether it is enabled ot not.
#vxdctl enable
Just check the man pages of vxdctl.

Thanks
G Manikandan

[Sanjay_6]

Hi Robert,

Take a look at the thread below for more info.

http://us-support.external.hp.com/cki/bin/doc.pl/sid=5ae42bd20f60b14cb2/screen=ckiDisplayDocument?docId=200000056262881

Hope this helps.

thanks

[Patrick Wallek]

It looks like you have gotten some good responses on your VxVM problem. I'm not addressing that.

I want to clear up a misconception about the -C option to make_recovery.

When you run a make_recovery with the -C option, it creates a status file (/var/opt/ignite/recovery/makrec.last) as a part of its actions. See 'man make_recovery' for more info.

When you then run check_recovery, it DOES NOT check the integrity of your make_recovery tape. It does not even look at the tape drive. What check_recovery does do is: "...compares the current state of the system to the System
Recovery status file (created by the last invocation of make_recovery) to determine if a new System Recovery Tape needs to be created." For more information see 'man check_recovery".

Now, you are correct in that the '-C'optoin is not included in the make_tape_recovery command. I recommend against using the '-C' option anyway. Reason 1: It adds a significant amount of time to the make_recovery process because it has to create the status file. Reson 2: I see no reason to check and see if you need to make another make_tape_recovery tape. If you think you need to make another tape, you probably do. I have the job scheduled to run every Sunday afternoon on all my machines.

[James R. Ferguson]

Hi Robert:

From the Technical Knowledge Base (#UIUXKBRC00007875):

/begin_quote/

PROBLEM
Running make_recovery produces the message:

vxvm:vxprint: ERROR: IPC failure: onfiguration daemon is not accessible

There are no VxVM disk groups configured on the system.

Ignite version is B.3.3.116.

Why is this happening?

RESOLUTION

With newer verisions of Ignite, make_recovery is aware that the VxVM product is installed. It will attempt to re-integrate the disk groups back onto the system after the recovery. Per the make_recovery man page:

VxVM disk groups not included in the disk groups managed by VERITAS Volume Manager (VxVM) cannot be included in the Ignite-UX archive. If they are included, make_recovery will error out. Those disk groups will be left
undisturbed and re-integrated to the system after the recovery is complete.

The above error indicates that the VxVM product is installed, but not configured. The vxconfigd daemon is not running and the vxinstall command has probably not been ran to
configure a disk group. The options are to either run vxinstall to set up a disk group or swremove the VxVM product if it's not being
used. The product numbers are:

B7961AA B.03.10.6 Base HP VERITAS Volume Manager 3.1
B9116AA B.03.10.6 HP VERITAS Volume Manager 3.1

/end_quote/

Regards!

...JRF...

[Eileen Millen]

After the archive is done, you can check the contents of the tape. The tape has to be rewound first and then skipped forward past the first fileset which is the LIF area. An index can be listed by using the pax command listed below.
mt ???t /dev/rmt/0m rew
mt ???t /dev/rmt/0mn fsf
pax ???vf /dev/rmt/0mn

The tape can also be listed and files can be extracted by using the tar command.
mt ???t /dev/rmt/0m rew
mt ???t /dev/rmt/0mn fsf
To list the contents of the tape:
tar ???tvf /dev/rmt/0mn
To extract a directory of a file:
tar ???xvf /full_path_to_file_or_directory

Eileen