NDMP Backup with Type zfs

When backing up with type "zfs", administrators specify the data to backup by its canonical name on Oracle ZFS Storage Appliance. This can be found underneath the name of the share in the BUI:


NDMP share name

or in the CLI as the value of the canonical_name property. Canonical names do not begin with a leading '/', but when configuring the backup path, the canonical name must be prefixed with '/'.

Both projects and shares can be specified for backup using type "zfs". If the canonical name is specified as-is, then a new snapshot is created and used for the backup. A specific snapshot can be specified for backup using the @snapshot suffix, in which case no new snapshot is created and the specified snapshot is backed up. For example:

Table 3-25 Canonical Names and Shares Backed Up

Canonical Name Shares Backed Up

pool-0/local/default

New snapshot of the local project called default and all of its shares.

pool-0/local/default@yesterday

Named snapshot yesterday of local project default, and all of its shares having snapshot yesterday.

pool-0/local/default/code

New snapshot of share code in local project default. code could be a filesystem or volume.

pool-0/local/default/code@yesterday

Named snapshot yesterday of share code in local project default. code could be a filesystem or volume.

Because level-based incremental backups using the "zfs" backup type require a base snapshot from the previous incremental, the default behavior for level backups for which a new snapshot is created is to keep the new snapshot so that it can be used for subsequent incremental backups. If the DMA indicates that the backup will not be used for subsequent incremental backups by setting UPDATE=n, the newly created snapshot is destroyed after the backup. Existing user snapshots are never destroyed after a backup. For details, see NDMP Incremental Backups.

Share metadata - Share metadata (that is, share configuration) is always included in "zfs" backups. When restoring a full backup with type "zfs", the destination project or share must not already exist. It will be recreated from the metadata in the backup stream. When restoring an incremental backup with type "zfs", the destination project or share must already exist. Its properties will be updated from the metadata in the backup stream. For details, see NDMP Incremental Backups.