Skip to content

Latest commit

 

History

History
executable file
·
72 lines (50 loc) · 5.4 KB

ha-dr.md

File metadata and controls

executable file
·
72 lines (50 loc) · 5.4 KB
copyright lastupdated subcollection
years
2019
2019-06-04
text-to-speech

{:shortdesc: .shortdesc} {:external: target="_blank" .external} {:tip: .tip} {:important: .important} {:note: .note} {:deprecated: .deprecated} {:pre: .pre} {:codeblock: .codeblock} {:screen: .screen} {:javascript: .ph data-hd-programlang='javascript'} {:java: .ph data-hd-programlang='java'} {:python: .ph data-hd-programlang='python'} {:swift: .ph data-hd-programlang='swift'}

High availability and disaster recovery

{: #ha-dr}

The {{site.data.keyword.texttospeechfull}} service is highly available within any {{site.data.keyword.cloud_notm}} location (for example, Dallas or Washington, DC). However, recovering from potential disasters that affect an entire location requires planning and preparation. {: shortdesc}

You are responsible for understanding your configuration, customization, and usage of the service. You are also responsible for being ready to re-create an instance of the service in a new location and to restore your data in any location.

High availability

{: #high-availability}

The {{site.data.keyword.texttospeechshort}} service supports high availability with no single point of failure. The service achieves high availability automatically and transparently by means of the multi-zone region (MZR) feature provided by {{site.data.keyword.cloud_notm}}.

{{site.data.keyword.cloud_notm}} enables multiple zones that do not share a single point of failure within a single location. It also provides automatic load balancing across the zones within a region.

Disaster recovery

{: #disaster-recovery}

Disaster recovery can become an issue if an {{site.data.keyword.cloud_notm}} location experiences a significant failure that includes the potential loss of data. Because MZR is not available across locations, you must wait for {{site.data.keyword.IBM_notm}} to bring a location back online if it becomes unavailable. If underlying data services are compromised by the failure, you must also wait for {{site.data.keyword.IBM_notm}} to restore those data services.

In the event of a catastrophic failure, {{site.data.keyword.IBM_notm}} might not be able to recover data from database backups. In this case, you need to restore your data to return your service instance to its most recent state. You can restore the data to the same or to a different location.

For the {{site.data.keyword.texttospeechshort}} service, only data for custom voice models is stored on {{site.data.keyword.cloud_notm}}. Your disaster recovery plan includes knowing, preserving, and being prepared to restore your custom voice models.

Backing up custom voice models

{: #disaster-recovery-backup}

Preserve the following information about your custom voice models and their custom entries:

  • A list of all of your custom voice models and their definitions. To list information about your custom models:
    • Use the GET /v1/customizations method to list information about all custom models. For more information, see Querying all custom models.
    • Use the GET /v1/customizations/{customization_id} method to list information about a specified custom model. For more information, see Querying a custom model.
  • Information about all custom entries (word/translation pairs) in your custom voice models:
    • Use the GET /v1/customizations/{customization_id}/words method to list information about all word/translation pairs from a custom model. For more information, see Querying all words from a custom model.
    • Use the GET /v1/customizations/{customization_id}/words/{word} method to list information about a specified word/translation pair from a custom model. For more information, see Querying a single word from a custom model.

It is a best practice to preserve this information in a format that you can use to re-create your custom voice models in the event of a failure. Actively maintaining the information about your custom models and custom entries, and preparing the calls listed in the following section ahead of time, can enable you to recover as quickly as possible.

Restoring custom voice models

{: #disaster-recovery-restore}

If you need to recover from a disaster, you can use the backup information to re-create your custom voice models and their custom entries:

  1. To re-create your custom voice models, use the POST /v1/customizations method. For more information, see Creating a custom model.
  2. To add multiple word/translation pairs to your custom voice models, use the POST /v1/customizations/{customization_id}/words method. For more information, see Adding multiple words to a custom model.
  3. To add single word/translation pair to your custom voice models, use the POST /v1/customizations/{customization_id}/words/{word} method. For more information, see Adding a single word to a custom model.

You can add all of your custom entries at once, in groups, or one at a time.