Many thanks for the details David

> I'm not exactly clear why you're using versioning on the S3 side. All versioning should be handled by our software. We do not support S3 versioning directly, but having it on should not pose any issues.

This was setup by my predecessor, so I'm not sure exactly why it was done this way. I understand now that we should be using a longer retention period in the Cloudberry software instead of depending on versioning in S3.

> If you restore the file from S3 versioning, and it's really in the correct format that we need, then you can try synchronizing the repository in the software as that will read what's in the bucket and synchronize it with the local database. Then you should see the file when you do the restore.

This worked perfectly! We did the following:
- Undeleted the object in S3
- Synchronized the repository from S3
- Performed a restore in the normal fashion

Thanks,

Brian