Re: [Networker] Recovering renamed directories

Are you using the change journal or relying on the archive bit?

I cannot duplicate your issue with a Windows 2K3 host and a Windows 2K3
server running Networker v7.1.3 and I use the change journal.

--Shawn


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Voetelink D.
Sent: Friday, September 29, 2006 4:05 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Recovering renamed directories

Hi,

Last week we needed to do a recovery of an entire drive of a windows 
system, because microsoft's SMS had wiped it clean.

So we started networker user, selected the drive and started to recover. 
For this it needed a full and a couple of incrementals.
After the recover was complete some users complained that not all files 
were there. With the 'change browsetime' option we were able to recover 
the files/directories.

The problem seems to be in directories which have been renamed/moved in 
the period between the full and the last incremental.

to reproduce:

See the following structure:

E:\
   map1\
     file1.txt
     file2.txt
   map2\
     file3.txt
     file4.txt

Now do a full backup of E:

- Now rename map1 to map1a
- Create a new file 'file5.txt' in map1a
- Create a new directory 'map3' and move 'map2' to 'map3'

This means the structure has become:

E:\
   map1a\
     file1.txt
     file2.txt
     file5.txt
   map3\
     map2\
       file3.txt
       file4.txt

Now do an incremental backup of E:

Now start the 'networker user', choose 'recover' and choose E:.
You'll see map1a and map3. This was the situation of the last 
incremental backup, so far so good.
However if you select map1a, you'll notice that only file5.txt is 
visible and selectable. file1.txt and file2.txt are not selectable.

Also map3 is without content, buth map2 should be in there.

the command line tool 'recover' has the exact same problem. I tried 
different versions of client and server software, all with the same 
problem.
Also Linux clients seem to have the exact same problem.

This way it's impossible to do a reliable restore of the last situation, 
because there are files missing!

And there I was, thinking the purpose of backup software was to be able 
to do a reliable recovery. What was I thinking?!? ;-)

Any thoughts anyone?

greetings,

Dennis


-- 
*******************************************************************

D. Voetelink
UNIX Systems Administrator

Energy research Centre of the Netherlands
Facilities Department - Automation Services

Petten, Netherlands

e-mail : voetelink AT ecn DOT nl
phone  : (+31) 224 564738

*******************************************************************

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
wit 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
wit 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