I beg to disagreed with you. Per Legato support "What I have to determine if
this is by design (as I mentioned before an incremental
backup looks at client file index to see what was backed up during a full) or
if this a code defect or possibly an incorrect error
message being generated.
"
-----Original Message-----
From: Craig Ruefenacht [mailto:craig.ruefenacht AT us.usana DOT com]
Sent: Wednesday, April 14, 2004 11:43 AM
To: Legato NetWorker discussion; Ed Skolnik
Subject: Re: [Networker] FW: Incremantal backups in Legato Networker 6.1.4
I hate to disagree, but, from the man page of Legato's "save" command (the
command that does the actual save):
-t date
The date (in nsr_getdate(3) format) by which files must have
been modified for them to be saved. This option is used by
savegrp(8) and savefs(8) to perform scheduled saves by
consulting with the media database to determine the appropriate
time value based on the previous saves for the save set and the
level of the scheduled save.
This is consistent from my post yesterday in this thread, as well as some posts
I made late in 2003 about this (search the mailing
list archives for subject "determing what files to backup based on modification
times" for a in-depth explanation). This almost bit
us because of our setup of using BCV volumes with an EMC Symmetrix and the
timing of our backups in relation to when the BCV volumes
were split.
Legato backups all files that have a modification time that is more recent than
the "-t <date>" argument to the save command (for
incremental saves). Its as simple as that. Legato doesn't do a comparison of
each file's actual mod time to the mod time of each
file in the on-line indexes.
This is for Networker 6.1.x, HP-UX server, HP-UX/Solaris/Linux clients.
It may be different for Microsoft Windows and Novell (we do backup Windows and
Novell, but haven't had the need to experiment to
find out how it behaves in those cases).
On Wed, 2004-04-14 at 10:05, Ed Skolnik wrote:
> Legato compares the date last changed from the client file index
> entry to the UNIX moddate, if the client file index does not exist due
> to exceeding the browse time, it will backup the file.
>
> -----Original Message-----
> From: Anuj [mailto:anuj AT ACE-DATA DOT NET]
> Sent: Tuesday, April 13, 2004 7:03 AM
> Subject: Re: Incremantal backups in Legato Networker 6.1.4
>
>
> Hi,
>
> Any backup application compares the date stamp of last modification
> for each file with the one when it was backed up last time. The file
> contents may not have changed but the change in date stamp indicates
> that it has been modified and therefore needs to be backed up.
>
> Regards,
> Anuj
>
> ----- Original Message -----
> From: "Mariusz Bogumil" <marbo AT TPI DOT PL>
> To: <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>
> Sent: Tuesday, April 13, 2004 3:43 PM
> Subject: [Networker] Incremantal backups in Legato Networker 6.1.4
>
>
> > I've go mysql database (on database each month is created. Updated
> > are
> > only cerrent month databases, others are only historical without
> > update)
> >
> > I've configured Legato Netowrker to do only incremental backups (im
> > my
> > opinion only current month database), but sometimes (I have no idea
> > why) it makes very huge backup. Legato say it's incremantal backup not
> > full (in my opinion it is very similar to full, bacause I've got
> > backed up all files). UNIX ls shows that none of previous months files
> > was changed (but they are backed up).
> >
> > My question is::
> >
> > How Legato Networker that file was changed from last backup and
> > should
> > be included to the current back up.
> >
> > Environment:: Sparc Solaris 8, Legato Networker 6.1.4
> >
> > Regards
> >
> > Mariusz Bogumil
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
