Response doesn't have a table tag

We have a nightly backup that successfully backups close to a hundred databases but lately 1 or 2 of them are failing, with the following error.

Failed to backup “db_151606423” database with “Full” backup type: Response doesn’t have a table tag.

There seems to be no pattern to which database this happens on, any idea?

Thanks

We have the same issue, random databases will fail backup with “Response doesn’t have a table tag”.
Then on another day it backs up fine.

Hello guys,

Could you please let us know what DBMS do you use and what server type is used during the connection?

Please let us know if you have any other questions.

Thank you and sorry for the inconvenience.

Hi Alexander,
Thanks for your reply, we are using MySQL on AWS RDS (version 8.0.28), we use a Windows server (also running in AWS) to host the backup agent.

Cheers,
Chris Oldershaw

Hi Chris Oldershaw,

Could you please try to execute scripting via SSMS and check if it works?

If you have any other questions, please let us know.

Thank you and sorry for the inconvenience.

Our DB’s are running in MySQL not MSSQL - SSMS is not available.
We can run command line backup which works.
Do you know if SQLbackupandFTP is passing the “TABLE TAG” error? I can’t find mention of that error in MySQL documentation.

Is there anyway to get the backup task to re-run on any failed jobs?

Hi Chris Oldershaw,

To investigate this case, we need more details. Could you please provide us with the full log of your job with the error message you get?

Please let us know if you have any other questions.

Thank you and sorry for the inconvenience.

Sure thing, can you provide a private method for me to share the logs?
Email address, private chat, FTP?
Thanks.

Hi Chris Oldershaw,

Sure, please send the details to support@sqlbackupandftp.com

Thank you and sorry for the inconvenience.

thank you, email sent.

Hi Chris Oldershaw,

Thank you for the details. We are working on the issue. We’ll reply to you by email.

Thank you and sorry for the inconvenience.

We are having the same issue. Any insights would be appreciated.

are you backing up AWS MySQL or OnPrem MySQL version?

After a lot of troubleshooting with sqlbackupandftp support the issue unfortunately remained unresolved.
last response 5 months ago was - “We have double-checked the issue, and it seems there is nothing we can help you in resolving the issue from our side.”

Try increasing the SQL Timeout from within sqlbackupandftp app settings, we still get the error but it seems to be less often.

Good luck and if you find a better fix, I’d be happy to hear it.