Non-Raid Disk Failure - 3Com VCX V7000 Installation Manual

Non-RAID Disk
Failure
Names of
Software Files
If a disk fails on a VCX server that does not use RAID technology, refer to
these procedures:
Replacing a Disk (Single Site)
■
Replacing a Disk (Regional Office)
■
Replacing a Disk (Branch Office)
■
Replacing a Disk (VCX Connect)
■
Assumption: The replacement disk arrives and may contain an older
version of the software that is installed on the running server.
The VCX system continues to deliver service to VCX system users.
Terminology: Throughout this appendix, the server on which the disk
failure has occurred is referred to as the "down server" regardless of
what state it is in. The partner server is referred to as the "running
server," again without reference to its state.
Over the history of the VCX 7.1 releases, the software file naming
conventions have changed. From the first release through the release of
7.1.12c, there were separate files for each type of server. For example:
Authentication and Directory Server: vcx-dataserver-<version>.tar
■
Call Processing Server: vcx-callserver-<version>.tar
■
Call Records Server: vcx-bss-<version>.tar
■
IP Telephony Server: vcx-softswitch-<version>.tar
■
IP Telephony and Messaging Server: vcx-all-<version>.tar
■
IP Messaging Server: vcx-ipmsg-<version>.tar
■
You must use the file that is appropriate to the server type.
Starting with VCX 7.1.14c, one software file can be used for all server
types. Two file name formats are possible:
VCX Connect Servers: vcxconnect-x86-<version>e.tar
■
VCX Enterprise Servers: vcx-x86-<version>c.tar
■
You must use the file that is appropriate to the type of installation (VCX
Enterprise or VCX Connect).

Non-RAID Disk Failure

377