Database Detection

After Veeam Plug-in is installed, Plug-in Manager running on the computer collects information about databases on this computer. Plug-in Manager saves collected information to the XML file and sends to Veeam Backup & Replication. The way Plug-in Manager collects information differs depending on the system installed on the computer:

Oracle
SAP HANA
SAP on Oracle

Oracle

On the Oracle server, Plug-in Manager collects information differently depending on the Oracle deployment way:

If you install Veeam Plug-in on the standalone Oracle server, the rescan process differs depending on the OS running on the target computer:

In case of Oracle server deployed on the Linux computer, Plug-in Manager scans the oratab or orainventory file. If you use Automatic Storage Management (Oracle ASM), Plug-in Manager rescans both files (oratab and orainventory).
In case of Oracle server deployed on the Microsoft Windows computer, Plug-in Manager checks Windows Registry and parses services that are running on the computer.

As a result, Veeam Backup & Replication gets 3 levels of the database hierarchy (from top to bottom): hostname, Oracle home, Oracle system identifier (SID).

If you install Veeam Plug-in on Oracle RAC, Plug-in Manager uses the srvctl utility. With this utility, Plug-in Manager collects information. Plug-in Manager uses, for example, the srvctl config scan and srvctl config database commands.

For Oracle RAC, Plug-in Manager uses a database unique name instead of SID. As a result, Veeam Backup & Replication gets 3 levels of the database hierarchy (from top to bottom): scanname, Oracle home, database unique name.

After rescan completes, you can create an application policy and add any level of the database hierarchy to the scope of this policy. For example, you can add a certain Oracle database or Oracle home that contains several databases.

SAP HANA

On the SAP HANA server, Plug-in Manager collects information depending on the SAP HANA deployment way:

If you install Veeam Plug-in on the standalone SAP HANA server, Plug-in Manager gets path to the saphostctrl (SAP Host Agent) utility. With this utility, Plug-in Manager gets the list of database instances.

As a result, Veeam Backup & Replication gets 3 levels of the database hierarchy (from top to bottom): hostname, SAP system name, database name.

If you install Plug-in Manager on the SAP HANA scale-out system, Plug-in Manager collects information from the veeam_config.xml file.

As a result, Veeam Backup & Replication gets 3 levels of the database hierarchy (from top to bottom): scale-out system name, SAP system name, database name.

Tip

During the Veeam Plug-in deployment on the scale-out system nodes, Veeam Backup & Replication sets the scale-out system name using domain name and SAP system name. If you want to set a custom name, use the --set-scale-out-cluster-name command on the computer side. This custom name will be saved in the veeam_config.xml file.

After rescan completes, you can create an application policy and add any level of the database hierarchy to the scope of this policy. For example, you can add a certain SAP HANA database or a host that contains several SAP HANA databases.

SAP on Oracle

On the SAP on Oracle server, Plug-in Manager gets path to the saphostctrl (SAP Host Agent) utility. With this utility, Plug-in Manager gets the list of database instances.

As a result, Veeam Backup & Replication gets 2 levels of the database hierarchy (from top to bottom): hostname, Oracle system identifier (SID).

Important

Veeam Backup & Replication does not support cluster deployment of SAP on Oracle.

MongoDB

. The selected mongo daemon resides on a computer. VAL, veeammongoagent and transports are already installed on it by a recent rescan of Mongo PG.

A customer will need to go through the PG wizard after he changes topology