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."],[[["This document provides reference documentation for the `VolumeDataRestorePolicy` enum within the Google Cloud GKE Backup v1 API."],["The `VolumeDataRestorePolicy` enum specifies how volume data should be handled during a restore operation, offering options such as restoring from backup, reusing the original volume, or not restoring volume data."],["The document presents the `VolumeDataRestorePolicy` fields `NoVolumeDataRestoration`, `RestoreVolumeDataFromBackup`, `ReuseVolumeHandleFromBackup`, and `Unspecified`, each with a detailed description of their functionality."],["This page also provides a list of versions for the document, ranging from the latest 2.6.0 version down to the 1.0.0-beta01."]]],[]]
