home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.seagate.com
/
2014.07.ftp.seagate.com.tar
/
ftp.seagate.com
/
pub
/
palindrome
/
technote
/
tn9501.asc
< prev
next >
Wrap
Text File
|
1995-04-12
|
21KB
|
557 lines
TECHNICAL NOTE : NW4.1 SERVER RECOVERY USING FLOPPY DISKETTES AND
PNA v3.1a NLM
VERSION NUMBER : 1.1
VERSION DATE : 10 Mar 95
TABLE OF CONTENTS
=================
SECTION 1.0 - INTRODUCTION & ASSUMPTIONS
SECTION 2.0 - PRELIMINARY PREPARATION
2.1 - PLAN AND GATHER INFORMATIONAL DOCUMENTATION
2.2 - GENERATE "DOS_BOOT AND BACKUPxxx" DISK(s)
2.3 - PREPARE NECESSARY FILES FOR RECOVERY
2.4 - CREATE RECOVERY DISKETTES
SECTION 3.0 - SERVER RECOVERY
3.1 - TIMESYNC
3.2 - RESTORE DOS PARTITION
3.3 - PLACE RECOVERY FILES ON SERVER'S DOS PARTITION
3.4 - RESTORE NETWARE PARTITIONS
3.5 - NETWARE DIRECTORY SERVICES (NDS)
SECTION 4.0 - RESTORE DATA
4.1 - RESTORE PALINDROME ENVIRONMENT
4.2 - RECOVER THE SYS VOLUME
4.3 - RECOVER OTHER VOLUMES
SECTION 5.0 - CONCLUSIONS
=====================================================================
SECTION 1.0 - INTRODUCTION
Using the steps listed within this technical note, NetWare will not need to
be reinstalled during a full server recovery. Instead, the server is brought
up in a minimal state (through pre-planning) 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 the last backup).
This procedure assumes the following:
* PKZIP.EXE and PKUNZIP.EXE are available.
* A good understanding of Novell, Netware Directory Services (NDS),
PNA, DSREPAIR, NWADMIN, NETADMIN, TIMESYNC, and PARTMGR.
* 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 4.1 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.
* The C:\NWSERVER (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 needs about 4 MB of free disk space.
In more detail, this technical note covers the general procedures for
rebuilding a Netware 4.1 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.
SECTION 2.0 - PRELIMINARY PREPARATION
2.1 - PLAN AND GATHER INFORMATIONAL DOCUMENTATION
a) Download PALFCOPY.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 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
partition). 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 server
object.
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.3.
If your listing contains any other required files, then you will
need to copy them during SECTION 2.3.
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) Document the server's NetWare configuration.
__ A. NetWare partitions and volumes.
__ B. Volume block size, file compression, sub-allocation, and
migration.
__ C. Volume name space support.
__ D. Server names.
2.2 - GENERATE "DOS_BOOT" and "BACKUPxxx" DISK(s)
The server must be brought down to perform this step. In order to restore
the DOS partition to a minimum operating state, that is 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 - 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 LOGIN
MD LOGIN\NLS
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
(or equiv) directory.
__ SERVER.MLS - from that server's Netware 4.1x License diskette.
__ 3C5X9.LAN - from the SYS:SYSTEM (or equiv) directory.
Or proper NIC driver(s) and their configuration files, if any.
__ ETHERTSM.NLM - from the SYS:SYSTEM (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.
__ 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.
__ TSA410.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.
__ IPXS.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ SPXS.NLM - from the SYS:\SYSTEM (or equiv) directory.
__ DS.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.
__ 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.
Copy the following files into the RECOV\LOGIN\NLS directory:
__ *.001 - from the SYS:\LOGIN\NLS directory. (8 files)
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.5 - CREATE RECOVERY DISKETTES
__ Have 2 blank formatted diskettes (HD 1.44 MB) ready and hand
label them
RECOV4_1 & RECOV4_2
__ Place one of the diskettes in the A drive and from the RECOV
directory, issue the following command:
PKZIP A:RECOV4.ZIP *.* -rp&
Note: This command will compress the directories and files
contained in the RECOV directory into a zip file named,
RECOV4.ZIP. This zip file will span two diskettes.
__ Copy PKUNZIP.EXE onto the second diskette, RECOV4_2.
SECTION 3.0 - SERVER RECOVERY
This part describes the basic steps needed to restore a server.
3.1 - TIMESYNC
a) Refer to timesync notes taken during section 2.1, step g, of
this tech note.
a) If the server to be recovered is a time server type of PRIMARY,
REFERENCE, or SECONDARY, proceed to SECTION 3.2.
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 - PLACE RECOVERY FILES ON DOS PARTITION
__ On the root of the C drive, make a directory named, RECOV
__ Place RECOV4_2 in the A drive, and from the C:\RECOV prompt, type:
PKUNZIP A:RECOV4.ZIP -d C:\RECOV
__ Follow the PKUNZIP prompts and unzip the recovery diskettes into
the C:\RECOV directory. PKUNZIP should prompt you for both
diskettes.
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
__ From Install Options, choose / Disk Options / Modify Disk
Partitions and re-create the former Netware disk partitions
according to prepared volume information.
__ From Install Options, choose / Volume Options and re-create the
former server volumes according to prepared volume information.
__ Mount all volumes.
__ From INSTALL.NLM, choose the License Option and license the server.
Press F3 to specify a different path, then type in:
C:\RECOV\SYSTEM
__ Press ALT/ESC to change to the server console, then type
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 IPXS
__ Type LOAD MATHLIB (or MATHLIBC)
__ Type LOAD DSAPI
__ Type LOAD DS.NLM
__ Type LOAD TSA410
__ Type LOAD BT4X (or equiv SCSI driver)
__ Type LOAD BTAPSI (or equiv ASPI driver)
3.5 - DIRECTORY SERVICES
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's volume(s) be removed and then re-installed
into the tree.
To proceed, follow the steps a listed below:
a) It is imperative to understand how the NDS tree is partitioned.
It is also imperative to know which servers in the tree contain
the master(s) and which contain read/write replicas.
b) Using NWADMIN'S Partition Manager, select each partition 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. (Refer to Novell documentation for proper procedures
on how to designate a new master). When completed, proceed to
step d.
__ At this point, the server to be restored should NOT contain a
master of a partition.
__ Using NETADMIN or NWADMIN, delete the server's volume objects
from the NDS tree.
__ From the server console, press ALT/ESC to change to the
INSTALL screen or load it if not already loaded.
__ From INSTALL.NLM's " Installation Options" menu, choose
Directory Options / Install Directory Services Onto This Server"
__ Select the original tree in which the server resided, then log in
to and re-establish the server into the tree with the same
context it had before. It is imperative that the server is
placed into the tree exactly as it was before.
Note: Since the server object already exists in the tree, you will receive
the following message from NetWare:
"An NCP server object (or an unknown object) with the name
<server name> already exists in the context "OU=YOUR.O=CONTEXT"
Press <enter> to continue. Install-4.1-389"
__ Press ENTER. You will receive the following message:
"Delete the existing NCP server object and continue?"
__ Choose YES.
__ After Directory Services Installation is complete, Install
the mounted volumes into the directory tree. From Install's
"Installation Options" menu, choose Directory Options / Upgrade
Mounted Volumes into the Directory. Be sure to install all
volumes into the tree.
Note: The volume objects may have already been installed into Directory
Services via Directory Services install. If this is the case, that's fine.
Continue to the next step.
Note: At this point, verify a read/write replica of the partition in which
the server resides exists on the server and the bindery context on the server
is set for that container as well.
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
__ Restore the SYS Volume History Database (HDB). At the server
console, type:
LOAD PNAREST /RH <Fileserver name>/SYS:
4.2 - RECOVER SYS
__ To recover the volume's directory structure, from the server
console, type:
LOAD PNAREST /RD /OA <Fileserver name>/SYS:
__ Once the above operations completes, recover the volume's 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 7,
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:
__ After server restoration is complete, verify your NDS partitions
are replicated properly according to Novell's recommendations.
__ Verify the recovered server's time is synchronized on the network
by typing TIME at the server console.
__ 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.
The synchronization may take some time depending on your network
traffic and such.
__ When the last restore command is complete, at the server console,
type the following commands:
DOWN
EXIT
__ At the DOS prompt, type SERVER
Your server is now restored to its former operating state.