Re: [Networker] User file deletions between incrementals
2009-10-29 03:50:51
Hello;
When you use recover, it go to the last backup, and in the last
backup, the deleted files in not present. You need use "changetime" or
"version" in recover interface.
You need position between the first backup and the last backup.
Regards;
Arkaitz
----------------------------------------------------------------------
ARKAITZ ABAD URIARTE
Euskal Herriko Unibertsitatea Email: arkaitz.abad @ehu.es
Bizkaiko I.I.S.I.G Tel. : 94 601 8390
----------------------------------------------------------------------
Aurreztu papera. E-posta hau inprimatu beharra daukazu?
Rick Brode <rick AT BRODETRAINING DOT COM> escribió:
When I started teaching NetWorker classes for Legato during the NW
4.x days, I had to verify for myself that deleted files weren't
recovered during a browsable recovery and that renamed files were
recovered only under their final name. Sure enough, that is the way
it worked, supposedly due to information stored in the CFI. For
many years the Legato admin course actually had a lab showing this
behavior.
Yesterday I verified the same proper behavior is still there in NW
7.5.1 (Windows 2003 NW server) with the following test:
1. Create a folder C:\Tester containing "file1", "file2", and "deleted".
2. Do a full backup of a test group containing a client whose save
set list contains "C:\Tester".
3. Delete "C:\Tester\deleted".
4. Do an incremental backup of the test group.
5. Rename "C:\Tester\file2" to "C:\Tester\renamed".
6. Do another incremental backup of the test group.
Firing up NetWorker User and looking in "C:\Tester", the only files
listed are "file1" and "renamed". Thus, the deleted file is not
recovered and the file that was renamed is recovered only under its
final name.
Rick
A Darren Dunham wrote:
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?
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
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
|
|
|