Cannot perform the \"backup\" action for the \"sas-risk-cirrus-core:fileSystem"

[neetschase]

we have deployed sasviya2024.08 on eks 1.28 cluster and trying the backup and restore.

the backup job fails with the error 

:"Cannot perform the \"backup\" action for the \"sas-risk-cirrus-core:fileSystem\" data source as the acknowledgement not received from the backup agent."}
{"level":"info","version":1,"source":"sas-backupjob","messageKey":"backupjob-log-icu.action.type.for.source.info.log","messageParameters":{"actionType":"killRsync","sourceType":"fileSystem"},"properties":{"logger":"backupj

job/handler","caller":"handler/backup.go:698"},"timeStamp":"2024-12-02T15:00:29.623488+00:00","message":"Publishing an event for the \"killRsync\" job and the \"fileSystem\" data source."}.

dded a backup job entry to the status file: 20241202-145419F"}
{"level":"warn","version":1,"source":"sas-backupjob","messageKey":"backupjob-log-icu.notification.warn.log","messageParameters":{"err":"missing port in address"},"properties":{"logger":"backupjob/events/publisher","caller":"notification/notification_publisher.go:42"},"timeStamp":"2024-12-02T15:00:29.635960+00:00","mes
sage":"Unable to get host name with error missing port in address"}
{"level":"error","version":1,"source":"sas-backupjob","messageKey":"backupjob-log-icu.notification.error.log","messageParameters":{"errNotification":"missing port in address"},"properties":{"logger":"backupjob","caller":"backupjob/main.go:465"},"timeStamp":"2024-12-02T15:00:29.635997+00:00","message":"backupjob-log-ic
u.notification.error.log [errNotification:missing port in address]"}
{"level":"info","version":1,"source":"sas-backupjob","messageKey":"backupjob-log-icu.updating.k8s.job.labels.info.log","messageParameters":{"jobName":"sas-scheduled-backup-job-20241202"},"properties":{"logger":"backupjob/kubeutils","caller":"kubeutils/kube_client.go:129"},"timeStamp":"2024-12-02T15:00:29.663600+00:00"
,"message":"Updating the Kubernetes job sas-scheduled-backup-job-20241202 with given label."}
W1202 15:00:29.687734 216 warnings.go:70] would violate PodSecurity "restricted:latest": seccompProfile (pod or containers "sas-certframe", "sas-backup-job", "sas-backup-agent" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
{"level":"info","version":1,"source":"sas-backupjob","messageKey":"backupjob-log-icu.updated.k8s.job.info.log","messageParameters":{"jobName":"sas-scheduled-backup-job-20241202"},"properties":{"logger":"backupjob/kubeutils","caller":"kubeutils/kube_client.go:155"},"timeStamp":"2024-12-02T15:00:29.688311+00:00","messag
e":"Updated the Kubernetes job the sas-scheduled-backup-job-20241202."}
{"level":"info","version":1,"source":"sas-backupjob","messageKey":"backupjob-log-icu.backup.backup.status.info.log","messageParameters":{"jobStatus":"Failed"},"properties":{"logger":"backupjob","caller":"backupjob/main.go:473"},"timeStamp":"2024-12-02T15:00:29.688350+00:00","message":"backupjob-log-icu.backup.backup.s
tatus.info.log [jobStatus:Failed]"

Does the error means : the backup is not configured for sas-risk-cirrus-core or its missing some configuration for the backup.

[JuanS_OCS]

Hi there,

while the message seems to point to a specific aspect of the backup (consequence), the message might indicate that the actual issue is some kind of timeout.

Could you please check if this works for you?

https://communities.sas.com/t5/Administration-and-Deployment/backup-purge-job-fails/m-p/950777

I see more folks are having issues with backups with the latest update of Viya.

[neetschase]

hi @JuanS_OCS  : ihave alread tried these ..but it still same 

[JuanS_OCS]

Thanks @neetschase . I notice now the message "missing port in address" in your logs.

Wondering if there is any port definition that is missing somewhere?

Also, I wonder if you check the configuration changes when there a new version of SAS Viya in the "What's new in Operations" guide.

Could you please check:

https://go.documentation.sas.com/doc/en/itopscdc/v_045/itopswn/n1s87rn4lff99wn16hodkkloq4zl.htm 

https://go.documentation.sas.com/doc/en/itopscdc/v_045/itopswn/n1s87rn4lff99wn16hodkkloq4zl.htm#n00v...

$deploy/sas-bases/docs/configure_connection_settings_for_sas_model_risk_management.htm

$deploy/sas-bases/examples/sas-risk-cirrus-mrm/resources/README.md

$deploy/sas-bases/docs/preparing_and_configuring_risk_cirrus_core_for_deployment.htm

Maybe check if the backup has a good definition for sas-risk-cirrus-core.

When everything else fails, I suggest to reach out to SAS Tech Support.