home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.seagate.com
/
2014.07.ftp.seagate.com.tar
/
ftp.seagate.com
/
pub
/
palindrome
/
technote
/
tn9405.asc
< prev
next >
Wrap
Text File
|
1995-03-20
|
14KB
|
400 lines
TECHNICAL NOTE:
PREPARING FOR AND RECOVERING A 3.1a NLM PNA INSTALLATION SERVER
FROM A FULL SERVER CRASH WITHOUT RE-INSTALLING NETWARE 3.12
Document revision: 1.5
Date: 03/14/95
CONTENTS:
SECTION 1.0 - INTRODUCTION
1.1 - ASSUMPTIONS AND REQUIREMENTS
SECTION 2.0 - PRELIMINARY PREPARATION
2.1 - PLAN AND GATHER INFORMATIONAL DOCUMENTATION
2.2 - GENERATE DOS_BOOT AND BACKUP DISKETTES
2.3 - PREPARE NECESSARY FILES FOR RECOVERY DISKETTES
2.4 - CREATE THE RECOVERY DISKETTES
SECTION 3.0 - SERVER RECOVERY
3.1 - RESTORE DOS PARTITION
3.2 - PLACE RECOVERY FILES ON DOS PARTITION
SECTION 5.0 - CONCLUSIONS
***************************************************************************
SECTION 1.0 - INTRODUCTION
This Technical Note covers procedures for rebuilding a PNA installation
Netware server on which the DOS partition and/or the Netware SYS volume
(and other miscellaneous Netware volumes on that server) have been destroyed
and a full recovery is necessitated.
This process does not require Netware to be reinstalled.
This Technical Note covers the steps necessary to:
* Prepare and build the DOS partition.
* Prepare and build any Netware partition.
* Restore server to previous operating state.
SECTION 1.1 - ASSUMPTIONS AND REQUIREMENTS
This procedure assumes the following:
* PKZIP.EXE and PKUNZIP.EXE are available.
* A good understanding of NetWare 3.1x, PNA, and DOS.
* The file server has a high-density floppy drive (the A: drive).
* The user has several blank formatted high-density floppy diskettes.
* The user is using Palindrome Network Archivist NLM 3.1A.
* The file server to be restored is a Netware 3.1x server.
* The C:\SERVER (or equiv) directory will be backed up and
restored as stated in Section 2.2 and Section 3.2 of this document.
By doing so, critical files such as startup.ncf and server.exe
are protected and restored during the DOS partition backup and
restore sections of this document.
* The server's DOS partition has at least 4 MB available.
* PALFCOPY.ZIP, PALUSER.ZIP, PALSDUMP.ZIP has been obtained from
Palindrome's BBS (708-505-3336, 8N1)
SECTION 2.0 - PRELIMINARY PREPARATION
2.1 - PLAN AND GATHER INFORMATIONAL DOCUMENTATION
a) Download PALFCOPY.ZIP, PALUSER.ZIP, and PALSDUMP.ZIP from
Palindrome's BBS (708-505-3336, settings are 8N1). Unzip and
place on your local C drive for easy access during SECTION 2.1,
Step e, and SECTION 2.2, Step a.
b) Review and understand the layout of the server. Is the SYS volume
physically on a separate hard drive compared to the DOS partition?
c) Review and understand the network protocols being used by the
server. (Is IPX and/or IP being used?). How do these protocols
interact with server related issues such as SAPs, ect..?
d) Copy the PALSDUMP.NLM to the server's system directory and run to
gather information about the server's environment, SET parameters,
and NCF files. To run PALSDUMP, from the server console, type:
LOAD PALSDUMP
Print the SYS:\PALSDUMP.DAT output file for reference later on in this tech
note.
Note: PALSDUMP.DAT contains valuable information which includes the
server's autoexec.ncf and startup.ncf files.
e) Either examine the PALSDUMP log file or enter MODULES at the server
console to display the modules currently running on the server.
Evaluate the need for each NLM module and decide whether it needs
to be available during the restoration process. NLMs such as Virus
or CDRom drivers do NOT need to be loaded, but special LAN drivers,
name space NLMs, or config files probably do.
Compare your listing to the file listing located in SECTION 2.3.
If your listing contains any other required files, then you will
need to copy them during SECTION 2.3.
f) At the server prompt (:) through either RCONSOLE or from the
server console, LOAD INSTALL and handwrite the DISK OPTIONS
PARTITION TABLES display. Also document the following volume
information using Install's Volume Options.
__ A. NetWare volumes.
__ B. Volume(s) block size.
__ C. Volume name space support.
(type VOLUMES at the : prompt)
__ D. Server names.
2.2 - GENERATE "DOS_BOOT" and BACKUP DISKETTES
Important note:
Completion of the steps contained within this section are imperative to the
server's recovery. It is within this section that critical server files,
such as SERVER.EXE, STARTUP.NCF ect, are backed up. (and restored from
in case of a disaster)
The server must be brought down to perform this step. In order to restore
the DOS partition to a minimum operating state,(i.e. one in which NetWare
can fully function), the DOS partition(s) needs to be backed up first.
You can use the BACKUP utility that comes with MS-DOS, although other
methods can be used to achieve the same result.
__ Format a boot floppy using the FORMAT A: /S command and copy
FORMAT.COM, FDISK.EXE, RESTORE.EXE, and any other utilities
you feel might be needed. Label it DOS_BOOT
__ From the DOS prompt, enter: BACKUP C:\ A: /S (modify as needed)
and insert as many floppy disks as needed to the DOS partition.
Label these disks as they are made.
__ Repeat step 2b as needed for additional DOS partitions.
__ Run FDISK.EXE and document the information about the DOS
partitions (e.g. sizes, etc). Be sure to record the DOS version,
and do not change DOS versions during this procedure.
2.3 - PREPARE NECESSARY FILES FOR RECOVERY DISKETTES.
__ Make a holding directory named RECOV. This directory can be
located on your local drive or a server volume. This operation
will require about 4 MB of free disk space.
__ Change directories into RECOV
__ From the RECOV directory, type the following commands to create
the following subdirectories:
MD SYSTEM
MD PNA (substitute your specific PNA path here)
Copy the following files into the RECOV\SYSTEM directory.
__ BT40.DSK - or proper SCSI driver (e.g. AIC7770.DSK)
__ BTASPI.DSK - or proper SCSI driver (e.g.ASPITRAN.DSK)
__ Any required name space support modules - from the SYS:SYSTEM
__ ISADISK.DSK - from the SYS:SYSTEM (or equiv) directory.
__ 3C5X9.LAN - from the SYS:SYSTEM (or equiv) directory.
(Or proper NIC driver(s) and their configuration files)
__ ETHERTSM.NLM - from the SYS:SYSTEM
(Or proper topology support modules (e.g. TOKENTSM.NLM))
__ MSM.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ NWSNUT.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ INSTALL.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ CLIB.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ MATHLIB.NLM - from the SYS:\SYSTEM (or equiv) directory (or MATHLIBC).
__ STREAMS.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ AFTER311.NLM - from SYS:\SYSTEM (or equiv) directory.
__ TLI.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ TSA312.NLM - from the SYS:\SYSTEM (or equiv) directory.
(For NetWare 3.11, copy TSA311.NLM instead)
__ SMDR.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ SPXS.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ A3112.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ Any other need modules as determined from section 2.1, step f.
__ PNAPATH.DAT - from the SYS:\SYSTEM (or equiv) directory.
__ PNAREST.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ PALALDRV.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ PALSDRV.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ PALLIB.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ PALFCOPY.NLM - from Palindrome's BBS or your local C drive.
__ PALUSER.NLM - from Palindrome's BBS or your local C drive.
Copy the following files into the RECOV\PNA (or equiv) directory:
__ AS*.PAC - from the SYS:\PNA (or equiv) directory. (2 files)
__ *.RSF - from the SYS:\PNA (or equiv) directory. (2 files)
2.4 - CREATE RECOVERY DISKETTES
__ Have 1 blank formatted diskette (HD 1.44 MB) ready and hand
label it
RECOV3
__ Place the diskette in the A drive and from the RECOV directory,
issue the following command:
PKZIP A:RECOV3.ZIP *.* -rp&
Note: This command will compress the directories and files
contained in the RECOV directory into a zip file named,
RECOV3.ZIP. If needed, this PKZIP command will span two
disks. If so, label the second diskette RECOV3_2.
__ Copy PKUNZIP.EXE onto the diskette, RECOV3.
SECTION 3.0 - SERVER RECOVERY
3.1 - RESTORE DOS PARTITION
NOTE: This section can only be completed if the DOS partition was prepared
for restoration.
a) Insert the DOS_BOOT floppy in drive A: and power on the PC.
b) Enter the date and time when prompted.
c) Using the FDISK and FORMAT utilities, re-generate the DOS
partition(s) (e.g. C: drive).
d) From the DOS prompt, enter: RESTORE A: C:\*.* /S
(modify as needed) and insert the requested floppy disks as needed
to restore the DOS
partition.
e) Repeat step 1d as needed for additional DOS partitions
restorations.
f) Reboot machine to ensure system is bootable.
3.3 - PLACE RECOVERY FILES ON DOS PARTITION
__ On the root of the C drive, make a directory named, RECOV
__ Place the RECOV3 (or last recovery diskette) in the A drive, and
from the C:\RECOV prompt, type:
PKUNZIP A:RECOV3.ZIP -d C:\RECOV
__ Follow the PKUNZIP prompts and unzip the recovery diskettes into
the C:\RECOV directory. If more than one diskette exists, PKUNZIP
should prompt you for both.
Note: This procedure will use about 4MB of disk space.
3.4 - CREATE NETWARE PARTITION(S) AND VOLUME(S)
__ From DOS, run SERVER.EXE and enter the file server name and
internal net address when prompted (See the PALSDUMP printout
of your autoexec.ncf file).
__ From the server console, type SEARCH ADD C:\RECOV\SYSTEM
__ Load hard disk drivers if not already loaded via the
startup.ncf file.
__ Load LAN drivers and bind proper protocols to them.
Reference the autoexec.ncf file found in the PALSDUMP print
out.
__ Type LOAD INSTALL.NLM
__ Choose DISK OPTIONS/PARTITION TABLES to create the Novell
partition according to prepared partition information.
__ After recreating the partitions, choose VOLUME OPTIONS and
press the INSERT key to re-create the volume(s). Again,
reference the prepared documentation from Section 2.1, step f.
__ Press ALT/ESC to change to the server prompt.
__ Type MOUNT ALL
__ Re-define the search path by typing SEARCH ADD C:\RECOV\SYSTEM
__ Load any name space modules (e.g. MAC.NAM) and ADD NAME SPACE
<name> to <volume> for all namespaces on all mounted volumes.
__ Type LOAD CLIB
__ Type LOAD PALFCOPY C:\RECOV\*.* SYS:\ /S
__ Type LOAD TSA312 (or TSA311 for NetWare 3.11)
__ Type LOAD BT312 (or equiv SCSI driver)
__ Type LOAD BTAPSI (or equiv ASPI driver)
SECTION 4.0 - RESTORE DATA
4.1 - RESTORE PALINDROME ENVIRONMENT
Make sure the most recent backup tape is inserted in the backup device.
__ Restore the System Control Database (CDB). From the server
console, type:
LOAD PNAREST /RC
At this point in the recovery process, the only valid user on the server is
SUPERVISOR with NO PASSWORD. Palindrome's control database needs to be
updated with this information. To do so,
__ At the server console, type LOAD PALUSER
Change Palindrome's autologin user to SUPERVISOR
with NO PASSWORD.
__ Restore the Bindery resource's History Database (HDB). At the
server console, type:
LOAD PNAREST /RH <Fileserver name>/BINDERY
4.2 - RECOVER THE BINDERY
__ At the server console, type
LOAD PNAREST /RO /OA <Fileserver name>/BINDERY \*.*
With the "real" bindery restored, Palindrome's autologin user must be updated
once more. This time, to the original autologin user and password. To do so,
__ At the server console, type LOAD PALUSER
Change Palindrome's autologin user back its original
autologin user and password. (example: Archivist with its
appropriate password)
Note: PALUSER.NLM does not create users within the bindery, it simply updates
the autologin user field within Palindrome's CDB. The user and password
presented to PALUSER.NLM must already be valid information within the bindery.
4.3 - RECOVER SYS
__ Restore the SYS Volume's History Database (HDB). At the server
console, type:
LOAD PNAREST /RH <Fileserver name>/SYS:
__ To recover the SYS volume's directory structure, from the server
console, type:
LOAD PNAREST /RD /OA <Fileserver name>/SYS:
__ Once the above operations completes, recover the SYS volume's
file data by typing:
LOAD PNAREST /RO /OA <Fileserver name>/SYS:\*.*
4.3 - RECOVER ADDITIONAL VOLUMES (if needed)
__ If your server contained ONLY a SYS volume, skip to Section 5,
otherwise, please continue.
For each additional volume, from the server console, type:
LOAD PNAREST /RH <Fileserver name>/<volume name>:
__ Once complete, type:
LOAD PNAREST /RD /OA <Fileserver name>/<volume name>:
__ Once complete, type:
LOAD PNAREST /RO /OA <Fileserver name>/<volume name>:\*.*
__ Repeat above steps until all volumes have been recovered.
SECTION 5.0 - Conclusions
Final steps:
When the last restore command is complete, at the server console (:),
__ Type DOWN
__ Type EXIT
__ At the DOS prompt, type SERVER
Your server is now restored to its complete operating state.