Table Of Contents

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

Index

A

about failover 4-1

accessing web applications after failover or failback 2-1

active

both servers at same time 4-18

server, determining the 3-1

automatic failover and failback, disabling for troubleshooting 3-4

B

backing up Cisco Unity system 1-9

C

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

causes

of both servers becoming active 4-18

of failback 4-14

of failover 4-14

changing

IP address of primary server 3-10

IP address of secondary server 3-16

Cisco Personal Communications Assistant

access after failover or failback 2-1

effect on when failover or failback occurs 4-8

Cisco Unity

exiting software A-1

file replication 4-10

restarting server A-2

shutting down server A-2

starting software A-3

Cisco Unity Administration

access after failover or failback 2-1

effect on when failover or failback occurs 4-8

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

standby redundancy 1-8

voice messaging ports on secondary server 1-4

confirming that failover and failback function correctly 3-5

conventions, documentation 1-vii

converting primary or secondary server 3-22

customizing failover and failback settings 1-12

D

data that is not replicated 4-11

default settings, failover and failback 1-12

delay

for failback to occur 4-16

for failover to occur 4-15

disabling

automatic failover and failback for standby redundancy 1-8

automatic failover and failback for troubleshooting 3-4

failover initiation for unanswered calls on primary server 1-8, 1-14

documentation

audience and use 1-vii

conventions 1-vii

E

effects

of failover and failback on calls in progress 4-8

of Force Failover setting 4-6

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-12

when failover occurs 4-12

exceptions to normal functionality on secondary server 4-5

Exchange message store, about installing on secondary server 4-2

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-4

effects on calls in progress 4-8

interval 4-16

list of possible causes 4-14

manual 3-2

preparing for failback when integrated via PIMG/TIMG units 2-1

process 4-12

failover

behavior during network outages B-1

cause, based on event ID 3-7

causes of both servers becoming active 4-18

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-4

disabling initiation for unanswered calls on primary server 1-14

effects on calls in progress 4-8

how it works 4-1

interval 4-15

list of possible causes 4-14

manual 3-2

process 4-12

requirements 4-6

setting up notification of 1-5

testing 1-9

uninstalling 3-21

file replication 4-9

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

I

initiating failover and failback manually 3-2

interval

failback 4-16

failover 4-15

IP address

changing primary server 3-10

changing secondary server 3-16

L

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

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

M

manual failback, initiating 3-2

manual failover

initiating 3-2

initiating by Event Monitoring Service 3-2

message store, about installing on secondary server 4-2

monitoring status of servers 4-9

MWIs, automatically resynchronizing daily 1-5

N

network, failover behavior during outages B-1

Node Manager service, replication 4-10

notification of failover, setting up 1-5

O

outages, network B-1

overview of failover 4-1

P

PCA. See Cisco Personal Communications Assistant

PIMG/TIMG units

Force Failover setting required 4-6

preparing for failback when integrated via PIMG/TIMG units 2-1

ports, configuring on secondary server 1-4

primary server

causes of unanswered calls 4-6

changing IP address 3-10

configuring failover 1-2

disabling failover initiation for unanswered calls 1-14

replacing or converting 3-22

starting first 3-1

voice messaging functions when active 4-4

prompt replication 4-10

R

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

replacing primary or secondary server 3-22

replication

Cisco Unity files 4-10

confirming UnityDb changes on inactive server 3-2

data that is not replicated 4-11

monitoring SQL Server replication 3-9

Node Manager service 4-10

of files 4-9

SQL Server database 4-11

UMR (Unity Messaging Repository) 4-11

UnityDb database 4-11

voice messages 4-11

requirements

Cisco Unity failover 4-6

Cisco Unity standby redundancy 4-6

restarting

Cisco Unity server A-2

servers, effects of 4-19

resynchronizing MWIs daily, automatic 1-5

S

scheduling backups of Cisco Unity system 1-9

secondary server

about installing with message store 4-2

changing IP address 3-16

configuring failover 1-2

configuring voice messaging ports 1-4

exceptions to normal functionality during failover 4-5

failing over manually when standby redundancy is configured 2-2

replacing or converting 3-22

using without primary server 4-19

voice messaging functions when active 4-5

servers

determining which is active 3-1

order for starting 3-1

restarting A-2

shutting down A-2

status monitoring 4-9

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

shutting down

Cisco Unity server A-2

servers, effects of 4-19

software

exiting Cisco Unity A-1

starting Cisco Unity A-3

SQL Server

database replication 4-11

monitoring replication 3-9

standby redundancy

configuring 1-8

failing over 2-2

how it works 4-6

requirements 4-6

starting

Cisco Unity software A-3

order for servers 3-1

Status Monitor

access after failover or failback 2-1

effect on when failover or failback occurs 4-8

status of servers 4-9

T

testing Cisco Unity failover 1-9

time

for failback to occur 4-16

for failover to occur 4-15

TIMG/PIMG units

Force Failover setting required 4-6

preparing for failback when integrated via TIMG/PIMG units 2-1

troubleshooting, disabling automatic failover and failback for 3-4

U

uninstalling failover 3-21

UnityDb

confirming that changes replicated to inactive server 3-2

database replication 4-11

monitoring SQL Server replication 3-9

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

V

voice message replication 4-11

voice messaging functions

when primary server is active 4-4

when secondary server is active 4-5

W

web applications, effect on when failover or failback occurs 4-8