- Le plus récent
- Le plus de votes
- La plupart des commentaires
Thanks for bringing this to our attention. A fix to the template has been published that resolves this issue. Please launch a new CloudFormation stack using the updated version of the template - (https://s3.amazonaws.com/solution-references/fsx/backup/fsx-scheduled-backup.template). Let us know if this resolves your issue.
I was able to create a backup plan using the cloud formation template and setting the backup frequency to 1-hour intervals.
I would like to set to 30 min intervals. I tried changing the 6 to a 0.5 in the CRON schedule (shown below) and the cloud formation template errored out (so I set it to 1-hr instead and that was fine).
How would I get backups every 30 min?
# Schedule for creating backups (and purging expired)
CronSchedule:
Description: CRON schedule for backups (default every 6 hours)
Type: String
Default: "0 0/6 ** ** ? *"
Hi BTS,
You can specify the following string for the CRON schedule to take backups every 30 minutes:
0/30 ** ** ** ? **
As described in the Amazon CloudWatch documentation page about Schedule Expressions for Rules (https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/ScheduledEvents.html):
- The CRON schedule string specifies values for six fields: Minutes, Hours, Day-of-month, Month, Day-of-week, and Year.
- The / (forward slash) wildcard specifies increments. The 0/30 value for the Minutes field specifies every thirtieth minute, starting from the first minute of the hour.
** The ? (question mark) wildcard specifies one or another. You can't specify the Day-of-month and Day-of-week fields in the same cron expression. If you specify a value (or a **) in one of the fields, you must use a ? (question mark) in the other.
You can also see the Examples section of the page referenced above for more examples of schedule expressions.
Thank you,
Amazon FSx team
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 2 ans