I am in the process of moving our Discourse pilot from the (I know unsupported) NodeChef to a VPS on OVH. I created a backup on NodeChef and wanted to restore this backup on the fresh Discourse install on OVH. Now, the upload of the back worked fine, but the Restore button remains greyed out?
I have no control over the version on NodeChef (which is at the time of the backup was 2.3.0 beta3 +115) and the new install on the VPS is 2.3.0 beta6 +70. Can I get this backup restored?
Thanks @pfaffman, that enabled the Restore button!
… it started ok but then ran into error and it rolled back the restore.
[2019-04-01 12:14:31] ERROR: relation "public.spatial_ref_sys" does not exist
[2019-04-01 12:14:31] invalid command \.
[2019-04-01 12:14:31] ERROR: current transaction is aborted, commands ignored until end of transaction block
[2019-04-01 12:14:31] ERROR: syntax error at or near "1"
[2019-04-01 12:14:31] LINE 1: 1 desktop 1dc8d521c04153d9db5348f3d45c749ec69c7dac /*! norm...
[2019-04-01 12:14:31] ^
[2019-04-01 12:14:31] ERROR: syntax error at or near "-"
[2019-04-01 12:14:31] LINE 1: -ms-text-size-adjust:100%;
[2019-04-01 12:14:31] ^
[2019-04-01 12:14:31] ERROR: syntax error at or near "-"
[2019-04-01 12:14:31] LINE 1: -webkit-text-size-adjust:100%}body{margin:0}article,aside,de...
[2019-04-01 12:14:31] ^
[2019-04-01 12:14:31] ERROR: syntax error at or near "vertical"
[2019-04-01 12:14:31] LINE 1: vertical-align:baseline}audio:not([controls]){display:none;
[2019-04-01 12:14:31] ^
[2019-04-01 12:14:31] ERROR: syntax error at or near "height"
[2019-04-01 12:14:31] LINE 1: height:0}[hidden],template{display:none}a{background:transpa...
[2019-04-01 12:14:31] ^
I have now installed the plugins which were enabled on the NodeChef install as well as imported the Themes I tested. The restore is still giving me errors and it always rolls back. Is there any way around these errors?
That looks like a Postgres version issue, but it’s surprising with the Discourse versions being so close. Do you have a way to see what version of PG was on the server?
Yeah, totally agree… but I would not recommend that without seeing the SQL file first so my first bet was to just see if installing postgis extensions would work - although that’s more like postponing the actual problem.