Configuring the Appliance Network
Note - If you used the Oracle Exadata Backup Configuration Utility, proceed to the next topic:
Configuring Exadata for The Appliance.
Configuring Appliance Shares
The default options for ZFS Storage Appliance shares provide a good starting point for general-
purpose workloads. Appliance shares can be optimized for Oracle RMAN backup and restore
operations as follows:
■
Create a project to store all shares related to backup and recovery of a single database. For a
two-pool implementation, create two projects; one for each pool.
■
Configure the shares supporting Oracle RMAN backup and restore workloads with the
following values:
■
Database record size (recordsize): 128kB
■
Synchronous write bias (logbias): Throughput (for processing backup sets and image
copies) or Latency (for incrementally applied backups)
■
Cache device usage (secondary cache): None (for backup sets) or All (when
supporting incrementally applied backups or database clone operations)
■
Data compression (compression): Off for performance-optimized systems, LZJB or
gzip-2 for capacity-optimized systems
■
Number of shares per pool: 1 for management-optimized systems, 2 or 4 for
performance-optimized systems
Additional share configuration options, such as higher-level gzip compression or replication,
can be applied to shares used to support Oracle Exadata backup and restore, as customer
requirements mandate.
Customers implementing additional ZFS Storage Appliance data services should consider
implementation-specific testing to verify the implications of deviations from the practices
described earlier.
Configuring Oracle RMAN and the Oracle Database Instance
Oracle RMAN is an essential component for protecting the content of Oracle Exadata. Oracle
RMAN can be used to create backup sets, image copies, and incrementally updated backups of
Oracle Exadata content on ZFS Storage Appliances. To optimize performance of Oracle RMAN
backups from Oracle Exadata to a ZFS Storage Appliance, the database administrator should
apply the following best practices:
■
Load balance Oracle RMAN channels evenly across the nodes of the database machine.
Integration 615