ADSM-L

Re: adsm 16 vs 32 bit

1997-11-14 08:31:41
Subject: Re: adsm 16 vs 32 bit
From: Keith Medcalf <kmedcalf AT DESSUS DOT COM>
Date: Fri, 14 Nov 1997 08:31:41 -0500
In <346C470E.AD1927F1 AT kent DOT edu>, on 11/14/97 at 07:41 AM,
   William Ball <wball AT KENT DOT EDU> said:

>Gee, I guess I didn't realize that my keyboard drawer could have such
>an affect on the ADSM restore. <BG> But I DO realize what the affect
>would be if I were to restore some 16 bit "system" files on a 32 bit
>system from ADSM. Sooner or later those 16 bit clients are going to
>have to upgrade, but I guess that'll have to be sometime other than a
>bare metal restore. It sounds like my simpliest solution is to
>continue to maintain a 16 bit and 32 bit ghost version and a record
>of what pc's are 16 and which are 32 bit so they can be recovered.

The problem is not the client, per se, but the Operating System
version you are trying to back up with it.  I have tried this
(yesterday) and the 16-bit DOS client *will* restore FAT-32 backed up
filessytems to either FAT-32, FAT-16, or FAT-12 (or NTFS or HPFS or
name-a-filesystem) without problems.  What it cannot do, however, is
kludge the Microsoft Long Filenames.

I still think the best solution is to install Win95 in a temp
directory (either a pre-preped minimum install with all LFNs removed)
or directly from CD, and then use the 32-bit client to do all the
restores.

For example, my recovery procedure (the one that actually works
properly) does the following:

  1) Re-format the client.

  2) Boot a DOS 7 (Win 95 startup) disk to get TCP/IP network
     connectivity with PCTCP so you can run the DSMCFTP.EXE client

  3) Restore a "special" recovery image with Win95 in \KICKER (Long
     File Names removed with the LFNBK utility) and including a
     pre-installed ADSM Win32 client.

  4) Reboot the client machine and use the ADSM client to restore the
     original backup (which has win95 in \WINDOWS).

  5) Reset the client (with the RESET button -- no shutdown)

  6) Delete the \KICKER.

This works flawlessly EXCEPT that you have to make sure you re-format
the client hard drive with DOS 7.0 in either FAT-16 or FAT-32 as
appropriate.  You can restore both FAT16 and FAT32 filesystems
interchangeably, though of course the restored system must support the
filesystem type you are using or you will not be able to restart the
system.

A backup made of a Win95 Long File Name filesystem with the 32-bit
client *cannot* always be reliably restored using the 16-bit client,
because the 16-bit client (for DOS) does not support Microsoft's Long
File Name kludge.

Note that this procedure almost duplicates the method you would use to
do a bare metal restore of an NT system running on an NTFS filesystem.
You (obviously) must have an operating system installed and running
before you can do a restore.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Keith Medcalf       (416) 410-5791       http://www.dessus.com/ IBM
OS/2, LAN Server, DB2, TCP/IP, DOS, Windows 95,  Windows NT
 Finger or email kmedcalf-pgp AT dessus DOT com for my PGP Public Key
<Prev in Thread] Current Thread [Next in Thread>