make_'disk'_recovery

[David Ledger at Bham]

Anyone know if it's possible to get Ignite to put its recovery data on disk?

If the disk area of the Ignite server that the other hosts do a make_net_recovery to is on the SAN, then the Ignite server could be recovered by presenting that VDISK to a temporary Ignite server, as long as I could do a 'make_disk_recovery' to get the recovery data there in the first place.

I've tried make_net_recovery, but the NFS mounts seem to go away after a bit, and it all hangs.

David

[Steven E. Protter]

Shalom David,

make_sys_image -d

make_sys_image is the actual binary program that make_tape_recovery uses.

Look at the options that make_tape_recovery uses, remove references to tape and add the -d and it will create a tar file where you tell it to.

SEP

[Mridul Shrivastava]

Hardware requirements is enough disk space on a filesystem to hold at least 1.5x the used disk space of the OS and apps for temporary files. For example,if the used disk space for OS and apps is 3 gig, then you need a filesystem with 4.5 gig available to create and hold the final image. This filesystem/directory will be known as the pseudo root.

Make a golden image using make_sys_image.
# /opt/ignite/data/scripts/make_sys_image -l LVL -u -d /DIR -s local
- LVL=image level (1 or 2)
- DIR=pseudo root directory for gzip tar ball image.

Run archive_impact(1M) to create the filesystem usage.
# /opt/ignite/lbin/archive_impact -t -g /DIR/IMAGE

- DIR/IMAGE = path and filename of gzip tar image.

Create a new cfg file to the pseudo root using /opt/ignite/data/examples/core11.cfg as a template.

#cp /opt/ignite/data/examples/core11.cfg /DIR
-Modify line source_type = "DSK"
-Remark out nfs_source + "X.X.X.X:/var/opt/ignite/archives"
-Update impacts using the results from archive_impact.

Run make_medialif(1M) to create the boot sector.
# make_medialif -f /opt/ignite/data/Rel_REL/config \
-f /DIR/core11.cfg \
-f /var/opt/ignite/config.local \
-o ipf -r REL -l /DIR/IPF.lif

- DIR=pseudo root directory.
- REL=OS release (B.11.22 or B.11.23)

Copy EFI_CD_image to pseudo root and run mkisofs to create the CD/DVD iso image.

# cp /opt/ignite/boot/EFI_CD_image /DIR
# mkisofs -U -max-iso9660-filenames -D -o /DIR/cdfs.iso \
-no-emul-boot -b EFI_CD_image -eltorito-alt-boot \
-no-emul-boot -b IPF.lif /DIR

Run instl_combine(1M) to relocate lif headers.

# /opt/ignite/lbin/instl_combine -C /DIR/cdfs.iso

Write the /DIR/cdfs.iso image as a raw file using Open Source software such as
cdrecord or software that comes CD/DVD writers.

[David Ledger at Bham]

Thanks both,

but ...

it wants to dump 42GB!

The -u flag is ignored so it fills the destination.

/var/opt/ignite/recovery/archive_content exists and contains
inc_entire vg00
and /var/opt/ignite/clients/<0xLLA>/recovery/archive_content is the same for that LLA.

The flags for make_tape_recovery and make_sys_image are very different.

Any further info please

David

[David Ledger at Bham]

It seems to me that it is not possible to use make_sys_image to generate an effective level 1 image of all of vg00 only without running the 'find' (internal to make_sys_image) across the entire system.

I can generate a '-f' file that makes it effectively a level 1 of vg00, but it still does the find.

David

[David G Ledger]

Just using this to recover my old login info after the PC died.
David - aka Author