Configuring Cloud Backup
Cloud backups provide the ability to back up full and incremental share snapshots from a local Oracle ZFS Storage Appliance to cloud targets in an Oracle Cloud Infrastructure account. Share snapshots are created as usual, and individual snapshots are selected for cloud backup. More than one appliance can back up to the same cloud target, and cloud backups can be restored on any Oracle ZFS Storage Appliance with access to the cloud target.
By using the "tar" archiving format for cloud backups, as opposed to the default "zfs" format, you can create full and incremental filesystem (not LUN) snapshot backups. These backups can be restored on any system, regardless of its operating system, that can access the cloud target. However, a tar cloud backup does not preserve the original filesystem properties.
After you have established an Oracle Cloud Infrastructure account and created buckets in Object Storage, you prepare Oracle ZFS Storage Appliance systems to use cloud backup, define cloud targets, and create cloud backups that can later be restored.
In the BUI, there are five tabs for the cloud data service:
Properties, Targets,
Backups, Jobs, and Logs
(service log). In the CLI, the cloud data service has three child nodes:
backups, targets, and jobs.
Objects in each of these CLI child nodes are assigned ordinal names, such as
backup-001. In either the BUI or CLI, creating a cloud backup creates
a cloud job with an operation of backup. The other operations for cloud
jobs are restore and delete. Like other services, user
operations are logged to the audit log, and results of operations are logged to the alert
log. Cloud service state changes are logged to the service log.
To manage cloud storage, you can view the cloud jobs, cancel and restart jobs, modify or delete cloud targets, view and filter cloud backups, and restore and delete cloud backups. To analyze backup and restore operations, see Data Movement: Cloud Bytes and Data Movement: Cloud Requests in Oracle ZFS Storage Appliance Analytics Guide, Release OS8.8.x. To set alerts, see Configuring Alerts.
Before using cloud backup on clustered controllers, it is important to understand clustering behavior in conjunction with this feature. The cloud data service is cluster aware, and each controller uses its own available network interfaces to communicate with configured cloud targets to perform backup and restore operations, and to refresh its list of available cloud backups. Therefore, a controller might not immediately have a refreshed list of cloud backups from its peer controller. Also, while both controllers share common service configurations, cloud targets, and cloud backups, each controller has its own Jobs list. After a restart or failover event, cloud backup or restore operations running on the impacted controller are automatically resubmitted on the peer controller, and the operations restart from the beginning.
This section contains the following topics and tasks: