For each PVC to be restored, PVCs will be created 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, will 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). Note that 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."],[[["The content outlines different versions of the `VolumeDataRestorePolicy` enum within the Google Cloud GKE Backup v1 API, ranging from version 1.0.0-beta01 to the latest version 2.6.0."],["The `VolumeDataRestorePolicy` enum defines the behavior for restoring volume data, providing options like `NoVolumeDataRestoration`, `RestoreVolumeDataFromBackup`, and `ReuseVolumeHandleFromBackup`."],["There is also an `Unspecified` field within the enum which is considered an illegal state."],["The documentation provides a detailed description of each field for the `VolumeDataRestorePolicy`, explaining how it affects the restoration process of PVCs (Persistent Volume Claims)."],["The API associated with this documentation is under the `Google.Cloud.GkeBackup.V1` namespace, and is contained within the `Google.Cloud.GkeBackup.V1.dll` assembly."]]],[]]
