Filter
Top Products
376 APPENDIX C: REPLACING A FAILED DISK ON A VCX SERVER
10 Back up the Oracle database on the running server. For instructions, see
the VCX Administration Guide.
11 Transfer the Oracle database backup files from the running server to the
down server. For instructions, see the VCX Administration Guide.
CAUTION: When you use the scp command to copy the database
backup files to the down server, you may see a warning message about a
“man in the middle” attack. This message indicates that the security key
that was associated with the down server has changed, and the running
server does not recognize the down server’s new security key. The change
to the security key is a normal consequence of the disk replacement
process.
To resolve this issue, locate the
known_hosts file on the running server
(
/opt/home/cworks/.ssh/known_hosts) and perform one of these
actions:
■ Edit the file, locate the line that contains the IP address of the down
server, and replace the old key with the new key.
■ Edit the file, locate the line that contains the IP address of the down
server and remove that line.
■ Delete the known_hosts file. If you use this method, the next time you
try to access any of the other VCX servers using commands such as
scp or ssh, you will be prompted to confirm that you want to trust the
target server.
12 Restore the database on the down server. For instructions, see the VCX
Administration Guide.
13 Set up Oracle database replication on either of the servers.
a On the running server or the down server, log in as cworks.
b Enter these commands:
cd /opt/3com/VCX/vcxdata/bin
./setupReplication
You must know which server is the Master Definition Site and provide the
IP address when the script prompts for this information.
The script asks for the IP addresses of the two servers and then checks the
replication state of the authentication databases on them. After the
check, database replication begins.