|
Re: [Networker] User file deletions between incrementals
2009-10-30 11:12:41
Mathew Harvest wrote:
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On >Behalf Of Preston de Guise
Sent: Friday, 30 October 2009 7:25 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] User file deletions between incrementals
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
.
.
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.
The only problem with this behaviour is that if a directory gets
renamed/moved and only the directory gets backed up/no record of its
containing files, when you perform a restore of that directory only
files that have changed will be recovered, not the entire directory, to
recover the files that have not changed you have to browse to a time
before the rename find them in the old directory name (this behaviour is
present in windows not sure about other OS's, but I suspect so) - but as
Preston said there is a workaround in 7.5.1, and they were supposed to
be completely re-writing the file broker for 8.0 but who knows when that
will arrive - perhaps its in the upcoming 7.6 release ...
That's a nice feature - having the option to implement on a per client
basis, anyway. Just hope that someone doesn't go out and move 10 TB of
data to another directory without letting you know in advance!!! Of
course, the same thing could happen in previous releases wherein someone
changes the permissions on 10 TB of data, affecting a change of file
status times - the default action for initiating incrementals.
However, on a related or rather earlier note, let's suppose I remove a
file after it's been backed up. My understanding of the client index is
that NW should update the index to reflect that the file has been
removed, and I'm pretty sure this is the case even with older 7.2.x
releases. So, if the file is backed up, removed and a subsequent
incremental is run, and you browse to that date/time, you shouldn't see
the file. The problem with this, however, is that this information is
only recorded in the index, so as long as you're running incrementals,
the information will remain in the index, but at some point won't it go
away, or will it only get truncated when another full is run?
George
Cheers,
Preston.
--
Preston de Guise
"Queensland celebrates its 150th anniversary in 2009. Check out
what's on today at www.q150.qld.gov.au."
********************************* DISCLAIMER
*********************************
The information contained in the above e-mail message or messages
(which includes any attachments) is confidential and may be legally
privileged. It is intended only for the use of the person or entity
to which it is addressed. If you are not the addressee any form of
disclosure, copying, modification, distribution or any action taken
or omitted in reliance on the information is unauthorised. Opinions
contained in the message(s) do not necessarily reflect the opinions
of the Queensland Government and its authorities. If you received
this communication in error, please notify the sender immediately
and delete it from your computer system network.
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
--
George Sinclair
Voice: (301) 713-3284 x210
- The preceding message is personal and does not reflect any official or
unofficial position of the United States Department of Commerce -
- Any opinions expressed in this message are NOT those of the US Govt. -
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
|
|
|
