Ignite backup hangs server

[ITeam]

Server is an Itanium rx7620 running 11.23 and ignite version c.6.9.150 issued the following command:

make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn

and the system became unresponsive could not kill off ignite backup through the console and ended up issuing a TOC. Has anyone experienced this problem before or know of any issues that caused this? When I look through the Ignite log all looks fine, and it did seem to be working however everyone else's sessions hung, which shouldn't happen normally.

Thanks.

[Steven E. Protter]

Shalom,

Ignite displays a log file. Reboot the system and check the log file.

The most common cause is unsufficient space on the /var filesystem. It also could be a problem with logical volumes.

Ignite is very picky because it wants to be as certain as possible that the image you make is going to be usable.

SEP

[Jaime Bolanos Rojas.]

ITeam,

That looks weird, is this the first time that it happened to you?

First make sure that the system got the latest patches and firmware on it.

If it still does it, you might want to run tusc against the system to see where is it that ignite is hanging the system.

If you get the output or need more assistance with it you might want to open a case with HP.

Regards,

Jaime.

[Fabian Briseño]

Hello.
See if you have a hardware problem look in your syslog file. and do an ioscan on your system.

And like jaime said, check firmware and patches.

[ITeam]

This is the first time they have done an ignite backup since upgrading ignite to version C.6.9.150. /var/has nearly 3 GB of free space so I don't think its that. System doesn't have the september QPKAPPS/BASE bundles installed so I'll install them.

Looking through the ignite log it appears to be hanging when exporting the volume groups to create the mapfiles, it is exporting vg01 - vg01 contains only 1 log volume which is actually on a SAN and is 31TB!!! - even though I explicitly specified just saving vg00, ignite still exports vg01 - could this be the problem, if I state -x exclude /disk2 will this stop this happening?

[ITeam]

Can anyone advise if it is possible to create an ignite image without having to vgexport all other volume groups that reside on the system - I only want an ignite backup of vg00, but vg01 gets exported - can I prevent this from happening? (I tried excludingt he directory mount point of that log vol - but it still exports vg01 to create a map file).

Thanks in advance!

[Coolmar]

I found the following link, doesn't look like it was resolved, but it might help.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1024443

[Coolmar]

Hi again,

Did you try the -x exclude=/dir within your command?

make_tape_recovery -x inc_entire=vg00 -x exclude=/dir -l -v -a /dev/rmt/0m

/dir = whatever filesystems are on vg01 vg02 etc

[ITeam]

Hi there,

Yes I did try the -x exclude=/dir .... it still exports ALL volume groups -even though they aren't included in the ignite backup. I've just tried using include/exclude as opposed to inc_entire=vg00 - and it still exports all volume groups to create mapfiles, even though again these don't get included in the ignite backup. Is there anyway to stop it vgexporting the other volume groups??

[Coolmar]

Try making the tape using the following command. I wonder if the -x include option is causing the problem.

/opt/ignite/bin/make_tape_recovery -Av

Also.../usr is not located on VG01 right? It will include any vg that has the /usr directory.

"The Ignite-UX serverâ s make_tape_recovery command creates a bootable recovery tape for an LVM or whole disk file system while it is up and running. When a system has a logical volume layout, the recovery tape will only include data from the root volume group, plus data from any non-root volume group containing the /usr directory.

You can run make_tape_recovery either on the Ignite-UX server or locally on the system from which you are trying to make a recovery tape.

To create the bootable recovery tape, enter:

/opt/ignite/bin/make_tape_recovery -Av

where: v is for verbose mode and A specifies the entire root disk or volume group. Also, more than one volume group can be specified with the -x option. "

[ITeam]

Closing ticket - the problem is the size of the other logical volume. Solution is to perform an ignite backup out of hours when the system is quiet.