home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
adsmboot.zip
/
README
< prev
Wrap
Text File
|
1996-01-07
|
7KB
|
173 lines
Warp Connect - ADSM 1.2.7 Disaster Recovery Disks
Description:
This command file will create the necessary disks to boot OS/2
with TCPIP loaded and ADSM command line functionality. The main
purpose is to allow total system restore from an ADSM backup,
although any ADSM functions can be performed.
This procedure was created for Warp Connect and ADSM 1.2.7.
Overview:
The Rexx script will create two boot disks - one for A: and one
for B: - and a third (post-boot) disk. When you boot, you will
place both boot disks in their respective drives and leave them
there during the boot process. Once you are at a command prompt,
you will replace the disk in drive A: with the third diskette.
From this diskette you will configure your TCPIP (IFCONFIG,
ROUTE), perform hard disk maintenance (FDISK, FORMAT), and run
ADSM restore functions.
The diskette in drive B: contains all the DLLs and TCPIP
PROTOCOL files which are required during boot as well as all
after-boot activity. It is required that this disk remain in
drive B: for the duration of your recovery session.
After the boot process is complete and you replace the A: boot
disk with the third disk you will need to type "SETUP" to
configure TCPIP. The SETUP.CMD file on this disk is copied from
your \MPTN\BIN directory, and has one line added to it which is
normally contained in your \MPTN\BIN\MPTSTART.CMD (which
normally runs SETUP.CMD). This added line is INETWAIT. You can
always compare this SETUP.CMD file to the one on your hard disk,
or if you are using these disks on a different machine, edit it
to match the SETUP.CMD on that machine. This is the file which
contains the IP and router address.
At this point you may FDISK, FORMAT and execute ADSM line
commands such as
DSMC QUERY FILESPACE
to gather volume names prior to formating your local drive so
that you can get your labels to match what you plan on
restoring (remember that volume names must match or you can't
restore). And
DSMC RESTORE C:* C:* -SUBDIR=YES -REPLACE=YES
to restore your drive(s). Or
DSMC RESTORE d:\DESKTOP\* -SUBDIR=YES
To restore your desktop.
The file CONFIG.DSM with this package is used to create
config.sys, and these ADSM commands are contained in this file
as remarks. If you boot up and forget the ADSM commands, you
can always TYPE config.sys to the screen to get a hint.
Installation:
You will need three blank disks to start. (Of course, if you
forget, you can always pop open another window to get them ready
:). Of those three disks, two should be for drive A: and one for
B:
You will need to edit the "ADSMBOOT.CMD" and modify the first
few variable assignments. These assignments tell the script
- The name of your ethernet adaptor driver.
- Which drive the OS2 system directory is located.
- Which drive the IBMCOM directory is located.
- Which drive the MPTN directory is located.
- Which drive the TCPIP directory is located.
- The full drive and path of your ADSM installation.
The drives/paths are used for copying files to the diskettes, so
it is imperative that you ensure these assignments match your
system.
The name of your ethernet adaptor is used 1) to copy the correct
file to diskette, and 2) to place the 'DEVICE=' statement in the
config.sys.
The ADSM drive/path assignment is used 1) to copy the needed
ADSM executables to diskette, and 2) to pick up your current
DSM.OPT file.
A few notes about this process:
Normally during boot, Warp Connect runs MPTSTART.CMD which
executes INETWAIT and then runs SETUP.CMD (which contains your
IP address, Router address, etc.) When creating the boot disks
your SETUP.CMD will be copied from \MPTN\BIN to the third
diskette and the INETWAIT command will be added to it. Thus,
when the diskette boot is complete, you will simply run
SETUP.CMD to configure your TCPIP. You can always edit
SETUP.CMD and compare it against an existing SETUP.CMD (such as
to use these disks on a different machine), but always remember
that INETWAIT is required and is normally executed in
MPTSTART.CMD prior to SETUP.CMD being invoked. Adding INETWAIT
to SETUP.CMD is just a kludge to keep the configuration in one
exec for this boot disk process.
Due to space constraints, and need for constant availability,
the PROTOCOL files are placed on drive B:. This requires that
"SET ETC" in the config.sys is set to drive B:, and that the
PROTMAN statement is set to look for its protocol file on drive
B:. Do not make any changes to the generated config.sys file in
this area or your TCPIP will fail.
A plain vanilla config.sys is used for the generated boot disk.
The hard drive .ADD file is echoed into the config.sys at the
top, and the ethernet adaptor DRIVER= statement is echoed in at
the end. If a SCSI drive application is required, it should not
be difficult modify the script to accommodate that.
Alternativly, it might be easier to generate the boot disks for
IDE, and then modify the generated disks for SCSI by deleting
the IBM1S506 file, adding the SCSI .ADD file, and editing the
config.sys accordingly.
Using Generated Diskettes On Other Workstations:
If you generate diskettes and wish to use them on another
workstation, you will need to edit SETUP.CMD to reflect the
other workstation's \MPTN\BIN\SETUP.CMD (be sure to retain the
INETWAIT which we add to mimic \MPTN\BIN\MPTSTART.CMD). You
will also need to edit the DSM.OPT to reflect the other
workstation. If the other workstation uses a different ethernet
adaptor, you will also need to 1) edit the config.sys to reflect
that adaptor and 2) copy the .OS2 file for that adaptor to the
B: diskette.
Limitations:
1. No nameserver definitions are present, so it is required that
the DSM.OPT file contain the dotted decimal address to the ADSM
server. The third disk contains TEDIT, so you can always edit
your DSM.OPT if you need to make this change at the last moment.
2. The script used to generate the disks is _VERY_ crude. It
does no error checking, and is designed to be used only with IDE
hard drives, non-Micro Channel hardware, and 3C507 (ELNK16)
ethernet adapters. The script is written in a straightforward
manner, and anyone needing to generate diskettes for SCSI hard
drives, Micro Channel hardware, or different adaptors should
have no problem adapting it for their needs. Feel free to email
acus10@email.mot.com for assistance.
3. It is required you have two floppy drives, and that A: be
1.44 meg in capacity. Drive B: may be 1.22 meg.
4. The files copied to diskettes, and their hard disk locations,
are based upon Warp Connect. The script will not operate on
Warp, Warp Fullpack since filenames and locations are different
in Warp Connect. Don't email me for help with non-Connect
applications since I don't understand the difference and I don't
have access to non-Connect Warp.