|Applies To||Keon Certificate Authority 6.0.2|
Keon Registration Authority 6.0.2
|Issue||Keon: Scheduled backup not made after KCA is restarted|
Scheduled backups do not resume after the KCA database is restored and/or the KCA services are restarted. The backups were being made as scheduled prior to stopping the KCA services.
Backups seem only to resume after the backup start time is reset to a time beyond the current system time.
|Cause||After restarting the KCA Secure Directory Server, the saved backup configuration is not active for up to 24 hours. The next backup cycle proceeds at that time.|
When KCA services are restarted, the KCA Secure Directory Server does not start making backups until it hits the automated backup start time "again" - which could be after a delay of anywhere between a few seconds to 24 hours.
For example, if KCA is configured to auto-backup every hour starting from Sept 5 at 11:00 a.m., with a full backup occurring after every 5 incremental backups. The backups will be made as configured while KCA keeps running. If KCA is restarted at say 4:30 p.m. expecting it to resume scheduled backups at 5:00 p.m., note that KCA will NOT resume backups until 11:00 a.m. the next day, which is its originally configured start time.
|Resolution||In normal production environments, this situation should not arise, primarily because backups would most likely be made on daily or weekly basis and not on hourly basis. If the backup schedule needs to be made on hourly basis, and KCA services are restarted, reset the backup start schedule to a time beyond the current system time while keeping all other backup configurations unchanged.|
|Workaround||Changed the backup schedule so the backups occurred every hour (or every few hours).|
|Legacy Article ID||a12895|