Cisco Unity Maintenance Guide (With IBM Lotus Domino), Release 4.0(5)
Cisco Unity Data and Log Files

Table Of Contents

Cisco Unity Data and Log Files

Introduction to Cisco Unity Data and Message Storage

Cisco Unity Functions When the Network Is Down

Managing the Location of Log Files and Database Files

Moving Subscriber Mailboxes

Moving the Unity Messaging System, UAmis, and UOmni Mail Files

Unity Messaging System Mail File

UAmis Mail File

UOmni Mail File


Cisco Unity Data and Log Files


Introduction to Cisco Unity Data and Message Storage

Information about subscriber accounts and other Cisco Unity data is stored in a SQL Server database on the Cisco Unity server. Additionally, a small subset of the Cisco Unity information is stored in the Domino directory. Cisco Unity keeps the information in the Domino directory and in the SQL Server database synchronized.

By storing its data in a SQL Server database, Cisco Unity derives many performance, reliability, and scalability benefits. Because very little information is stored in the Domino directory, and because that information is not likely to change often, directory replication caused by changes to Cisco Unity data is minimal after the initial creation of subscriber accounts.

Cisco Unity Functions When the Network Is Down

In addition to the SQL database that contains subscriber names and extensions, the Unity Messaging Repository (UMR) is also on the Cisco Unity server. When a Domino server or even the entire Domino network is down, Cisco Unity can answer calls, allow unidentified callers to look up subscriber extensions, and take voice messages. While the e-mail system or network is off line, new voice messages are stored in the UMR on the Cisco Unity server. When the Domino server or network is back on line, the voice messages stored in the UMR are routed to the subscriber mailboxes.

Note that the UMR conversation is disabled by default. If you are running Domino without clustering, you can enable the UMR conversation. (If you run Domino with clustering, you are already protected from circumstances in which there could be problems with the availability of messages.) You use the Advanced Settings tool in Tools Depot to enable the UMR conversation. The setting is called Conversation—(Unity Domino only) Enable UMR Conversation. For detailed instructions, refer to the Advanced Settings tool Help.

Managing the Location of Log Files and Database Files

The way in which logical drives on the Cisco Unity server are partitioned and what content is located on the drives depends on the size of the Cisco Unity system and the RAID volume configuration used.

The partition and drive content recommendations from the Cisco Unity Installation Guide should continue to be followed when maintaining your system.

Moving Subscriber Mailboxes

From time to time you may need to move subscriber mailboxes to another server that is faster or has more disk space available, or you may want to move mailboxes when you add new servers to your network. It is possible to move subscribers between servers without having to shut down Cisco Unity.


Caution If you are moving a group of subscriber mail files at once, confirm that you do not inadvertently select the Unity Messaging System, UAmis, or UOmni mail files. To move these special mail files, see the "Moving the Unity Messaging System, UAmis, and UOmni Mail Files" section.

To Move Subscriber Mail Files Between Servers


Step 1 Follow the Lotus Domino procedures for moving mail files between servers.

Step 2 Verify that the new mail file has been created on the destination server, and that the subscriber Person document has been updated with the new mail server name in the directory replica on the Domino server that Cisco Unity monitors. (This is the Domino server that was selected in the Message Store Configuration wizard during Cisco Unity setup.)

Step 3 If the destination server contains at least one other Cisco Unity subscriber mail file associated with the same Cisco Unity server, skip to Step 5.

If the destination server does not contain at least one other Cisco Unity subscriber mail file associated with the same Cisco Unity server, notifications will not be sent when activity occurs on that subscriber mail file, including MWI notifications. To fix the problem, continue with Step 4.

Step 4 Do one of the following (each action will result in the identical result, so do the one that is most convenient to you):

Restart the Cisco Unity server.

Wait for the next scheduled MWI resynchronization. By default, MWIs are resynchronized each day at midnight, but the time can be changed in the Cisco Unity Telephony Integration Manager (UTIM).

Use UTIM to resynchronize MWIs, as follows:

On the Windows Start menu of the Cisco Unity server, click Programs > Cisco Unity > Manage Integrations.

Expand the tree in the left pane.

Click Properties.

In the Integration section of the properties page, click Resynchronize Now.

Exit UTIM.

Step 5 Verify that Cisco Unity has become aware of the new location of the mail file, which occurs after Cisco Unity synchronizes its database with the Domino directory. Cisco Unity synchronizes with the Domino directory every minute, but you can verify that the synchronization has occurred by using the Cisco Unity Data Link Explorer (CUDLE) tool, as follows:

a. On the Cisco Unity server, double-click the Cisco Unity Tools Depot icon on the desktop.

b. In the left pane, expand Diagnostic Tools.

c. Double-click Data Link Explorer.

d. Click View > Query Builder.

e. In the Query Builder window, enter the following text: select alias, homeserver from subscriber where alias = `ShortName'

For ShortName, enter the short name of the subscriber whose mail file you just moved, enclosing the short name in single quotes.

f. Click Execute.

g. In the results pane, verify that the homeserver field has been updated.

h. Close the Query Builder window and exit CUDLE.


Moving the Unity Messaging System, UAmis, and UOmni Mail Files

The Unity Messaging System, UAmis, and UOmni mail files are used for specific functions in Cisco Unity. You use the same procedures to move these special mail files that you use to move ordinary subscriber mail files—but with a few extra steps to prevent problems that can occur after the mail files are moved.

The following sections describe the mail files and how to move them correctly:

Unity Messaging System Mail File

UAmis Mail File

UOmni Mail File

Unity Messaging System Mail File

When an unidentified caller—an outside caller or a caller from inside the organization who is calling from a phone that is not associated with a subscriber account (such as a conference room)—leaves a message for a subscriber, Cisco Unity gives the message to the subscriber home server and stores it in the subscriber mail file. Such messages are identified as coming from the Unity Messaging System mail file, which is homed on the server that Cisco Unity gives the message to, and has the display name Unity Messaging System.

For more information on the Unity Messaging System mail file and its associated account, refer to the "Default Accounts and Message Handling" chapter in the Cisco Unity System Administration Guide. The guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/sag/sag405/dom/index.htm.

To Move the Unity Messaging System Mail File


Step 1 Follow the Lotus Domino procedures for moving mail files between servers.

Step 2 Verify that the new mail file has been created on the destination server, and that the Person document has been updated with the new mail server name in the directory replica on the Domino server that Cisco Unity monitors. (This is the Domino server that was selected in the Message Store Configuration wizard during Cisco Unity setup.)

Step 3 If the destination server contains at least one other Cisco Unity subscriber mail file associated with the same Cisco Unity server, skip to Step 5.

If the destination server does not contain at least one other Cisco Unity subscriber mail file associated with the same Cisco Unity server, notifications will not be sent when activity occurs on that subscriber mail file, including MWI notifications. To fix the problem, continue with Step 4.

Step 4 Do one of the following (each action will result in the identical result, so do the one that is most convenient to you):

Restart the Cisco Unity server.

Wait for the next scheduled MWI resynchronization. By default, MWIs are resynchronized each day at midnight, but the time can be changed in the Cisco Unity Telephony Integration Manager (UTIM).

Use UTIM to resynchronize MWIs, as follows:

On the Windows Start menu of the Cisco Unity server, click Programs > Cisco Unity > Manage Integrations.

Expand the tree in the left pane.

Click Properties.

In the Integration section of the properties page, click Resynchronize Now.

Exit UTIM.

Step 5 Verify that Cisco Unity has become aware of the new location of the mail file, which occurs after Cisco Unity synchronizes its database with the Domino directory. Cisco Unity synchronizes with the Domino directory every minute, but you can verify that the synchronization has completed by using the Cisco Unity Data Link Explorer (CUDLE) tool, as follows:

a. On the Cisco Unity server, double-click the Cisco Unity Tools Depot icon on the desktop.

b. In the left pane, expand Diagnostic Tools.

c. Double-click Data Link Explorer.

d. Click View > Query Builder.

e. In the Query Builder window enter the following text: select alias, homeserver from subscriber where alias = `Unity_<ServerName>'

For ServerName, enter the Cisco Unity server name for the Unity Messaging account, enclosing the Unity_<ServerName> in single quotes.

f. Click Execute.

g. In the results pane, verify that the homeserver field has been updated.

h. Close the Query Builder window and exit CUDLE.

Step 6 If you did not restart the Cisco Unity server in Step 4, messages from unidentified callers may become stuck in the Unity Messaging Repository (UMR). Do the following sub-steps to prevent the problem:

a. On the Windows Start menu, click Programs > Administrative Tools > Services.

b. From the Services window, stop and restart the AvUMRSyncSvr service.


UAmis Mail File

Outgoing AMIS messages are placed in a Domino mail file that has the name UAmis_<Servername>. For more information on the UAmis mail file, refer to the "UAmis Account" section in the "AMIS Networking" chapter of the Networking in Cisco Unity Guide. The guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/dom/index.htm.

To Move the UAmis Mail File


Step 1 Follow the Lotus Domino procedures for moving mail files between servers.

Step 2 Verify that the new mail file has been created on the destination server, and that the Person document has been updated with the new mail server name in the directory replica on the Domino server that Cisco Unity monitors. (This is the Domino server that was selected in the Message Store Configuration wizard during Cisco Unity setup.)

Step 3 If the destination server contains at least one other Cisco Unity subscriber mail file associated with the same Cisco Unity server, skip to Step 5.

If the destination server does not contain at least one other Cisco Unity subscriber mail file associated with the same Cisco Unity server, continue with Step 4.

Step 4 Do one of the following (each action will result in the identical result, so do the one that is most convenient to you):

Wait for the next scheduled MWI resynchronization. By default, MWIs are resynchronized each day at midnight, but the time can be changed in the Cisco Unity Telephony Integration Manager (UTIM).

Use UTIM to resynchronize MWIs, as follows:

On the Windows Start menu of the Cisco Unity server, click Programs > Cisco Unity > Manage Integrations.

Expand the tree in the left pane.

Click Properties.

In the Integration section of the properties page, click Resynchronize Now.

Exit UTIM.

Step 5 Verify that Cisco Unity has become aware of the new location of the mail file, which occurs after Cisco Unity synchronizes its database with the Domino directory. Cisco Unity synchronizes with the Domino directory every minute, but you can verify that the synchronization has completed by using the Cisco Unity Data Link Explorer (CUDLE) tool, as follows:

a. On the Cisco Unity server, double-click the Cisco Unity Tools Depot icon on the desktop.

b. In the left pane, expand Diagnostic Tools.

c. Double-click Data Link Explorer.

d. Click View > Query Builder.

e. In the Query Builder window enter the following text: select alias, homeserver from subscriber where alias = `UAmis_<ServerName>'

For ServerName, enter the Cisco Unity bridgehead server name for the UAmis account, enclosing the server name in single quotes.

f. Click Execute.

g. In the results pane, verify that the homeserver field has been updated.

h. Close the Query Builder window and exit CUDLE.

Step 6 Restart the Cisco Unity server.


UOmni Mail File

Administrative messages from the Cisco Unity Bridge to create, modify, or delete Bridge subscribers are placed in the special mail files that has the display name UOmni_<ServerName>. For more information on the UOmni mail file, refer to the "UOmni Account" section in the "About Bridge Networking" chapter of the Cisco Unity Bridge Networking Guide. The guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/bnet/dom/index.htm.

To Move the UOmni Mail File


Step 1 Follow the Lotus Domino procedures for moving mail files between servers.

Step 2 Verify that the new mail file has been created on the destination server, and that the Person document has been updated with the new mail server name in the directory replica on the Domino server that Cisco Unity monitors. (This is the Domino server that was selected in the Message Store Configuration wizard during Cisco Unity setup.)

Step 3 If the destination server contains at least one other Cisco Unity subscriber mail file associated with the same Cisco Unity server, skip to Step 5.

If the destination server does not contain at least one other Cisco Unity subscriber mail file associated with the same Cisco Unity server, notifications will not be sent when activity occurs on that subscriber mail file, including MWI notifications. To fix the problem, continue with Step 4.

Step 4 Do one of the following (each action will result in the identical result, so do the one that is most convenient to you):

Wait for the next scheduled MWI resynchronization. By default, MWIs are resynchronized each day at midnight, but the time can be changed in the Cisco Unity Telephony Integration Manager (UTIM).

Use UTIM to resynchronize MWIs, as follows:

On the Windows Start menu of the Cisco Unity server, click Programs > Cisco Unity > Manage Integrations.

Expand the tree in the left pane.

Click Properties.

In the Integration section of the properties page, click Resynchronize Now.

Exit UTIM.

Step 5 Verify that Cisco Unity has become aware of the new location of the mail file, which occurs after Cisco Unity synchronizes its database with the Domino directory. Cisco Unity synchronizes with the Domino directory every minute, but you can verify that the synchronization has completed by using the Cisco Unity Data Link Explorer (CUDLE) tool, as follows:

a. On the Cisco Unity server, double-click the Cisco Unity Tools Depot icon on the desktop.

b. In the left pane, expand Diagnostic Tools.

c. Double-click Data Link Explorer.

d. Click View > Query Builder.

e. In the Query Builder window enter the following text: select alias, homeserver from subscriber where alias = `UOmni_<ServerName>'

For ServerName, enter the Cisco Unity bridgehead server name for the UOmni account, enclosing the server name in single quotes.

f. Click Execute.

g. In the results pane, verify that the homeserver field has been updated.

h. Close the Query Builder window and exit CUDLE.

Step 6 On Cisco Unity bridgehead server, on the Windows Start menu, click Programs > Administrative Tools > Services.

Step 7 From the Services window, stop and restart CsBridgeConnector, which is the Bridge Connector service.

The Bridge Connector monitors the UOmni mail file. Restarting it immediately after the mail file move ensures that Person files that are associated with Bridge subscribers are created correctly and messages do not get stuck in the UOmni mail file. After you have restarted the Connector, Bridge subscribers can be added, modified, and deleted without any problems.

Step 8 Restart the Cisco Unity server.