Enterprise Workloads Editions: ✅ Business | ✅ Enterprise | ✅ Elite
After you deploy a Phoenix Backup Store, you can create backup mounts and use RMAN to store backup data on a backup mount. The Phoenix Backup Store starts creating recovery points of the Oracle RMAN backups and uploads the recovery points to the Druva Cloud. You can use these recovery points to restore the data to a backup mount on one of the Phoenix Backup Stores registered with Druva, and use RMAN to fetch data from the backup mount. However, in some cases, you may want to stop the Phoenix Backup Store from creating and sending the recovery points to the cloud. Or, you may want to delete all the recovery points uploaded to the Druva Cloud from a backup mount.
This articles provides you information on how to use Druva to manage the following:
Manage a Phoenix Backup Store
You can perform the following actions on a registered Phoenix Backup Store:
View Phoenix Backup Store details page
Log in to the Management Console.
Click Oracle > Phoenix Backup Store from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization where the Phoenix Backup Store is registered and then click Oracle > Phoenix Backup Store.
The Phoenix Backup Stores page appears.In the Store Name column, click the Phoenix Backup Store name for which you want to view its details. The Phoenix Backup Store details page appears.
The Phoenix Backup Store details page displays the following fields:
OVERVIEW
Platform:The operating system on which the Phoenix Backup Store is deployed.
Client Version:The version of the Phoenix Backup Store deployed in your infrastructure.
Connection Status:The status of the connection of the Phoenix Backup Store with the Druva Cloud.
Administrative Group:The administrative group associated with the Phoenix Backup Store.
Source + Changes (Total):The total volume of the backup data generated at the source. This size includes the initial full backup and incremental data from all subsequent backups.
Current Source (Total):The total volume of the data on the source server at the time of the last backup.
Phoenix Storage Usage:The storage available on the Phoenix Backup Store.
BACKUP MOUNTS
Backup Mount:The list of backup mounts created on this Phoenix Backup Store.
Storage:The storage on the {[druvacloud}} on which the recovery points uploaded from the backup mount are stored.
Backup Enabled:The status of the backup if the Phoenix Backup Store can upload recovery points from the backup mount. The backup mount gets disabled if the Phoenix Backup Store is unable to upload recovery points from the backup mount to the Druva Cloud for a while.
Last Backup Status:The status of the the last backup job run.
The following actions are available on the Phoenix Backup Store details page:
Register Phoenix Backup Store:Click this button to start the registration. For more information, see Deploy and register a Phoenix Backup Store.
Search bar:Use this field to search for a Phoenix Backup Store using the store name or its administrative group.
Create Backup Mount:Click this option to create a backup mount on the selected Phoenix Backup Store. For more information, see Configure the Phoenix Backup Store and RMAN hosts to backup databases.
Edit Store Name:Click this option to edit the Phoenix Backup Store name. For more information, see Edit the Phoenix Backup Store name.
Change Admin Group:Click this option to change the administrative group of the selected Phoenix Backup Store. For more information, see Manage administrative groups.
Upgrade:Click this option to upgrade the selected Phoenix Backup Store to the latest available revision. For more information, see Upgrade the client.
Disable:Click this option to disable the selected Phoenix Backup Store. For more information, see Disable Phoenix Backup Store.
Delete:Click this option to delete the selected Phoenix Backup Store. For more information, see Delete Phoenix Backup Store.
Edit the Phoenix Backup Store name
You can edit the store name on the Management Console.
Procedure
Log in to the Management Console.
Click Oracle > Phoenix Backup Store from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization where the Phoenix Backup Store is registered and then click Oracle > Phoenix Backup Store.
The Phoenix Backup Stores page appears.In the Store Name column, select a Phoenix Backup Store and then click the More icon > Edit Store Name.
Alternatively, you can also click on the Phoenix Backup Store name for which you want to edit its name. On the Phoenix Backup Store details page that appears, click the More icon > Edit Store Name.
In the Edit Store Name dialog, enter a new name in the Store Name box and click Save. Ensure that you enter alphanumeric characters.
Change the administrative group
An administrative group is a logical categorization of the servers that share something in common. For example, Phoenix Backup Stores located in one region can belong to one administrative group.
Procedure
Log in to the Management Console.
Click Oracle > Phoenix Backup Store from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization where the Phoenix Backup Store is registered and then click Oracle > Phoenix Backup Store.
The Phoenix Backup Stores page appears.In the Store Name column, select a Phoenix Backup Store and then click the More icon > Change Admin Group.
Alternatively, you can also click on the Phoenix Backup Store name for which you want to change its administrative group. On the Phoenix Backup Store details page that appears, click the More icon > Change Admin Group.
In the Change Administrative Group dialog box that appears, select an administrative group from the drop-down menu and click Save.
Upgrade the client
Druva occasionally releases updates to the Phoenix Backup Store that include bug-fixes, new features, and stability enhancements. You can use the options on the Management Console to automatically update the client-side binaries on the Phoenix Backup Store.
Procedure
Log in to the Management Console.
Click Oracle > Phoenix Backup Store from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization where the Phoenix Backup Store is registered and then click Oracle > Phoenix Backup Store.
The Phoenix Backup Stores page appears.In the left pane, click the Phoenix Backup Stores tab. The Phoenix Backup Stores page appears.
In the Store Name column, select a Phoenix Backup Store and then click the More icon > Upgrade.
Alternately, you can also click on the Phoenix Backup Store name for which you want to upgrade the client-side binaries. On the Phoenix Backup Store details page that appears, click the More icon > Upgrade.
The client-side components on the Phoenix Backup Store are upgraded automatically. However, the Phoenix Backup Store will not be upgraded in the following cases:
Phoenix Backup Store is already of the latest version
Phoenix Backup Store upgrade is already scheduled
Phoenix Backup Store needs a manual upgrade
Disable the Phoenix Backup Store
If you do not want the Phoenix Backup Store to create recovery points of the Oracle RMAN backups stored on its backup mounts and upload them to the Druva Cloud, you can disable the Phoenix Backup Store.
📝 Notes
The most recent recovery point cannot be deleted as long as the Phoenix Backup Store exists in the Management Console, regardless of whether the Phoenix Backup Store is marked as inactive or disabled.
The retention period would not be honored for the most recent recovery pointwhen a Phoenix Backup Store is disabled.This allows you to restore the latestrecovery point later if required.
Procedure
Log in to the Management Console.
Click Oracle > Phoenix Backup Store from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization where the Phoenix Backup Store is registered and then click Oracle > Phoenix Backup Store.
The Phoenix Backup Stores page appears.In the Store Name column, select a Phoenix Backup Store that you want to disable and then click the More icon > Disable.
Alternately, you can also click on the Phoenix Backup Store name that you want to disable. On the Phoenix Backup Store details page that appears, click the More icon > Disable.
After a Phoenix Backup Store is disabled:
It completes the Druva backup jobs that are in progress
No new backup jobs are run on the Phoenix Backup Store
You cannot restore databases to the Phoenix Backup Store
All the backup mounts on the Phoenix Backup Store are disabled
Re-register the Phoenix Backup Store
Re-register a Phoenix Backup Store to replace it with a new Phoenix Backup Store or if it gets disconnected. The Phoenix Backup Store can get disconnected from the Druva Cloud if:
A hardware refresh has been performed on the Phoenix Backup Store
A Phoenix Backup Store is replaced with a different server
A Phoenix Backup Store virtual machine is deleted from the vCenter host
For more information, see re-register a Phoenix Backup Store.
Delete the Phoenix Backup Store
If you want to delete the Phoenix Backup Store, delete all the backup mounts on it. Perform the following steps to delete the Phoenix Backup Store:
Log in to the Management Console.
Click Oracle > Phoenix Backup Store from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization where the Phoenix Backup Store is registered and then click Oracle > Phoenix Backup Store.
The Phoenix Backup Stores page appears.In the Store Name column, select a Phoenix Backup Store that you want to delete and then click the More icon > Delete.
📝 Note
You can delete a Phoenix Backup Store only in the disabled state.Click Yes on the confirmation message.
Manage backup mounts on a Phoenix Backup Store
You can perform the following actions on the backup mounts created on a Phoenix Backup Store:
View backup mount details page
Log in to the Management Console.
Click Oracle > Phoenix Backup Store from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization where the Phoenix Backup Store is registered and then click Oracle > Phoenix Backup Store.
The Phoenix Backup Stores page appears.In the left pane, click the Backup Mounts tab. The Backup Mounts page appears.
In the Backup Mount column, click the name of the backup mount for which you want to view details. The backup mount details page appears.
The following table describes the fields and options available on the Summary tab.
OVERVIEW
Phoenix Backup Store:The name of the Phoenix Backup Store on which the backup mount is created.
Backup Enabled:The status of the backup if the Phoenix Backup Store can upload recovery points from the backup mount. The backup mount gets disabled if the Phoenix Backup Store is unable to upload recovery points from the backup mount to the Druva Cloud for a while.
# Recovery point:The number of recovery points that Phoenix Backup Store has uploaded to Druva Cloud.
# Upload Pending Recovery points:The number of recovery points on the backup mount that the Phoenix Backup Store is yet to upload to the Druva Cloud.
BACKUP CONFIGURATION
Storage:The storage on the Druva Cloud on which the recovery points uploaded from the backup mount are stored.
Max Bandwidth:The bandwidth available to the Phoenix Backup Store to upload a recovery point to the Druva Cloud.
Retention:The retention policy applied to the recovery points on the Druva Cloud. For more information, see Retention.
IP Allowlist:The list of IP addresses that can write data to the backup mount.
DATABASES
Database Name:The name of databases whose data is backed up to the backup mount.
Backup Trend: Illustrates the trend of backups for the last seven days and displays the count of Successful, Successful with Errors, and Failed backups.
Backup Data Trend: llustrates the following backup data for the last 90 days:
Source+Change: Shows the amount of backup data generated at the source. This includes the initial full backup and incremental data from all subsequent backups.
Current Source: Shows the size of the data on the source server(s) at the time of the last backup.
Data Change Rate Trend: Illustrates the following change rate for the last 90 days:
Data Growth: Difference between the data sizes of the source data and the total source + changes data.
Average Change Rate: Average of the daily change rate for a backup set calculated since the time of the first backup.
The following table describes the fields and options available on the Backups tab.
Total Recovery points:
The count of the committed recovery points. Druva triggers the Recovery point expiry at 11:45 PM UTC and updates the Total Recovery points count. Druva updates the count immediately when a backup completes successfully.
Latest Recovery Point:The date of the last committed recovery point for a successfully completed backup.
Oldest Recovery Point:The date of the oldest committed recovery point for a successfully completed backup.
Recovery point:The list of recovery points available to restore databases to.
Recovery pointType:The type of recovery points, such as hot or warm, available to restore databases from.
Size:The size of the recovery point.
Edit IP allowlist, bandwidth, and retention
Perform the following steps to edit the settings to retain recovery points on the Druva Cloud, the list of IP addresses of RMAN hosts that can read from or write to a backup mount on the Phoenix Backup Store, and bandwidth to upload the recovery points of the Oracle RMAN backups that RMAN stores on the backup mount.
Log in to the Management Console.
Click Oracle > Phoenix Backup Store from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization where the Phoenix Backup Store is registered and then click Oracle > Phoenix Backup Store.
The Phoenix Backup Stores page appears.Click the name of the Phoenix Backup Store that hosts the backup mount for which you want to edit the [[pbs}} setting. The #####{{pbs}} details page appears. The backup mounts hosted on the #####{{pbs}} are listed in the page that appears.
In the Backup Mounts section, select the backup mount whose settings you want to edit, and click the More icon > Edit. The Edit Backup Mount page appears. Update the required settings.
Edit IP allowlist: In the IP Aallowlist box, add the IP addresses of the RMAN hosts that can access the backup mount. To allow multiple IP addresses, either use a comma or a wildcard. For example, if you enter
192.0.*.*, all the servers with the IP addresses starting192.0.0.0through192.0.255.255can access the mount. If you want to allow servers with specific IP addresses to access the mount, enter the IP addresses using a comma. For example, you want two servers with IP addresses192.0.2.0and198.51.100.1to access the mount. To allow access to the mount, enter192.0.2.0, 198.51.100.1.Edit bandwidth: In the Max Bandwidth box, provide the maximum bandwidth you want the Phoenix Backup Store to use.
Edit retention period: To edit the retention settings, specify the retention duration as per your requirement:
Daily Recovery points for:
Duration in number of days, for which you want to retain all the daily recovery points.
Weekly Recovery points for:
Specify the number of weeks for which you want to retain the latest weekly recovery point.
Monthly Recovery points for:
Specify the number of months for which you want to retain the latest monthly recovery point.
Yearly Recovery points for:
Specify the number of years, for which you want to retain the latest yearly recovery point.
Enable Long Term Retention:
Toggle to enable or disable LTR for the backup policy. You can enable LTR only if the retention period is greater than or equal to one year. To know more about LTR, refer to About Long Term Retention.
In the Keeprecovery pointsin warm tier drop-down list, specify the duration in days to retain the recovery points in the warm tier. For example, 15, 30, 45, and 60 days. See Impact of changing the threshold on the existing recovery points.
📝 Note
Ensure that you enter a value in at least one of the fields. Druva treats the values in the empty fields as zero.
Click Save. Druva saves the updated retention settings.
Enable a backup mount
If a Phoenix Backup Store is unable to upload recovery points to the Druva Cloud for a while, the backup mount gets disabled. The RMAN can be used to restore data from the mount, however, it cannot write backup data to the mount. You can enable the backup mount from the Management Console after resolving the issue that stops the Phoenix Backup Store from uploading recovery points to the cloud. To enable a backup mount:
Log in to the Management Console.
Click Oracle > Phoenix Backup Store from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization where the Phoenix Backup Store is registered and then click Oracle > Phoenix Backup Store.
The Phoenix Backup Stores page appears.In the Store Name column, select the name of the Phoenix Backup Store that hosts the backup mount that you want to enable for storing backups.
Click the More icon > Enable on the backup mount that you want to enable.
Alternatively, you can click the Phoenix Backup Store name on the Phoenix Backup Stores page. The Phoenix Backup Store details page opens. Click the More icon > Enable to enable it for storing backups.
The backup mount is enabled, and RMAN can store backups on it.
Delete a backup mount
Delete a backup mount if you want to:
Stop RMAN from storing Oracle RMAN backups on the backup mount
Delete all recovery points uploaded to the Druva Cloud from backup mount
Perform the following steps to delete a backup mount:
Log in to the Management Console.
Click Oracle > Phoenix Backup Store from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization where the Phoenix Backup Store is registered and then click Oracle > Phoenix Backup Store.
The Phoenix Backup Stores page appears.In the left pane, click Backup Mounts.
On the Backup Mounts page, select the backup mount that you want to delete.
On the Backup Mounts detailspage,click the More icon > Delete.
A confirmation dialog is displayed. Provide a reason in the Reason for deletion box and click Delete. The reason is required to confirm your action and to prevent any accidental deletion. This is a mandatory field, and you can use a minimum of 10 characters and a maximum of 150 characters to provide the reason for deletion. Note that all deletion requests with a reason will be reported to the Audit Trails.
For more information, see View Admin Audit Trails page.
The backup and restore jobs running on the backup mount will be canceled.