vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see [High availability for Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-ha-dr) and [Business continuity and disaster recovery for Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-bc-dr).



Table 5. Responsibilities for disaster recovery
The first column describes the task that the customer or IBM might be responsible for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM Responsibilities Your Responsibilities 

 Copy your data to another region. It is your responsibility to copy the data to another region. For more information, see [Regions](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions). 
 Restore the contents of the data in a single region. It is the responsibility of IBM to restore the contents of the data in a single region.
<br><br> * [Granting permissions to users](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-grant-permissions-serverless)<br><br><br> 
 Choose the right IBM Cloud Object Storage configuration <br><br> * Disaster Recovery (DR) Resiliency: You should use the IBM Cloud Object Storage Cross Regional resiliency option that backs up your data across several different cities in a region. In contrast, the Regional resiliency option back ups data in a single data center.<br> * Encryption: IBM Cloud Object Storage comes with default built-in encryption. You can also configure Object Storage to work with the BYOK Key Protect service.<br> * Service credentials: By default, IBM Cloud Object Storage uses IAM-style credentials. If you want to work with AWS-style credentials, you need to use the "Include HMAC Credential" option as described in Service credentials.<br> * Direct endpoints for IBM Cloud Object Storage: Always use direct endpoints for connectivity to the IBM Cloud Object Storage instance. This applies to the IBM Cloud Object Storage home instance as well as endpoints used from your applications (either your code or what you pass as parameters in the configurations at instance level or application level). Direct endpoints provide better performance than public endpoints and do not incur charges for any outgoing or incoming bandwidth.<br><br><br> <br><br> * Disaster Recovery (DR) Resiliency: [IBM Cloud Object Storage documentation.]
Disaster recovery is about surviving a catastrophic failure or loss of availability in a single location.

IBM Cloud Monitoring follows IBM Cloud requirements for [planning and recovering from disaster events](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimedisaster-recovery).

If a regional disaster occurs, consider the following information:



* The estimated recovery time for rebuilding the regional site and restoring the service at another location is 24 hours.
* You will have to update the endpoints of applications and monitoring agents to point to the ingestion endpoint in the new location.
* You will have to restore the service instance's metadata, that is, dashboards and alerts definitions, from your backups.



Historical data may be lost during a disaster. If you require historical metrics for auditing purposes, backup the metrics regularly by querying the metrics from the service and storing them at a remote backup site.



 Manual recovery of the service 

If a regional disaster occurs, the recovery time of the service depends on the recovery time for the region. To minimize the downtime of the service and impact to your business, you could implement a manual failover to switch to another region while the region is being restored. To reduce the time to get up and running in a new location, consider using access groups to manage permissions working with the service, and backup the monitoring metadata of each instance. You should backup your alerts, notifications, dashboards and team definitions on a regular basis.

How to continue working while a DR site is rebuilt?

If the applications and services that you are monitoring through a monitoring instance are all co-located in the same region, then you must wait for the region to be available again for business.

If you have deployed monitoring agents on your systems, and those systems are not impacted by the regional failure, you may choose to redirect metrics to other instances of monitoring in a different region. To redirect metric data, complete the following steps:



1. [Provision a monitoring instance](https://cloud.ibm.com/docs/monitoring?topic=monitoring-provision)
2. Reconfigure the monitoring agent of each system: Change the access key and ingestion endpoints in the agent configuration.
For more information about disaster recovery see the [IBM Disaster Recovery Plan](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimedisaster-recovery). Customer can help meet DR objectives by deploying their project in a development or test environment before deploying to production.<br><br>There are no other actions the customer needs to take to prepare for an event of a catastrophic failure in a region. 
 Meet high availability objectives IBM is available globally and load balanced from a single URL. It is highly available and continues to run even if your resources are unavailable. For more information about high availability, please see the [IBM service level objectives](https://cloud.ibm.com/docs/overview?topic=overview-slo) and the [sample application architecture](https://cloud.ibm.com/docs/overview?topic=overview-bcdr-app-recovery). N/A 
 Back up project data IBM performs regular electronic backups of project data with Recovery Time Objective (RTO) and Recovery Point Objective (RPO) of hours as documented in the [IBM Disaster Recovery Plan](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimedisaster-recovery). Customers are not responsible for backups for data stored by projects. However, customers can use project data via API, CLI, or by downloading the project.json from the UI and as a backup. 
 Restore project data IBM automatically restores project data from backups in case of a data loss event. Customers can retrieve project data via API, CLI, or by downloading the project.json from the UI
Disaster recovery includes tasks such as providing dependencies on disaster recovery sites, provision disaster recovery environments, data and configuration backup, replicating data and configuration to the disaster recovery environment, and failover on disaster events.



Table 5. Responsibilities for disaster recovery
The first column describes the task that a customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM Responsibilities Your Responsibilities 

 Meet disaster recovery objectives IBM follows best practices for disaster recovery. All IBM applications automatically recover and restart after any disaster event. For more information about disaster recovery, see the [IBM Disaster Recovery Plan](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimedisaster-recovery). Customers can help meet disaster recovery objectives by deploying their project in a development or test environment before they deploy to production. <br>\nThe customer does not have to take other actions to prepare for an event of a catastrophic failure in a region. 
 Meet high availability objectives IBM Cloud is available globally and load balanced from a single URL. It is highly available and continues to run even if your resources are unavailable. For more information about high availability, see the [IBM service level objectives](https://cloud.ibm.com/docs/overview?topic=overview-slo) and the [sample application architecture](https://cloud.ibm.com/docs/overview?topic=overview-bcdr-app-recovery). N/A
IBM restores the service in an alternative MZR from an IBM-managed backup. Existing DNS names are migrated to the backup deployment. When the disaster recovery process is complete, API traffic resumes automatically.

When the primary MZR is restored, the secondary deployment is migrated back to the primary site. After the migration is complete, the DNS is restored to its original routing.

For regional disaster recovery, you must create and maintain backup instances in other regions. To synchronize a service instance in one region with an instance in a different region, use the APIs.

If you need zero downtime during a regional disaster recovery, create and maintain backup instances in other regions. Review the API documentation and decide the data that you want backed up and restored if there is a disaster. To synchronize a service instance in one region with an instance in a different region, you can use the APIs mentioned [here](https://cloud.ibm.com/apidocs/event-notifications).

Some API examples are as follows:



Table 2. Example API endpoints

 Entity Endpoint Description 

 sources /v1/instances/{instance_id}/sources Your platform sources 
 topics /v1/instances/{instance_id}/topics All registered topics 
 rules /v1/instances/{instance_id}/rules All rules created on topics 
 destinations /v1/instances/{instance_id}/destinations All registered destinations 
 subscriptions /v1/instances/{instance_id}/subscriptions All the subscriptions 



For each data set that you need to back up and restore, use GET calls to get a copy of the data. And use the corresponding PUT / POST API to populate the new instance on a different region.
(https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-encryption) 
 Meet security and compliance objectives Maintain controls that are commensurate to various industry compliance standards such the Financial Services specification. Set up and maintain security and regulation compliance for your apps and data. 







 Disaster recovery 



Table 5. Responsibilities for disaster recovery

 Task IBM Responsibilities Your Responsibilities 

 Restore functionality for Activity Tracker Event Routing Automatically recover and restart Activity Tracker Event Routing components after any disaster event. <br>In case of a regional disaster, IBM Cloud service teams, who are responsible for the operations of services that generate auditing events, will point their service to Activity Tracker Event Routing endpoints in their alternate region within the same regulatory boundaries. [Complete the disaster recovery (DR) steps for Activity Tracker Event Routing](https://cloud.ibm.com/docs/atracker?topic=atracker-ha_drdr-atracker). 
 Backup Activity Tracker Event Routing components Daily backup of the Activity Tracker Event Routing infrastructure and components. N/A 



[] Recovered and restarted service components will not have customer data reloaded.
* A region might be a specific postal code area, a town, a city, a state, a group of states, or even a group of countries.
* A region contains [multiple availability zones](https://www.ibm.com/cloud/data-centers/) to meet local access, low latency, and security requirements for the region.



* MZR means multi-zone region. [Learn more](https://cloud.ibm.com/docs/overview?topic=overview-locationsmzr-table).







 Disaster recovery (DR) for App Configuration service in a region 

App Configuration is a regional service, and does not offer automatic cross-regional failover or cross-regional disaster recovery. If all of the availability zones in a region fail, App Configuration becomes unavailable in that region.

If an entire MZR becomes inoperative (usually due to a catastrophic disaster or failure), IBM runs disaster-recovery plans to restore service within 24 hours or less. IBM restores the service in an alternative MZR from an IBM-managed backup. Existing DNS names are migrated to the backup deployment. When the disaster recovery process is complete, API traffic resumes automatically.

When the primary MZR is restored, the secondary deployment is migrated back to the primary site. After the migration is complete, the DNS is restored to its original routing.

If you need zero downtime during a regional disaster recovery, create and maintain backup instances in other regions. To synchronize a service instance in one region with an instance in a different region, you can use the APIs mentioned [here](https://cloud.ibm.com/apidocs/app-configuration).
For more information, see MySQL's [Making MySQL Secure Against Attackers](https://dev.mysql.com/doc/refman/5.7/en/security-against-attack.html) documentation.







 Data Resilience 



* [Backups](https://cloud.ibm.com/docs/databases-for-mysql?topic=cloud-databases-dashboard-backups) are included in the service. Databases for MySQL backups are located in [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-about-cloud-object-storage&cloud-object-storage-about-cloud-object-storage) and are also [encrypted](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-security).
* Databases for MySQL deployments are configured with replication. Deployments contain a cluster with three data members. All members contain a copy of your data through [semisynchronous replication](https://dev.mysql.com/doc/mysql-replication-excerpt/8.0/en/replication-semisync.html), with a distributed consensus mechanism to maintain cluster state and handle failovers.
* If you deploy to an IBM Cloud Single-Zone Region (SZR), each database member is on a different host in the data center.
* If you deploy to an IBM Cloud Multi-Zone Region (MZR), the members are spread over the region's availability zone locations.







 Terms 



* [The IBM Privacy Policy](https://www.ibm.com/privacy/us/en/)
* [The IBM Cloud Notices and Terms of Use](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-terms)
The sections above describe how IBM MQ on Cloud provides high availability to handle outages or failures that might occur for individual workers on which queue managers are running, however there is a more extreme failure scenario in which a catastrophic failure causes all of the existing infrastructure and data to be unavailable or corrupted. We call the process of restoring the service following this type of failure "Cold Disaster Recovery", shortened to "Cold DR".

As an example a Cold DR scenario would occur if the entire data center in which MQ on Cloud infrastructure for a given region has been deployed is taken offline, for example due to a major natural disaster. In this case the persistent volume on which the queue manager runtime state is stored is no longer available (because it is stored within the single data center) so it will not be possible to restore the queue manager to its exact original state from before the catastrophic failure.



 IBM Responsibilities 

To enable IBM to restore the service following this type of catastrophic failure a configuration backup of every paid queue manager is taken every 24 hours and saved in an encrypted format in a storage location outside the active data center. The configuration backup includes the admin definitions of the queues, topics and channels that exist within the queue manager as well as TLS certificates that have been applied, but does not include runtime state such as persistent messages or channel sequence state because runtime state in a queue manager changes so frequently that restoring a copy of that data up to 24 hours old is typically less desirable to an enterprise than starting from a clean state.

Since restoring a queue manager from this configuration backup results in the loss of the runtime state such as persistent messages it is not an action that is taken lightly by IBM and so the IBM Operations team will first work with the infrastructure provider (e.g. IBM or Amazon Web Services) to recover the existing infrastructure. Only once it has been determined that the original infrastructure cannot be recovered in an acceptable timeframe will the Cold DR process be activated.

Once the decision has been made to trigger the Cold DR process IBM will launch new infrastructure in a different data center to host the paid queue managers, and use the configuration backup for each paid queue manager to recreate a copy of the queue manager deployed in the new infrastructure. Finally the DNS hostname that is used by applications to access the queue manager is updated to point to the new infrastructure deployment.
Most of these products replicate data with a software solution that is an agent installed in the source VM or Hypervisor that intercepts the updates and sends them to a correspondent receiving software-based replicator at the DR location.

Software Defined Storage (SDS)
: Instead of using native storage functions of the cloud, SDS products from the marketplace use cloud resources (compute, storage, network) to provide a user-controllable disk subsystem, including data replication functions.

OS disks might not be duplicated with an SDS solution as you might have limitations in having a VM to boot from an SDS replicated disk.

For an emergency, compute could be provisioned on demand, leveraging dynamic provisioning, subject to verification that cloud can commit on a provisioning time that allows you to meet the RTO of the applications or can be pre-provisioned and in stand-by mode, eventually. DR tests will be completed on a new set of on-demand, dynamically provisioned compute instances, that are duplicated by using snapshot functions.

Zoom

![Advanced recovery class network architecture](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/overview/images/BCDR-Architecture-Diagram-Image13.svg)

Figure 2. Advanced recovery class network architecture

In the diagram, you can see production is performed by applications, both in Production Zone 1 and Production Zone 2, and data is stored in their respective sites.

Production Zone 1 and Production Zone 2 might run the same workload type or can run different workloads. In the case that they run the same workload type (same application), it is likely that application data is stored in a single site.

The storage replication functions onboard the storage subsystems in both production sites perform the data replication (synchronous or asynchronous) to the correspondent SDS solution in the DR-cloud space, where data is kept available for emergency restarts.

Storage replication requires likewise storage on both sites, so the two options on Production Zone1 and Production Zone2 might also use different technologies, each one coupled with the appropriate SDS match.
Continuous Delivery high availability and disaster recovery 

IBM Cloud® Continuous Delivery is a general availability (GA) service with a Service Level Agreement of 99.99% availability that is offered in multiple regions: Dallas, Washington, Toronto, Sao Paulo, Frankfurt, Tokyo, Sydney, Osaka, and London. Each location has three different data centers for redundancy. The data for each location is kept in the three data centers near that location. If all of the data centers in a location fail, the Continuous Delivery service for that location becomes unavailable.

Continuous Delivery does not replicate data outside of a region, except for backup data. When possible, backup data is kept within the data centers of a country but data is always kept within a geography. European data does not leave the EU. To learn more about where Continuous Delivery backup data is stored, see [Object Storage Location](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-cd-compute-isolationcd-object-storage).

Continuous Delivery is available only on the public cloud, but the tools that are used with Continuous Delivery can run in public cloud environments and in on-premises environments.

See [ensure zero downtime](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimezero-downtime) to learn more about the high availability and disaster recovery standards in IBM Cloud. For more information about high availability and disaster recovery for Continuous Delivery, see [Your responsibilities with using Continuous Delivery](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-responsibilities-cddisaster-recovery). You can also find information about [Service Level Agreements](https://cloud.ibm.com/docs/overview?topic=overview-slas).
* The service is designed to withstand a single zone failure with no interruption.



The MZR architecture offers automatic failover between zones within the region, and high availability for a logging instance withing a region.

The SZR architecture offers failover across 3 distinct systems within the single datacenter so that you get high availability from a system failure, but not from a datacenter failure.





 Disaster recovery (DR) of the logging service in a region 

Disaster recovery is about surviving a catastrophic failure or loss of availability in a region.

IBM Log Analysis follows IBM Cloud requirements for [planning and recovering from disaster events](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimedisaster-recovery).

If a regional disaster occurs, consider the following information:



* The estimated recovery time for rebuilding the regional site and restoring the service at another location is 24 hours.
* Older data will not be available when the service is restored. Services that are restored will be available to receive data buffered at end points during course of the outage and future ingested data. Data previously retained is available through your archives and is not reloaded into your service instance. You can access your archive data directly in IBM Cloud Object Storage or use the Data Engine service to access it.
* You might have 1 or more logging instances in the region. When these service instances are available in the new location, you will be able to use them. However, you will have to update the endpoints of applications and logging agents to point to the ingestion endpoint in the new location.





 DR recovery time 

The following table indicates the estimated recovery times in the event of a DR situation:



Table 4. Recovery objectives for DR

 Recovery objective for DR Estimated time 

 Maximum Tolerable Downtime (MTD) / Recovery Time Objective (RTO) Less than 24 hours 
 Recovery Point Objective (RPO) Less than 4 hours