home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.seagate.com
/
2014.07.ftp.seagate.com.tar
/
ftp.seagate.com
/
pub
/
palindrome
/
technote
/
tn9404.asc
< prev
next >
Wrap
Text File
|
1994-11-21
|
12KB
|
339 lines
TECH NOTE ON MOVING A PNA 3.1 NLM INSTALLATION
==============================================
CONTENTS:
=========
SECTION 1.0 - OBJECTIVES
SECTION 2.0 - Assumptions and Requirements
SECTION 3.0 - Moving a PNA installation that is currently
accessible on the network.
SECTION 4.0 - Moving a PNA installation that is no longer on the
network.
=================================================================
SECTION 1.0 - OBJECTIVES
This tech note covers procedures on moving a PNA installation
from one server/volume to another.
How to:
* Move a PNA installation to new location while it is still
accessible on the network.
* Move a PNA installation to a new location when PNA is NOT
currently accessible on the Network. (in other words, the
databases must be recovered from backup media)
SECTION 2.0 - Assumptions and Requirements
Assumptions:
The server/volume PNA is being moved FROM is referred to as
the SOURCE SERVER. In examples, the source server will be
referred to as FS1.
The server/volume PNA is moving TO is referred to as the
TARGET SERVER. In examples, the target server will be
referred to as FS2.
The PNA auto login user, referred to as "Archivist", exists
on the target server with same password and rights as the
PNA auto login user on the source server.
The user has a good working knowledge of PNA, NetWare and
related terminology.
Requirements:
1. This is a PNA 3.1 NLM installation.
2. PNA must retain the same directory name on the
Target Server.
3. The archivist user exists on the target server with the
same password and appropriate rights as the archivist
user on the source server.
4. The target server/volume supports the same name spaces as
the source server/volume.
SECTION 3.0 - PROCEDURES FOR MOVING A PNA INSTALLATION CURRENTLY
ACCESSIBLE ON THE NETWORK.
Step 1: Set up hardware on target server.
This would include the host adapter SCSI card, backup device
and necessary SCSI drivers. After setting up hardware and
loading drivers, use PALDIAG.NLM to test the hardware
setup. (PALDIAG should be located in the source server's
system directory)
After hardware is set up and proper drivers loaded, from the
server console, type
LOAD PALDIAG /S
PALDIAG should scan the SCSI bus and display all SCSI
devices attached. If the backup device is not displayed,
you have some type of hardware issue that needs to be
resolved and is beyond the scope of this tech note. Check
your hardware installation procedures.
Step 2: Using the /S parameter, XCOPY the PNA installation and
its subdirectories from the source server/volume to the
target server volume maintaining the same PNA directory
name. This would include all *.exe files and *.pac
files.
Step 3: From the source server's sys: system directory, copy all
PNA NLM's and appropriate TSA's over to the target server's
sys:system directory.
List of NLM's to copy from source server's sys:system directory
to target server's sys:system directory:
PAL*.NLM
PNA*.NLM
TSA*.NLM
WS_MAN.NLM
SMDR*.NLM
Step 4: Create a PNAPATH.DAT file in target server's sys:system
directory using any text editor.
Example PNAPATH.DAT
FS2/SYS:\PNA
FS2 INFOSYS
Required information for first line in PNAPATH.DAT:
PNA installation Server = FS2
PNA installation Volume = SYS
PNA installation directory:\PNA
Optional information for second line in PNAPATH.DAT:
Print server = FS2
Print Queue = INFOSYS
Step 5: From the target server console, load PNASM.
Step 6: Load appropriate TSA's on target server. Refer to
Palindrome's Target Service Agent Installation guide if you
are unsure which TSA's need to be loaded.
Step 7: If you haven't done so already, log in to target server
as Archivist (your PNA Auto Login User) and set up a search
map to the target server's PNA installation.
Note: Archivist needs to match the auto login user and
password specified in PNA's System Parameter screen.
Step 8: From the PNA directory on the target server, type PNACFG
/P and press enter. The Protected Resource List (PRL) should
appear.
Complete Steps 9-14 only if the PNA installation's databases are
CENTRALIZED.
Step 9: Choose HISTORY and highlight CENTRAL HISTORY LOCATION
and press [enter]. A pick list should appear listing the
target server as a choice. (if not, then the TSA and SMDR
NLM's are not loaded on the target server)
Step 10: Choose the target server, then select the target volume
that corresponds to where PNA currently resides.
This step will change the centralized history location from
the source server/volume to the target server/volume.
Step 11: Additionally, each Resource on the PRL must have the
History database location updated to reflect the target
server.
Highlight the first Resource on the PRL and choose
OPERATION, then choose CONFIGURE.
Step 12: Arrow key down and highlight HISTORY, press [enter].
(notice history path is still pointing to source server)
Step 13: A pick list appears listing the target server as a
choice. Choose the target server, then select the target
volume that corresponds to where PNA currently resides.
At this point, you'll receive a message, APCF-8 Databases already
exist, do you want to overwrite?" Choose "USE EXISTING
HISTORIES".
Step 14: Repeat steps 11 though 13 for the rest of the resources
on the PRL.
The HISTORY path should now be updated and reflect the target
server.
Step 15: If the host adapter number or SCSI id on the backup
device has changed from the original setup, then the backup
device may need to be re-configured. To do so, access PNA's
System Screen, choose Configure, then choose Devices. You
may need to delete the current device and re-scan the bus to
find the new Host Adapter number and/or SCSI id.
SECTION 3.0 Moving a PNA installation that is no longer
accessible on the network.
Requirements:
* PNA 3.1A NLM diskettes
* Valid PNA serial number
* Archivist user with appropriate rights set up on target
server.
Step 1: Set up hardware on target server.
This would include the host adapter SCSI card, backup device
and necessary SCSI drivers. After setting up hardware and
loading drivers, use PALDIAG.NLM to test the hardware
setup. (PALDIAG should be located in the source server's
system directory)
After hardware is set up and proper drivers loaded, from the
server console, type
LOAD PALDIAG /S
PALDIAG should scan the SCSI bus and display all SCSI
devices attached. If the backup device is not displayed,
you have some type of hardware issue that needs to be
resolved and is beyond the scope of this tech note. Check
your hardware installation procedures.
Step 2: Log in to target server as Archivist (your Auto Login
User). Create a search map to the PNA directory on the
target server. Make sure no other search maps point to any
other PNA installation.
Note: Archivist needs to match the auto login user and
password specified in PNA's System Parameter screen.
Step 3: Install PNA on the target server. When installing, make
sure to:
Install PNA into the same directory name that was used on
the source server. Copy all PNA installation diskettes
including the TSA diskette on the target server.
Keep the same Auto Login User (archivist).
Do not add any resources to the Protected Resource List
(PRL)at this time. You will receive a warning screen if you
exit the installation program without adding to the
Protected Resource List. This is expected and ok.
Step 4: After installation completes, access the PNA directory
and delete the AS*.PAC files.
Step 5: Access target server console and LOAD PNASM.
Step 6: Load appropriate TSA's on target server. Refer to
Palindrome's Target Service Agent Installation guide if you
are unsure which TSA's to load.
Step 7: Place the tape last used for a backup by this PNA
installation in the backup device.
Note: The examples below assume FS2/SYS: is the target
server.
Step 8: From the server console, type
LOAD PNAREST /RC=FS2/SYS:
where FS2/SYS is the target server/volume
PNA will open the media and ask you to verify the date of
the System Control database you are restoring. If this is
the most current System Control Database, continue below.
If not, find your most current backup media and retry Step
8.
Note: The command, "PNAREST /RC=FS2/SYS:" recovers the System
Control Database from media to the target server/volume.
The System Control Database contains two files (ASDB.PAC and
ASNX.PAC). These two files contain information on your
Protected Resource List and other installation configuration
settings.
Step 9: Log into the target server as Archivist if you haven't
done so already. Create a search map to the PNA directory
on the target server. Make sure no other search drive point
to any other PNA installation.
Step 10: At the DOS prompt, type PNACFG /P and press [enter].
Complete Steps 11-17 only if the PNA installation databases are
CENTRALIZED.
Step 11: Choose HISTORY and highlight CENTRAL HISTORY LOCATION
and press [enter]. A pick list should appear listing the
target server as a choice. (if not, then the TSA and SMDR
NLM's are not loaded on the target server)
Step 12: Choose the target server, then select the target volume
that corresponds to where PNA currently resides.
This step will change the centralized history location from
the source server to the target server.
Step 13: Highlight the first Resource on the PRL and choose
OPERATION, then choose CONFIGURE.
Step 14: Arrow key down and highlight HISTORY.(notice history
path is still pointing to source server)
Step 15: Press [enter] and a pick list should appear listing the
target server as a choice. Choose the target server, then
select the target volume that corresponds to where PNA
currently resides. This should update the history path to
reflect the target server/volume.
Step 16: Repeat steps 10 though 15 for the rest of the resources
on the PRL.
Step 17: Once all resource's history paths have been updated,
ESC out to DOS and type PNA to access the System Screen.
Tag all resources listed and choose Restore, then choose
History Databases.
At this point, PNA should recover history files for each resource
on the PRL and place them in a directory called \PNA\DB.
The PNA installation on the target server should be operational
and perform backups as usual.