vania-janet/multiturn-rag-retrieval-data huggingface dataset:
High availability and disaster recovery 

IBM Watson™ Discovery is highly available within multiple IBM Cloud locations (for example, Dallas and Washington, DC). However, recovering from potential disasters that affect an entire location requires planning and preparation.

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. See [How do I ensure zero downtime?](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimezero-downtime) for more information.



 High availability 

IBM Watson™ Discovery supports high availability with no single point of failure. The service achieves high availability automatically and transparently by using the multi-zone region (MZR) feature provided by IBM Cloud.

IBM Cloud 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 can become an issue if an IBM Cloud location experiences a significant failure that includes the potential loss of data. Because MZR is not available across locations, wait for IBM to bring a location back online if it becomes unavailable. If underlying data services are compromised by the failure, also wait for IBM to restore those data services.

If a catastrophic failure occurs, IBM 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.

Your disaster recovery plan includes knowing, preserving, and being prepared to restore all data that is maintained on IBM Cloud.





 Backing up your data in Watson Discovery 

There are several methods for backing up the data stored in IBM Watson™ Discovery. Consider including these methods in your disaster recovery plan. Also consider backing up the following data types:



* Data that you might want a copy of, such as source documents
* Data that Discovery stores and that you want to extract and back up



Some data you cannot back up and must be recreated. For example, feedback events.



 Ingested documents
Other than physical failure, a common source of data loss is accidental deletion or modifications of files by users. Block Storage for Classic is only accessible to authorized hosts within your network. You control who can access it. Another measure to protect against accidental deletion and modification of files by users is a snapshot. If a user accidentally modifies or deletes crucial data from a volume, the data can be easily and quickly restored from a snapshot copy. For more information about this feature, see [Snapshots](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-snapshots).

The 11 nines durability target applies to a single Availability Zone. To protect against natural or human-made disasters that might destroy an entire Availability Zone, consider storing your most important data in multiple locations. For more information, see [Replicating Data](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-replication).





 High Availability 

Block Storage for Classic is built upon best-in-class, proven, enterprise-grade hardware and software to ensure high availability and uptime. The data is stored redundantly across multiple physical disks on HA paired nodes. Each storage node has multiple paths to its own Solid-State Drives and its partner node's SSDs as well. This configuration protects against path failure and controller failure because the node can still access its partner's disks for continued productivity. Redundant network ports and paths protect against network failures across the cloud connections.





 Encryption 

IBM Cloud® provides full-disk encryption without compromising storage application performance. For more information about encryption of Block Storage for Classic, see [Securing your data in Block Storage for Classic](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mng-data). For more information about provider- and customer-managed encryption in a VPC, see [Data encryption for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-aboutvpc-customer-managed-encryption).
Backups and Disaster Recovery 



 Application Backups 

Data used by applications within the Maximo Application Suite portfolio are backed up according to the following:

All backups are encrypted. Communication between applications, backup scripts the storage layer and DB services are perfromed via secure transport and accessed only via private endpoints that are offered by the service. Production backups are performed once a day. Backups are stored in a separate IBM Cloud data center location.





 System Configuration Backups 

Maximo Application Suite utilizes different components to deliver the applications to clients. Each of these services are backed up using the appropriate backup tool for that component. In general, all component backups:



* are encrypted
* are taken daily
* are stored in a separate data center
* are saved for 30 days







 Database Backup Retention 

Database backups will be retained for the standard duration of 14 days for Production environments and 7 days for Non-Production environments. In scenarios where the customer would like to retain a backup for longer than the standard duration outlined, the IBM SRE team will perform a database backup and save it to the COS bucket. It will then be the responsibility of the customer to download and maintain these backups. If a restore using one of these downloaded backups is required, the customer will need to upload the backup back to the COS bucket and open a case specifying which backup to use and for which environment they would like the restore.





 Restore 

Restore requests must be submitted via case (ticket) through the IBM Support Community Portal. The expected turn around time will depend on the severity and the size of the restore required. Generally for non-production systems, expect 1 - 3 days for a restore to happen. Database restore can only be done to one of the previous daily backups (cannot restore to point in time).





 Disaster Recovery 

In the event of a DR issue with the Maximo Application Suite Dedicated Service offering for a specific customer, IBM's focus will be in the following order:



1. Recover the existing infrastructure in place
2. Recover within the same IBM Cloud data center to a new infrastructure
3. Recover to a secondary IBM Cloud data center
High availability and disaster recovery 

IBM Watson® Discovery is highly available in all IBM Cloud® regions where Discovery is offered. However, recovering from potential disasters that affect an entire region requires planning and preparation.

IBM Cloud

This information applies only to managed deployments.

You are responsible for understanding your customization and usage of the service. You are also responsible for being ready to re-create an instance of the service in a new region and to restore your data in any region. See [How do I ensure zero downtime?](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimezero-downtime) for more information.



 High availability 

IBM Watson® Discovery supports high availability with no single point of failure. The service achieves high availability automatically and transparently by using the multi-zone region (MZR) feature provided by IBM Cloud.

IBM Cloud 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 can become an issue if an IBM Cloud region experiences a significant failure that includes the potential loss of data. Because MZR is not available in all regions, wait for IBM to bring a region back online if it becomes unavailable. If underlying data services are compromised by the failure, also wait for IBM to restore those data services.

If a catastrophic failure occurs, IBM 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 region.

Your disaster recovery plan includes knowing, preserving, and being prepared to restore all data that is maintained on IBM Cloud.





 Backing up your data in Watson Discovery 

There are several methods for backing up the data that is stored in IBM Watson® Discovery. Consider including these methods in your disaster recovery plan. Also, consider backing up the following data types:



* Data that you might want a copy of, such as source documents
* Data that Discovery stores and that you want to extract and back up
If underlying data services are compromised by the failure, you must also wait for IBM to restore those data services.

If a catastrophic failure occurs, IBM 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, including a vCenter Server instance.

Your disaster recovery plan includes knowing, preserving, and being prepared to restore all data that is maintained on IBM Cloud.







 Related links 



* [VMware Shared overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_overview)
* [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
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. You can also find information about [Service Level Agreements](https://cloud.ibm.com/docs/overview?topic=overview-slas).

The following sections contain information about high availability, disaster recovery for Cloud Functions as well as HIPAA-related considerations.



 High availability 

Cloud Functions is highly available within multiple [IBM Cloud regions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cloudfunctions_regions). Cloud Functions supports high availability to avoid a single point of failure. This service achieves high availability automatically and transparently through the multi-zone region (MZR) feature provided by IBM Cloud.





 Disaster recovery 

Customer data, such as action code, is automatically synchronized between database instances in different zones. In addition, IBM Cloud backs up your data by taking snapshots for use in data restoration in a disaster situation. If a disaster occurs, Cloud Functions switches over to use these snapshot backups automatically.

The likelihood of a region-wide disaster is low. However, if a disaster happens, IBM executes disaster-recovery plans to restore the service into another region. IBM Cloud® Functions then uses the regional backup of your data and the compute resources of another region to process your requests.



IBM Cloud® Functions regional failover locations

 Location Failover location 

 US South US East 
 US East US South 
 Tokyo EU Central 
 UK South EU Central 
 EU Central Amsterdam 
 Sydney Tokyo 



Because Amsterdam does not have any active compute resources for IBM Cloud® Functions, the failover period in the EU Central region might be longer than in other regions.

Cloud Functions is a Function-as-a-Service offering, and as such, it offers only compute services. It does not back up the data that your workload (actions) processes. To store data, you can use separate cloud-based data stores with separate disaster recovery options, which depend on the storage service's SLAs.





 HIPAA
Backups and Disaster Recovery 



 Application Backups 

Data used by applications within the Maximo Application Suite portfolio are backed up according to the following:

All backups are encrypted. Communication between applications, backup scripts the storage layer and DB services are perfromed via secure transport and accessed only via private endpoints that are offered by the service. Production backups are performed once a day. Backups are stored in a separate AWS data center location.





 System Configuration Backups 

Maximo Application Suite utilizes different components to deliver the applications to clients. Each of these services are backed up using the appropriate backup tool for that component. In general, all component backups:



* are encrypted
* are taken daily
* are stored in a separate data center
* are saved for 30 days







 Database Backup Retention 

Database backups will be retained for the standard duration of 14 days for Production environments and 7 days for Non-Production environments. In scenarios where the customer would like to retain a backup for longer than the standard duration outlined, the IBM SRE team will perform a database backup and save it to the COS bucket. It will then be the responsibility of the customer to download and maintain these backups. If a restore using one of these downloaded backups is required, the customer will need to upload the backup back to the COS bucket and open a case specifying which backup to use and for which environment they would like the restore.





 Restore 

Restore requests must be submitted via case (ticket) through the IBM Support Community Portal. The expected turn around time will depend on the severity and the size of the restore required. Generally expect 1 - 3 days for a restore to happen. Database restore can only be done to one of the previous daily backups (cannot restore to point in time).





 Disaster Recovery 

In the event of a DR issue with the Maximo Application Suite SaaS offering for a specific customer, IBM's focus will be in the following order:



1. Recover the existing infrastructure in place
2. Recover within the same AWS data center to a new infrastructure
3. Recover to a secondary AWS data center



In the event a disaster is declared, the base parameters are:
When you create a new retention scheme or modify an existing retention, make sure that the Archiving option is not selected. Archiving is not supported.





 What is Delta Technology? 

The first backup is a "seed" (a complete, full backup), the next and subsequent ones are "deltas" (that is, changes only), but they are equivalent to, and still considered a "full backup". That is, you're able to restore all or any files from it. With this technology, "full backups" are created at each session, but it saves enormous amounts of space on the vault and decreases the amount of time each subsequent backup takes to complete.





 Are the backups secure? 

By default all encryption over the wire (OTW) is encrypted with AES 256-bit encryption. You can also choose to store data in encrypted format by using AES 256-bit.

You must remember your encryption password. Your data can't be restored without your password. If you lose your password, you can't get your data back.

Compression ratios allow for zero compression to a maximum ratios compression that, depending on file type, might be compressed anywhere from 20 percent to 30 percent.





 What information is stored with system state backups? 

The system state backups include, but aren't limited to COM + class registration database, registry, boot files, system files, performance counter. It's all dependent on your system. System files vary by system O/S and service packs. Usually there are several thousand of them. MS Windows makes a dynamic list of these DLLs when you include them in the backup. By including the system files, you can recover from corrupted system files, or if you accidentally remove some service packs, or want to recover with a bare-metal restore. You can return to the state of the backup without having to reinstall the O/S from the installation kit, and then installing each service pack separately.

No user data file is included in System state backup. A system state backup job must be configured as a stand-alone job. There mustn't be any other data source that is included in the System State backup job.





 What happens to open files?
Dual region Disaster Recovery overview 

The IBM Cloud® for VMware® Regulated Workloads instance is a single regional deployment, which includes a number of High Availability (HA) and business continuity features. However, this single regional design does not address Disaster Recovery (DR).

DR is defined as a plan to recover critical business systems and normal operations if a catastrophic disaster occurs. For example, a major weather event, a cyberattack, or another cause of significant downtime. Key concepts that differentiate DR from HA include: policy-based management, nondisruptive testing, and automated orchestration.

IBM Cloud provides three tiers of regions: multizone regions (MZRs), single campus MZRs, and data centers.



* Single campus multizone region - Single campus MZRs contain three availability zones in different sections of the same building or within multiple buildings on a campus where the power, cooling, networking, and physical security dependencies overlap but are not identical between any two availability zones. For more information, see [Single campus MZRs](https://cloud.ibm.com/docs/overview?topic=overview-locationssingle-campus-mzr).
* Data centers - More than 50 data centers exist around the world, including MON01 in Montreal, AMS02 in Amsterdam, and MEL01 Melbourne. For more information about all data centers, see [Data centers](https://cloud.ibm.com/docs/overview?topic=overview-locationsdata-centers). For more information about the data centers in which VMware Solutions can be deployed, see [IBM Cloud data center availability](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_planningvc_planning-dc-availability).



The focus of the IBM Cloud for VMware Regulated Workloads DR design has the following specifications.



* A design to deliver against the two key requirements:



* Establish an alternative site in a different region for failover of workloads if a failure occurs in the primary site.
* Failover of the workloads that meets customer’s Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) application requirements.
Does the service replicate the data? 

All customer data in IBM Cloud Container Registry is replicated and backed up. Backups include service and policy settings and image data, but not vulnerability results, which can be reconstructed. All data, including vulnerability results, is replicated within each region so that the loss of a single availability zone is tolerated transparently. Regular point-in-time backups are used by IBM to restore the content if the data is corrupted. Extra backups are created in other regions with compatible privacy policies that are used by IBM to restore the service in a disaster situation.

The following table shows the backup locations.



Table 2. Backup locations

 Environment Active location Backup location 

 ap-north jp-tok au-syd 
 ap-south au-syd jp-tok 
 br-sao br-sao us-south 
 ca-tor ca-tor us-east (service and policy settings)<br><br>ca-mon (images) 
 eu-de eu-de eu-gb 
 eu-gb eu-gb eu-de 
 global us-east us-south 
 jp-osa jp-osa jp-tok 
 us-south us-south us-east 







 What data is backed up or replicated? 

The image data, service settings, and policy settings are backed up by IBM.





 Are users required to replicate the data? 

You are not expected to replicate your images. However, you can create a service instance in another IBM Cloud Container Registry region. You can also choose from a range of tools, including pushing to multiple locations from your development pipeline, and the use of replication tools, such as [skopeo copy](https://github.com/containers/skopeo/blob/main/docs/skopeo-copy.1.md). IBM doesn't replicate service instances.
High availability and disaster recovery 

IBM Cloud

The IBM Watson® Speech to Text service is highly available within any IBM Cloud location (for example, Dallas or Washington, DC). However, recovering from potential disasters that affect an entire location requires planning and preparation.

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 

The Speech to Text 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 IBM Cloud.

IBM Cloud 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 can become an issue if an IBM Cloud location experiences a significant failure that includes the potential loss of data. Because MZR is not available across locations, you must wait for IBM to bring a location back online if it becomes unavailable. If underlying data services are compromised by the failure, you must also wait for IBM to restore those data services.

In the event of a catastrophic failure, IBM 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.

Your disaster recovery plan includes knowing, preserving, and being prepared to restore all data that is maintained on IBM Cloud. This includes data from custom language models, custom acoustic models, and asynchronous speech recognition requests.

Re-creating custom models, especially custom acoustic models, from saved data can take a significant amount of time. Maintaining parallel service configurations in multiple locations can eliminate the turnaround time associated with disaster recovery.



 Disaster recovery for custom language models 

For custom language models, you need to maintain and be prepared to re-create and restore your custom language models and their corpora, grammars, and custom words. You also need to be prepared to retrain your custom language models on their data and words resources.



 Backing up custom language models
* [VMware® disaster recovery guide](https://docs.vmware.com/en/Site-Recovery-Manager/index.html) Documentation for VMware® Site Recovery Manager.
* [Vormetric Encryption of VMware®](http://go.thalesesecurity.com/rs/480-LWA-970/images/VMware-Encryption-and-KMIP-Integration-with-Vormetric-Data-Security-Manager-Integration-guide.pdf) Vormetric protects VMware® workloads by encrypting VM data.
* [Deploy a trusted cloud solution with IBM, VMware®, and HyTrust](https://www.hytrust.com/solutions/ibm-cloud-secure-virtualization/) You can integrate the various architectural elements to create a chain of trust from hardware up through the hypervisor and management applications.
Table 5. Responsibilities for disaster recovery

 Task IBM Responsibilities Your responsibilities 

 Backup of domain configuration data The customer is responsible for maintaining backup copies and records pertaining to the configuration of the customer's domain. This includes DNS records, firewall rules, and any custom configuration of the customer's domain. 
 Recovery and verification of domain configuration IBM is responsible for restoring the domains and configurations it manages, and for restoring full data path functionality between client and origin. After disaster recovery, it is the customer's responsibility to verify their domain is functional, and their configuration is as expected. The customer is also responsible for the health of origins that are serving their site content. 
 Recovery of control path capabilities IBM is responsible for recovering control path capabilities and making sure API, CLI, and/or UI are available to customers to manage their domains. IBM works with our partner, Cloudflare, to restore capabilities end to end.