vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The instance is restarted on another host automatically unless Host failure auto restart is set to stop. The provisioned disks are now empty.

In rare cases, a physical disk error might occur. If a physical disk error occurs, the instance fails to read/write to the failed disk. The instance is not automatically restarted in this scenario. Contact your support representative to report the problem and identify next steps. You can stop and then start your instance to effectively place it on a different disk that is functional. If you stop and then start your instance in order to place it on a different disk, this scenario does erase your instance storage data.

Virtual servers that are deployed with multiple instance storage disks are spread across multiple physical disks. No two instance storage disks within a single virtual server instance lands on the same physical backing disk.

Block storage volumes and instance storage are complementary technologies. Volumes can be attached to instances that have instance storage. In fact, instances that use instance storage generally utilize block storage volumes for the persistent storage requirements of the workload.





 Encryption and isolation 

Instance storage data is secured with on-disk encryption. The physical disks used for instance storage are self-encrypting with the strong AES-256 encryption standard. The data is automatically decrypted when your instance accesses the data. When your instance is shut down or deleted, the underlying storage space is erased and unrecoverable. At that point, the data is unrecoverable.

Data is automatically encrypted on the physical media at the drive level. However, customer-managed keys are not supported for instance storage. For sensitive data, it is strongly recommended that users utilize software-based file system encryption such as LUKS for Linux® or BitLocker for Windows®. This technology allows end users to encrypt entirely within the instance, and can provide additional protection for sensitive data in-transit between the instances and the physical drive media. Some operating systems also provide FIPS certified encryption algorithms that may also be used.
PATCH /floating_ips/{fip-id} Subnet Operator is.subnet.subnet.operate 







 Storage known issues 



 Cross-regional copy array issue 

Issue: When you create a snapshot or list details of a snapshot with the API, the copies array in the API response lists only the direct copies of the snapshot that you specified. If you create a copy of a copy, the second copy is not returned when you query the original snapshot.





 Fast restore snapshots with customer-managed encryption issue 

Issue: When you restore a volume from a snapshot by using the fast restore feature and the encryption key of the snapshot and volume are different, and then you delete the snapshot encryption key from the key management service, the volume might become inaccessible when it's attached or reattached to the virtual server instance.

Workaround: To recover the snapshot encryption key, use [the key recovery procedure](https://cloud.ibm.com/docs/key-protect?topic=key-protect-restore-keys). When the key is recovered, the volume becomes accessible.
Duplicates can be created from both primary and replica volumes. The new duplicate is created in the same data center as the original volume. If you create a duplicate from a replica volume, the new volume is created in the same data center as the replica volume.

Duplicate volumes can be accessed by a host for read/write as soon as the storage is provisioned. However, snapshots and replication aren't allowed until the data copy from the original to the duplicate is complete.

For more information, see [Creating a duplicate Block Storage for Classic](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-duplicatevolume).





 Using replicas to failover when disaster strikes 

When you fail over, you’re "flipping the switch" from your storage volume in your primary data center to the destination volume in your remote data center. For example, your primary data center is London and your secondary data center is Amsterdam. If a failure event occurs, you’d fail over to Amsterdam – connecting to the now-primary volume from a compute instance in Amsterdam. After your volume in London is repaired, a snapshot is taken of the Amsterdam volume to fail back to London and the once-again primary volume from a compute instance in London.



* If the primary location is in imminent danger or severely impacted, see [Failover with an accessible primary volume](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-dr-accessible).
* If the primary location is down, see [Failover with an inaccessible primary volume](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-dr-inaccessible).
See the topics on setting up multi-region HA deployments for steps to configure your IBM Blockchain Platform [peers](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-hadr-mr) and [ordering nodes](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-hadr-mr-os) across multiple regions.







 Disaster recovery (DR) 

The most important step for disaster recovery is to configure your environment across multiple regions as documented in the previous section. Multi-region configuration ensures that your environment can handle a datacenter or regional disaster with zero downtime or data loss. However, this does not protect against data corruption or accidental deletion. To do this, you may want to also take periodic backups.

It is recommended that you regularly back up the storage associated with every deployed component. Because the ledger is shared across all the peers and ordering nodes, taking regular backups is critical. For example, if incorrect data is accidentally propagated to a peer's ledger or if data is mistakenly deleted, the incorrect data might spread to the ledgers of some other peers. This would require the restoration of the ledgers of all the peers from an established backup point to ensure synchronicity. You can decide how often to perform the backups based your recovery needs, but a general guideline would be to take daily backups.

All nodes must be [stopped](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-stop-nodes) in order to ensure a reliable backup.



Table 2. Backup recommendations for storage

 Storage solution provider Guidance 

 IBM Cloud storage solution You can leverage the [capability provided by IBM Cloud Kubernetes service](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesibmcloud-backup-restore) or [OpenShift](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesibmcloud-backup-restore).
For more information about the arguments and attributes, see [ibm_is_backup_policy_plan](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_backup_policy_plan).





 Creating a backup plan with cross-regional copy option with Terraform 

New

To create a backup plan with cross-regional copy option, use the ibm_is_backup_policy_plan resource. If the source snapshot is not encrypted with a customer key, the encryption of the copy remains provider-managed. If the source snapshot is protected by a customer-managed key, you must specify the customer-managed key that you want to use to encrypt the new copy with the --encryption-key option. See the following example.

resource "ibm_is_backup_policy_plan" "example" {
backup_policy_id = "ibm_is_backup_policy.example.id"
cron_spec = "30 /2 * * 1-5"
name = "my-policy-plan"
deletion_trigger {
delete_after = 20
delete_over_count = 20
}
remote_copy_policies {
delete_over_count = 1
encryption_key = "crn:v1:bluemix:public:kms:us-south:a/dffc98a0f1f0f95f6613b3b752286b87:e4a29d1a-2ef0-42a6-8fd2-350deb1c647e:key:5437653b-c4b1-447f-9646-b2a2a4cd6179"
region = "us-south"
}
}

For more information about the arguments and attributes, see [ibm_is_backup_policy_plan](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_backup_policy_plan).







 Next steps 

After you create a backup policy, you can do the following actions.
The use of different multizone regions enables DR due to:



* Colocation of services - KMIP™ for VMware and Hyper Protect Crypto Services are hosted in multizone regions.
* Geographical distance - the risk that the same physical event impacts both multizone regions is low.
* Resiliency - logical services in each region are independent, such that a failure in one service does not impact the service in the other region.



Hyper Protect Crypto Services is not available in the London multizone region.

This paring of IBM Cloud for VMware Regulated Workloads instances enables management and workload virtual machines (VM) to fail over between regions. As each region is a separate IBM Cloud for VMware Regulated Workloads instance, the regions have a similar physical layer and virtual infrastructure designs. The IBM Cloud for VMware Regulated Workloads disaster recovery design requires two IBM Cloud locations:



* Protected region - This region contains the protected VMs that require DR.
* Recovery region - This region provides an environment to host VMs from the protected region if a disaster occurs.

Notes



* The recovery region management cluster requires sufficient free capacity to host the protected management applications from the protected region.
* The recovery region workload cluster requires sufficient free capacity to host the protected workloads from the protected region.
* In normal operations, workload VMs can run in the recovery region if required. However, there needs to be enough initial capacity in the recovery region to run the recovered workload VMs upon DR invocation. These workloads might be test and development workloads that are considered to be sacrificial upon DR.





Recovery Point Objective (RPO) and Recovery Time Objective (RTO) depend on many variables. Therefore, the VMware Regulated Workloads dual region design provides no standard Service Level Agreement (SLA) for RPO or RTO. However, review the following information about RPO and RTO:



* The VMware vSphere clusters in the recovery region are provisioned and are available to run workloads as soon as these workload VMs are started after DR invocation.
"resource_group": "5g9f447903254bb58972a2f3f5a4c711",
"resource_plan_id": "databases-for-mongodb-standard"
}'

The parameters name, target, resource_group, and resource_plan_id are all required.







 List of Additional Parameters 



* backup_id- A CRN of a backup resource to restore from. The backup must be created by a database deployment with the same service ID. The backup is loaded after provisioning and the new deployment starts up that uses that data. A backup CRN is in the format crn:v1:<...>:backup:<uuid>. If omitted, the database is provisioned empty.
* version - The version of the database to be provisioned. If omitted, the database is created with the most recent major and minor version.
* disk_encryption_key_crn - The CRN of a KMS key (for example, [Hyper Protect Crypto Services](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-get-started) or [Key Protect](https://cloud.ibm.com/docs/key-protect?topic=key-protect-about)), which is then used for disk encryption. A KMS key CRN is in the format crn:v1:<...>:key:<id>.
* backup_encryption_key_crn - The CRN of a KMS key (for example, [Hyper Protect Crypto Services](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-get-started) or [Key Protect](https://cloud.ibm.com/docs/key-protect?topic=key-protect-about)), which is then used for backup encryption. A KMS key CRN is in the format crn:v1:<...>:key:<id>.
It can be quicker to save backup files on physical media and transport them to a location for a restore than to restore data from a vault in a remote data center. Note: You cannot restore from backups to disk (SSI files) until the safe set is imported into the vault and the IBM Cloud® Backup for Classic Agent is synchronized with the vault.
10. In the Database Selection box, select the checkbox for each database that you want to restore.
11. In the Encryption Password field, enter the data encryption password. To view the password hint, click Hint.
12. Select a database name.



* To restore one or more databases with their original names, select Original Database Names.
* To restore one database with a new name, select Alternate Database Name. In the field that appears, enter the new name for the restored database.



You can restore only one database if Alternate Database Name is selected.
13. Select the appropriate setting for overwrites.



* To overwrite the existing database if you restore a database with the same name as the existing database, select Overwrite existing databases.
* To fail the restore if a database with the same name exists, clear Overwrite existing databases. If Overwrite existing databases is not selected, and you are restoring multiple databases, the restore fails for all databases if even one database has the same name as an existing database.



14. To restore the database in restoring state, select Restore by using No Recovery. If this option is selected, you can apply transaction logs to the database after it is restored. The transaction logs must be backed up by using an alternative method (for example, a native SQL Server backup) first.
15. To specify an alternative location for database files, select Alternate Path. Click the folder. In the Select Folder dialog box, select the alternative file location, and click Okay.

The alternate file location is only used if the original location for database files is not available.
16. To change the log detail level, bandwidth throttling setting, or hard recovery option, click Advanced Restore Options. In the dialog box, select the following options:



* In the Log Level Detail list, select the level of detail for job logging.
Databases are deployed on a virtual server. Backup is enabled and replication is set up between regions. The alternative would be to use a database-as-service, a topic discussed later in the tutorial.
5. IBM Cloud File Storage for Classic to store the application images and files, File Storage for Classic offers the capability to take a snapshot at a given time and date, this snapshot then can be reused within another region, something that you would do manually.



The tutorial [Use Virtual Servers to build highly available and scalable web app](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-highly-available-and-scalable-web-applicationhighly-available-and-scalable-web-application) implements this architecture.





 Back up and restore procedures 

Refer to the following backup and restore procedures:



* [Managing backups for Databases for Elasticsearch](https://cloud.ibm.com/docs/services/databases-for-elasticsearch?topic=cloud-databases-dashboard-backups)
* [Managing backups for Databases for PostgreSQL](https://cloud.ibm.com/docs/services/databases-for-postgresql?topic=cloud-databases-dashboard-backups)
* [Backups and restoration for Databases for Redis](https://cloud.ibm.com/docs/services/databases-for-redis?topic=cloud-databases-dashboard-backupsbackups-and-restoration)
Backup and restore 



 Backup 

For paid plans, encrypted backups of the database are done daily. A daily backup is kept for each of the last 14 days.

All paid plans make use of Cross-Regional IBM Cloud Object Storage (COS), by default, to keep backups offsite.

The following is an example of the manual backup operation in the web console UI:



 Enterprise and Standard plans 



1. Click Administration in the left menu and select the Backups tab. Click the Run backup button.

Zoom

![View of the highlighted selection of the backup option](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/backup_v2.png)

Figure 1. Selection of the backup option
2. Click Run to run a manual backup.

Zoom

![View of Run Backup page option](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/backup_run_v2.png)

Figure 2. View of Run backup
3. When the backup starts, some features might not be available until the backup is completed.

Zoom

![View of the backup initiation](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/backup_initiated_v2.png)

Figure 3. View of the backup initiation
4. After backup completion, a new backup entry in the list of backups appears as a Full (Manual) type. The new backup is in an available state.

Zoom

!
Storage for Satellite reference architecture 

You need to consider storage options both in IBM Cloud and in the on-premises Satellite location.



 Storage in IBM Cloud 

All Satellite control plane data is backed up to an [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-about-cloud-object-storage) service instance within IBM Cloud. This is done so that your location can be restored after a disaster. When you create a location, you also provide a Object Storage service instance that you control for backup of the location control plane worker nodes. Control plane master data is backed up by IBM and stored in an IBM-owned Object Storage instance. Satellite cluster master data is backed up to the Object Storage instance that you own.

Aside from backing up data from the Satellite location, Object Storage is also used to store auditable IBM Cloud events. For more information, see [Audit logging of IBM Cloud events](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-logging-audit).



 About Object Storage 

[Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-about-cloud-object-storage) stores encrypted and dispersed data across multiple geographic locations. Object Storage is available with three types of resiliency: Cross Region, Regional, and Single Data Center. Cross Region provides higher durability and availability than using a single region at the cost of slightly higher latency. Regional service reverses those tradeoffs, and distributes objects across multiple availability zones within a single region. If a given region or availability zone is unavailable, the object store continues to function without impediment. Single Data Center distributes objects across multiple machines within the same physical location.

Users of Object Storage refer to their binary data, such as files, images, media, archives, or even entire databases as objects. Objects are stored in a bucket, the container for their unstructured data. Buckets contain both inherent and user-defined metadata. Finally, objects are defined by a globally unique combination of the bucket name and the object key, or name.
Enter a bucket name for the Unique bucket name field.

Note: All buckets in all regions across the globe share a single namespace.
5. Choose the type of resiliency and a location where you would like your data to be physically stored.

Resiliency refers to the scope and scale of the geographic area across which your data is distributed.

Cross Region resiliency will spread your data across several metropolitan areas.

Regional resiliency will spread data across a single metropolitan area.

A Single Data Center will only distribute data across devices within a single site.

For more information, see [Select regions and endpoints](https://cloud.ibm.com/docs/services/cloud-object-storage?topic=cloud-object-storage-endpoints).
6. Choose the type of Storage class.

You can create buckets with different storage classes. Choose the storage class for your bucket based on your requirements to retrieve data. For more information, see [Use storage classes](https://cloud.ibm.com/docs/services/cloud-object-storage?topic=cloud-object-storage-classes).

It is not possible to change the storage class of a bucket once the bucket is created. If objects need to be reclassified, it is necessary to move the data to another bucket with the wanted storage class.
7. Optionally, add additional encryption to your bucket. For example, configure Key Protect Key in your bucket to encrypt data at rest.

You can only add additional encryption when you create the bucket.

All objects are encrypted by default using randomly generated keys and an all-or-nothing-transform. While this default encryption model provides at-rest security, some workloads need to be in possession of the encryption keys used. For more information, see [Manage encryption](https://cloud.ibm.com/docs/services/cloud-object-storage?topic=cloud-object-storage-encryption).









 Getting the bucket configuration details through the IBM Cloud UI 

When you configure a target, you need the bucket name and the private endpoint.
To protect your data from a zone failure, you can [replicate snapshots](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-replicationreplication) to a block storage instance that is set up in another zone.

Data can be replicated from the primary storage to the backup storage only. You can't mount a replicated block storage instance to a cluster. When your primary storage fails, you can manually set your replicated backup storage to be the primary one. Then, you can mount it to your cluster. After your primary storage is restored, you can restore the data from the backup storage.





 Duplicating storage 

You can [duplicate your block storage instance](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-duplicatevolumeduplicatevolume) in the same zone as the original storage instance.

A duplicate has the same data as the original storage instance at the point in time that you create the duplicate. Unlike replicas, use the duplicate as an independent storage instance from the original. To duplicate, first set up snapshots for the volume.





 Backing up data to IBM Cloud® Object Storage 

You can use the [ibm-backup-restore](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesbackup-restore-pvc) Helm chart to spin up a backup and restore pod in your cluster.

This pod contains a script to run a one-time or periodic backup for any persistent volume claim (PVC) in your cluster. Data is stored in your IBM Cloud® Object Storage instance that you set up in a zone.

Block storage is mounted with an RWO access mode. This access allows only one pod to be mounted to the block storage at a time. To back up your data, you must unmount the app pod from the storage, mount it to your backup pod, back up the data, and remount the storage to your app pod.

To make your data even more highly available and protect your app from a zone failure, set up a second Object Storage instance and replicate data across zones.