vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If a local restore is needed, the VMware datastore encryption storage policy is used to reencrypt the VM by using an encryption key from the protected region HPCS instance through the KMIP for VMware service.
5. Veeam network encryption is used for file and backup copy jobs to the recovery region.
6. VM backup files are encrypted on disk in the recovery region Veeam Repository with Veeam encryption.
7. If a restore is needed in the recovery region, the Veeam datastore encryption storage policy is used to reencrypt the VM by using an encryption key from the recovery region HPCS instance through the KMIP for VMware service.



For more information about Veeam encryption, see [Encryption standards](https://helpcenter.veeam.com/docs/backup/vsphere/encryption_standards.html?ver=100).

In the IBM Cloud for VMware® Regulated Workloads dual region design for SaaS Consumer key management, then the same encryption keys are required in the recovery region as used in the protected region. Currently, HPCS does not support the same encryption keys in two regions. If a failure of the first HPCS instance occurs, keys can be restored to another HPCS instance in another region.

For more information, see:



* [HPCS cross-region disaster recovery](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-ha-drcross-region-disaster-recovery)
* [Restoring your data from another region](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-restore-data)







 Related links 



* [Caveonix integration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-caveonix)
* [Veeam on IBM Cloud overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeamvm_overview)
If you intend to store sensitive information in an IBM Cloudant database, you must use client-side encryption to render data unreadable to IBM Cloudant operators. For example, for PCI DSS compliance, you must encrypt the Primary Account Number (PAN) before sending a document that contains it to the database. 







 Disaster recovery 

Disaster recovery includes the following tasks:



* Provide dependencies on disaster recovery sites.
* Provision disaster recovery environments.
* Back up data and configuration.
* Replicate data and configuration to the disaster recovery environment.
* Fail over disaster events.





Table 4. 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 

 HA/DR (cross-region) Customer is responsible for creating more IBM Cloudant instances in separate regions and configuring replications to achieve the cross-region HA/DR architecture they want. See [Configuring IBM Cloudant for cross-region disaster recovery](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-configuring-ibm-cloudant-for-cross-region-disaster-recovery) for more details.
High availability and disaster recovery 

IBM® Key Protect for IBM Cloud® is a highly available, regional service with automatic features that help keep your applications secure and operational.

The high availability of Key Protect and the disaster recovery of data are guaranteed by IBM Cloud and Key Protect. Users are not required to perform any further actions. Note that "disaster recovery" does not include the ability to recover from user-initiated accidental deletions.



 Locations, tenancy, and availability 

Key Protect is a multi-tenant, regional service.

You can create Key Protect resources in one of the supported [IBM Cloud regions](https://cloud.ibm.com/docs/key-protect?topic=key-protect-regions), which represent the geographic area where your Key Protect requests are handled and processed. Each IBM Cloud region contains [multiple availability zones](https://www.ibm.com/cloud/blog/announcements/expansion-availability-zones-global-regions) to meet local access, low latency, and security requirements for the region.

There are three regions, us-south (located in Dallas, Texas, United States), jp-tok (located in Tokyo, Japan), and eu-de (located in Frankfurt, Germany) where Key Protect has failover support into a separate region where data is replicated into standby infrastructure. The us-south region has data replicated into the us-east region (located in Washington DC, United States), the jp-tok region has data replicated into the jp-osa region (located in Osaka, Japan), and the eu-de region has data replicated into a datacenter in the Paris region. This means that if service in us-south, jp-tok, or eu-de is disrupted, requests to Key Protect in those regions are routed to the region where the data has already been replicated. Note that the standby infrastructure in the region with failover support is completely separate from the Key Protect service available in that region, and that failover only goes in one direction. Your data in us-east, for example, is not currently replicated to us-south.

Because your requests are routed automatically, you can continue to call your original endpoint. Initially, read-only operations are all that will be available.
Responsibilities for security and regulation compliance for VMware Solutions offerings (other than VMware Shared)
The rows are read from left to right. The first column describes the task that a 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 

 Encryption Provide integration with Key Protect and Hyper Protect Crypto Services through KMIP service as an option for implementing data at-rest encryption. Configure and manage encryption for both data at rest and in transit, as needed. 









 Disaster recovery 

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
* Fail over on disaster events





 Disaster recovery for VMware Shared 

The following table describes the responsibilities that are related to disaster recovery for VMware Shared.



Table 8. Responsibilities for disaster recovery for VMware Shared
The rows are read from left to right. The first column describes the task that a 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 

 Backup of configuration data Backups are conducted of the shared management components to include customer environment configurations. Offsite backup copies are enabled and they run daily. 
 Backup of workload Backup services are enabled for customer workload. Configure individual backup jobs to include critical systems. Offsite copies can be enabled per request. 
 Recovery of configuration Recovery will be conducted in the original data center after the infrastructure is available. If long-term outage occurs, offsite recovery is conducted. 
 Recovery of workloads Restore capabilities are available in normal operations. For configuration restores, customer restore services will be provided after the infrastructure is available. If an offsite recovery is required, IBM works with the customer to help recover. Restore systems from the configured backup jobs. 







 Disaster recovery for VMware Solutions offerings (other than VMware Shared)
Disaster recovery and backup for IBM Cloudant 

Your data is important and valuable. You want to protect your data to help ensure it's secure, available, and maintains integrity. IBM® Cloudant® for IBM Cloud® provides several ways to protect your data and help keep your applications operational.

Some of these protection features are automatic. For other forms of protection, IBM Cloudant provides you with supported tools that help you to create your own high availability and disaster recovery capabilities.

The IBM Cloud® Service has Business Continuity plans in place to provide for the recovery of the Cloud Service within hours if a disaster occurs. You are responsible for your data backup, and associated recovery of your content.

This document provides an overview of the automatic capabilities and supported tools that are offered by IBM Cloudant.



 Types and levels of protection 

The type of protection you might want depends on the problem you're trying to solve.

For example, you might want to have a high level of data availability so that you can still access your data, even if a limited amount of hardware within the system failed. This requirement is necessary for "High Availability" (HA). It means that you provide the best possible continuous data availability after a hardware failure. Different HA techniques tolerate different levels of failure before operations are affected.

You might want to have quick and easy ways of backing up and restoring data. For example, after a severe or extensive hardware failure, you want the ability to make all the data available on an alternative system as quickly as possible. This requirement is necessary for "Disaster Recovery" (DR). A disaster generally means that a database is no longer available in one or more locations. For example, a power outage might cause all systems in a database cluster to fail. Or a large-scale network failure might mean systems in a cluster can't be contacted, even though they continue to work correctly.

Addressing your HA or DR requirements often begins by simplifying the problem into more generic requirements. When you identify your requirements, you can apply the tools and features that help solve the generic needs. Together, the tools and features can address your HA or DR requirements.

Different tools and features provide different levels of protection. The different features might be more or less suitable for your specific HA or DR requirement.
[HIPAA](https://en.wikipedia.org/wiki/Health_Insurance_Portability_and_Accountability_Act) compliance is available upon request, so request HIPAA compliance during the purchase process with an IBM sales representative.





 High availability, disaster recovery, and backup 

To provide high availability (HA) and disaster recovery (DR) within a data center, all data is stored in triplicate across three separate physical servers in a cluster. When available, you can provision accounts in multiple locations, then use continuous data replication to provide HA/DR across data centers. IBM Cloudant data isn't automatically backed up, but supported tools are provided to handle backups. Review the [Disaster recovery and backup](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-disaster-recovery-and-backupdisaster-recovery-and-backup) guide to explore all HA, DR, and backup considerations to meet your application requirements.
Business continuity and disaster recovery for Container Registry 

Find out about the business continuity and disaster recovery strategy for IBM Cloud® Container Registry.

Disaster recoveryinvolves 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.



 Your responsibilities when you're using Container Registry 

For more information about your responsibilities when you're using IBM Cloud Container Registry, see [Shared responsibilities for IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_responsibilities).





 Disaster recovery strategy 

IBM Cloud has

business continuityplans in place to provide for the recovery of services within hours if a disaster occurs. You're responsible for your data backup and associated recovery of your content.

Container Registry provides mechanisms to protect your data and restore service functions. Business continuity plans are in place to achieve targeted

recovery point objective(RPO) andrecovery time objective(RTO) for the service. The following table outlines the targets for Container Registry.



Table 1. RPO and RTO for Container Registry

 Disaster recovery objective Target Value 

 Recovery point objective (RPO) 48 hours 
 Recovery time objective (RTO) 24 hours 







 Locations for service availability 

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).





 Frequently asked questions about disaster recovery 

Review the following FAQs about disaster recovery.



 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.
The disaster recovery kit is an off-site and protected repository that includes hardware, software, and system secure configurations, one-time keys, and the disaster recovery plan. Use this disaster recovery kit during an incident response to restore services.



 Infrastructure as code 

Infrastructure as code ensures that good backup practices are implemented in a uniform way across the organization. Include implementation of backups as part of deployable architectures. Keep backup configuration close to provisioning code so that it is easier to ensure that backups are adjusted as information system changes occur. Create and configure backup accounts as code.





 Backup accounts 

Each BU account group should include a separate backup account and an additional backup account should be used for the centralized accounts. These backup accounts provide an extra layer of protection for the confidentiality and integrity of the backed up data. If credentials to a source account are compromised, it should not be possible to use that access to tamper with backups.

Supporting this effort, authorization to backup data in the backup account should use service-to-service or service to trusted profile authorization where possible. Otherwise, use secure storage of credentials with least privilege access.

If you are using Cloud Object Storage for backup, at minimum, use separate buckets for backing up different workload accounts. Also, use separate backup credentials for each bucket where service to service policies are not possible. Use Cloud Object Storage versioning or [immutable buckets](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-immutable) for maximum security.

Services that provide built in backup facilities might have limitations regarding backup accounts.





 Service-specific considerations 



 IBM Cloud Databases 

[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.
None. IBM and Key Protect are fully responsible for managing disaster recovery. 
 Virtual Private Endpoints (VPE) VPE does not support automatically switching to backup during failover at this time. VPE settings, specifically the Internet Protocol (IP) address, need to be manually updated during disaster recovery procedures. 
 Private Endpoint (PE) PE will not support allowed IP settings during disaster recovery at this time, but an announcement on this topic will be made soon. PE settings, specifically the Internet Protocol (IP) address, need to be manually updated during disaster recovery procedures.
Disaster recovery 

Disaster recovery (DR) backups for IBM® Db2® Warehouse on Cloud are enabled by default and supplement daily snapshot backups. DR backups are used exclusively for system recovery purposes by IBM service operators if there is a disaster or system loss.

If a disaster event occurs at the data center where your Db2 Warehouse on Cloud instance is deployed, IBM service operators will work with you to stand up a new data warehouse in a different data center, by using the most recent disaster recovery backup. There is no additional charge for these backups.

The RPO (Recovery Point Objective) and RTO (Recovery Time Objective) for DR backups for each cloud provider are described in the following sections. On IBM Cloud, DR backups are geo-replicated by default. You can open a support ticket to not have your DR backups replicated to certain regions to comply with your data retention policies. On AWS, DR backups are stored in another Availability Zone in the same region and can also be geo-replicated at an additional cost.

For more information about DR and replication on Db2 Warehouse on Cloud, see [Replication](https://www.ibm.com/support/knowledgecenter/SS6NHC/com.ibm.swg.im.dashdb.idrca.doc/overview/ovu-db2woc.html).



 IBM Cloud 

When deployed on IBM Cloud, a full backup of the database is taken once a week for disaster recovery. This DR backup is encrypted and stored in IBM Cloud Object Storage (COS).

IBM COS replicates each DR backup across multiple IBM Cloud regions to ensure availability if a single zone fails.

DR backups of the last 2 weeks are retained by default. The RPO for DR backups on IBM Cloud is 1 week. The RTO if a disaster occurs is dependent upon the size of the database – 1.5 hours per terabyte of data.





 Amazon Web Services 

When deployed on Amazon Web Services, a full backup of the database is taken once a day for disaster recovery. This DR backup is encrypted and stored in Amazon Web Services S3.

DR backups of the last 7 days are retained by default.
Business continuity and disaster recovery 

A holistic strategy for business continuity and disaster recovery is critical when you are managing cloud at scale. This recommendation extends the business continuity recommendations from the [IBM Cloud framework for Financial Services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-bcdr) and provides some additional specifics that extend the IBM Cloud [General disaster recovery strategy](https://cloud.ibm.com/docs/overview?topic=overview-understanding-drbcdr-general).

Key points from the IBM Cloud Framework for Financial Services:



* Establish backup storage in a geographically separate region from the workload that is backed up
* Conduct regular and frequent backups of all information necessary to restore operation of the system
* Monitor backups and test recovery procedures to ensure success if recovery is required
* Protect the confidentiality, integrity, and availability of backup information at storage locations
* Establish contingency plans that include procedures for validating successful recovery and reconstitution of the original configuration





 High availability deployments 

For [high availability deployments](https://cloud.ibm.com/docs/overview?topic=overview-understanding-drdr-categories), additional copies of infrastructure and applications should be deployed in the same workload account and by the same projects as the primary infrastructure. This makes it easier to ensure that additional regions are kept in sync and simplifies configuring access for DevOps teams.



 Infrastructure as Code 

Infrastructure as code should be used to create any additional deployments for high availability, whether it be Active/Active, Active/Standby, or Active/Passive. This helps ensure that additional regions that are created for high availability are kept in sync with the primary regions and provides all the other security, compliance, and governance benefits of using infrastructure as code.





 Active/Passive 

When using an active/passive (cold standby) strategy, infrastructure as code enables contingency plans that include use of automation to create infrastructure on demand. This allows for very inexpensive active/passive configurations as costly infrastructure does not need to be maintained.
For more information about particular high availability and disaster recovery practices specific to each service or infrastructure option, refer the documentation for that service.





 High availability for the network 

Except for the oldest pod that still has some single points of failure, the IBM Cloud network is designed in such a way that a single point of failure never happens. Diverse, redundant connectivity exists at every point of the network, by using diverse telecommunication providers for the same service connectivity whenever possible within each region. Diverse dark fiber providers are used to connect every edge site to all of the regional compute facilities. Each edge site additionally has redundant backbone connectivity into other regions, and peers with multiple providers, both directly and indirectly, through a local exchange. No single event should ever result in a service disruption that is noticed by our customers.

You can always choose to "break" having no single point of failure with how you order or configure your SoftLayer classic servers. For Direct Link, you must order redundant connections if you want full redundancy because it's not built-in or automatic.





 Disaster recovery 

Disaster recovery is about surviving a catastrophic failure or loss of availability in a single location. For the console and platform services, there are no actions that you need to take to prepare for an event of a catastrophic failure in a region.



 Disaster recovery plan 

IBM Cloud follows best practices for disaster recovery. All IBM Cloud applications automatically recover and restart after any disaster event. Recovery is from electronic backups at a recovery center or alternative computing facilities that restore computing. Before any potential disaster, the disaster recovery plan includes the systems and hosting requirements for hardware, software, networking connectivity, and offsite backup capabilities.

The following list includes the requirements that IBM adheres to for a disaster recovery plan:



* A design document explains how load balancing is used to keep a service highly available.
* Where multi-site failover occurs, the disaster recovery plan must explain who does what to cause the failover and ensure restart.
* The disaster recovery plan must define how the solution works and include restore point objectives that clearly explain how much data might be lost in the outage, if any. The disaster recovery plan also includes a detailed recovery workflow for restoring services and data if a multi-availability zone failure.