home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.seagate.com
/
2014.07.ftp.seagate.com.tar
/
ftp.seagate.com
/
pub
/
palindrome
/
technote
/
tn9503.asc
< prev
next >
Wrap
Text File
|
1995-05-04
|
8KB
|
253 lines
Tech Note#: 9503
Date: 20 March 1995
Subject: SFT III v4.1 and Palindrome 3.1a
Keywords: SFT III 4.1
Versions: Palindrome 3.1a NLM versions
NOTE: Currently the SMS version is NOT supported running 'on' SFT III
version 3.1x servers due to TSA/SMDR/SFTIII conflicts.
WHAT IS SFT III?
This is a unique version of Novell 4.1 that gives you the capability of
mirroring or duplexing Netware servers. The concept is to have two
identical servers running at the same time. One a primary server, the
latter a secondary server. Both are connected through a high speed
Mirror Server Link (MSL) which enables them to become a mirror image of
each other. The object is that if the primary server were to go down, the
secondary server would sense the loss of the primary server and
immediately take over operation. This transfer is transparent to the user.
PRIMARY SERVER SECONDARY SERVER
┌────────────────┐ ┌─────────────────┐
│ │ │ │
│ LEFT_IO │ │ RIGHT_IO │
│ │ │ │
└────────────────┘ └─────────────────┘
┌────────────────┐ mirroring ┌ ─ ─ ─ ─ ─ ─ ─ ─ ┐
│ │ ---------> │ │
│ MSEngine ╞════════════╡ MSEngine │
│ │ MSL │ │
└────────┬───────┘ └ ─ ─ ─ ─┬─ ─ ─ ─ ┘
│ │
│ │
════════════╧═════════════════════════════╧═══════════════
Network Backbone
The core architecture of the SFT III 4.1 consists of basically 3 server
engines split between 2 different machines. Each server has its own
independent Input/Output server engine (IOEngine) that handles the
physical hardware of the server. The MSEngine is the 'virtual'
server engine that the enduser sees. This MSEngine is actually
running on the Primary server as the master, and is constantly being
mirrored (instructions, memory, and volumes) to the slave secondary
server. Both servers make sure the other is 'alive', by sending a
dignostic packet to the other 18 times per second. If one server
dies, the other will act accordingly. For more info on this topic,
read the Novell SFT III 4.1 manual.
COMMON PROBLEMS
---------------
Most SFT III 4.1 specific problems are related to the following:
- Loading Palindrome components in the wrong engine.
- Incorrect SFT III 4.1 installation and/or setup.
- Make sure that the loading of the MSL driver is the LAST thing
done in the IOSTART.NCF files.
HOW DO I BACKUP MY SFT III 4.1 SERVER?
----------------------------------
- Backup a remote SFT III 4.1 server.
1) Create an ARCHIVIST user per the PNA manual.
2) Backing up remote SFT III 4.1 servers is as simple as putting the
Server/Volume on the Protect Volume List (PVL). *Note: Make sure
that the TSA410.NLM & SMDR.NLM are loaded prior to this.
- Backup and run 'ON' the SFT III 4.1 server.
1) Install PNA as normal. Consult the PNA manual for details.
2) Modify the SFT III 4.1 servers .NCF files as in the example
below.
.NCF FILE USAGE
---------------
An SFT III 4.1 server has 6 basic .NCF files that are used to automate
loading and setting of server resources. This is described in more
detail in the SFT III 4.1 manual. but to summarize:
MSSTART.NCF - This file is located on the DOS partition and is used
to SET MSEngine statup parameters.
MSAUTO.NCF - This file is located on SYS: and is used to define
the MSEngine server specifications and load NLMs that
do NOT access anything on the hardware level.
IOSTART.NCF - This file is located in the DOS partition and is used
to set & load hardware drivers that do not require and
active MSEngine, such as .LAN, .DSK, .MSL drivers.
IOAUTO.NCF - This file is located on SYS: and is used to load and
set IOEngine resources that DO require an active
MSEngine and/or mounted SYS: volume.
SAMPLE .NCF FILES - This is for illustration only.
------------------
═══ MSSTART.NCF ═══════════════════════════════════════════════════════════
SET Maximum Alloc Short Term Memory = 5000000
SET Minimum Packet Recieve Buffers = 500
SET Maximum Packet Recieve Buffers = 700
═══ MSAUTO.NCF ════════════════════════════════════════════════════════════
SET Time Zone = CST6CDT
SET Daylight Savings Time Offset = 1:00:00
SET Start Of Daylight Savings Time = (APRIL SUNDAY FIRST 2:00:00 AM)
SET End Of Daylight Savings Time = (OCTOBER SUNDAY LAST 2:00:00 AM)
SET Default Time Server Type = SINGLE
SET Bindery Context = O=Palindrome
MSENGINE NAME SYST_SFT3
MSENGINE IPX INTERNAL NET 3333
MOUNT ALL
LOAD TSA410
LOAD TSANDS
LOAD CONLOG FILE=SYS:\CONLOG\MS
LOAD MONITOR
═══ IOSTART.NCF on primary server ═════════════════════════════════════════
IOENGINE NAME RIGHT_IO
IOENGINE IPX INTERNAL NET 333A
SET Secondary Take Over Delay Amount=5
Set New Start Address for Unclaimed Memory Block = 20864320
Set New End Address for Unclaimed Memory Block = 33735232
LOAD IDE.DSK INT=E PORT=1F0
LOAD e16odif port=300 int=3 frame=ethernet_ii
BIND ipx to e16odif net=5
LOAD AHA1740 PORT=330
LOAD C:\SERVER.41\TCMSL.MSL MEM=DC000 INT=F
═══ IOAUTO.NCF on primary server ══════════════════════════════════════════
LOAD PNASM
LOAD PNASTART
LOAD CONLOG FILE=SYS:\CONLOG\IO1
═══════════════════════════════════════════════════════════════════════════
═══ IOSTART.NCF on secondary server ═══════════════════════════════════════
IOENGINE NAME LEFT_IO
IOENGINE IPX INTERNAL NET 333B
SET Secondary Take Over Delay Amount=5
Set New Start Address for Unclaimed Memory Block = 20864320
Set New End Address for Unclaimed Memory Block = 33735232
LOAD IDE.DSK INT=E PORT=1F0
LOAD e16odif port=300 int=3 frame=ethernet_ii
BIND ipx to e16odif net=5
LOAD C:\SERVER.41\TCMSL.MSL MEM=DC000 INT=F
═══ IOAUTO.NCF on secondary server ════════════════════════════════════════
LOAD Remote PASSWORD
LOAD RSPX
═══════════════════════════════════════════════════════════════════════════
QUESTIONS AND ANSWERS:
----------------------
Q: Do I install on the Primary or Secondary I/O Engine?
A: Actually, the Network Archivist will work on either IO Engine, but on
average, the Primary IO Engine installation will see slightly better
performance than Secondary IO Engine installations when backing up local
server volumes. This is due to the fact that Seconday IO Engines
must go 'across-the-wire' to access local data. It is for this
reason that Palindrome recommends running ONLY on the Primary
IOEngine.
_________________________________________________________
Q: Where do I put the storage device & controllers ?
A: The storage device and SCSI controller are the only things that are not
mirrored on both servers. Due to this you will need to have all the SCSI
devices associated with the backups to exist on the IO Engine that you
have specified to be the backup engine, or the Primary IO in this tech
note.
_________________________________________________________
Q: Where are the common NLMs loaded?
A: This info is available in the Novell SFT III 4.1 manual,
but to summarize:
TSANDS.NLM - MSEngine
TSA410.NLM - MSEngine
SMDR.NLM - MSEngine * Autoloaded by TSA410.NLM
INSTALL.NLM - MSEngine
MONITOR.NLM - MSEngine
VREPAIR.NLM - MSEngine
REMOTE.NLM - IOEngine
RSPX.NLM - IOEngine
_________________________________________________________