be_save script failing on aix 5.3

[billo102]

I am trying to do a be_save on aix with the following oslevel 5300-00 and it will not finish properly as it doesn't have enough space in the file system to write, see below


Now I have the same be_save script on another machine with maintenance level 5300-08 with approx same amount of space on the file system where it is saving the info and it saves no problem but i notice that the number of files it is trying to back up is significantly lower see below . I am just trying to figure out why the difference in the number of files ( the systems are a little different but shouldn't be that different)

The savevg command is the same on both
/usr/bin/savevg -f $SAVEDIR/savevg.${vg}.bin -i -m -e -X -p -v $vg

My question is this: given different maintenance levels on the machine would the savevg command be different??


This is in the failing machine
Creating information file for volume group oravg_p..

Creating list of files to back up...
Backing up 109542 files.
0512-005 savevg: Backup Completed.
The backup command completed with errors.
The messages displayed on Standard Error contained additional
information.
######################

This is the succeeding machine
Creating information file for volume group oravg_p.

Creating list of files to back up.
Backing up 32 files
Backing up to /be_save/DRINFO/*********/SYSINFO/090924/savevg.oravg_p.bin.
Cluster 51200 bytes (100 blocks).
Volume 1 on /be_save/DRINFO/*********/SYSINFO/090924/savevg.oravg_p.bin
a 552 ./tmp/vgdata/vgdata.files843984
a 552 ./tmp/vgdata/vgdata.files
a 3449 ./tmp/vgdata/oravg_p/filesystems
a 0 .
a 14511 ./tmp/vgdata/oravg_p/oravg_p.data
a 1225 ./tmp/vgdata/oravg_p/backup.data
a 948 ./tmp/vgdata/oravg_p/fslv00.map
a 24 ./tmp/vgdata/oravg_p/fslv01.map
a 24 ./tmp/vgdata/oravg_p/fslv02.map
a 192 ./tmp/vgdata/oravg_p/fslv03.map
a 204 ./tmp/vgdata/oravg_p/fslv04.map
a 1884 ./tmp/vgdata/oravg_p/fslv05.map
a 192 ./tmp/vgdata/oravg_p/fslv07.map
a 960 ./tmp/vgdata/oravg_p/fslv08.map
a 1404 ./tmp/vgdata/oravg_p/fslv10.map
a 228 ./tmp/vgdata/oravg_p/fslv12.map
a 96 ./tmp/vgdata/oravg_p/fslv13.map
a 96 ./tmp/vgdata/oravg_p/fslv14.map
a 12 ./tmp/vgdata/oravg_p/loglv00.map
a 12 ./tmp/vgdata/oravg_p/loglv01.map
a 0 ./nmon_reports
a 0 ./audit
a 0 ./u02P
a 0 ./u07P
a 0 ./u04P
a 0 ./u03P
a 0 ./interfaces
a 0 ./dba
a 0 ./u06P
a 0 ./u05P
a 0 ./clife_p
a 0 ./u01P
The total size is 26565 bytes.
Backup finished on Thu Sep 24 14:19:51 BST 2009; there are 100 blocks on 1 volumes

 

[p5wizard]

...
Backing up [red]109542[/red] files.
...
Backing up [red]32[/red] files.
...

32 files on one server, more than 100000 files on the other server, no wonder the backup file wants to take up more space...


HTH,

p5wizard

 

[billo102]

YEs this is my point exactly, why does one server only have 32 files and the other 109542 files. There is no way there could only be 32 files on that machine, where is it getting this figure?

 

[p5wizard]

Because one server has filesystems unmounted? Or perhaps the exclude list (you specify -e flag) makes for a big difference in what files are backed up?

Look at contents of /etc/exclude.oravg_p on both servers.


HTH,

p5wizard