home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.seagate.com
/
2014.07.ftp.seagate.com.tar
/
ftp.seagate.com
/
pub
/
palindrome
/
technote
/
tn9406.asc
< prev
next >
Wrap
Text File
|
1994-12-16
|
21KB
|
527 lines
TECHNICAL NOTE:
NW4.02 SERVER RECOVERY USING PNA v3.1a NLM
VERSION 1.7 as of: 16 Dec 94
TABLE OF CONTENTS
=================
SECTION 1.0 - INTRODUCTION
SECTION 2.0 - PRELIMINARY PREPARATION
2.1 - PLAN AND GATHER INFORMATIONAL DOCUMENTATION
2.2 - GENERATE "DOS_BOOT AND BACKUPxxx" DISK(s)
2.3 - GENERATE "SERVER1" DISK
2.4 - GENERATE "NETWORK" DISK
2.5 - GENERATE "PALINDROME1 DISK
SECTION 3.0 - SERVER RECOVERY
3.1 - TIMESYNC
3.2 - RESTORE DOS PARTITION
3.3 - RESTORE NETWARE PARTITIONS
3.4 - SERVER LICENSING
3.5 - NETWARE DIRECTORY SERVICES (NDS)
3.6 - LOAD SERVER RESOURCES
SECTION 4.0 - RESTORE DATA
4.1 - RESTORE PALINDROME ENVIRONMENT
4.2 - RESTORE PNA HISTORY DATABASES (if needed) AND VOLUME DATA
SECTION 5.0 - CONCLUSIONS
=====================================================================
SECTION 1.0 - INTRODUCTION
This Technical Note covers the general procedures for rebuilding a Netware
server on which the DOS partition and/or the Netware SYS volume (and other
miscellaneous Netware volumes on that server) have been destroyed
necessitating a full recovery. Use this tech note as a template for your
own server recovery procedure. This is a complicated procedure and may
need to be customized to a particular server configuration.
The first step is to read and understand this procedure completely before
attempting it. Additionally, it is advisable that you perform this procedure
on a test server first in order to fine tune it for your server's environment.
This will also give you experience with unexpected issues and problems that
may arise.
This recovery process makes the assumption that the server is protected by
PNA 3.1a NLM and has been backed up recently. It is also assumed the server
to be recovered will retain the same name and volume structure. This procedure
is not intended for server cloning purposes or use with non-managed (EXPORT)
media as this would require different command lines.
Using this procedure, NetWare will not need to be reinstalled. Instead, the
server is brought up in a minimal state which will allow PNA to restore the
server to it's former operating state.
This Technical Note covers the steps necessary to:
* Prepare and build the DOS partition(s).
* Prepare and build the Netware partition(s).
* Restore server to previous operating state (as of last backup).
This procedure assumes the following:
* A good understanding of Novell, Netware Directory Services (NDS),
PNA, DSREPAIR, NWADMIN, NETADMIN, TIMESYNC, and PARTMGR.
* The fileserver 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 fileserver to be restored is a Novell Netware 4.02 server.
* NDS partitions have been replicated according to Novell
recommendations. In other words, either a MASTER or R/W replicas of
the partition which contains the server to be recovered exists on
other servers within the tree.
SECTION 2.0 - PRELIMINARY PREPARATION
2.1 - PLAN AND GATHER INFORMATIONAL DOCUMENTATION
a) Download FLOPCOPY.ZIP and PALSDUMP.ZIP (and optionally SMSTEST.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 and TIMESYNC?
d) Review and understand the structure of your NDS tree and how the
server to be recovered fits into it. Are the NDS partitions
replicated according to Novell recommendations? (3 replicas per
partion). Does the server to be recovered contain a read/write
replica or a master?
Is the ARCHIVIST (or equiv) user object properly configured?
Some things to consider about Archivist are:
Does Archivist exist in the same container as the server?
If Archivist is backing up NDS then it requires supervisor
object rights to the ROOT object. This right will also
allow access to all file system volumes within the tree.
(unless blocked at a sub-level in the NDS tree)
If Archivist is only backing up a server's file system, then
it requires supervisory object rights to the file system's
volumes.
e) 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.
f) 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.4.
If your listing contains any other files, then you will need to
copy them during SECTION 2.4.
g) Document what type of time server this is. Refer to the PALSDUMP
output or at the server console, type:
SET TIMESYNC TYPE
If the server is a PRIMARY, REFERENCE, or SECONDARY time server
type, then no further action will be needed. If the server is
SINGLE time server, then another server in the tree will need to
be desginated as a new SINGLE time server type. This will be
covered in SECTION 3.1.
h) Run the INSTALL.NLM and document ALL information about the netware
partitions and volumes. Pay close attention to the volume names,
volume sizes, block sizes, file compression, sub-allocation, and
migration.
2.2 - GENERATE "DOS_BOOT" and "BACKUPxxx" DISK(s)
NOTE: If the DOS partition does not need protection, skip this step.
The server must be brought down to perform this step. In order to restore
the DOS partition to a minimum operating state that is (i.e., one in which
NetWare can fully function) The DOS partition(s) needs to be backed up.
You can use the BACKUP utility that comes with MS-DOS, although other
methods can be used to achieve the same result.
a) 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
b) 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.
c) Repeat step 2b as needed for additional DOS partitions.
d) 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 - GENERATE "SERVER1" DISK
NOTE: The server might need to remain down from the above step, or as another
option, possibly extract the needed files from the NW4.x install disks/CD.
Format a floppy and label it "SERVER1".
a) Copy onto this floppy (and verify) the following:
SERVER.EXE - from the C:\NETWARE.40 (or equiv) directory.
SERVER.MSG - from the C:\NETWARE.40 (or equiv) directory.
STARTUP.NCF - from the C:\NETWARE.40 (or equiv) directory.
FLOPCOPY.NLM - from the Palindrome BBS) or your local C drive.
SMSTEST.NLM - from the Palindrome BBS) or your local C drive.
PS2SCSI.DSK - from the C:\NETWARE.40 (or equiv) directory
(substitute PS2SCSI drivers for the server's hard disks
e.g. IDE.DSK, etc as needed.)
b) If any of the volumes have any namespaces other than DOS on them,
you will need to copy the .NAM modules (e.g. MAC.NAM) onto the
SERVER1 floppy disk. To see the names spaces loaded on the
server, at the server console, type:
VOLUMES
c) If this is the PNA installation server, copy the appropriate
drivers for your installed SCSI card from the SYS:\SYSTEM
directory.
(or proper locatation) to the SERVER1 floppy.
BT40.DSK - or proper driver (e.g. AIC7770.DSK, etc).
BTASPI.DSK - or proper driver (e.g. ASPITRAN.DSK, etc).
2.4 - GENERATE "NETWORK1" DISK
Format a floppy and label it "NETWORK1" and copy (and verify) the following
files onto the NETWORK1 diskette:
SERVER.MLS - from that server's Netware 4.0x License diskette.
3C509.LAN - from the C:\NETWARE.40 (or equiv) directory or proper
NIC driver(s) and their configuration files, if any.
ETHERTSM.NLM - from the C:\NETWARE.40 (or equiv) directory
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.
DSI.NLM - from the SYS:\SYSTEM (or equiv) directory.
DSAPI.NLM - from the SYS:\SYSTEM (or equiv) directory.
DSREPAIR.NLM - from the SYS:\SYSTEM (or equiv) directory.
EDIT.NLM - from the SYS:\SYSTEM (or equiv) directory.
AUTOEXEC.NCF - 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.
TLI.NLM - from the SYS:\SYSTEM (or equiv) directory.
IPXS.NLM - from the SYS:\SYSTEM (or equiv) directory.
SPXS.NLM - from the SYS:\SYSTEM (or equiv) directory.
TSA400.NLM - from the SYS:\SYSTEM (or equiv) directory.
TSANDS.NLM - from the SYS:\SYSTEM (or equiv) directory.
SMDR.NLM - from the SYS:\SYSTEM (or equiv) directory.
PALSDUMP.DAT - from SYS:\ (or equiv) directory
Include any additional NLM or files that might be needed as determined by
SECTION 2.1, step f (modules review) of this tech note.
2.5 - GENERATE "PALINDROME1" DISK
NOTE: If this server is NOT the PNA installation server, skip this step.
Format a floppy and label it "PALINDROME1". Copy (and verify) the following
files onto the PALINDROME1 disk.
PNAPATH.DAT - from the SYS:\SYSTEM (or equiv) directory.
PNAREST.NLM - from the SYS:\SYSTEM (or equiv) directory.
PNADEV.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.
PALIMP.NLM - from the SYS:\SYSTEM (or equiv) directory.
ASDB.PAC - from the SYS:\PNA (or equiv) directory.
ASNX.PAC - from the SYS:\PNA (or equiv) directory.
ARNANDX.RSF - from the SYS:\PNA (or equiv) directory.
ARNADAT.RSF - from the SYS:\PNA (or equiv) directory.
SECTION 3.0 - SERVER RECOVERY
This part describes the basic steps needed to restore a server.
3.1 - TIMESYNC
a) If the server to be recovered is a time server type of PRIMARY,
REFERENCE, or SECONDARY, proceed to SECTION 3.1.
b) If the server to be recovered is a time server type of SINGLE,
then another server in the tree must be designated as the SINGLE
time server. Locate another server in the tree and at that
server's console, type:
SET TIMESYNC TYPE = SINGLE
NOTE: There can only be one SINGLE type time server within the network.
3.2 - 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 - CREATE NETWARE PARTITION
a) 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).
b) At server prompt (the ":" character) type SEARCH ADD A:
c) Type MODULES at the server console to verify whether hard disk
drivers have been loaded via the startup.ncf file. If not, please
do steps 1 & 2 listed directly below.
Steps:
1) Insert the SERVER1 floppy into the A: drive.
2) Load your disk drivers for each volume.
For example, type LOAD PS2OPT and choose parameters according to NCF files.
(If these drivers are loaded from your startup.ncf file, then this step is
not required.)
d) Insert the NETWORK1 floppy disk.
e) Load LAN drivers and bind the proper protocols to them.
Reference the autoexec.ncf file found in the PALSDUMP print
out.
f) Type LOAD INSTALL.NLM
g) Choose Maintenance / Selective Install / Disk Options /
Modify Disk Partitions and re-create the former Netware disk
partitions according to prepared volume information.
h) Choose Maintenance / Selective Install / Volume Options and
re-create the former server volumes according to prepared
volume information.
i) Mount all volumes.
j) At the server prompt, type SEARCH ADD A:
k) Load any namespace modules (e.g. MAC.NAM) and ADD NAME SPACE
<name> to <volume> for all namespaces on all mounted volumes.
3.4 - SERVER LICENSING
a) From the INSTALL.NLM, choose the License Option and license
the server using the SERVER.MLS file on the NETWORK1 floppy.
3.5 - NETWARE DIRECTORY SERVICES (NDS)
Because the NDS database is located on the SYS Volume, a hard drive crash
involving the SYS volume is equivalent to removing Netware 4.x from the file
server, (besides recovering the volume) you will need to re-install NDS.
This also requires the server be removed and then re-installed into the tree.
To do so proceed to step a listed below:
a) It is imperative to understand how the NDS tree is partitioned
and which servers in the tree contain the replicas. It is also
important to understand which servers contain a master compared
to which servers contain read/write replicas.
b) Using Partition Manager, select the server object in the tree
and record the replicas listed. Be sure to document what type
of replica (if any) the server to be recovered contains. If the
server contains the master of a partition, proceed to step c,
otherwise proceed to step d.
c) IMPORTANT NOTE: If the server to be recovered contains a master
of a partition, you must designate a new master on a different
server within the tree.
Locate another server in the tree which contains an up-to-date
read/write replica of the partition you need to change and run
DSREPAIR. When completed proceed to step d. (Refer to Novell
documentation for proper procedures on how to designate a new
master). When completed, proceed to step d.
d) At this point, the server to be restored should NOT contain a
master of a partition.
e) Use PARTMGR to delete the server object from the NDS tree.
f) Use NETADMIN to delete the volume objects associated
with the server to be recovered.
g) Run INSTALL.NLM to install Directory Services onto the server.
h) From INSTALL.NLM's " Installation Options" menu, choose
Directory Options / Install Directory Services Onto This Server".
i) Select the tree on which the server resided, and then log in to
NDS and re-establish the server into the tree with the same
context that it had before. It is imperative that the server
is placed into the tree exactly as it was before.
j) Install the mounted volumes into the directory tree. From
INSTALL.NLM's " Installation Options" menu, choose Directory
Options / Upgrade Mounted Volumes into Directory". Be sure
to install ALL volumes into the tree.
6 - LOAD SERVER RESOURCES
With the NETWORK1 disk still in the server's A drive,
a) Type LOAD CLIB.
b) Type LOAD IPXS.
c) Type LOAD MATHLIB (or MATHLIBC).
d) Type LOAD TSA400.
SECTION 4.0 - RESTORE DATA
4.1 - RESTORE PALINDROME ENVIRONMENT
If this is not the backup server, skip this step.
a) Insert the SERVER1 floppy disk.
b) Enter LOAD A:FLOPCOPY A:\FLOPCOPY.NLM SYS:\SYSTEM\FLOPCOPY.NLM.
c) Load SCSI device drivers (e.g. ASPITRAN.DSK and AIC7770.DSK).
d) Insert the PALINDROME1 floppy disk.
e) Type LOAD FLOPCOPY A:PNAPATH.DAT SYS:\SYSTEM\PNAPATH.DAT.
* f) Type LOAD FLOPCOPY A:ARNADAT.RSF SYS:\PNA\ARNADAT.RSF.
* g) Type LOAD FLOPCOPY A:ARNANDX.RSF SYS:\PNA\ARNANDX.RSF.
* h) Type LOAD FLOPCOPY A:ASDB.PAC SYS:\PNA\ASDB.PAC.
* i) Type LOAD FLOPCOPY A:ASNX.PAC SYS:\PNA\ASNX.PAC.
* NOTE - The directory name, \PNA, should be used as an example only.
Substitute your own specific PNA directory name and path in its place.
4.2 - RESTORE PNA DATABASES (if needed) and VOLUME DATA:
Make sure the most recent backup tape is inserted in the backup device. If
any of these operations yields a PLSM-53, verify the SMDR/TSA400 have been
properly loaded. If PLSM-110 occurs, this indicates the AUTOLOGIN user or
password defined in the current set of Control Databases (AS*.PAC) does not
have login rights to the server through the SMDR/TSA400.
a) Verify the PALIDROME1 diskette is in server's A drive.
b) If this is the backup server, restore the System Control Database
(CDB). From the server console, type:
LOAD PNAREST /RC
c) If the volume databases are not available, restore the SYS:
Volume History Database (HDB). At the server console of the
backup server, type:
LOAD PNAREST /RH <Fileserver name>/SYS:
For additional server volume HDBs, from the server console, type:
LOAD PNAREST /RH <Fileserver name>/<volume name>:
d) Restore the contents of the SYS: volume, from the server console,
type:
LOAD PNAREST /RD /OA <Fileserver name>/SYS:
LOAD PNAREST /RO /OA <Fileserver name>/SYS: \*.*
e) For add'l server volumes, type:
LOAD PNAREST /RD /OA <Fileserver name>/<volume name>:
LOAD PNAREST /RO /OA <Fileserver name>/<volume name>:\*.*
SECTION 5.0 - CONCLUSIONS
Final steps:
a) After server restoration is complete, verify your NDS partitions
are replicated properly according to Novell's recommendations.
b) Verify the time server type is correct on the recovered server.
Note there can only be one SINGLE time server type on the network.
c) Verify the recovered server's time is synchronized on the network
by typing TIME at the server console.
d) If the recovered server contains partition replicas or a master,
verify the server's synchronization state. To do this, at the
server console, type the following commands:
SET DSTRACE=ON
SET DSTRACE=*H
Toggle to the directory services screen and check it for the
message "ALL processed=YES" for each partition on the server.
e) When the last restore command is complete, at the server console,
type the follwing commands:
DOWN
EXIT
f) At the DOS prompt, type SERVER
Your server is now restored to its former operating state.