Table Of Contents

A - B - C - D - E - F - I - L - M - N - O - P - R - S - T - U - V -

Index

A

about failover 4-1

accessing web applications after failover or failback 2-1

active

both servers at same time 4-14

server, determining the 3-1

analog voice lines, connecting B-1

automatic failover and failback, disabling for troubleshooting 3-3

B

backing up Cisco Unity system 1-9

C

cables

connecting analog voice lines B-1

enabling phone system to send calls to active server in T1 integration 2-2

calls in progress, effects of failover and failback 4-6

causes

of both servers becoming active 4-14

of failback 4-11

of failover 4-10

changing

IP address of primary server 3-8

IP address of secondary server 3-13

Cisco Personal Communications Assistant, access after failover or failback 2-1

Cisco Unity

exiting software A-1

file replication 4-7

restarting server A-2

server name requirements 4-4

shutting down server A-2

starting software A-3

Cisco Unity Administrator, access after failover or failback 2-1

Configure Cisco Unity Failover wizard, running 1-2

configuring

automatic daily resynchronization of MWIs 1-5

event notification 1-5

failover, task list 1-1

failover and failback settings 1-12

failover on Cisco Unity servers 1-2

scheduled backups of Cisco Unity system 1-9

voice messaging ports on secondary server 1-3

confirming that failover and failback function correctly 3-5

connections

analog voice lines B-1

DTMF integration (illustration) 4-2

enabling phone system to send calls to active server in T1 integration 2-2

IP integration (illustration) 4-2

lines between phone system and Cisco Unity servers B-1

serial data cable B-6

serial integration (illustration) 4-3

conventions, documentation -viii

converting primary or secondary server 3-18

customizing failover and failback settings 1-12

D

data splitter for RS-232 serial cable (illustration) 4-3

data that is not replicated 4-8

default settings, failover and failback 1-12

delay

for failback to occur 4-12

for failover to occur 4-12

disabling

automatic failover and failback for troubleshooting 3-3

failover initiation for unanswered calls on primary server 1-14

documentation

audience and use -vii

conventions -viii

E

effects

of failover and failback on calls in progress 4-6

of Force Failover setting 4-5

enabling

phone system to send calls to active server in T1 integration 2-2

subscriber logon by phone after failover 1-4

event ID, using to determine cause of failover or failback 3-7

Event Monitoring Service

configuring for failover notification 1-5

initiating manual failover 3-2

event notification 1-5

events

when failback occurs 4-9

when failover occurs 4-9

exceptions to normal functionality on secondary server 4-4

exiting Cisco Unity software A-1

F

failback

cause, based on event ID 3-7

configuration settings (table) 1-13

confirming functionality 3-5

customizing settings 1-12

default settings 1-12

disabling automatic for troubleshooting 3-3

effects on calls in progress 4-6

effects on using phone as recording or playback device 2-2

interval 4-12

list of possible causes 4-11

manual 3-2

process 4-9

updating server name in Media Master after 2-2

failover

behavior during network outages C-1

cause, based on event ID 3-7

causes of both servers becoming active 4-14

configuration settings (table) 1-13

configuration wizard 1-2

configuring, task list 1-1

confirming functionality 3-5

customizing settings 1-12

default settings 1-12

disabling automatic for troubleshooting 3-3

disabling initiation for unanswered calls on primary server 1-14

effects on calls in progress 4-6

effects on using phone as recording or playback device 2-2

how it works 4-1

interval 4-12

list of possible causes 4-10

manual 3-2

process 4-9

requirements 4-4

setting up notification of 1-5

testing 1-9

uninstalling 3-18

updating server name in Media Master after 2-2

file replication 4-6

Force Failover setting, effects of using or not using 4-5

I

initiating failover and failback manually 3-2

installing lines between phone system and Cisco Unity servers B-1

integrations

analog connections B-1

DTMF connections (illustration) 4-2

IP connections (illustration) 4-2

serial connections B-1

serial connections (illustration) 4-3

interval

failback 4-12

failover 4-12

IP address

changing primary server 3-8

changing secondary server 3-13

L

licensing, restrictions on using secondary server without primary server 4-15

lines

connecting analog voice B-1

connecting serial cable B-6

Local Status, meanings of values (table) 3-1

M

manual failback, initiating 3-2

manual failover

initiating 3-2

initiating by Event Monitoring Service 3-2

Media Master, failover behavior 2-2

monitoring status of servers 4-6

MWIs, automatically resynchronizing daily 1-5

N

network, failover behavior during outages C-1

Node Manager service, replication 4-7

notification of failover, setting up 1-5

O

outages, network C-1

overview of failover 4-1

P

PCA. See Cisco Personal Communications Assistant

phone as recording or playback device, effects of failover and failback 2-2

pinouts

phone system serial port acting as DCE B-7

phone system serial port acting as DTE B-7

RJ-11 connector (illustration) B-2

RJ-14 connector (illustration) B-2

ports, configuring on secondary server 1-3

primary server

causes of unanswered calls 4-5

changing IP address 3-8

configuring failover 1-2

disabling failover initiation for unanswered calls 1-14

enabling phone system to send calls to active server in T1 integration 2-2

replacing or converting 3-18

starting first 3-1

voice messaging functions when active 4-3

prompt replication 4-7

R

Remote Status, meanings of values (table) 3-1

replacing primary or secondary server 3-18

replication

Cisco Unity files 4-7

confirming UnityDb changes on inactive server 3-2

data that is not replicated 4-8

Node Manager service 4-7

of files 4-6

SQL Server database 4-8

UMR (Unity Messaging Repository) 4-8

UnityDb database 4-8

voice messages 4-8

requirements for Cisco Unity failover 4-4

restarting

Cisco Unity server A-2

servers, effects of 4-15

resynchronizing MWIs daily, automatic 1-5

RJ-11, connector pinout (illustration) B-2

RJ-14, connector pinout (illustration) B-2

routing rule for subscriber logon by phone after failover 1-4

RS-232 serial cable, using data splitter for serial integration B-6

S

scheduling backups of Cisco Unity system 1-9

secondary server

changing IP address 3-13

configuring failover 1-2

configuring voice messaging ports 1-3

DTMF integration connections B-1

DTMF integration connections (illustration) 4-2

enabling phone system to send calls to active server in T1 integration 2-2

enabling subscriber logon by phone after failover 1-4

exceptions to normal functionality during failover 4-4

IP integration connections (illustration) 4-2

replacing or converting 3-18

serial integration connections B-1

serial integration connections (illustration) 4-3

using without primary server 4-15

voice messaging functions when active 4-3

serial cable

connecting B-6

wiring between data splitter and Cisco Unity servers B-8

server name

requirements 4-4

updating in Media Master after failover or failback 2-2

servers

determining which is active 3-1

order for starting 3-1

restarting A-2

shutting down A-2

status monitoring 4-6

settings for failover and failback configuration (table) 1-13

shutting down

Cisco Unity server A-2

servers, effects of 4-15

software

exiting Cisco Unity A-1

starting Cisco Unity A-3

SQL Server, database replication 4-8

starting

Cisco Unity software A-3

order for servers 3-1

Status Monitor, access after failover or failback 2-1

status of servers 4-6

subscriber logon, enabling on secondary server 1-4

T

T1 integration, enabling phone system to send calls to active server 2-2

testing Cisco Unity failover 1-9

time

for failback to occur 4-12

for failover to occur 4-12

troubleshooting, disabling automatic failover and failback for 3-3

U

uninstalling failover 3-18

UnityDb

confirming that changes replicated to inactive server 3-2

database replication 4-8

UTIM, configuring voice messaging ports on secondary server 1-3

V

voice message replication 4-8

voice messaging functions

when primary server is active 4-3

when secondary server is active 4-3