|
Wednesday, 12 October 2005 15:47 |
How to cluster Avaya Voicemail Pro using Veritas Cluster Server.
This isn't the only way to do it, and it may not be the best, but it works and it has been tested. If you have any comments, or ideas for improvement, let me know.
Add a new domain user, called 'voicemail'.
In the absense of any documentation from Avaya listing the privileges required for the voicemail user, I made it a domain administrator.
Set the password not to expire.
Create a new dynamic disk group (cluster). I chose a 1GB disk group initially, and named it VMDG.
Create a 20MB partition and mount it. This partition is for registry replication, so I named it VMRRVol.
Create another partition using the remaining available space and mount it. This partition is for Voicemail data, so I named it VMVol.
Run Avaya Voicemail Pro Setup on node 1.
Select English (US) language (there's no UK English option :( )
Enter company details.
Select compact install
Select the newly created voicemail user when prompted.
If you get an error about IIS not being avaialable, ignore it, as we're not using web campaigns.
When prompted, reboot the node.
When the node has rebooted, enter the details for your email server.
Import the Disk Group (VMDG).
Stop the VoicemailPro and VoicemailProDB services.
Run regedit.
Navigate to HKLM\Software\Network Alchemy
Change all occurences of "C:\Program Files\Avaya\IP Office\VMPro" to the drive letter of VMVol, e.g. R:\
Copy the contents of "C:\Program Files\Avaya\IP Office\VMPro" to the drive letter of VMVol, e.g. R:\
Test the voicemail, by starting the VoicemailPro and VoicemailProDB services.
Stop the VoicemailPro and VoicemailProDB services.
Now the services are working, it's time to brng them under VCS control.
Run the VCS Application Configuration Wizard.
Select New Service Group. Name it Voicemail.
In the list of available systems, select node 1.
Create a resource of type GenericService, and select the VoicemailPro service. Select Yes when prompted to set the startup type to Manual.
Create a resource of type GenericService, and select the VoicemailProDB service. Select Yes when prompted to set the startup type to Manual.
Select Configure other components.
Select the Registry Replication and Network resources.
Set the Registry Replication resource to monitor:
- HKLM\Software\Avaya
- HKLM\Software\Network Alchemy
Set the virtual server IP address as required.
Configure the Application dependancy.
I found that the password for the voicemail user for the VoicemailPro service resource wasn't correct. To edit this, edit the resource properties and enter the encrypted password. To get the encrypted password, at a command prompt, run "vcsencrypt -agent", and enter the unencrypted password.
Test the voicemail, by bringing the service group online.
To add additional nodes (as a 1-node service group isn't very redundant), take the service group offline.
Import the disk group on node 2.
Install the Voicemail Pro software, using the same settings as on node 1.
Run the VCS Application Configuration Wizard on node 2.
Modify the service group, and make no changes, other than adding node 2 to the available systems list.
I found that the MAC address of node 2 wasn't added to the IP and NIC resources, so I had to add these manually.
Test the service group, including switching, and ensure that messages etc are retained.
Congratulate yourself.
Optional: You might like to delete the following directories off the nodes, for tidiness sake:
- Accounts
- Campaigns
- Conference Data
- Greetings
- Logs
- Names
- VRL
- Wavs
These files can be found in C:\Program Files\Avaya\IP Office\VMPro\VM
|
