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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThe document details the \u003ccode\u003eRestoreConfig.Types.VolumeDataRestorePolicy\u003c/code\u003e enum within the Google Cloud GKE Backup v1 API, showcasing different version references.\u003c/p\u003e\n"],["\u003cp\u003eThis enum defines various methods for restoring volume data during a backup restore operation within the GKE environment.\u003c/p\u003e\n"],["\u003cp\u003eFour possible \u003ccode\u003eVolumeDataRestorePolicy\u003c/code\u003e field values include: \u003ccode\u003eNoVolumeDataRestoration\u003c/code\u003e, \u003ccode\u003eRestoreVolumeDataFromBackup\u003c/code\u003e, \u003ccode\u003eReuseVolumeHandleFromBackup\u003c/code\u003e, and \u003ccode\u003eUnspecified\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe latest version in this document is version 2.6.0, while version 2.2.0 is the main version displayed on the page.\u003c/p\u003e\n"]]],[],null,[]]
