make_tape_recovery completed with warnings,why ?

[amirwap]

#[/]make_tape_recovery -Av
* Creating local directories for configuration files and archive.

======= 04/03/09 09:04:36 EAT Started make_tape_recovery. (Fri Apr 03
09:04:36 EAT 2009)
@(#) Ignite-UX Revision C.6.1.44
@(#) net_recovery (opt) $Revision: 10.672 $

* Testing for necessary pax patch.
* Passed pax tests.
* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = /dev/rmt/0mn

* Number of Archives to Save = 2

* Pax type = tar


In? dsk/vg name minor# Associated disks/mountpoints
2 v /dev/vg00 0x00 /dev/dsk/c2t1d0s2 /dev/dsk/c3t0d0s2
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2
/dev/vg00/lvol4 /tmp 2
/dev/vg00/lvol5 /home 2
/dev/vg00/lvol6 /opt 2
/dev/vg00/lvol7 /usr 2
/dev/vg00/lvol8 /var 2
/dev/vg00/weblogic /weblogic 2
/dev/vg00/lvswap
/dev/vg00/webapp /webapp 2

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2009-04-03,09:04/system_cfg vg00
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg00.mapfile /dev/vg00

* Creating Control Configuration.
* Creating Archive File List
* Creating Archive Configuration

* /opt/ignite/bin/make_arch_config -c
/var/opt/ignite/recovery/2009-04-03,09:04/archive_cfg -g
/var/opt/ignite/recovery/2009-04-03,09:04/flist -n 2009-04-03,09:04 -r
64 -d Recovery\ Archive -t -i 1 -m t
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Tape Archive
* Checking configuration file for Syntax
Adding /opt/ignite/Version file to LIF.
* Writing boot LIF to tape
71274+0 records in
71274+0 records out
* Complete writing boot LIF onto tape.
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/0mn -t n -s
local -n 2009-04-03,09:04 -m t -w
/var/opt/ignite/recovery/2009-04-03,09:04/recovery.log -u -R -g
/var/opt/ignite/recovery/2009-04-03,09:04/flist -a 20800640

* Preparing to create a system archive.

* Archiving contents of via tar image to local device/dev/rmt/0mn.
* Creation of system archive complete.
NOTE: The following files are in the list of files that were on the
system, but they are no longer present. These files are not
included in the backup:
/var/tmp/hsperfdata_root/18533
/var/tmp/ign_configure/make_sys_image.log
/var/spool/cron/tmp/croutYDOa01926
/weblogic/bea/user_projects/domains/pcs_csb/myserver/myserver.heur.1032.tlog
/weblogic/bea/user_projects/domains/pcs_csb/myserver/myserver.1032.tlog

WARNING: There was a problem with the list of files/directories to archive.
Input: /var/opt/ignite/recovery/2009-04-03,09:04/flist
The following line(s) had too few/incorrect entries:
Problem lines:
line: 12 webapp/csb/ 40700 1141352684 96 0
NOTE: Could not read the /etc/resolv.conf file.
* Cleaning up old configuration file directories

======= 04/03/09 10:27:35 EAT make_tape_recovery completed with warnings
You have mail in /var/mail/root

[Torsten.]

There were some temp files present during the start of backup, but already deleted during the backup - don't worry.

You probably don't have a /etc/resolv.conf file - check this.

[Taifur]

Hi amirwap,
Some files deleted during backup but backup completed properly.

Rgds,
Taifur

[Basheer_2]

Hello,

warning is:
NOTE: Could not read the /etc/resolv.conf file.

as you can see it could not read /etc/resolv.conf

check ls -ls /etc/resolv.conf
you may get these errors:
1) when the files are being modified at the time it tried to backup that file

2) some temp files being created by apps/dbs and later on removed

/etc/resolv.conf is an very important file for DNS resolutions. (basically it has 5 entries)

if you are not using DNS, its OK.

[Michal Kapalka (mikap)]

Hi,

NOTE: Could not read the /etc/resolv.conf file.

- that's normal if you dont resolv hostnames from DNS server but with the /etc/hosts, this is normal warning message, you can simply ignore.

- if you test the hostname resolving

nslookup, yo will see similiar output

kmspsdev:/mikap>nslookup
Using /etc/hosts on: kmspsdev


Michal

[Bill Hassell]

None of the messages is a problem -- the backup will be OK. However, there is an invalid file or directory name:

line: 12 webapp/csb/ 40700 1141352684 96 0

You'll need to locate this directory, then check each pathname with ll -db. The b option will show non-printing characters including spaces. Trailing or imbedded spaces in filenames can cause some application and shell difficulties, but the backup will be OK. Rename the offending name and the next Ignite backup should be warning-free.

[Fabio Ettore]

Hi,

just like an additional note not directly about your warnings on make_tape_recovery as it was already indicated they're not a problem.

I see you're using make_tape_recovery -Av, which means including all files from /opt/ignite/recovery/mnr_essentials or /var/opt/ignite/recovery/mnr_essentials. It doesn't mean including all files and directories of vg00, like was -A on make_recovery.

This just is a note to suggest being sure to check what mnr_essentials contains before of continuing with use of -A on make_tape_recovery. I often saw customers using -A on make_tape_recovery who think it has the same goal to get included everything of vg00, instead you can get exactly the same beahviour of -A on make_recovery by using -x inc_entire=vg00 on make_tape_recovery.

If you knew that before then just ignore my note ;)

HTH.

Best regards,
Fabio

[Jeeshan]

check the NOTE and WARNING messages as you posted.

[Steven E. Protter]

Shalom,

This can happen on a system that is busy and rapidly changing during the backup.

I would schedule a recovery test in the lab and run through the motions of using the image pretend before needing it.

SEP