Ignite-UX shows large archive size

[Igor Sovin]

Hi!

How does Ignite-Ux estimates archive size? I wonder how is it possible to have such summary:

* The archive is estimated to reach 35116340 kbytes.
* Free space on /var/opt/ignite/recovery/arch_mnt
after archive should be about 0 kbytes.

I use command make_net_recovery -s lev.snos.ru -x inc_entire=vg00

here is my bdf output:
bdf |grep vg00
/dev/vg00/lvol3 327680 205680 121064 63% /
/dev/vg00/lvol1 327680 220280 106600 67% /stand
/dev/vg00/lvol8 34045952 2154464 31658648 6% /var
/dev/vg00/lvol7 3276800 2409944 861096 74% /usr
/dev/vg00/lvol4 1048576 780648 266808 75% /tmp
/dev/vg00/oracle 2064384 370240 1680952 18% /oracle
/dev/vg00/oraclestage
/dev/vg00/lvol6 2523136 1825864 691992 73% /opt
/dev/vg00/install 5144576 1233464 3880568 24% /install
/dev/vg00/lvol5 32768 27768 5000 85% /home
/dev/vg00/depot 1048576 126707 864254 13% /depot

after calculating used space on vg00 I dont get such large size as Ignite-UX does.
Where did I go wrong?

[Luk Vandenbussche]

Igor, is this a bdf off the server lev.snos.ru?

The ignite image is on this server.

[Igor Sovin]

No, it is bdf of the client machine

[Sandy Chen]

Hi Igor,

Are you sure you didn't miscalculate?
/var -> 31 GB
/install -> 3.8 GB

These 2 mountpoint has the size 34.8 GB. I think the archive estimation make sense.

regards,
Sandy

[Igor Sovin]

Hi Sandy!

it is the size of available free disk space, isnt it?
but the used space:
/var -> 2154464
/install -> 1233464


I think I do not understand something..

[Bill Hassell · Accepted solution]

Part of the problem is that non-OS filesystems are located on the vg00 volume. That's why it is recommended never to put data and application directories on VG00. You want to isolate the OS from the rest of the system. The mountpoints that should not be in vg00 would be:

/oracle 370Mb
/install 1233Mb
/depot 127Mb

These 3 mountpoints currently occupy more than 1700 megs. There are also very large temp directories that may need to be cleaned:

/var 2154Mb
/tmp 780Mb

But there may be a large amount of sparse data files which appear to use very little space even though the file contains millions of records (most of which are empty). This is another reason to keep the database files on a separate volume.

Here's a way to view the distribution of space in the /tmp and /var directories:

du -kx /var | sort -rn | head -20
du -kx /tmp | sort -rn | head -20

The largest directories will be sorted to the top of the list. Use this command to see the largest files in a specific directory:

ll /var/tmp | sort -rnk5

You might also include the -v option for make_net_recovery to watch the progress of the archive process.

[Igor Sovin]

I've excluded /oracle
/oracle/stage
/depot
/install

from backup, but the archive file size that Ignite calculates still over 30Gb.