Skip to main content

Oracle Direct to Cloud FAQs

Updated this week

What type of backups does Druva perform on Oracle databases?

The first backup of your databases is a full backup. Thereafter, Druva performs an incremental backup. Additionally, Druva also supports archive log backups of Oracle databases. For more information, see Backup methods.

Does Druva support both on-premise and cloud infrastructure to backup and recover Oracle Server?

Yes, Druva supports backup and restore of Oracle Servers running on the on-premise physical and virtual infrastructure, as well as cloud infrastructure such as Amazon EC2, Azure VMs, Google Compute Engines, and so on.

Do I need to install separate agents for File Server and Oracle Database backups on a Linux server?

No, you do not need separate agents. You can use a single Enterprise Workloads agent that handles both workloads. While you can activate agents for specific tasks, using a combined activation parameter (such as fs-mssql) activates support for both file systems and databases (including Oracle DTC). This allows you to protect both your Oracle database (Oracle DTC) and file system with a single agent installation.

How does Druva protect the Oracle workloads on Microsoft Azure?

Druva supports agent-based backup for databases that enables you to leverage Oracle agent and deploy it in any of the supported Operating Systems on an Azure VM and protect these workloads. Configuration and backup/restore workflows remain the same whether data is located on-premise or on any Cloud like Azure. Another added advantage is that you can restore the data to any target residing either in the customer’s data center or private or public cloud.
Databases like Oracle on Azure VM instances can be backed up using the agent-based backup method.

How do I configure Oracle databases for backup?

To know how you can configure Oracle databases for backup, see Configure databases for backup.

What databases does Druva back up?

Druva allows you to back up container databases, pluggable databases, and standalone databases.

What components can I restore from a database?

Druva not only allows you to restore a complete database but also enables DBAs to recover individual database elements, such as data files, control files, system parameter file, archive logs, and metadata from the downloaded backup data.

Can I reconfigure a database for backup?

Yes, you can reconfigure a database for backup by changing the backup policy or administrative group associated with the database. To know more, see Reconfigure database.

Can I restore my database to a server in another organization under Druva?

Organizations in Druva are independent entities by design. Druva does not have a functionality that allows inter-Organizational restore.

Can I restore my database to ASM storage?

Yes. To restore a database to ASM storage, make sure that you select the Restore SP File check box. Also, make sure that you have configured ASM on the target server and the path variables such as Oracle Home and Oracle Base of the source and target server are the same.
If SP File is set to false, the database will be restored to File system. For more information, see Restore database to alternate server.

How do I reconnect my Oracle Server host to the Druva Cloud?

The Hybrid Workloads agent may get disconnected from the Druva Cloud because of the following reasons:

  • Druva service on the Oracle Server host is stopped.

    Resolution: Start the Druva service on the Hybrid Workloads agent using the service PhoenixOracle restart command.

  • Hybrid Workloads agent is uninstalled from the Oracle Server host.

    Resolution: Install or re-register the Hybrid Workloads agent on the Oracle Server host.

  • Hybrid Workloads agent upgrade on the Oracle Server host is in progress.

    Resolution: Wait for the agent upgrade to complete.

  • Network drop on the Oracle Server host.

    Resolution: Check the network connection on the Oracle Server host.

  • The Oracle database instance is offline.

When should I use PDB restore instead of full CDB restore?

Use PDB Level Selective Restore when:

  • Only one or a few PDBs are corrupted or deleted

  • You need to meet aggressive RTO requirements (under 2 minutes)

  • Storage space is limited, and you cannot accommodate a full CDB restore

  • You want to migrate specific PDBs to a different CDB

Do I need a different backup policy to perform PDB-level restores?

No. Selective PDB restores utilize your existing full CDB backups. There is no need to configure a new backup type or policy to leverage this feature.

Can I restore a PDB to a completely different CDB than the one it was backed up from?

Yes. Cross-CDB restore is supported. You can restore PDBs to a different CDB on an alternate server seamlessly. For more information, see Restore to alternate standalone instance.

How many PDBs can I restore at once?

You can select and restore multiple PDBs in a single restore operation. Oracle supports up to 252 PDBs per CDB. The restore operation handles all selected PDBs in one job.

What happens if I attempt an automated PDB restore to the original server, but the source CDB was deleted or is not running?

The restore job will fail. To restore a PDB to its original server, the parent CDB must be present and running. If it is not, you should perform an alternate server restore or a full CDB restore.

Where can I see which mounts were used for my restored datafiles?

Following the restore operation, you can view the exact restore locations and data distribution in the "Data Transfer" section of the Job Details page on the Console.

What is the default restore location if I leave the "Restore Location" field empty?

If you provide the Oracle Home and Oracle Base but leave the restore location blank, the Oracle Base of the specified server is used as the target destination for the PDB's data files.If you provide the Oracle Home and Oracle Base but leave the restore location blank, the Oracle Base of the specified server is used as the target destination for the PDB's data files.

How can I prioritize a specific storage path, such as ASM?

Locations specified in the db_create_file_dest parameter (for ASM paths) of the Other Server Parameters field take the highest priority and will override other default location settings.

What happens if I recover the SP file but do not provide an Oracle Base or Home?

In this case, the locations defined within the recovered SP file are used. For this, the target server must have a directory structure identical to the source server.

In what order does the system prioritize restore locations if I provide multiple mount locations during restore?

If the Oracle home and Oracle base are provided but the restore location is not provided, the Oracle base of the given server is used as the target location for the PDB's data files. If locations are provided in the Other Server Parameters field (db_create_file_dest parameter (for ASM paths), those locations will be prioritized. When the SP file is recovered, and the Oracle base or home is not provided, the location set on the recovered SP file is used.

In a nutshell, the prioritization follows this order:

  1. Location defined in the Other Server Parameters field (db_create_file_dest parameter). If a single location is provided along with db_create_file_dest, then db_create_file_dest gets the priority. If multiple locations are provided along with db_create_file_dest, then those specified locations are given priority. The locations are prioritized based on the available mount size.

  2. The path provided in the Restore Location field.

  3. Paths set within the restored SP file (if no Home/Base is provided).

  4. The provided Oracle Base (if the Restore Location field is empty).

Did this answer your question?