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."],[[["The content provides documentation for the `RestoreConfig.Types.VolumeDataRestorePolicy` enum within the Google Cloud GKE Backup v1 API, covering versions from 1.0.0-beta01 to 2.6.0."],["This enum defines different strategies for restoring volume data, including `NoVolumeDataRestoration`, `RestoreVolumeDataFromBackup`, and `ReuseVolumeHandleFromBackup`."],["The `NoVolumeDataRestoration` field creates PVCs without restoring data, relying on Kubernetes provisioning."],["`RestoreVolumeDataFromBackup` creates new volumes and PVs from the backup for each restored PVC."],["`ReuseVolumeHandleFromBackup` attempts to reuse the original PV from the backup, which is mainly for restoring workloads to their original cluster."]]],[]]
