For each PVC to be restored, create PVC without any particular
action to restore data. In this case, the normal Kubernetes provisioning
logic would kick in, and this would likely result in either dynamically
provisioning blank PVs or binding to statically provisioned PVs.
RestoreVolumeDataFromBackup
For each PVC to be restored, create a new underlying volume and PV
from the corresponding VolumeBackup contained within the Backup.
ReuseVolumeHandleFromBackup
For each PVC to be restored, attempt to reuse the original PV contained
in the Backup (with its original underlying volume). This option
is likely only usable when restoring a workload to its original cluster.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["This document provides reference information for the `RestoreConfig.Types.VolumeDataRestorePolicy` enum within the Google Cloud GKE Backup v1 API."],["The `VolumeDataRestorePolicy` enum defines how volume data should be handled during a restore operation, with options including no restoration, restoring from a backup, or reusing the original volume."],["Version 2.6.0 is the latest version of the API, while a range of versions including 2.5.0, 2.4.0, 2.3.0, 2.2.0, 2.1.0, 2.0.0, and 1.0.0-beta01 are also available for `RestoreConfig.Types.VolumeDataRestorePolicy`."],["There are 4 fields available in this specific enum, `NoVolumeDataRestoration`, `RestoreVolumeDataFromBackup`, `ReuseVolumeHandleFromBackup`, and `Unspecified` each with their specific actions described."]]],[]]
