Backup Frequency

You may want to start here - Policies — Veeam Kasten 7.5.8

I have not used Kasten much so hopefully one of the gurus here will chime in more.

Hello!

By default, the "hourly" frequency in Kasten means every hour. To run every 4 hours, you’ll need to use a cron expression instead of the basic frequency selector.

spec:
  frequency: "0 */4 * * *"
  retention:
    ttl: 6h
  actions:
    - action: backup

This configuration will run the backup every 4 hours, at minute 0 of every 4th hour, and retain snapshots for 6 hours.

​@matheusgiovanini Thanks! I tried to put as below, but i am getting invalid frequency

spec:
  frequency: "0 */4 * * *"
  retention:
    hourly: 6
    daily: 1
    weekly: 1

So, the cron expresssion is not working. It is saying “invalid Frequency”

The "invalid frequency" error occurs because the value in the frequency field conflicts with using retention in the hourly, daily, weekly, etc., style. Retention must be defined using ttl (time-to-live) instead of hourly, daily, or weekly retention settings

To configure a backup job that runs every 4 hours, retains backups for 6 hours, and has daily and weekly retention, use the following configuration:

spec:
  frequency: "0 */4 * * *"  
  retention:
    ttl: 6h
    daily: 7
    weekly: 4
  actions:
    - action: backup

In this configuration:

ttl: 6h ensures backups are retained for 6 hours.

daily: 7 retains one backup per day for the last 7 days.

weekly: 4 retains one backup per week for the last 4 weeks.

Note that hourly, daily, and weekly are basic frequency settings, but with cron expressions like frequency: "0 */4 * * *"  you can specify more flexible scheduling, such as running the job every 4 hours.

Hello ​@matheusgiovanini Thanks for your response! Still with the below configuration, I am getting “invalid frequency”

spec:
  frequency: "0 */4 * * *"  
  retention:
    ttl: 6h
  actions:
    - action: backup

Hi!

Since the ttl and frequency settings look correct, could you please confirm two things for me?

Which version of Kasten K10 are we using?

Is the configuration wrapped properly inside a valid policy object?

Just trying to rule out any compatibility or formatting issues.

Thanks

Hello! I am using version 7.5.4

You can try removing the quotes from the cron expression, like this:

frequency: 0 */4 * * *

However, if that still triggers the “invalidy frequency” error (which sometimes happens depending on the K10 version), a more reliable alternative would be using @hourly with subFrequency like this:

frequency: "@hourly"
subFrequency:
  hours: [0, 4, 8, 12, 16, 20]
retention:
  ttl: 6h

This way, the policy will run every 4 hours and keep the snapshots for 6 hours, avoiding issues with custom cron parsing in certain K10 versions.

Now I am getting “frequency-subfrequency mismatch” using subFrequency