Currently, if a DB is unhealthy (e.g. in the initializing state) and the schedule time comes the operator will still try to run the backup operation that will immediately fail. Instead of running the backup in that state, the backup could be postponed to when the DB is healthy again.

The aforementioned behaviour should be liked to the backupIfUnhealthy unsafe flag.