BACKUP PROBLEMS VERITAS FILE SYSTEM

BACKUP PROBLEMS VERITAS FILE SYSTEM

Post by Chris Thom » Wed, 09 Apr 2003 23:26:32



We are having problems will our backup on our E3500 (solaris2.6). We
backup to a StorEDGE L280 device.

We are running a script that it supposed to do a full backup at the
weekend (sunday) and an incremental backup  from monday through to
sunday. We are running veritas file system ver. **.  As far as I am
aware this has never worked and does a full backup everynight.

The backups are taken via ufs and vfs. The reason being for this is
that vfs doesnt back up ufs filesystems (or atleast the the
verion we have doesnt).

The problem is that the data increase on the server means we can no
longer do a full backup everynight so, we need to get the incremental
backup working.   The vfs command for running the incremental backup
appears to be correct. E.g. /usr/sbin/vxdump 1ulbf 96 $TAPE $dir |&
grep v and yet even when you run the command manually it still
does a full backup.  Is there a problem with Veritas File Syetm?

 
 
 

BACKUP PROBLEMS VERITAS FILE SYSTEM

Post by Anthony Greau » Thu, 10 Apr 2003 03:22:53



Quote:> We are having problems will our backup on our E3500 (solaris2.6). We
> backup to a StorEDGE L280 device.

> We are running a script that it supposed to do a full backup at the
> weekend (sunday) and an incremental backup  from monday through to
> sunday. We are running veritas file system ver. **.  As far as I am
> aware this has never worked and does a full backup everynight.

What is the exact command you use ?

Quote:> The backups are taken via ufs and vfs. The reason being for this is
> that vfs doesn’t back up ufs filesystems (or atleast the the
> verion we have doesn’t).

> The problem is that the data increase on the server means we can no
> longer do a full backup everynight so, we need to get the incremental
> backup working.   The vfs command for running the incremental backup
> appears to be correct. E.g. /usr/sbin/vxdump 1ulbf 96 $TAPE $dir |&
> grep –v and yet even when you run the command manually it still
> does a full backup.  Is there a problem with Veritas File Syetm?

As far as I knowthere is not.

The reason why full backups are done may reside in the fact that even if you
think that files were not modified, they were.
I mean that they were not really modified, i.e their content did not change,
but the inode time (mtime) has been changed.

Try the following command with some of your files that must not be backuped
but are :
# truss -vlstat -tlstat ls -l <Your_file>

What is the mtime of your file ?
If it changes day after day, so here is the reason why full backups are
done. A script or an applicative may change the mtime of a file.
We observed this behavior with some firewalls or with home-made scripts.

HTH,
Anthony