Re: [Networker] User file deletions between incrementals
2009-10-29 17:28:29
On 30/10/2009, at 07:59 , George Sinclair wrote:
Dag Nygren wrote:
torsdag 29 oktober 2009 01:59:26 skrev A Darren Dunham:
On Wed, Oct 28, 2009 at 05:59:06PM -0400, George Sinclair wrote:
Hmm ... I was always under the impression that this was not the
case, at
least not with a browsable recover. I thought the whole point of a
browse recover was that NW was supposed to be able to rebuild the
directory, or file system, exactly the way it last appeared, so
it ought
to remove deleted files since the deletion of files gets updated
in the
client index, assuming, of course, that they were ever backed up.
In the old days, this wasn't possible. An unmodified file
wouldn't be
backed up in an incremental saveset, so the server couldn't
distinguish
between "not modified" and "deleted". Where is the image of the
filesystem kept that would show file deletions?
What happens here is the Networker tracks the changetime of the
directory (which will change by a deletion in the POSIX compliant
setups). If changed, the directory info was backed up again in its
new form. In Windows this has been a problem as Windows doesn't
seem to consider a deletion of a directory a change :-( and that
generated a problem in some versions of Networker. Should work fine
in the more recent Networkers though.
Same thing with a unchanged but renamed file BTW.
On a related note - and one gotcha to keep in mind - at least with
Unix, anyway, is that when you move a directory (/bin/mv dir1) it
doesn't change the file status times on the constituent files or sub-
directories, only the directory itself (dir1), so this is all NW
records in the index. As a result, until the file status times
change on the constituent data or a level full is run, that data
will not get backed up. This obviously won't happen, however, if
someone moves a specific named file because it would get its file
status time updated. NW incrementals back up files based on change
of file status time since the last incremental. Fulls of course get
everything.
Actually, that's not quite the reason in NetWorker.
In NetWorker it was a "by choice" design feature - only the directory
had changed, not the files in the directory, so only the directory got
backed up.
This was known to be confusing for some time, and in NetWorker 7.5
they introduced the client attribute "Backup renamed directives" ...
it's unchecked/disabled by default, but when checked/enabled, if a
directory is moved or renamed, then NetWorker will backup the contents
as well as the directory.
The old behaviour was for Windows as well as Unix, as is the above
change.
Cheers,
Preston.
--
Preston de Guise
"Enterprise Systems Backup and Recovery: A Corporate Insurance Policy":
http://www.amazon.com/Enterprise-Systems-Backup-Recovery-Corporate/dp/1420076396
http://www.enterprisesystemsbackup.com
NetWorker blog: http://nsrd.wordpress.com
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
|
|