From b474b5ee5f08638c02d4522221547a994f4c5cc7 Mon Sep 17 00:00:00 2001 From: Werner Beroux Date: Fri, 22 Jan 2016 17:11:32 +0100 Subject: [PATCH] Update README.md --- README.md | 35 +++++++++++++++++++++++++---------- 1 file changed, 25 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 1d874c8..3091152 100644 --- a/README.md +++ b/README.md @@ -2,14 +2,36 @@ Dockerized [duplicity](http://duplicity.nongnu.org/) backup tool. ### Usage +#### Backup to Google Cloud Storage example + +**WORK IN PROGRESS** + +[Google Cloud Storage](https://cloud.google.com/storage/) *nearline* [costs about $0.01/GB/Month](https://cloud.google.com/storage/pricing). + +Set up: + + 1. [Sign up, create an empty project, enable billing, and create a *bucket*](https://cloud.google.com/storage/docs/getting-started-console) + 2. Under "Storage" section > "Interoperability" tab > click "Enable interoperable access" and then "Create a new key" button and note both *Access Key* and *Secret* (alternatively use [gcloud's `gsutil config -a`](https://cloud.google.com/storage/docs/getting-started-gsutil) to generate the `~/.boto` configuration file and mount it as `/home/duplicity/.boto`). + +Now you're ready to perform a backup: + + $ docker run --rm --user $UID -v /:/data:ro -e PASSPHRASE=P4ssw0rd -e GS_ACCESS_KEY=MYGOOGLEACCESSKEY -e GS_SECRET_ACCESS_KEY=SomeVeryLongAccessKey duplicity duplicity /data gs://my-bucket-name/some_dir + +To restore, you'll need: + + * Keep keys or regenerate them to access your Google Cloud Storage. + * The `PASSPHRASE` you've used. + +**TODO** see [note on Google Cloud Storage](http://duplicity.nongnu.org/duplicity.1.html#sect15). + + #### Backup to Google Drive example [Google Drive](https://drive.google.com/) offers [15GB for free](https://support.google.com/drive/answer/2375123). Set up: - 1. - 2. Follow notes [on Pydrive Backend](http://duplicity.nongnu.org/duplicity.1.html#sect20) to generate a P12 credential file (call it `pydriveprivatekey.p12`) and note also the associated service account email generated (e.g. `duplicity@developer.gserviceaccount.com`). + 1. Follow notes [on Pydrive Backend](http://duplicity.nongnu.org/duplicity.1.html#sect20) to generate a P12 credential file (call it `pydriveprivatekey.p12`) and note also the associated service account email generated (e.g. `duplicity@developer.gserviceaccount.com`). 2. Convert P12 to PEM: $ docker run --rm -i --user $UID -v $PWD/pydriveprivatekey.p12:/pydriveprivatekey.p12:ro wernight/duplicity openssl pkcs12 -in /pydriveprivatekey.p12 -nodes -nocerts > pydriveprivatekey.pem @@ -21,16 +43,9 @@ Now you're ready to perform a backup: To restore, you'll need: - * Regenerate a PEM file (or keep it somewhere) + * Regenerate a PEM file (or keep it somewhere). * The `PASSPHRASE` you've used. -#### Backup to Google Cloud Storage example - -[Google Cloud Storage](https://cloud.google.com/storage/) *nearline* [costs about $0.01/GB/Month](https://cloud.google.com/storage/pricing). - -**TODO** see [note on Google Cloud Storage](http://duplicity.nongnu.org/duplicity.1.html#sect15). - - #### Backup via rsync example **TODO**