Backing Up the Configuration
To understand configuration backups, use these topics:
■
“Configuration Backup Contents” on page 274
■
“Configuration Restore Impact” on page 275
■
“Security Considerations for Configuration Backups” on page 276
Configuration Backup Contents
A configuration backup
does
include:
■
Metadata associated with the system as a whole, such as settings for NTP, NIS, LDAP, and
other services.
■
Network device, datalink, and interface configuration.
■
User accounts, roles and privileges, preferences, and encrypted passwords for local users
(not directory users).
■
Alerts and thresholds and their associated rules.
■
SRP targets and initiators.
■
Encryption configuration: All contents of the LOCAL keystore, including the keys (stored
in an encrypted form). Configuration details, including the Registration PIN for OKM and
the names only of the keys.
Note -
In a cluster configuration, configuration backups are visible only on the node on which
they were created or imported.
A configuration backup
does not
include:
■
User data (shares and LUNs). Your user data must be backed up separately, using NDMP
backup software, snapshots, and/or remote replication.
■
User passwords for directory users. These remain stored solely in your separate network
directory service, such as LDAP or Active Directory, and are not stored in the backup or
restored.
■
Metadata directly associated with user data, such as snapshot schedules, user quotas,
compression settings, and other attributes of shares and LUNs.
■
Analytics and logs. Events can be redirected to external SNMP trap receivers or e-mail
destinations using Alerts rules.
■
System software. The system software is automatically backed up as part of the System
Update capability.
■
Replication targets.
■
iSCSI targets and initiators.
274
Oracle ZFS Storage Appliance Customer Service Manual • February 2016
