vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Other than physical failure, a common source of data loss is accidental deletion or modifications of files by users. File 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/FileStorage?topic=FileStorage-snapshot).

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/FileStorage?topic=FileStorage-replication).





 High Availability 

File Storage for Classic is built upon best-in-class, proven, enterprise-grade hardware and software to ensure high availability and uptime. As mentioned previously, 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 setup protects against path failure and controller failure because the node can still access its partner's disks for continued productivity. In fact, the system can lose multiple disks in the cluster simultaneously without degrading customer performance or adverse risk of data loss. 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 File Storage for Classic, see [Securing your data in File Storage](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mng-data).
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?
* 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 auditing 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.

When you provision an auditing instance, you select the MZR (location) where the instance is created. The region determines where the auditing data is processed and the data is hosted.





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

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

IBM Cloud Activity Tracker 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:



* Data and the auditing metadata such as dashboards, alerts, views, screens, templates are backed up every 24 hours. In the event of an un-recoverable disaster, up to 24 hours of data and metadata changes to the auditing instance in the failure region can be lost.
* The estimated recovery time for rebuilding the regional site and restoring the service at another location is 24 hours.
* Due to the large volume of data, older data might not be available at the time the service is restored, as this process requires additional time to recover data from the backups.
* When the auditing instance in the DR region is available in the new location, you will be able to use it while the data is restored into the newly constructed region.





 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
High availability and disaster recovery 

IBM Cloud

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

For the Text to Speech service, only data for custom models, custom words, speaker models, and custom prompts is stored on IBM Cloud. Your disaster recovery plan includes knowing, preserving, and being prepared to restore your customization information.



 Backing up custom models and speaker models 

Preserve the following information about your custom models, custom entries, speaker models, and custom prompts:



* A list of all of your custom models and their definitions. To list information about your custom models:



* Use the GET /v1/customizations method to list information about all custom models.
To use failover crypto units to restore data in a regional disaster, make sure that you initialize and configure all the failover crypto units the same as the operational crypto units before the disaster happens. For more information about initialization approaches, see [Introducing service instance initialization approaches](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-instance-mode).





 Restoring your data by opening an IBM support ticket 

If you don't enable failover crypto units or you are using Hyper Protect Crypto Services with Unified Key Orchestrator, you need to open an IBM support ticket to restore your data. IBM can then provision a new service instance for you in another region by using the same instance ID, and restore all the key resources from the backup. And then, you need to load your

master keyto the new service instance in the new region.

In the process, you're the only person who owns the master key. IBM administrators or any third-party users cannot access your data or keys in the backup or the restored service instance.

To restore a backup to an existing service instance, follow these steps:



1. In the IBM Cloud console, click the Help icon ![Help icon](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/icons/help.svg) > Support center from the IBM Cloud console menu barto enter the Support Center. Click View all in the Recent support cases panel and click Create new case. Or, you can directly go to the [Manage cases page](https://cloud.ibm.com/unifiedsupport/cases) and click Create new case.
2. On the Create a case page displayed, select the offering Hyper Protect Crypto Services, and then specify the following values:



Table 1. Describes the fields required for creating a case

 Field name Action 

 Subject Enter Disaster recovery.
Transfer the backups of the key management, Object Storage, and database services related to the Data Security Broker deployment, as well as the Data Security Broker Manager backup files, to a reliable backup storage location.







 Restore procedure 

The Data Security Broker deployment can be recovered in a disaster recovery situation to a state that was previously backed up, provided that all the dependent services are also recovered in the same manner. This applies to any services that has suffered a irrecoverable failure. If the dependent services were not affected, all that is required is to ensure that the network connectivity between the Data Security Broker deployment and the dependent services is restored.

Since Data Security Broker Manager contains all the configuration and metadata needed for a Data Security Broker deployment, the goal of the process is to restore Data Security Broker Manager to a previous state so that a new shield can be deployed to enforce the previously configured security policies.





 Restoring Data Security Broker Manager deployed on a Kubernetes or Red Hat OpenShift cluster to a previous state 

A new Data Security Broker Manager deployment needs to be set up in a Kubernetes or Red Hat OpenShift cluster, in order to return Data Security Broker Manager to its previous state. The administrator carrying out the restore operation requires network connectivity to the cluster as well as access to a workstation with permission to use the command-line tools for Kubernetes or Red Hat OpenShift cluster.

To restore a Data Security Broker deployment, follow the steps:



1. Log in to the workstation using command-line tools, and use the recently installed Data Security Broker Manager to access the Kubernetes or Red Hat OpenShift cluster.
2. To create a temporary storage area on the workstation, copy the Data Security Broker Manager backup files there. The names of the backup files includes the following:



Release-DSB.<release>MONGO.tar.gz
Release-DSB.<release>BM.tar.gz



1. To restore the Data Security Broker Manager configuration files and MongoDB collections, create and execute the script provided below. As an input to the script, specify the location of the temporary storage location for backup files.



!/bin/bash
if [ $ -eq 0 ]
then
echo "No arguments supplied"
Understanding high availability and disaster recovery for Secrets Manager 

IBM Cloud® Secrets Manager is a highly available, regional service that runs in the Dallas (us-south), Frankfurt (eu-de), London (eu-gb), Osaka (jp-osa), Sydney (au-syd), Sao Paulo (br-sao), Tokyo (jp-tok), Toronto (ca-tor), and Washington DC (us-east) regions.

In each supported region, the service exists in multiple availability zones with no single point of failure. All the data that is associated with your instance of the service, including your secrets, is backed up across regions.

However, because Secrets Manager is a regional service, cross-regional failover, and cross-regional disaster recovery are not automatic. If all the availability zones in a region fail, Secrets Manager becomes unavailable in that location. When the region is available again, data and traffic is restored without any need for action from you.

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



 Manually backing up secrets 

To manually back up your secrets across regions, you must first have an instance of Secrets Manager in another region. Then, use the following steps to ensure cross-region availability.



1. List and download secrets from your instance by using the [Secrets Manager API](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2) or CLI.

If you have existing configurations on secrets engines in your instance, you can also retrieve the information programmatically so that it can be re-created in a new instance. For more information, see the [Get the configuration of a secret type](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2get-config) API.
2. Add your downloaded secrets to the newly created instance.







 Automatically backing up secrets
This stored data includes the training data for your models.

Re-creating models from saved data takes time. You can maintain parallel service configurations in multiple locations to help eliminate the turnaround time associated with disaster recovery.



 Disaster recovery for models 

For models, understand which data can be backed up, restore and re-create necessary artifacts, and then retrain and redeploy the models.



 Backing up data 

Some data can be backed up, and some must be re-created:



1. [Understand which data can be backed up](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-backup-restoredata)
2. [Prepare for backup](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-backup-restoreprepare)
3. [Download artifacts from the current instance](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-backup-restoreexport)







 Restoring data, models, and tasks 

To recover from a disaster:



1. [Recreate workspaces on the new instance](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-backup-restorerecreateproj)
2. [Restore the workspace data](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-backup-restorerestoredata)
3. [Restore the models](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-backup-restorerestoremodels)
4. [Restore any incomplete annotation tasks](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-backup-restorerestoretasks)
Managing global replication service 

Disasters are unplanned events that cause severe damage, incur a loss to our business, and affect all organizations. Since most workloads nowadays run on cloud infrastructure, it’s essential to have robust and resilient cloud infrastructure that is prepared to handle these catastrophic hits and have minimal impact on business.

The IBM® Power® Systems Virtual Server provides a set of APIs that can enable disaster recovery (DR) solution for your virtual server instances. IBM Cloud infrastructure internally uses Global Mirror Change Volume (GMCV) as storage technology that provides asynchronous replication, and advance network configuration for fast data transfer.

A new resource volume group is introduced to enable, disable, and manage storage replication consistency group. Volume group holds the set of volumes that needs to be recovered at the time of disaster. To make the volume DR capable, you must add the volume in the volume group. Failover and failback operations are triggered by using the volume group start and stop operations.

GRS aims to automate the complete DR solution and provide the API and CLI interfaces to create the recipe for the DR solution. GRS currently does not have any user interface.

The scope of the GRS service is to create and manage replicated resources that include the following items:



* Volume lifecycle operations support on replicated volumes.
* APIs to manage volume groups through create, update, delete, start, and stop operations.
* Virtual server instance life-cycle operations by using replicated volumes.
* Onboard auxiliary volume on secondary site for volume recovery.





 Additional information 

If you need a more detailed information on Gobal Replication Service, see [Global Replication Services Solution using IBM Power Virtual Server](https://cloud.ibm.com/media/docs/downloads/power-iaas/Global_Replication_Services_Solution_using_IBM_Power_Virtual_Server.pdf)





 Locations that support global replication service 

You can use the GRS location APIs to determine the locations that support storage replication and their mapped location. For more information, see [all disaster recovery locations supported by Power System Virtual Server](https://cloud.ibm.com/apidocs/power-cloudpcloud-locations-disasterrecovery-getall).
Understanding business continuity and disaster recovery for IBM Cloudant 

Disaster recovery involves a set of policies, tools, and procedures for returning a system, an application, or an entire data center to full operation after a catastrophic interruption. It includes procedures for copying and storing an installed system's essential data in a secure location, and for recovering that data to restore normalcy of operation.



  Responsibilities 

For more information about your responsibilities when you use IBM Cloudant, see [Shared responsibilities for IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-cloudant-responsibilities).



  Disaster recovery strategy 

IBM Cloud has business continuity plans in place to provide for the recovery of services within hours if a disaster occurs. You are responsible for your data backup and associated recovery of your content.

IBM Cloudant provides mechanisms to restore service functions. Business continuity plans are in place to achieve targeted recovery point objective (RPO) and recovery time objective (RTO) for the service. The following table outlines the targets for IBM Cloudant.



Table 1. RPO and RTO for IBM Cloudant

 Disaster recovery objective  Target Value  

 RPO                          24 hours      
 RTO                          < 24 hours 









  Locations 

For more information about service availability within regions and data centers, see [Service and infrastructure availability by location](https://cloud.ibm.com/docs/overview?topic=overview-services_region).
[IBM Cloud® Object Storage provides several options to encrypt your data.](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 as SOC2, PCI, HIPAA and Privacy Shield. Set up and maintain security and regulation compliance for your apps and data. This includes: <br>[Defining the account management strategy](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-adoptionadoption_account) <br>[Configuring the accounts settings for compliance](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-adoptionadoption_acc_settings) <br>Define IAM Strategy <br>[Define the notification strategy](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-adoptionadoption_alerts) 







 Disaster recovery 



Table 5. Responsibilities for disaster recovery

 Task IBM Responsibilities Your Responsibilities 

 Restore the service[] Automatically recover and restart service components after any disaster event. N/A 
 Backup the IBM Log Analysis key resources that are provided by the service Daily backup of the IBM Log Analysis infrastructure and components. N/A 
 Backup logging agents N/A Backup each logging agent YAML file that is deployed in your organization. 
 Recovery of logging agents N/A [Reinstall](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-logdna_agentlogdna_agent_configure) the logging agent in the event of any disaster event that impacts the agent runtime. 
 Backup the metadata of a logging instance Backup metadata that is used by the service. [Backup the metadata such as views, dashboards, screens, parsing templates, and alerts for each logging instance.](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-reuse_resource_definitionsexport_config_res)
This documentation is for the classic Watson Assistant experience. To see the documentation for the new Watson Assistant, please go [here](https://cloud.ibm.com/docs/watson-assistant).



  High availability and disaster recovery 

IBM Watson® Assistant 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 Watson Assistant. 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 

Watson Assistant supports high availability with no single point of failure. The service achieves high availability automatically and transparently by using the multi-zone region 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 the multi-zone region feature 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.

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. See [Backing up and restoring data](https://cloud.ibm.com/docs/assistant?topic=assistant-backup) for information about how to back up your service instances.