make_tape_recovery including too many volume groups

[Steve Murphy_3]

Hi,

I am running make_tape_recovery on one of my servers, an RX2600 running 11.23, and am using the -A option.
On my other servers on our site, I am using the -A option, and when make_tape_recovery runs the save_config step, it just includes VG00.
However, on my RX2600, it includes two other volume groups as well as VG00, which causes tape fill problems.
Has anyone else experienced this?

[Peter Godron]

Steve,
please check your
/opt/ignite/recovery/mnr_essentials
file. Are there any non-vg00 files listed ?

Please see:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=679080

[Chan 007]

Hi Steve,

Why not use

"-x inc_entire=vg00 -x exclude=/tmp -x exclude=/var/adm/crash"

something like this. Only vg00 is most important. So avoid taking all in you ignite archive.

Take vg00 in ignite and use normal backup for other vg00.

During failure, use ignite "vg00" to recover and then restore from your normal backup for other 2 vgs.

Chan

[Fabian Briseño]

Hello steve.

yes i have experienced this problem, and my solution was to use the following instruction.
make_net_recovery -Av -x inc_entire=vg00.

This solved my problem.

[Calandrello]

Friend
the commands to effect are in the answers above. ja I used this option and in the hour of restore I had problems therefore the added VG being the VG00 did not come back completely.

[Bill Hassell]

Using the -A option is not recommended since it is not predictable as to which volume groups will be included. The Ignite/UX product is designed to copy and restore the bootable volume group VG00 and while other may be specified, it is not recommended due to efficiency and time requirements, and of course, tape length. It is assumed that you vahe a reasonably-sized VG00 (not 100's of Gb). Use this as your MTR backup string:

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

[Steve Murphy_3]

Thank you all for your responses, and there are several ways around this I can use.
However I am trying to understand why the other volume groups are included. I suspect that there are symbolic links withing vg00 to the other volume groups (though for the life of me I cannot find them).
Does anyone know why using the -A option would cause these VGs to be included as part of the inc_all_affected in the archive_content file under /var/opt/ignite/recovery/2006-12-11,14:50

[Fabian Briseño]

Hello steve.

check your /var/opt/ignite/local/ directory

There you will find the configuration info for your ignite backup.

[Patrick Wallek]

If you read the make_tape_recovery man page, the info for '-A' says:


Based on the files that are specified for nclusion, this option determines which disk(s) and/or volume group(s) contain those specified files, and includes all files from those disk(s) and/or volume group(s) in the archive.


So basically, there are files listed for inclusion that reside in other VGs. As a result the ENTIRE VG that contains those files is included.

Have a look at your file system list and file list and see what is being included. If possible remove those non-vg00 files and filesystems and your problem should go away.

[Steven E. Protter]

Shalom,

My two shekels.

Ignite will not get a clean backup of an open database anyway, so exclude such volume groups. Ignite is as stated best used for saving bootable images. I've used it for system replication with all databases down and that DOES work, but its not practical to take backup s that way.

SEP
More like a shekel and a half.