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-04-17 UTC."],[[["The `RestoreConfig.Types.VolumeDataRestorePolicy` enum in the Google Cloud GKE Backup v1 API defines how volume data is handled during a restore operation."],["The latest version of this API is 2.6.0, with several previous versions available, including 2.5.0, 2.4.0, 2.3.0, 2.2.0, 2.1.0, 2.0.0, and 1.0.0-beta01."],["This enum offers four distinct options for restoring volume data: `NoVolumeDataRestoration`, `RestoreVolumeDataFromBackup`, `ReuseVolumeHandleFromBackup`, and `Unspecified`."],["`NoVolumeDataRestoration` results in creating new PVCs without restoring data, `RestoreVolumeDataFromBackup` creates new volumes and PVs from the backup, while `ReuseVolumeHandleFromBackup` attempts to reuse the original PV from the backup."],["The `Unspecified` option of the enum is invalid."]]],[]]
