on Viya 4 kubernetes, the backup is successful but the purge fails. By getting the log:
kubectl logs BackupPurgeJobPod -n Namespace.
Error:
"Can not perform the purge action for the sas-backup-purge-job configurations,postgres data source as the acknowledgement not received from the backup agent."
it happened for a few days in a row.
Wondering if happened to anyone, and if so how to fix.
Thank you a lot,
Hi, thanks for your reply on this one @drhorg
I am still not fully sure what is the issue here. I wonder what is your version of Viya and cadence, and if your PSQL was deployed externally from the beginning or if was moved from internal to external.
The message you receive is not one I know, but it might be related to a time out. If that is the case, there is a quick solution here:
https://documentation.sas.com/doc/en/itopscdc/v_057/calbr/p1ry8zzqwfqmfpn1cm4p1uk9saib.htm
Else, I would highly suggest to review, step by step, the requirements:
- The job must tun as Kubernetes administrator - RBAC can play against you
- Ensure the workflow for external PSQL https://documentation.sas.com/doc/en/itopscdc/v_057/calbr/p03jdb7rdhf8x8n1gs9q2liiqzh1.htm
- Try first if an ad-hoc backup works okay https://documentation.sas.com/doc/en/itopscdc/v_057/calbr/p0cw7yuvwc83znn1igjc16zah2se.htm
- If PSQL has been moved from internal to external at a certain point in the lifetime of Viya, you might need to review these steps https://documentation.sas.com/doc/en/itopscdc/v_057/pgdatamig/titlepage.htm
Hi there,
first question here: is your PSQL database the internal crunchy one or is it external, and if it is external, can you provide more information?
Hi, thanks for your reply on this one @drhorg
I am still not fully sure what is the issue here. I wonder what is your version of Viya and cadence, and if your PSQL was deployed externally from the beginning or if was moved from internal to external.
The message you receive is not one I know, but it might be related to a time out. If that is the case, there is a quick solution here:
https://documentation.sas.com/doc/en/itopscdc/v_057/calbr/p1ry8zzqwfqmfpn1cm4p1uk9saib.htm
Else, I would highly suggest to review, step by step, the requirements:
- The job must tun as Kubernetes administrator - RBAC can play against you
- Ensure the workflow for external PSQL https://documentation.sas.com/doc/en/itopscdc/v_057/calbr/p03jdb7rdhf8x8n1gs9q2liiqzh1.htm
- Try first if an ad-hoc backup works okay https://documentation.sas.com/doc/en/itopscdc/v_057/calbr/p0cw7yuvwc83znn1igjc16zah2se.htm
- If PSQL has been moved from internal to external at a certain point in the lifetime of Viya, you might need to review these steps https://documentation.sas.com/doc/en/itopscdc/v_057/pgdatamig/titlepage.htm
That was correct. By increasing the timeout, the issue has been fixed
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.