ADSM-L

client restore fails trying to replace files that don't exist

2003-11-10 18:29:45
Subject: client restore fails trying to replace files that don't exist
From: Roger Deschner <rogerd AT UIC DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 10 Nov 2003 17:29:22 -0600
I'm having a client problem that has gotten me stumped. (And that takes
some doing.)

The client node is Windows ME. The hard drive crashed, they got a new
one, and reinstalled WinME from the original install CD. They started
with an old V3.7 client program when this issue first started, but I
since upgraded them to the latest WinME client, V5.1.6. It didn't help.
(Our server is AIX TSM 5.1.6.5)

The owner of this node decided against doing a total full "bare metal"
restore, and is instead restoring whole directories containing his
documents.

On several occasions, restores are failing like this:

They open the GUI client, and navigate to a directory they want to
restore. They click on it, and click Restore. They leave the default
"Original Location" selected. It begins to issue a series of
"File/Directory already exists" and "File is read/only" error messages.
No matter how many times you tell it that it's OK to Replace, and "Apply
action to all remaining files", it gets stuck asking this question on
the SAME FILE over and over.

I was called to this person's office to diagnose it. They are doing
nothing wrong that I can see. The files and directories being complained
about indeed do not exist yet. I looked carefully in Windows Explorer,
after being sure to turn on Windows Explorer's options to show hidden
files, and show known file types.

I have seen this kind of thing once before, long long ago, and I thought
it was fixed several releases ago. Both client and server are now
up-to-date. Has anybody else seen this?

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu

<Prev in Thread] Current Thread [Next in Thread>