home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.seagate.com
/
2014.07.ftp.seagate.com.tar
/
ftp.seagate.com
/
pub
/
palindrome
/
technote
/
tn9304.asc
< prev
next >
Wrap
Text File
|
1995-03-21
|
6KB
|
143 lines
Tech Note Number: 9304
Date: March 31, 1993
Subject: Procedures for Cloning a Server
Using the Network Archivist NLM
Keywords: CLONING, SERVER, NETWORK ARCHIVIST NLM,
RESTORATION, TAPE SET, RCONSOLE, TNARECOV
Network Archivist Version: Network Archivist NLM Version 2.0x
Requirements
The following Tech Note details the procedure for cloning a server
using the Network Archivist NLM. The requirements are Network
Archivist NLM base software diskettes. The source server is the
server to be cloned. The destination server must be named the same
as the source server, with the same volume structure; and the
destination server must have NetWare TM version 3.11 installed.
Procedure
STEP 1: Place a blank, formatted tape in your tape drive and issue
the following command from the DOS prompt:
TNA2TAPE /AF /Q
The command can be issued from the server console by placing a
LOAD statement in front of the command; (i.e., LOAD TNA2TAPE /AF
/Q).
Rotating to a blank tape ensures that files deleted from disk
since the last rotation will be noted as deleted in the Network
Archivist history databases.
Also, since this is a brand new tape set (and no other tapes
exist in the set) the TNA2TAPE /AF command will copy to tape all
files that are not already on the tape set (i.e., full system
snapshot). This includes all volumes on the protected volume
list. Please remember that any file with rules set to
"checkpoint never" will not be copied to tape during a /AF
operation.
Restoration to the destination server will be accomplished using
one tape (or tape set) instead of multiple tapes (or tape sets).
By forcing in a blank tape, tape sets are increased by one. For
instance, if your highest tape set is G (TAPE_G1), then the blank
tape will become TAPE_H1. After the cloning process is complete
and regular backups are started again, TAPE_H1 will become the
most frequently used backup tape and will be requested every
second rotation according to the Tower of Hanoi rotation scheme.
STEP 2: After the full backup is complete, check the TNA_LOG file
to verify that the backup completed successfully, that no open
files were skipped, and to check for any important messages
communicated by the Network Archivist.
(Optional) It is recommended to repeat the first step in order to
have another tape available if media failure should occur. It is
a good idea to clean your tape drive after introducing new, blank
tapes.
STEP 3: Bring the source server down and the destination server
up. Once again, these two servers have identical server names
and volume structures. The destination server should have the
tape drive and controller already installed with the necessary
drivers loaded. Refer to Palindrome's Hardware Installation
Guide.
Note: If the source server cannot be brought down, clone the
destination server offline.
Note: After cloning is complete, the clone must remain off the
network or the server's name must be changed.
STEP 4: Login as "SUPERVISOR" on the destination server and
install the Network Archivist NLM base software and expand disks
if you have them. Refer to Chapter 2 (software installation
section) of the Network Archivist NLM documentation.
Be sure to install the Network Archivist into the same directory
specified on the source server. There is no need to add
additional volumes to the protected volume list during this
installation.
Check SYS:\SYSTEM\TNAPATH.DAT, make sure the first line of
TNAPATH.DAT file contains correct path information to the Network
Archivist installation directory.
Load REMOTE and RSPX modules for access to RCONSOLE during the
cloning process.
STEP 5: After completing the Network Archivist NLM installation
procedures outlined in Chapter 2 of the Network Archivist NLM
Documentation, login as "SUPERVISOR" and have search maps set up
for the Network Archivist installation directory and SYS:SYSTEM
directory.
STEP 6: Change into the Network Archivist installation directory
and delete the *.PAC files.
STEP 7: Type TNARECOV.
Type "O" to recover the System Control Database to its original
location (ASNX.PAC, ASDB.PAC).
Press F9 to access the server console using RCONSOLE.
STEP 8: The Network Archivist will open the tape:
Type "Y" to restore the database.
STEP 9: When the System Control Database is recovered, exit
RCONSOLE. You will receive a message that the job has completed
successfully and you will be brought to the TNARECOV Menu. It
will display the list of protected volumes that resided on the
source server.
STEP 10: Exit out to DOS and type TNACFG /O.
Edit the Network Login field so that the Network Login is
"SUPERVISOR."
Enter the "SUPERVISOR" password in the network password field,
and then exit to DOS.
STEP 11: From the DOS prompt, type TNARECOV to display the
TNARECOV screen. Tag/Select all volumes listed and then type "O"
for Operation. Choose "Recover Volume". The Network Archivist
will then recover all data for each of the tagged volumes.
Monitor the Network Archivist's progress through RCONSOLE or
directly from server console.
It is normal to receive an 897 warning when File History
Databases are recovered.
STEP 12: After the cloning process is complete, access the
Network Archivist configuration screen at the DOS prompt:
TNACFG /O
Change the Network login back to "ARCHIVIST" and change the
Network password to match the Archivist password.