Nope. The ctime changes every time the inode itself changes. Thus, the
very act of resetting the atime changes the
ctime to the current time. The only way to backup without affecting the
inode is to read the blocks of the filesystem
directly rather than going through the filesystem interface (this is how
dump works.) The ctime cannot be modified,
or if it can, the change is not persistent since it is immediately updated.
--PLB
At 05:48 PM 12/20/2001 +0100, Jonas Blåberg wrote:
>Thanks for the quick and correct answer. When having something to search
>for I found this:
>http://www.eng.auburn.edu/pub/mail-lists/veritas-users.Nov98/msg00011.html
>
>But shouldn't it be possible for the netbackup client to first reset the
>atime, and then reset the ctime also?
>
>/jonas
>
>
>
>
>-----Ursprungligt meddelande-----
>Från: Larry Kingery [mailto:larry.kingery AT veritas DOT com]
>Skickat: den 20 december 2001 17:25
>Till: Jonas Blåberg
>Kopia: veritas-bu AT mailman.eng.auburn DOT edu
>Ämne: Re: [Veritas-bu] netbackup changing ctime of files
>
>
>When NetBackup backs up a file, that changes the atime. The ctime is
>changed when NBU resets the atime to it's original value.
>
>See USE_CTIME_FOR_INCREMENTALS and DO_NOT_RESET_FILE_ACCESS_TIME for
>info on changing the atime and not the ctime
>
>=?iso-8859-1?Q?Jonas=5FBl=E5berg?= writes:
> > hello!
> >
> > It seems like the Solaris Netbackup client is modifying the inode for
> > some reason, and that the ctime timestamp is therefore changed. Is there
> > any way to get around this?
> >
> > We are using tripwire to trace changes of files, but the tripwire logs
> > are rather useless when every file exists in them.
> >
> >
> > Is NetBackup changing the inode when resetting the atime?
> >
> > /jonas
> >
> >
> > Jonas Blåberg
> > Cell Network Sverige AB
> > Kruthusgatan 17,6
> > S-411 04 Göteborg
> > jonas.blaberg AT cellnetwork DOT com
> > @office: +46-(0)31-707 69 85
> > not@office: +46-(0)709-95 00 68
> >
> >
> >
> > -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
> > <HTML>
> > <HEAD>
> >
> > <META NAME="Generator" CONTENT="MS Exchange Server version 6.0.5762.3">
> > <TITLE>netbackup changing ctime of files</TITLE>
> > </HEAD>
> > <BODY>
> > <!-- Converted from text/rtf format -->
> >
> > <P><FONT SIZE=2 FACE="Arial">hello!</FONT>
> > </P>
> >
> > <P><FONT SIZE=2 FACE="Arial">It seems like the Solaris Netbackup client
> is modifying the inode for some reason, and that the ctime timestamp is
> therefore changed. Is there any way to get around this?</FONT></P>
> >
> > <P><FONT SIZE=2 FACE="Arial">We are using tripwire to trace changes of
> files, but the tripwire logs are rather useless when every file exists in
> them.</FONT></P>
> > <BR>
> >
> > <P><FONT SIZE=2 FACE="Arial">Is NetBackup changing the inode when
> resetting the atime?</FONT>
> > </P>
> >
> > <P><FONT SIZE=2 FACE="Arial">/jonas</FONT>
> > </P>
> > <BR>
> >
> > <P><FONT SIZE=2 FACE="Arial">Jonas Blåberg</FONT>
> >
> > <BR><FONT SIZE=2 FACE="Arial"> Cell Network Sverige AB</FONT>
> >
> > <BR><FONT SIZE=2 FACE="Arial"> Kruthusgatan 17,6</FONT>
> >
> > <BR><FONT SIZE=2 FACE="Arial"> S-411 04 Göteborg</FONT>
> >
> > <BR><FONT SIZE=2 FACE="Arial">jonas.blaberg AT cellnetwork DOT com</FONT>
> >
> > <BR><FONT SIZE=2 FACE="Arial">@office: +46-(0)31-707 69 85</FONT>
> >
> > <BR><FONT SIZE=2 FACE="Arial">not@office: +46-(0)709-95 00 68</FONT>
> > </P>
> > <BR>
> >
> > </BODY>
> > </HTML>-
>Larry Kingery
> Of couse, I could be wrong.
>_______________________________________________
>Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
