If backup storage credentials are wrong, PBM agent doesn’t allow the backup to start. but after PBM inserts the backup meta into db, we consider the backup as “running” while in the meta the backup status is “starting”. Since backups can run for hours according to db size, users may not suspect there is something wrong until it’s too late. We should handle “starting” status in https://github.com/percona/percona-server-mongodb-operator/blob/main/pkg/controller/perconaservermongodbbackup/backup.go#L102 

After a certain duration, we should update the backup status as "error" if it's not "running". PBM cli uses something like 33 seconds.