fbackup problem

[RAJESH GANGADHARAN]

Hi
We are facing a problem while taking backup using"fbackup".
Using NFS we are mounting filesystems of sunmachine on a HP machine
and taking the backup using fbackup. the problem is, we are
mentioning the options for incremetal backup but insted of taking
an incrementel backup, it is taking a full backup every time.
can any one give some solution for this

Thnnks in adv.
Raj

[Steven Sim Kok Leong]

Hi,

You may like to show us your graph file. Note that subdirectories have to be explicitly excluded in your graph file eg.

i /usr
e /usr/lib
e /usr/bin

If /usr/lib and /usr/bin are not explicitly excluded, the /usr backup will encompass all the child subdirectories.

Hope this helps. Regards.

Steven Sim Kok Leong

[RAJESH GANGADHARAN]

Hi steven,
Thanks for the immediate response, here is some more input.
i /pk29_ntl
i /pk29_nvapp
e /pk29_etsi
i /pk26_navbas
i /pk26_ntllnsus
i /pk26_ntllncor
i /pk26_navloads
i /pk21_ntl
i /pk39_ntl
i /var/mail
i /pk18_trs2
i /pksun_ntl
i /pksun_ntlprj
e /pk16_ntlcat
e /pk16_lnptest
e /pksun_ntl/OMS1.7/oracle/oradata/control

above shown is the map file. Except /pksun_ntl , /pksun_ntlprj filesystems , all the other filesystems incremental backup is happening. but a full backup of above mentioned filesystems are taking even if we are giving the option for incremental backup.

Thanks in adv
Raj

[Animesh Chakraborty]

Hi,
Are you scheduling fbackup using SAM?
What is your OS version?


<<<cron utility in order to perform scheduled backups. In order for
fbackup to perform and incremental backup, two things must be true:
1) A full backup must have been performed, and 2) The same graph file
must be used for the full and the incremental backup.

The problem here is that SAM creates each scheduled backup using a
different, and/or new graph file.

The resolution is the modify the crontab entries that SAM creates in
the root users crontab file. You must modify the graph file on the
incremental backup job to match that of the full.

The first step is to copy the current root crontab file to a
temporary file to be modified.

% cd /usr/spool/cron/crontabs
% cp root root_file

This crontab file that SAM creates/modifies may appear like the following.
Note that the name of the graph files are different (slightly).

00 22 * * 5 /usr/sam/backup/backauto.scr MAG FULL y /dev/rmt/0m
/usr/sam/backup/grapha01499 root #sambackup
00 22 * * 1-4 /usr/sam/backup/backauto.scr MAG PART y /dev/rmt/0m
/usr/sam/backup/graphb01499 root #sambackup
^^^^^^^^^^^^^
Now you should modify the graph file for the Incremental backup to match
the full. The entries would then appear as follows:

00 22 * * 5 /usr/sam/backup/backauto.scr MAG FULL y /dev/rmt/0m
/usr/sam/backup/grapha01499 root #sambackup
00 22 * * 1-4 /usr/sam/backup/backauto.scr MAG PART y /dev/rmt/0m
/usr/sam/backup/grapha01499 root #sambackup>>>>>>>>>>
^^^^^^^^^^^^^

[Steven Sim Kok Leong]

Hi,

I agree with Animesh that you have to use the same graph map files for both full and incremental fbackups.

If you are already using the same graph map files, are the filesystems /pksun_ntl, /pksun_ntlprj by any chance nfs-mounted? Check that you run fbackup with the -n option because by default fbackup does not cross NFS mount points, regardless of paths specified by the -i or -g options.

Hope this helps. Regards.

Steven Sim Kok Leong

[Animesh Chakraborty]

FYI.
http://us-support3.external.hp.com/cki/bin/doc.pl/sid=3a2d51f50112bccff4/screen=ckiDisplayDocument?docId=200000024615166

[RAJESH GANGADHARAN]

First of all we are not using SAM, but command line, and it is not a cron job.
OS versions are HP UNIX 10.20
SUn Solaris 7
while taking fbackup -n option is included for NFS mounts, hence no issues with command options.
-Raj

[Steve Steel]

Hi

It must be something like this.

SUMMARY:

P: Customer uses incremental backup for his file system with nfs-mounted
file system. The first full backup works well. But the next day the
incremental backup stores all files on the nfs-mounted filesystem
even when they didn't change. This incremental backup works as
expected on the non nfs-mounted system.

S: On the nfs-server was a cron which stored all files with cpio in the
night. But cpio changes the inode modification time. So the fbackup
on the nfs clients backups all files on the nfs mounted file system
because the inode-modification time changed. This is the reason
why it looks like that fbackup does a full-backup instead of
incremental on the nfs-mounted filesystem.



Is there anything on the sun which could change the mtimes.


Steve Steel