Integration of SAP on Oracle and Veeam Plug-in requires additional environment planning. When you deploy the plug-in, keep in mind the following requirements and limitations.
You can schedule backup processes using Cron.
Also, you can schedule and run existing SAP BR*Tools backup scripts within image-level or file-level backup job of Veeam Backup & Replication or Veeam Agent. For details, see the Pre-Freeze and Post-Thaw Scripts section of the Veeam Backup & Replication.
Veeam Plug-in for SAP on Oracle uses the Windows authentication methods of the Veeam Backup & Replication server to establish a connection to this server and to the backup target.
If this user will be later changed manually, the new user must have at least the Veeam Backup Operator and Veeam Restore Operator rights within the Veeam Backup & Replication user management. To learn how to assign Veeam Backup & Replication roles, see the Roles and Users section of the Veeam Backup & Replication User Guide.
Any parallel data stream started by SAP Backint will use one backup repository task slot. It is recommended to carefully plan repository task slots, so that SAP Backint can work with multiple channels in parallel.
The following hardware resources are recommended based on tests on Skylake processors:
- SAP on Oracle server: 1 CPU core and 200 MB of RAM per currently used channel. Note that resource consumption on the SAP on Oracle server depends on hardware and Oracle settings.
- Backup repository server: 1 CPU core and 1 GB of RAM per 5 currently used channels.
These resources are recommended only if you use a dedicated backup repository for Veeam Plug-in backups. If you use the same backup repository for Veeam Plug-in backups and VM backups created by Veeam Backup & Replication or Veeam Agents, consider adding the mentioned above hardware resources based on usual load on your backup repository. For details on hardware requirements for a backup repository, see the System Requirements section of the Veeam Backup & Replication User Guide.
It is recommended to contact your Veeam system engineer to optimize the channel settings and resource allocation.
It is recommended to use a separate backup repository for Veeam Plug-in backups.
- Veeam Backup & Replication server: during manual metadata operations such as import of backup files, the Veeam Backup & Replication server needs additional 15 GB of RAM per 1 million files located in the same backup job folder.
Veeam Plug-in stores backup files in the following formats:
- A .VAB file stores compressed and deduplicated copy of an Oracle database. Veeam Plug-in creates VAB files for both full and incremental backups.
- A .VASM file stores metadata that contain information about the backup. A .VASM file is created for each .VAB file. The .VASM files are used by Veeam Backup & Replication to get data about Veeam Plug-in backups.
- A .VACM file stores metadata of a backup job object.
Veeam Plug-in generates a name for a .VAB backup file and stores up to 1000 FIB's (file in backup) in one .VAB file. The FIB file names match the external backup ID's (EBID) generated by Veeam Plug-in during the backup.
Also, for each backup file, Veeam Plug-in creates a metadata file that has the same name as the backup file but a different extension (.VASM).