#ASAr2 using hourly config-backup schedule?

1 messages · Page 1 of 1 (latest)

brazen tapir
#

We noticed that ASAr2 systems do not use "8hour" for the schedule1 of config-backup but have "hourly" configured. Looks like this only happens with ASAr2 systems.
Since you can't edit the schedule1 you would need to edit the hourly-schedule to bring it back to 8hour...

You see that too? Seems like a bug to me.

cluster::*> system configuration backup settings show                                                                 
                  Backup Destination URL: ftp://[IP]
                Username for Destination: [user]
            Validate Digital Certificate: -
                              Schedule 1: hourly      <-----
Number of Backups to Keep for Schedule 1: 4
                              Schedule 2: daily
Number of Backups to Keep for Schedule 2: 4
                              Schedule 3: weekly
Number of Backups to Keep for Schedule 3: 4
       Location for backup scratch space: disk
Reserved size of scratch space in memory: 1GB
                   Allow backup via TFTP: false

cluster::*> version
NetApp Release 9.17.1P3: Sun Dec 07 04:46:28 UTC 2025

Job schedule 8hour still exists:

cluster::*> job schedule cron show
Cluster Vserver  Name        Description
------- -------- ----------- --------------------------------------------------
cluster
        cluster
                 10min       @:00,:10,:20,:30,:40,:50
                 12-hourly   @0:15,12:15
                 3-hourly    @0:15,3:15,6:15,9:15,12:15,15:15,18:15,21:15
                 5min        @:00,:05,:10,:15,:20,:25,:30,:35,:40,:45,:50,:55
                 6-hourly    @0:15,6:15,12:15,18:15
                 8hour       @2:15,10:15,18:15      <-----
                 Balanced Placement rebalance @0:10
                 daily       @0:10
                 hourly      @:05                   <-----
                 monthly     1@0:20
                 pg-15-minutely @:10,:25,:40,:55
                 [...]
#

The man-pages still say that schedule1 would be "8hour":

     [-numbackups1 <integer>] - Number of Backups to Keep for Schedule 1
         Use this parameter to specify the number of backups created by backup job schedule 1 to keep on the
         destination system. If the number of backups exceeds this number, the oldest backup is removed.
         Schedule 1 is pre-programmed to be '8hour'
#

It's the same on another ASA A30 which is on 9.18.1RC1.