Ignite cloned system, /var "used space" less than original

[Masaki Birchmier]

I created a make_recovery tape with the -A option. This backups up everything in the root volume group. (I only have 1 volume group)
When I brought the cloned system up, the used space of /var was ~32 Mbytes less than the original.

Is this normal? Does ignite not backup some files in /var even with the -A option?

Masaki

[A. Clay Stephenson · Accepted solution]

This difference could easily be (and almost certainly is) /var/tmp, var/spool, /var/mail - transient files.

[Cheryl Griffin]

Check the make_recovery logs. Sparse files could make up the difference. Or it could be the difference between essential files and non-essential files.

Check what was written to the logs.
/var/opt/ignite/logs/makrec.log2 contains all files that were written to tape. Check makrec.log1 for errors.

make_recovery is going to be obsoleted in favor of make_tape_recovery and make_net_recovery. You may want to make sure you have an updated version from:
http://www.software.hp.com/products/IUX/

Cheryl

[Martin Johnson]

If you interact with the recovery, which is what you usually do when you are cloning, ignite does not restore everything. The "missing" file were usually in /var/tmp, and /var/spool.

With earier versions of ignite, some of the config files would be replaced with templates, which could cause problems (like DNS resolution not working properly).

HTH
Marty

[John Bolene]

also /var/opt/perf/datafiles, /var/adm/syslog

all those files are meaningless on another machine

[Masaki Birchmier]

I think I know what happened. I ran "bdf" "during" the make_recovery process.
I'm sure there were active temp files for the make_recovery process which increased the size of /var.

When I checked the size of /var on the original system "after" make_recovery, the size matched up to the new system.

Thanks everyone for your input,
Masaki