0

I want to export from Google Cloud SQL with function Export, in a cloud bucket. But do not work at all. Nothing happen. There is a bug.

It's not first time when I made exports, but right now the export function do not work.

Any ideas?

Explained with a Gif Desktop Record

Alexcsandru
  • 29
  • 1
  • 3
  • Nice, -1, but can you say what is not clear? I made a GIF, pretty clear. Function export do not work. – Alexcsandru Feb 18 '19 at 23:54
  • Got the exact same problem. Click the button and nothing happens. Have successfully exported before. – Matt Feb 19 '19 at 02:29
  • The problem is not resolved. I tried again several times, I cloned the SQL server and tried from there but same problem. Export did not work. – Alexcsandru Feb 19 '19 at 11:21

2 Answers2

1

The problem is generated by the settings of bucket where you try to export:

To resolve export function issue, please try the steps below:

  1. Go to Cloud Storage and click the bucket you trying to export data from.
  2. Click “Edit bucket”.
  3. Select “Set object-level and bucket-level permissions” for “Access control model”.
  4. Save the changes.
  5. Configure/Try the export again.

Print screens:
Step-1
Step-2
Step-2-with-custom-db-export
Final-Export-Running

A suggestion to Google Cloud Engineers is to post an error message or something when you try to export in a bucket with wrong Access Control Model. Right now you don't have any clue what is happening.

Alexcsandru
  • 29
  • 1
  • 3
0

I have got the same problem. It seems to be a bug with the GCP console.

A work around is to use the command line tool instead.

First you will need to give your cloudSQL service account permissions to access your bucket. Do this by copying the service account name and adding it on the bucket permissions in the GCP console. It will need Storage Object Creator permissions.

Next to export, use the following command.

gcloud sql export <<instancename>> gs://<<bucket name>>/<<file Name>>.gz —database=<<DB name>>
Matt
  • 101
  • 3
  • 1
    Thanks for the work around! It's nice to know this. I posted the steps how to solve this issue without GCP console. (the problem is that the bucket's now have to be with Access Control Model on “Set object-level and bucket-level permissions”. – Alexcsandru Feb 21 '19 at 12:42
  • 1
    Great. Your solution worked perfectly. Thanks. Google really should put a message explaining this. – Matt Feb 22 '19 at 05:05