| Title: | NetWorker |
| Notice: | kits - 12-14, problem reporting - 41.*, basics 1-100 |
| Moderator: | DECWET::RANDALL .com::lenox |
| Created: | Thu Oct 10 1996 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 750 |
| Total number of notes: | 3361 |
Hi,
One of my customers has asked if it is possible to recover using
Windows 95 Client 4.2 another Windows 95 clients files. I have looked
through the windows documentation but can't see anything on it.
I have been doing similar recovers using the UNIX version of networker
by specifying the -c option on the recover command to recover other
UNIX machines's data and setting up the
relevant recover access permission on the client setup.
I tried to bluff networker by renaming the old index files from the
client that I need to recover data from and setting up a new windows
95 client to access the renamed index files. This enabled me to browse
the backed up file data but no information on the backup media was
available - "no ssid available for recover" messages given.
The reason for this scenario is that the old windows 95 client was
fully backed up prior to being shutdown and Windows NT 4.0 installed.
Customer now has a need to recover data from the backup made before
NT installation to another Windows 95 client. The NT 4.0 system has
retained the computer name it was allocated when Windows 95 was
installed.
Any ideas ?
Thanks,
Brian McQuillan.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 445.1 | Another bit of info.. | ALERT::BMCQUILLAN | Fri Feb 28 1997 08:15 | 16 | |
I've just installed Networker 4.3 NT intel client on the machine that
was upgraded using the old computer name - I now have access to the
file index's and all the media detail is now available.
Is there something that ties the windows client name to the physical
hardware id on which the software is installed. I;m trying to figure
out why changing another client PC's hostname and connecting to the
index's of another client caused the 'no ssid' error.
I recovered the files that were required but would still like to know
what needs to be done WRT browsing & recovering other windows clients
files or workarounds to do this.
Thanks,
Brian.
| |||||