Reference documentation and code samples for the Google Cloud AlloyDB for PostgreSQL V1 Client class WeeklySchedule.
A weekly schedule starts a backup at prescribed start times within a
day, for the specified days of the week.
The weekly schedule message is flexible and can be used to create many
types of schedules. For example, to have a daily backup that starts at
22:00, configure the start_times field to have one element "22:00" and
the days_of_week field to have all seven days of the week.
Generated from protobuf message google.cloud.alloydb.v1.AutomatedBackupPolicy.WeeklySchedule
Namespace
Google \ Cloud \ AlloyDb \ V1 \ AutomatedBackupPolicy
The times during the day to start a backup. The start times are assumed to be in UTC and to be an exact hour (e.g., 04:00:00). If no start times are provided, a single fixed start time is chosen arbitrarily.
↳ days_of_week
array
The days of the week to perform a backup. If this field is left empty, the default of every day of the week is used.
getStartTimes
The times during the day to start a backup. The start times are assumed
to be in UTC and to be an exact hour (e.g., 04:00:00).
If no start times are provided, a single fixed start time is chosen
arbitrarily.
[[["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-09-04 UTC."],[],[],null,["# Google Cloud AlloyDB for PostgreSQL V1 Client - Class WeeklySchedule (1.4.1)\n\nVersion latestkeyboard_arrow_down\n\n- [1.4.1 (latest)](/php/docs/reference/cloud-alloydb/latest/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [1.4.0](/php/docs/reference/cloud-alloydb/1.4.0/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [1.3.0](/php/docs/reference/cloud-alloydb/1.3.0/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [1.2.0](/php/docs/reference/cloud-alloydb/1.2.0/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [1.1.3](/php/docs/reference/cloud-alloydb/1.1.3/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [1.0.0](/php/docs/reference/cloud-alloydb/1.0.0/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [0.10.3](/php/docs/reference/cloud-alloydb/0.10.3/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [0.9.0](/php/docs/reference/cloud-alloydb/0.9.0/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [0.8.0](/php/docs/reference/cloud-alloydb/0.8.0/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [0.7.1](/php/docs/reference/cloud-alloydb/0.7.1/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [0.6.0](/php/docs/reference/cloud-alloydb/0.6.0/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [0.5.0](/php/docs/reference/cloud-alloydb/0.5.0/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [0.4.0](/php/docs/reference/cloud-alloydb/0.4.0/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [0.3.0](/php/docs/reference/cloud-alloydb/0.3.0/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [0.2.1](/php/docs/reference/cloud-alloydb/0.2.1/V1.AutomatedBackupPolicy.WeeklySchedule)\n- [0.1.3](/php/docs/reference/cloud-alloydb/0.1.3/V1.AutomatedBackupPolicy.WeeklySchedule) \nReference documentation and code samples for the Google Cloud AlloyDB for PostgreSQL V1 Client class WeeklySchedule.\n\nA weekly schedule starts a backup at prescribed start times within a\nday, for the specified days of the week.\n\nThe weekly schedule message is flexible and can be used to create many\ntypes of schedules. For example, to have a daily backup that starts at\n22:00, configure the `start_times` field to have one element \"22:00\" and\nthe `days_of_week` field to have all seven days of the week.\n\nGenerated from protobuf message `google.cloud.alloydb.v1.AutomatedBackupPolicy.WeeklySchedule`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ AlloyDb \\\\ V1 \\\\ AutomatedBackupPolicy\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getStartTimes\n\nThe times during the day to start a backup. The start times are assumed\nto be in UTC and to be an exact hour (e.g., 04:00:00).\n\nIf no start times are provided, a single fixed start time is chosen\narbitrarily.\n\n### setStartTimes\n\nThe times during the day to start a backup. The start times are assumed\nto be in UTC and to be an exact hour (e.g., 04:00:00).\n\nIf no start times are provided, a single fixed start time is chosen\narbitrarily.\n\n### getDaysOfWeek\n\nThe days of the week to perform a backup.\n\nIf this field is left empty, the default of every day of the week is\nused.\n\n### setDaysOfWeek\n\nThe days of the week to perform a backup.\n\nIf this field is left empty, the default of every day of the week is\nused."]]
