vania-janet/multiturn-rag-retrieval-data huggingface dataset:
High-Availability 

IBM Cloud® Databases for Redis is a managed cloud database service that is fully integrated into the IBM Cloud environment. The database, storage, and supporting infrastructure all run in IBM Cloud.



 Database HA Features 

Databases for Redis provides replication, fail-over, and high-availability features to protect your databases and data from infrastructure maintenance, upgrades, and failures. Deployments contain a cluster with two data members in a primary plus replica configuration, and kept in sync by using asynchronous replication. High-availability is monitored and managed with three [Redis sentinels](https://redis.io/topics/sentinel).

By default, data persistence is enabled on all deployments and your data is written to disk. The data persistence model uses [preamble snapshots and AOF (Append Only File)](https://redis.io/topics/persistence). The interval for Redis to write to disk (fsync) is set to [once every second](https://redis.io/topics/persistencehow-durable-is-the-append-only-file).

You can turn off data persistence, which is useful for [configuring Redis as a cache](https://cloud.ibm.com/docs/databases-for-redis?topic=databases-for-redis-redis-cache).





 HA for your Application 

You want to design your applications to handle a temporary loss in connectivity to your deployment or to IBM Cloud.

Many Redis clients have features for error checking and handling. For example,



* The Python client [Redis.py](https://github.com/andymccurdy/redis-pyconnections) produces a ConnectionError when a connection fails and another command is run. The client can also issue health checks periodically or before commands.
* The Java client [Jedis](https://github.com/xetorthio/jedis/wiki) produces a JedisConnectionException when it can't reach the database, and it tries to reconnect.
General Data Protection Regulation (GDPR) 

If you have an account with IBM Cloud, your personal data is held by IBM Cloud. The IBM Data Processing Addendum (Addendum) applies to the processing of client's personal data by IBM on behalf of client in order to provide IBM standard services.
[IBM DPA](https://www.ibm.com/support/customer/zz/en/dpa.html)

Databases for Redis processes limited client Personal Information (PI) in the course of running the service and optimizing the user experience.

Databases for Redis provides a [Data Sheet Addendum (DSA)](https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=FCCD4BA07A5D11E89D57EFEED3CB8BE9) with its policies as a Data Processor regarding content and data protection.





 HIPAA 

Databases for Redis meets the required IBM controls that are commensurate with the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Security and Privacy Rule requirements. These requirements include the appropriate administrative, physical, and technical safeguards required of Business Associates in 45 CFR Part 160 and Subparts A and C of Part 164. HIPAA must be requested at the time of provisioning and requires a representative to sign a Business Associate Addendum (BAA) agreement with IBM.





 PCI DSS 

Databases for Redis are compliant with the Payment Card Industry Data Security Standard (PCI DSS). IBM Cloud completes annual PCI DSS assessments by using an approved Qualified Security Assessor (QSA), and the resulting Attestations of Compliance (AOCs) and Service Responsibility Matrix (SRM) guides are available upon customer request. Auditors reviewed Databases for Redis for compliance under PCI DSS version 3.2.1 at Service Provider Level 1.

Customers are responsible for the storing, processing, and transmission of their cardholder data, and can create cardholder data environments (CDEs) that can store, transmit, or process cardholder data by using Databases for Redis.
Database (IBM Data Virtualization, IBM Db2, Microsoft SQL, Oracle, Postgres) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) 
 FileNet P8 ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) 
 HCL Notes ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) 
 IBM Cloud Object Storage ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) 
 Local file system ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) 
 Salesforce ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) !
Monitoring Integration 

Monitoring for IBM Cloud® Databases for Redis deployments is provided through integration with the IBM Cloud® Monitoring service. Your deployments forward selected information so you can monitor deployment health and resource usage. To see your Databases for Redis dashboards in IBM Cloud Monitoring, you have to [Enable Platform Metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling) in the same region as your deployment. If you have deployments in more than one region, you have to provision IBM Cloud Monitoring and enable platform metrics in each region.

To access IBM Cloud Monitoring from your deployment, use the Monitoring link from the right menu. (If you do not already have a monitoring service in the same region as your deployment it says Add monitoring.)

Zoom

![The Monitoring link in a deployment](https://cloud.ibm.com/docs-content/v1/content/c1b02d6157702384a9668d8c58bb951e69117793/databases-for-redis/images/monitoring-ui-link.png)

Figure 1. The Monitoring link in a deployment

To access your deployment's monitoring dashboard from IBM Cloud Monitoring, it's in the sidebar, under IBM.

Zoom

![Cloud databases dashboard in monitoring](https://cloud.ibm.com/docs-content/v1/content/c1b02d6157702384a9668d8c58bb951e69117793/databases-for-redis/images/monitoring-ibm-list.png)

Figure 2. Cloud databases dashboard in monitoring



 Monitoring Availability 

IBM Cloud Monitoring is available for deployments in every region. Deployments in Multi-zone Regions (MZRs) - eu-gb, eu-de, us-east, us-south, jp-tok, au-syd - have their metrics in the corresponding region.

If you have deployments that are in Single-zone Region (SZR) che01 then your logs are forwarded to a IBM Cloud Monitoring instance in another region.
Database Versioning Policy 

When you provision a Cloud Databases deployment, you can choose from the versions currently available on IBM Cloud. Find the latest versions from the [catalog pages](https://cloud.ibm.com/catalog?category=databases), the [IBM Cloud Databases CLI](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployables-show), or the [IBM Cloud Databases API](https://cloud.ibm.com/apidocs/cloud-databases-apiget-all-deployable-databases).



 Version Tags 

Preferred - The recommended and default database version for all new deployments. It's the most stable, up-to-date version of the database from both a database-level and service-level perspective.

Preview - A preview database version is released for a limited time to try available functions. Often it is the newest available version available from the database project maintainers in preparation for making it the "Preferred" version. While deployable, preview versions are not suitable for production, as they are excluded from service-level agreements and support. Also, a preview version isn't guaranteed to become a production-level release. IBM reserves the right to ask a customer to delete a deployment that uses a preview version.

Deprecated - Old versions and versions nearing their end of life dates are marked as "Deprecated". Provisions and restores of deployments that run a deprecated version are still available and deployments that are running a deprecated version continue to be supported. However, you are encouraged to upgrade to the new "Preferred" version of the database as deprecated versions are eventually removed from IBM Cloud and are no longer provisionable, restorable, or supported.

Untagged - Untagged database versions are fully supported and deployable versions. They are usually slightly older than the current preferred version, but they are still supported by the database project maintainers. They continue to be supported on Cloud Databases deployments until their deprecation is announced.





 Deprecation of Major Versions 

IBM Cloud Databases tries to support a major version of a database for 3 years from its release.
High-Availability 

IBM Cloud® Databases for Elasticsearch is a managed cloud database service that is fully integrated into the IBM Cloud environment. The database, storage, and supporting infrastructure all run in IBM Cloud.

Databases for Elasticsearch provides replication, fail-over, and high-availability features to protect your databases and data from infrastructure maintenance, upgrades, and failures. Deployments contain a cluster with three nodes where all three are data nodes and any node can be the primary node. Elasticsearch clusters work on a quorum system, if one data member becomes unreachable, your cluster continues to operate normally. If more nodes go down and the cluster can't maintain a quorum, it becomes read-only to protect your data. The cluster resumes normal operations when the nodes are recovered or new nodes are added.

When you add an index to Elasticsearch, it splits the data into shards and spreads those shards across the nodes in the cluster. The sharded configuration allows for Elasticsearch to run concurrent operations on your data across all the nodes. Concerning high-availability, not all shards contain a complete copy of all the data in the index. To enforce that multiple complete copies of the data are spread across the cluster in a node failure, you should ensure that when you create an index you set the replica count to at least 1. Setting the replica count to 0 can cause data loss.

If you [add nodes to your cluster](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-horizontal-scaling), Elasticsearch automatically rebalances the shards and replicas of your indexes across the newly added node or nodes. Adding nodes can provide more stability in a multi-node failure, since you can lose more nodes and maintain a quorum. More nodes also improves performance.



 Staying Production Ready 

To keep your IBM Cloud® Databases for Elasticsearch database up and running, do not drop the icd-auth index. This index stores your database, as well as all user accounts and is critical to operational integrity.





 Application-level High-Availability 

Applications that communicate over networks and cloud services are subject to transient connection failures.
Integrating services 

IBM® Key Protect for IBM Cloud® integrates with a number of IBM Cloud services to enable encryption with customer-managed keys for those services. Encryption with customer-managed encryption keys is sometimes called Bring Your Own Key (BYOK).



 Database service integrations 

You can integrate Key Protect with the following database services.



Table 1. Supported database services.

 Service Description Links 

 [IBM Cloudant for IBM Cloud (IBM Cloud Dedicated)](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloud-dedicated) IBM Cloudant is a document-oriented database as a service (DBaaS). It stores data as documents in JSON format. [View docs](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-securing-your-data-in-cloudant) 
 [IBM Cloud Databases for DataStax](https://cloud.ibm.com/docs/databases-for-cassandra?topic=databases-for-cassandra-getting-started) IBM Cloud Databases for DataStax, an enterprise-grade Apache Cassandra cloud solution with high performance, workload flexibility, and proven reliability. [View docs](https://cloud.ibm.com/docs/databases-for-cassandra?topic=cloud-databases-key-protect) 
 [IBM Cloud Databases for Elasticsearch](https://cloud.ibm.com/docs/databases-for-elasticsearch) IBM Cloud Databases for Elasticsearch is a managed Elasticsearch service that is hosted in the IBM Cloud and integrated with other IBM Cloud services. [View docs](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=cloud-databases-key-protect) 
 [IBM Cloud Databases for EnterpriseDB](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-getting-started) IBM Cloud Databases for EnterpriseDB offers a single source for purchase, deployment and support of EDB Postgres Enterprise and Standard editions based on PostgreSQL.
IBM Cloud® Databases for MySQL docs 

IBM Cloud® Databases for MySQL is a serverless, cloud database service that is fully integrated into the IBM Cloud environment. Use IBM Cloud® Databases for MySQL to use a cloud database system without purchasing and setting up your own hardware, installing your own database software, or managing the database yourself.

 Developer tools 

[API & SDK reference](https://cloud.ibm.com/apidocs/cloud-databases-api/cloud-databases-api-v5introduction)[CLI reference](https://cloud.ibm.com/docs/databases-cli-plugin)[Terraform reference](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/database)

 Recommended content 

[Getting Started A brief tutorial to introduce using an IBM Cloud® Databases for MySQL deployment.](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-getting-started)[Setting the Admin Password The IBM Cloud® Databases for MySQL service is provisioned with an admin user, so you can manage MySQL by using its command line tool, mysql.](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-admin-password)[Managing MySQL Connections Connections to your IBM Cloud® Databases for MySQL deployment use resources, so it is important to consider how many connections you need when tuning your deployment's performance.](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-managing-mysql-connections)

 Learn more 

[IBM Developer<br><br>Visit IBM Developer for technical articles, code patterns, tutorials, and more.<br><br>!
Monitoring Integration 

Monitoring for IBM Cloud® Databases for PostgreSQL deployments is provided through integration with the IBM Cloud® Monitoring Monitoring service. Your deployments forward selected information so you can monitor deployment health and resource usage. To see your Databases for PostgreSQL dashboards in IBM Cloud Monitoring, you must [Enable Platform Metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling) in the same region as your deployment. If you have deployments in more than one region, you must provision IBM Cloud Monitoring and enable platform metrics in each region.

To access IBM Cloud Monitoring from your deployment, use the Monitoring link from the right menu. (If you do not already have a monitoring service in the same region as your deployment it says Add monitoring.)

Zoom

![The Monitoring link in a deployment](https://cloud.ibm.com/docs-content/v1/content/3505da55c475bf1edbe3eb3496324ba13941b783/databases-for-postgresql/images/monitoring-ui-link.png)

Figure 1. The Monitoring link in a deployment

To access your deployment's monitoring dashboard from IBM Cloud Monitoring, it's in the sidebar, under IBM.

Zoom

![Cloud databases dashboard in monitoring](https://cloud.ibm.com/docs-content/v1/content/3505da55c475bf1edbe3eb3496324ba13941b783/databases-for-postgresql/images/monitoring-ibm-list.png)

Figure 2. Cloud databases dashboard in monitoring



 Monitoring Availability 

IBM Cloud Monitoring monitoring is available for deployments in every region. Deployments in Multi-zone Regions (MZRs) - eu-gb, eu-de, us-east, us-south, jp-tok, jp-osaau-syd - have their metrics in the corresponding region.
* Outside of the EU, see [Requesting support for resources outside the European Union](https://cloud.ibm.com/docs/watson/getting-started-gdpr-sar.htmlrequest-non-EU).





 European Union General Data Protection Regulation (GDPR) 

IBM is committed to providing our clients and partners with innovative data privacy, security and governance solutions to assist them on their journey to GDPR compliance.

Learn more about IBM's own GDPR readiness journey and our GDPR capabilities and offerings to support your compliance journey [here](http://www.ibm.com/gdpr).





 Health Insurance Portability and Accountability Act (HIPAA) 

US Health Insurance Portability and Accountability Act (HIPAA) support is available for Premium plans in the Washington, DC location created on or after 1 April 2019. See [Enabling EU and HIPAA supported settings](https://cloud.ibm.com/docs/account?topic=account-eu-hipaa-supportedeu-hipaa-supported) for more information.





 Labeling and deleting data in Language Translator 

The Language Translator service temporarily caches translation data from translation requests and stores training data that is used to create custom models.



 Translation data and documents 

Documents that are submitted to the service for translation through the Translate document method are stored internally to provide the translated file, and to support additional Translate document requests by reference to the original uploaded document. The original document and any associated translated documents are deleted only after they are not used in subsequent Translate document requests for a period of 15 days. The Delete document method can be used to delete documents before the deletion deadline.

Translation data and documents are encrypted in flight and at rest.





 Custom model training data 

When you train a custom model, the training data that you use to create the model is stored to provide you with the custom model. Custom models and training data are encrypted in flight and at rest. The encrypted training data persists in storage until the model is deleted with the Delete model method.

Custom models can only be deleted at the model level. Component data used to create a custom model cannot be deleted.
Additionally, Databases for PostgreSQL provides independent scaling of disk, RAM, and vCPU, as well as auto-scaling capabilities and hourly billing. These features help provide greatly increase granularity on right-sizing database use for application workload.

Databases for PostgreSQL is a multi-tenant offering by design and customers have multiple levers for increased isolation that is detailed in our [Security and Compliance section](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-manage-security-compliance). For example, configuring a database with vCPUs (referred to as Dedicated Cores) introduces hypervisor-level isolation. Alternatively, if that particular lever of isolation is not necessary, customers can configure databases to pay solely for RAM and disk capacity, without restrictions on movement between these modes. It is an online activity to introduce or remove your usage of Dedicated Cores.





 Step 1: Before you begin 



* You need an [IBM Cloud account](https://cloud.ibm.com/registration).
* You also nneed a Databases for PostgreSQL deployment. Provision one from the [IBM Cloud catalog](https://cloud.ibm.com/catalog/services/databases-for-postgresql). Give your deployment a memorable name that appears in your account's Resource List.
* [Set the Admin Password](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-admin-password) for your deployment.
* Install [pgAdmin4](https://www.pgadmin.org/download/).
* Review the [Getting to production](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-best-practices) documentation for general guidance on setting up a basic Databases for PostgreSQL deployment.







 Step 2: Connect to your database with the CLI
Monitoring Integration 

Monitoring for IBM Cloud® Databases for MongoDB deployments is provided through integration with the IBM Cloud® Monitoring service. Your deployments forward selected information so you can monitor deployment health and resource usage. To see your Databases for MongoDB dashboards in IBM Cloud Monitoring, you have to [Enable Platform Metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling) in the same region as your deployment. If you have deployments in more than one region, you have to provision IBM Cloud Monitoring and enable platform metrics in each region.

To access IBM Cloud Monitoring from your deployment, use the Monitoring link from the right menu. (If you do not already have a monitoring service in the same region as your deployment it says Add monitoring.)

Zoom

![The Monitoring link in a deployment](https://cloud.ibm.com/docs-content/v1/content/ec83e0c9f915f4acf715222aaa5b8387c028200c/databases-for-mongodb/images/monitoring-ui-link.png)

Figure 1. The Monitoring link in a deployment

To access your deployment's monitoring dashboard from IBM Cloud Monitoring, it's in the sidebar, under IBM.

Zoom

![Cloud databases dashboard in monitoring](https://cloud.ibm.com/docs-content/v1/content/ec83e0c9f915f4acf715222aaa5b8387c028200c/databases-for-mongodb/images/monitoring-ibm-list.png)

Figure 2. Cloud databases dashboard in monitoring



 Monitoring Availability 

IBM Cloud Monitoring is available for deployments in every region. Deployments in Multi-zone Regions (MZRs) - eu-gb, eu-de, us-east, us-south, jp-tok, au-syd - have their metrics in the corresponding region.

If you have deployments that are in Single-zone Region (SZR)che01 then your logs are forwarded to an IBM Cloud Monitoring instance in another region.
[IBM Cloud Databases](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-about) provide automatic daily backups that are stored in the same account and geography. Backups are typically stored in [cross-regional storage](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-dashboard-backups&interface=uibackup-locations) and should therefore be immune to a single region outage. This facility is reliable and convenient, but does not currently support backup storage in a specified alternate region or account. However, backups can be [restored to another region or account](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-dashboard-backups&interface=ui), so recovery to a passive deployment (cold standby) is supported.

It is also possible to use database-specific clients (for example pg_dump for PostgreSQL) to backup IBM Cloud Databases to arbitrary storage by using customer automation. If used, these backups should be stored in Cloud Object Storage in an alterative region and in the backup account as described in [Backup accounts](https://cloud.ibm.com/docs/enterprise-account-architecture?topic=enterprise-account-architecture-bcdraccounts).





 Virtual servers 

Both [volume snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-backups-vpc-best-practices&interface=ui) and [Veeam](https://cloud.ibm.com/docs/vpc?topic=vpc-about-veeam) are available to backup virtual servers. Veeam is preferred for extensive feature set and its ability to backup application workloads. However, Veeam does require deploying an agent to backup workloads not hosted on VMWare. The Veeam server that is used for backups should be located in a alterative region and in the backup account as described in [Backup accounts](https://cloud.ibm.com/docs/enterprise-account-architecture?topic=enterprise-account-architecture-bcdraccounts).