Jump to: navigation, search

Configure Regional Voicemail Storage

If any portion of your data center deployment lies in a geographic area where data is required to remain within that area, then you must configure regional restrictions on voicemail storage.

You can now comply with those restrictions by using replication options for regional voicemail keyspaces. With these options, Feature Server can specify that data storage and replication occur in data centers located in a particular region.

Important
Do not use voicemail while you make these changes, to avoid errors.


1

We'll continue to use us_east and us_west from the Add a New Data Center example, (illustrated at left) and add two more for Europe: eu_east and eu_west. In this configuration:

  • Voicemail messages that were processed in the U.S. data centers must be stored in the U.S., and those received in the European data centers must be stored in Europe.
  • All voicemail messages must be accessible from any Feature Server nodes in the cluster, regardless of where the messages are physically stored.
This example satisfies the regional voicemail storage requirement by using separate and dedicated Cassandra keyspaces for storing voicemail messages. Your role is to configure the necessary replication options for those special keyspaces. You can follow these instructions, but substitute your installation’s specifics (such as key space names) for the names used here.


1

The example continues. The general (global) keyspace contains these replication options:

us_east=2, us_west=2, eu_east=2, eu_west=2

Read below how to implement them.

  • regionalKeyspace defines the keyspace name.
    Add these regional keyspace definitions to the TServer/Cassandra section in all Feature Servers of a region, to create two new regional keyspaces: us_vm (which will hold voicemails for us_east and us_west) and eu_vm (which will hold voicemails for eu_east and eu_west):
    regionalKeyspace = us_vm
    and
    regionalKeyspace = eu_vm
  • regionalReplicationOptions defines the number of replication options.
    Add these replication option definitions to the TServer/Cassandra section of the master Feature Server and the confSync Feature Server of each region, to configure the number of replication options:
    regionalReplicationOptions = us_east=2,us_west=2
    and
    regionalReplicationOptions = eu_east=2,eu_west=2
    Important
    You must set regionalKeyspace and regionalReplicationOptions when all the feature servers of a region are up and running, or before the first start of the feature servers.
  • replicationStrategyClassName defines the replication strategy.
    Specify this option in TServer/Cassandra section of Confsync Feature Servers of each region before their first start, to set the replication strategy:
    replicationStrategyClassName = NetworkTopologyStrategy

Now, voicemail that is stored at particular location should be accessible from any Feature Server in a Cassandra cluster when all the Feature Servers in a particular region are down; then the voicemails stored in that region are not accessible by any Feature Server.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on July 21, 2017, at 01:34.