Update - I think I have the old version of the CB software so I can install that on another computer

ah ok - I noted in the software logs/history that it detailed the filename where it got stuck with that error. Could combine the Google error w/ the 'current' filename to give more detail within the CB app?

No matter if it's in the pipeline to be fixed anyway :)

- Just as a suggestion...forgive me if this is already done in later editions of the backup software.

Would it be worth catching the '%' character based errors with a more meaningful error message if it's a known issue?

"Error occurred during backup: The provided security credentials are not valid." isn't very descriptive of the actual issue and it took me a bit of digging to get to the bottom of the issue (i.e. days without backup running).

Hi Matt. That was exactly the issue. A filename with a % in the name caused it to fail.
I sanitised the file in question and after a couple of days to sort itself out the backup is working again.

Thanks David - yea agreed. I think that will potentially bring additional headaches though!

I might have found the issue. It seemed to be stalling on a particular file so I've removed that from the equation to test. I will see if the backup works tonight.

@Matt - There has been a notification from Google saying there are upcoming changes (June 20th) to JSON API requests to Cloud Storage. This only seems to affect code that checks for endpoint specific details. Do you know, is this likely to have any side-effects for the older version of Cloudberry we are using or is the change not applicable?

Hi Matt,
Touch wood things seem to have reverted back to normal. I gave it a couple of days to sort itself out and the backups have been running successfully again. With that in mind I'll leave it for now but thank you for your help.

Ah ok - we're on a very old version of the app - 3.4.0.92 . I'm not certain of server compatibility if we were to upgrade.