Table of Contents
Advertisement
Replica Backups
The Oracle ZFS Storage Appliance supports direct backup of replicas and replica snapshots
with the "zfs" backup type. It is not necessary to first clone a replica dataset (project or share) in
order to back it up.
Because the backup is of a replica, the source dataset properties are backed up rather
Note -
than those of the target.
Enabling Replica Backups
To enable replica backups, apply the corresponding deferred update. For more information,
■
see
"Deferred Updates" in Oracle ZFS Storage Appliance Customer Service
Replica backups require software version 2011.1.0 (or later on the source.
■
If the replica backup will be restored to the source with the original replicated dataset, the
■
source must run software version 2013.1.4 (or later).
Replica Backup Syntax
To back up a replicated project or share, input the ZFS dataset name without a snapshot
extension into the DMA. ndmpd uses the appliance software to determine the latest complete
replica snapshot to back up. To specify a replica dataset for backup, use copy and paste to avoid
mistyping long replica dataset names which may include a UUID.
If a user-generated snapshot extension is included, ndmpd backs up the indicated user snapshot.
If a system-generated extension is included (begins with .rr) the backup fails and generates a
message that is logged to the DMA console.
Replica Backup Persistent Holds
Persistent holds are taken on backed-up snapshots when the backups complete. This is
necessary for future incremental backups, which use current snapshots as a base, otherwise the
replication subsystem may delete replica snapshots it no longer needs. Holds are released by
ndmpd when the snapshots are no longer needed.
Persistent holds can be cleared manually. When deleting a replica snapshot with a hold on it, a
confirmation is displayed warning of the potential impact to ongoing or future NDMP backups.
Snapshots required by the replication subsystem cannot be deleted.
If incremental backups are not needed, prevent persistent holds by setting the DMA UPDATE
parameter to no (UPDATE=n). UPDATE=y is the default mode. For more information about the
UPDATE NDMP environment variable, see the whitepaper
Sun ZFS Storage Appliance (http://www.oracle.com/technetwork/server-storage/sun-
unified-storage/documentation/index.html).
Adding HTTP Access to a Share (BUI)
Manual.
NDMP Implementation Guide for the
Appliance Services
273
Advertisement
Table of Contents
