NFS Backup Configuration

NFS Backup Configuration

By default, the Swift object store is used for the backup repository. To use an NFS export as the backup repository, the Cinder backup service must be restarted after adding at least the following two configuration lines to the [DEFAULT] section of the Cinder configuration file cinder.conf:

backup_driver=cinder.backup.drivers.nfs
backup_share=HOST:EXPORT_PATH

Other configuration options may be specified in the [DEFAULT] section as appropriate. Table 4.23, “Configuration options for NFS backup service” below lists the configuration options available for the Cinder Backup service when an NFS export is leveraged as the backup repository.

Option

Type

Default Value

Description

backup_driver

Required

cinder.backup.drivers.swift

Determines the driver that the backup service will load. [1]

backup_share

Required

Set to HOST:EXPORT_PATH. [2]

backup_mount_options

Optional

Comma separated list of options to be specified when mounting the NFS export specified in backup_share [3].

backup_compression_algorithm

Optional

zlib

The compression algorithm to be used when sending backup data to the repository. Valid values are zlib, bz2, and None. [4]

backup_file_size

Optional

1999994880

Data from Cinder volumes larger than this will be stored as multiple files in the backup repository. This option must be a multiple of backup_sha_block_size_bytes.

backup_sha_block_size_bytes

Optional

32768

Size of Cinder volume blocks for digital signature calculation.

Table 4.23. Configuration options for NFS backup service