Storage settings¶

One of the most helpful feature of django-dbbackup is the avaibility to store and retrieve backups from a local or remote storage. This functionality is mainly based on Django Storage API and extend its possibilities.

You can choose your backup storage backend by set settings.DBBACKUP_STORAGE, it must be a full path of a storage class. For example: django.core.files.storage.FileSystemStorage for use file system storage. Below, we’ll list some of the available solutions and their options.

Storage’s option are gathered in settings.DBBACKUP_STORAGE_OPTIONS which is a dictionary of keywords representing how to configure it.

Warning

Do not configure backup storage with the same configuration than your media files, you’ll risk to share backups inside public directories.

DBBackup uses by default the built-in file system storage to manage files on a local directory. Feel free to use any Django storage, you can find a variety of them at Django Packages.

Note

Storing backups to local disk may also be useful for Dropbox if you already have the offical Dropbox client installed on your system.

File system storage¶

Setup¶

To store your backups on the local file system, simply setup the required settings below.

DBBACKUP_STORAGE = 'django.core.files.storage.FileSystemStorage'
DBBACKUP_STORAGE_OPTIONS = {'location': '/my/backup/dir/'}

Available settings¶

location

Absolute path to the directory that will hold the files.

base_url

URL that serves the files stored at this location.

file_permissions_mode

The file system permissions that the file will receive when it is saved.

directory_permissions_mode

The file system permissions that the directory will receive when it is saved.

See FileSystemStorage’s documentation for a full list of available settings.

Amazon S3¶

Our S3 backend uses Django Storages which uses boto.

Setup¶

In order to backup to Amazon S3, you’ll first need to create an Amazon Webservices Account and setup your Amazon S3 bucket. Once that is complete, you can follow the required setup below.

pip install boto3 django-storages

Add the following to your project’s settings:

DBBACKUP_STORAGE = 'storages.backends.s3boto3.S3Boto3Storage'
DBBACKUP_STORAGE_OPTIONS = {
    'access_key': 'my_id',
    'secret_key': 'my_secret',
    'bucket_name': 'my_bucket_name',
    'default_acl': 'private'
}

Available settings¶

Note

More settings are available see official documentation for get more about.

access_key - Required

Your AWS access key as string. This can be found on your Amazon Account Security Credentials page.

secret_key - Required

Your Amazon Web Services secret access key, as a string.

bucket_name - Required

Your Amazon Web Services storage bucket name, as a string. This directory must exist before attempting to create your first backup.

host - Default: 's3.amazonaws.com' (boto.s3.connection.S3Connection.DefaultHost)

Specify the Amazon domain to use when transferring the generated backup files. For example, this can be set to 's3-eu-west-1.amazonaws.com'.

use_ssl - Default: True

default_acl - Required

This setting can either be 'private' or 'public'. Since you want your backups to be secure you’ll want to set 'default_scl' to 'private'.

location - Optional

If you want to store your backups inside a particular folder in your bucket you need to specify the 'location'. The folder can be specified as 'folder_name/'. You can specify a longer path with 'location': 'root_folder/sub_folder/sub_sub_folder/'.

See Django Storage S3 storage official documentation for more information about available settings.

Dropbox¶

In order to backup to Dropbox, you’ll first need to create a Dropbox account and set it up to communicate with the Django-DBBackup application. Don’t worry, all instructions are below.

Setup your Dropbox account¶

Login to Dropbox and navigate to Developers » MyApps. https://www.dropbox.com/developers/apps
Click the button to create a new app and name it whatever you like. For reference, I named mine ‘Website Backups’.
After your app is created, note the options button and more importantly the ‘App Key’ and ‘App Secret’ values inside. You’ll need those later.

Setup your Django project¶

pip install dropbox django-storages

…And make sure you have the following required settings:

DBBACKUP_STORAGE = 'storages.backends.dropbox.DropBoxStorage'
DBBACKUP_STORAGE_OPTIONS = {
    'oauth2_access_token': 'my_token',
}

Available settings¶

Note

See django-storages dropbox official documentation for get more details about.

oauth2_access_token - Required

Your OAuth access token

root_path

Jail storage to this directory

FTP¶

To store your database backups on a remote filesystem via [a]FTP, simply setup the required settings below.

Setup¶

pip install django-storages

Warning

This storage doesn’t use private connection for communcation, don’t use it if you’re not sure about the link between client and server.

DBBACKUP_STORAGE = 'storages.backends.ftp.FTPStorage
DBBACKUP_STORAGE_OPTIONS = {
    'location': 'ftp://user:pass@server:21'
}

Settings¶

location - Required

A FTP URI with optional user, password and port. example: 'ftp://anonymous@myftp.net'

base_url

URL that serves with HTTP(S) the files stored at this location.

Setup¶

We use FTP backend from Django-Storages (again).

pip install django-storages

Here a simple configuration:

DBBACKUP_STORAGE = 'storages.backends.ftp.FTPStorage'
DBBACKUP_STORAGE_OPTIONS = {'location': ftp://myftpserver/}

SFTP¶

To store your database backups on a remote filesystem via SFTP, simply setup the required settings below.

Setup¶

This backend is from Django-Storages with paramiko under.

pip install paramiko django-storages

The next configuration admit SSH server grant a the local user:

DBBACKUP_STORAGE = 'storages.backends.sftpstorage.SFTPStorage'
DBBACKUP_STORAGE_OPTIONS = {'host': 'myserver'}

Available settings¶

host - Required

Hostname or adress of the SSH server

root_path - Default ~/

Jail storage to this directory

params - Default {}

Argument used by method:paramikor.SSHClient.connect(). See paramiko SSHClient.connect() documentation for details.

interactive - Default False

A boolean indicating whether to prompt for a password if the connection cannot be made using keys, and there is not already a password in params.

file_mode

UID of the account that should be set as owner of the files on the remote.

dir_mode

GID of the group that should be set on the files on the remote host.

known_host_file

Absolute path of know host file, if it isn’t set "~/.ssh/known_hosts" will be used.