### Author:  [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [2018年四月4日 20:30 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/41 "2018-04-04T20:30:39Z")
Yes, except that Jay doesn’t see any files on Google drive while I seem to get a few bytes transferred. Also, I’ve had this working for months. Not sure about Jay.
Can anyone confirm that the plugins are working for them?
---
### Author:  [@Jay91](https://meta.discourse.org/u/Jay91)
#### Post date: [2018年四月7日 18:39 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/42 "2018-04-07T18:39:00Z")
I hope the author fix it soon.
---
### Author:  [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [2018年四月7日 20:54 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/43 "2018-04-07T20:54:27Z")
I’m not sure we’ve confirmed that there is a problem with the plugin. I’m sure many are using this plugin but it seems only we are having problems.
On the other side, the problem is quite unlikely to be discovered and nobody has confirmed that the plugin is working for them either…
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [2018年五月27日 10:56 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/44 "2018-05-27T10:56:41Z")
你好，我正在尝试安装 Google Drive 存储插件，但在重建 Discourse 时遇到了错误。
我已在 `app.yml` 中添加了以下内容，并且重建可以正常进行：
```yaml
- git clone https://github.com/berlindiamonds/discourse-sync-base.git
```
然而，一旦我在下一行添加：
```yaml
- git clone https://github.com/berlindiamonds/discourse-sync-to-googledrive.git
```
重建就会失败：
```plaintext
185:M 27 May 10:52:31.659 # User requested shutdown...
185:M 27 May 10:52:31.659 * Saving the final RDB snapshot before exiting.
2018-05-27 10:52:31.684 UTC [69] LOG: database system is shut down
185:M 27 May 10:52:33.213 * DB saved on disk
185:M 27 May 10:52:33.213 # Redis is now ready to exit, bye bye...
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development --retry 3 --jobs 4'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]}
5c0c7ec5ac63127128822d5f5175eb5874753b7f34f30d05bc4e90013b306b26
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one
root@canapin:/var/discourse#
```
以下是我的 `app.yml` 中的 `cmd` 部分：
```yaml
cmd:
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/communiteq/discourse-migratepassword.git
- git clone https://github.com/berlindiamonds/discourse-sync-base.git
- git clone https://github.com/berlindiamonds/discourse-sync-to-googledrive.git
```
请注意，`sync-to-dropbox` 没有任何问题，因此这似乎是 `sync-to-googledrive` 特有的问题。
---
### Author:  [@dax](https://meta.discourse.org/u/dax)
#### Post date: [2018年五月30日 23:20 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/45 "2018-05-30T23:20:45Z")
I temporarily moved it in #plugin:broken-plugin .
As soon as one of the engineers gets rid of the other jobs he will fix it properly.
---
### Author:  [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [2018年五月31日 05:34 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/46 "2018-05-31T05:34:52Z")
> [@Canapin](#):
>
> I have no issue with `sync-to-dropbox`
Are you sure that the files that end up in your dropbox are actually full backups? I only get files sized 48 bytes.
---
### Author:  [@dax](https://meta.discourse.org/u/dax)
#### Post date: [2018年五月31日 06:38 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/47 "2018-05-31T06:38:19Z")
My issue with Dropbox is quite different from yous. New backups goes to Dropbox but the old backups are not canceled. In this way, the storage space fills up quickly and the new backups are no longer synchronized and remain on the server.
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [2018年五月31日 10:16 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/48 "2018-05-31T10:16:14Z")
I didn’t try to restore from them but they are the same size as on Discourse, ~300MB so I guess they are good.
However, the first (auto ?) backup from Discourse, before importing my phpbb, didn’t import successfully (1KB file instead of 2 MB), which I didn’t care.
I didn’t try to pass the limit of max backups so I don’t know if I’ll have the same issue as you Daniela, however an option I’d like to have would be that if we delete a backup manually from Discourse, it would get deleted on Dropbox as well.
---
### Author:  [@kajatiger](https://meta.discourse.org/u/kajatiger)
#### Post date: [2018年五月31日 10:31 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/49 "2018-05-31T10:31:28Z")
Hey hey,
I am very sorry but I don’t currently have time anymore to volunteer to the project due to my job.
But if you want, you can always make pull requests to our repo on github or open an issue there and document exactly what the problem is.
---
### Author:  [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [2018年五月31日 12:58 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/50 "2018-05-31T12:58:59Z")
> [@dax](#):
>
> My issue with Dropbox is quite different from yous. New backups goes to Dropbox but the old backups are not canceled
Hm, for me the deletion of old backup works.
This is very weird. Now we have at least three different issues with the backup plugins but none of these issues seem to occur simultaneously or multiple times (except for by Dropbox issue which I have on two independent forums).
Does it make sense to try and get to the bottom of this or will it simply be fixed via
> [@dax](#):
>
> one of the engineers gets rid of the other jobs he will fix it properly.
---
### Author:  [@dax](https://meta.discourse.org/u/dax)
#### Post date: [2018年五月31日 13:18 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/51 "2018-05-31T13:18:52Z")
You just have to be patient, we are at the finish line for a new release and, as always, we are under pressure during this period 😉
---
### Author:  [@Jay91](https://meta.discourse.org/u/Jay91)
#### Post date: [2018年六月4日 20:40 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/52 "2018-06-04T20:40:06Z")
Dear,
Noted, we will take an action when required.
Do we have any hope for fixing this soon ?
---
### Author:  [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [2018年六月7日 16:20 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/53 "2018-06-07T16:20:00Z")
@misaka4e21 is updating this plugin but there is no ETA.
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [2018年七月3日 21:56 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/63 "2018-07-03T21:56:53Z")
Hi,
I want to switch from dropbox to gdrive, but I’m confused about the service account key.
I enabled the Drive api:
I followed the plugin instructions and downloaded the json file here:
I pasted the content of the json here:
But when I do a backup from Discourse, no backup is sent to gdrive. Plus, when creating the json, it is never stated that the purpose is managing google drive.
Also in drive credentials, it doesn’t show the service account key (the api key shown is something else):
And in Discourse, the “Google Drive Downloader” added button leads to a 404:
What am I missing? Plus, it is possible to chose the destination directory of the backups?
---
### Author:  [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [2018年八月10日 10:18 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/65 "2018-08-10T10:18:29Z")
> [@dax](#):
>
> I temporarily moved it in #plugin:broken-plugin .
> As soon as one of the engineers gets rid of the other jobs he will fix it properly.
Can’t find the plugin anywhere on meta anymore. Does that mean it will not be fixed?
I was looking for the topic to share the following information: I noticed that the dropbox cache on my local PC actually seems to contain the backups:
So somehow the backups do get uploaded but then they seem to be deleted again. Hope that helps in fixing the plugin.
---
### Author:  [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)
#### Post date: [2018年九月2日 16:49 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/66 "2018-09-02T16:49:25Z")
Would be possible to upload backups to a [Team Drive](https://gsuite.google.com/learning-center/products/drive/get-started-team-drive/#!/)?
As we have GSuite, we have unlimited Google Drive Storage, and we would like backups to be accessible by anyone of our team, so uploading to a Team Drive is really useful
---
### Author:  [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)
#### Post date: [2018年九月10日 21:19 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/67 "2018-09-10T21:19:53Z")
> [@kajatiger](#):
>
> The discourse-sync-to-googledrive
Where are Google Drive Backups? 😅
Maybe it’s a simple question, but Drive Backup are not on my Drive. However, API reports upload success, and the Drive Downloader shows the backups have been uploaded
---
### Author:  [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [2018年九月16日 19:04 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/68 "2018-09-16T19:04:15Z")
> [@barreeeiroo](#):
>
> Where are Google Drive Backups?
Neither Google Drive nor Dropbox backups work these days and the corresponding topics seem to have vanished. Luckily, there is a workaround that will work for lots of storage providers:
> [@Use rclone to sync backups to Dropbox or Google Drive](https://meta.discourse.org/t/how-to-sync-your-backups-to-cloud-storage-alternative-method/97294):
>
> There is a [plugin that allows you to sync your discourse backups to various cloud storage providers](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018). Unfortunately, it currently doesn’t work with Dropbox and Google Drive. If you nevertheless want to store your backup on your Dropbox or Google Drive follow the steps below. I will use dropbox as an example but the instructions will also work with any other [backend supported by rclone](https://rclone.org/). Disclaimer: The instructions have been tested on Ubuntu 16.04. and they work for me but I am not an expert at …
---
### Author:  [@vitorl](https://meta.discourse.org/u/vitorl)
#### Post date: [2018年九月26日 07:22 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/69 "2018-09-26T07:22:22Z")
Are you sure this is not working currently? I was about to try it, but your solution does seem to be better and more portable, easier to download, you can access it on the web interface.
[https://github.com/berlindiamonds/discourse-sync-to-googledrive](https://github.com/berlindiamonds/discourse-sync-to-googledrive)
---
### Author:  [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [2018年九月26日 13:39 UTC](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018/70 "2018-09-26T13:39:04Z")
> [@vitorl](#):
>
> Are you sure this is not working currently?
If by “this” you mean the base plugin described in the OP, then the answer is yes and no. The thing is: you need two plugins: the base plugin and another plugin for whatever storage backend you’re using. I think the base plugin still works, but the dropbox plugin definitely doesn’t work and I seem to have read somewhere that the google drive plugin is also broken, but I have not tried it myself.
[上一頁](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018.md?page=2)
[下一頁](https://meta.discourse.org/t/synchronizer-base-for-any-backup-provider/68018.md?page=4)