Oracle Backup
You can use Veeam Agent for Linux to create transactionally consistent backups of Veeam Agent machines that run the Oracle database system.
NOTE
You can use Veeam Explorer for Oracle to restore Oracle databases from a Veeam Agent for Linux backup. For information about item-level recovery of Oracle systems, see Veeam Explorers User Guide .
How Oracle Processing Works
To ensure that the backed-up data is in the consistent state, Veeam Agent for Linux performs the Oracle database system processing. To process the database system, Veeam Agent performs the following operations:
- When the backup job starts, Veeam Agent obtains information about Oracle databases that run on the Veeam Agent machine.
- Veeam Agent connects to the Oracle database and operates depending on the database state:
- Shutdown state
- ARCHIVELOG mode
- NOARCHIVELOG mode
After Veeam Agent for Linux finishes database system processing, Veeam Agent proceeds to the next step of the backup process. To learn more, see How Backup Works .
If the database is shut down, Veeam Agent skips it and connects to the next database. The skipped database will be included in the backup. To restore such database, you must restore the entire volume that contains the database. You cannot restore the database as an independent item using Veeam Explorer for Oracle. To learn more, see Veeam Explorers User Guide .
Veeam Agent displays a warning message about the database that is shut down in the job session logs. The backup job does not fail.
If the Oracle database is running in the ARCHIVELOG mode, the Oracle database system keeps archived logs that allow to recover all committed transactions of the database . To learn more, see Oracle documentation .
If the database operates in the ARCHIVELOG mode, Veeam Agent performs the following operations:
- Veeam Agent switches the database to the backup mode. Veeam Agent changes the database state using the Oracle functionality.
- Veeam Agent creates a snapshot of the volume .
- Veeam Agent returns the database to the initial state.
If the Oracle database is running in the NOARCHIVELOG mode, the Oracle database system does not create archived logs. Logs that are created before the database is switched to NOARCHIVELOG remain untouched. In this mode, you can only restore the database to the point of full database backup. You cannot recover transactions subsequent to that full database backup.
If the database operates in the NOARCHIVELOG mode, Veeam Agent performs the following operations:
- Veeam Agent shuts down the database. Veeam Agent changes the database states using the Oracle functionality.
- Veeam Agent creates a snapshot of the volume .
- Veeam Agent returns the database to the initial state.
Veeam Agent for Linux can connect to the Oracle database system and perform Oracle archived logs backup and/or deletion using one of the following account types:
- System account — Veeam Agent uses the account of the Veeam Agent machine OS. To connect to the Oracle database system, the account must be a member of the group that owns configuration files for the Oracle database (for example, the oinstall group).
- Oracle account — Veeam Agent uses the Oracle account. To connect to the Oracle database system, the account must have SYSDBA rights.
Archived Log Processing
NOTE
Veeam Agent for Linux operating in the standalone mode supports the backup of archived logs, but does not support a separate schedule and retention policy for the backup of archived logs. This functionality is available only for Veeam Agent for Linux operating in the managed mode within the Veeam Agent management scenario. For more information, see Oracle Archived Log Settings section in the Veeam Agent Management Guide.
In the ARCHIVELOG mode, the Oracle database system stores database archived logs to a certain location on the machine that runs the database system, as specified by the database administrator. Veeam Agent allows you to set up the following ways of archived logs processing:
- Delete logs older than the specified time (in hours) . After the backup job completes, Veeam Agent deletes archived logs that are older than the specified time from the Veeam Agent machine. This helps make sure that logs do not overflow the storage space on the processed machine .
- Delete oldest logs larger than the specified size (in GB) . After the backup job completes, Veeam Agent checks whether the total size of archived logs exceeds the specified size. After that, Veeam Agent deletes oldest archived logs that exceed the specified size from the processed machine . This helps make sure that logs do not overflow the storage space on the Veeam Agent machine .
- Do not delete archived logs . Log files remain untouched on the Veeam Agent machine .
Veeam Agent processes archive logs via Oracle Call Interface (OCI) .
Requirements and Limitations for Oracle Processing
- Oracle Database versions 11g – 21c are supported for all operating systems supported by Veeam Agent for Linux . To learn more, see System Requirements .
- Automatic Storage Management (ASM) is not supported.
- Oracle Real Application Clusters (RAC) are not supported.
- Oracle Grid Infrastructure is not supported.
- Oracle Database Express Edition is not supported.
- SAP on Oracle is not supported.
- Oracle Database architectures with Data Guard are not supported.
Источник
Installing Veeam Agent for Linux
NOTE
To make UEFI systems with Secure Boot work with the pre-built veeamsnap kernel module, you need to enroll the Veeam public key to the MOK list using the mokutil utility. The key is available in the veeamsnap-ueficert-5.0.1.4493-1.noarch package residing on the Veeam repository. To enroll the key:
- Request the enrollment of the public key with the following command: mokutil —import veeamsnap-ueficert.crt .
- Reboot the Veeam Agent computer and complete the enrollment in the UEFI console.
To install Veeam Agent for Linux :
- Download the Veeam software repository installation package ( veeam-release ) from the this Veeam webpage , and save the downloaded package on the computer where you plan to install the product.
TIP
If the computer where you want to install Veeam Agent for Linux is not connected to the internet, you can download and install Veeam Agent for Linux packages manually. To learn more, see Installing Veeam Agent for Linux in Offline Mode .
- Navigate to the directory where you have saved the veeam-release package and install the package with the following commands:
For CentOS / RHEL / Oracle Linux / Fedora
rpm -ivh ./veeam-release* && yum check-update
For openSUSE / SLES
zypper in ./veeam-release* && zypper refresh
For Debian / Ubuntu
dpkg -i ./veeam-release* && apt-get update
For CentOS / RHEL / Fedora
yum install veeam
NOTE
[For CentOS / RHEL] If the dkms package is already installed in the OS, you can install Veeam Agent with one of the following commands:
With this command, the veeamsnap kernel module will be installed from the source RPM package using dkms .
- yum install kmod-veeamsnap veeam
With this command, the non-DKMS version of the veeamsnap kernel module will be installed from the pre-built kmod-veeamsnap binary package.
For Oracle Linux
yum install veeamsnap
yum install veeam
For openSUSE Tumbleweed
zypper in veeam
For openSUSE Leap 15.3
zypper in veeamsnap-kmp-default
zypper in veeam
For SLES with Default kernel
zypper in veeamsnap-kmp-default
zypper in veeam
For SLES with Trace kernel
zypper in veeamsnap-kmp-trace
zypper in veeam
For SLES with Xen kernel
zypper in veeamsnap-kmp-xen
zypper in veeam
For SLES with PAE kernel
zypper in veeamsnap-kmp-pae
zypper in veeam
For SLES with Preempt kernel
zypper in veeamsnap-kmp-preempt
zypper in veeam
For Debian / Ubuntu
apt-get install veeam
The following dependency packages may require special handling in case you see installation errors:
- The dkms package is not present in default repositories for some Linux distributions. You should obtain it from third-party repositories:
- EPEL repository (for CentOS / RHEL / Oracle Linux / Fedora)
- Packman repository (for openSUSE). To learn more , see Installing dkms in openSUSE .
For SLES, the dkms package is not available in the Packman repository. You must use the package intended for openSUSE. To learn more, see this Veeam KB article .
- Extended kernels, such as kernel-pae , kernel-uek and other, require appropriate kernel-devel packages to be installed, for example, kernel-pae-devel , kernel-uek-devel , and so on.
Version of the kernel-devel package must match your current kernel version. To check your current kernel version, run the uname -r command.
[For RHEL and derivatives] If the yum package manager installs packages that do not match your current kernel version, you should either update your system or fetch older versions of the required packages from the CentOS Vault repository .
In openSUSE systems, while installing the dkms package, you may see an error similar to the following:
Problem: nothing provides kernel-devel needed by dkms-2.2.0.3-14.1.noarch
Solution 1: do not install dkms-2.2.0.3-14.1.noarch
Solution 2: break dkms-2.2.0.3-14.1.noarch by ignoring some of its dependencies
To install the dkms package, do the following:
- Make sure that you have an appropriate kernel-devel package installed and its version matches your kernel version. For example:
> rpm -qa | grep kernel-default
kernel-default-devel-3.0.101-91.1
kernel-default-3.0.101-91.1
Источник
System Requirements
The protected Linux computer must meet requirements listed in the table below.
NOTE
The following system requirements apply to the following Veeam Agent for Linux configuration:
- Veeam Agent version is 5.0.1 .
To learn system requirements for Veeam Agent 5.0, see Release Notes for Veeam Agent for Linux 5.0 .
- Veeam Agent is operating in the standalone mode.
To learn about system requirements for Veeam Agent managed by Veeam Backup & Replication , see the System Requirements section in the Veeam Agent Management Guide.
- Veeam Agent is installed with veeam and veeamsnap packages.
To learn about system requirements for Veeam Agent installed using veeam-nosnap package, see Appendix A. Requirements for veeam-nosnap .
CPU: x86-64 processor (i386 or later).
Memory: 1 GB RAM or more. Memory consumption varies depending on the backup type and the total amount of backed-up data.
Disk Space: 100 MB free disk space for product installation.
Network: 10 Mbps or faster network connection to a backup target.
System firmware: BIOS or UEFI.
Disk layout: MBR or GPT.
For virtual machines: Only full virtualization type is supported. Containers and paravirtualized instances are not supported. Oracle VM virtual machines are supported with limitations .
Important! Check considerations and limitations that apply to the list of supported OSes.
Linux kernel version 2.6.32 or later is supported.
Both 64-bit and 32-bit versions (if applicable) of the following distributions are supported:
- Debian 9.0 – 11.0
- Ubuntu 14.04, 16.04, 18.04, 20.04, 20.10, 21.04
- RHEL 6.0 – 8.4
- CentOS 7.0 – 8.4
- Oracle Linux 6 – 8.4 (RHCK)
- Oracle Linux 6 (starting from UEK R2) – Oracle Linux 8 (up to UEK R6 U2, kernel version 5.4.17-2102)
- SLES 11 SP4, 12 SP2 – 15 SP3
- SLES for SAP 11 SP4, 12 SP2 – 15 SP3
- Fedora 33, 34
- openSUSE Leap 15.2 – 15.3
- openSUSE Tumbleweed
Important! Check considerations and limitations that apply to the list of supported file systems.
Veeam Agent for Linux supports consistent snapshot-based data backup for the following file systems:
- Btrfs (for OSes that run Linux kernel 3.16 or later)
- Ext 2/3/4
- F2FS
- FAT16
- FAT32
- HFS
- HFS+
- JFS
- NILFS2
- NTFS
- ReiserFS
- XFS
The supported file system (except for Btrfs) can reside on a simple volume or LVM2 volume; volumes protected with encryption software such as dm-crypt are supported. Btrfs is supported only if it resides directly on a physical device with no additional abstraction layers (such as LVM, software RAID, dm-crypt and so on) below or above it.
Data that resides on other file systems and volumes (including NFS and SMB shares) can be backed up using the snapshot-less mode. For details, see Snapshot-Less File-Level Backup .
Important! Check considerations and limitations that apply to the list of supported components.
Protected computer must have the following components installed:
- dkms
- gcc
- make
- perl
- linux-headers (for Debian-based systems)
- kernel-headers (for RedHat-based systems)
- kernel-devel (for RedHat-based systems)
- kernel-uek-devel (for Oracle Linux with UEK)
- libudev
- libacl
- libattr
- lvm2
- libfuse
- libncurses5
- dmidecode
- libmysqlclient
- libpq5
- python3
- efibootmgr (for UEFI-based systems)
- isolinux (for Debian-based systems)
- syslinux (for RedHat-based systems)
- btrfs-progs (for backup of Btrfs file system)
- mksquashfs (for custom Veeam Recovery Media)
- unsquashfs (for custom Veeam Recovery Media)
- wget (for custom Veeam Recovery Media)
- xorriso (for custom Veeam Recovery Media with EFI support)
- linux-image- -dbg (for Debian 11.0)
where — the Linux kernel version that you use
- Linux kernel version 2.6.32 or later is supported as long as you use kernels supplied by your distribution. Consider the following limitations:
- Fedora is supported up to kernel 5.13.19.
- openSUSE Tumbleweed is supported up to kernel 5.13.13.
- Linux kernel 2.6.32-754.6.3 in RHEL and Oracle Linux (RHCK) is not supported.
- If you work with the Veeam Agent for Linux 5.0 build earlier than 5.0.1.4493 and the protected computer is running Linux kernel version 5.8 or later, only file-level backup is supported.
- Only GA versions of the supported distributions that have been released before the current version of Veeam Agent for Linux are supported.
- Use the dkms packages with the following distributions instead of the pre-built binary veeamsnap kernel module packages:
- Debian 9.0 – 11.0
- Ubuntu 14.04, 16.04, 18.04, 20.04, 21.04
- Oracle Linux 6 – 8.4 (RHCK)
- Oracle Linux 6 (starting from UEK R2) – Oracle Linux 8 (up to UEK R6 U2, kernel version 5.4.17-2102)
- Fedora 33, 34
- openSUSE Tumbleweed
- The Linux OS must be set up to receive software updates from the default repositories enabled in the OS after installation.
- For cloud-based installations that use customized kernels (such as Linux distributions deployed from AWS Marketplace or Azure Marketplace), the veeamsnap kernel module has experimental support status. For details about experimental support, see this Veeam KB article .
- Pre-built binary veeamsnap kernel module packages require kernel 2.6.32-131.0.15 or later for RHEL 6 (excluding 2.6.32-279.el6.i686) and 3.10.0-123 or later for CentOS / RHEL 7.0 – 7.9.
- RHEL, CentOS and Oracle Linux (RHCK) are supported up to certain kernel versions. For details, see this Veeam KB article .
- Veeam Agent for Linux does not back up the following objects:
- LVM snapshots
- volumes that reside on USB devices and SD cards
- Total size of all file systems included in a file-level backup must not exceed 218 TB. Size of a file included in a file-level backup must not exceed 16 TB.
- Veeam Agent supports backup of extended attributes with the following limitations:
- Veeam Agent backs up extended attributes only with the following public namespaces: system, security, trusted, and user.
- All extended attribute names and values of a file must not exceed 4096 bytes (size of a default ext4 file system block). Veeam Agent does not back up attributes exceeding the limit.
For the kernel version 4.13 or later, if a value of extended attribute exceeds the limit, Veeam Agent uses the ea_inodes feature. Backups created using the ea_inodes feature cannot be mounted on kernel versions up to 4.12.
- Backup of file and directory attributes (for example, a — append only, c — compressed, and so on) is not supported.
- Each volume included in a backup must have a unique UUID.
- The veeamsnap module provides RAM-based changed block tracking (CBT) mechanism. Every time the module is unloaded or Veeam Agent for Linux computer is rebooted, CBT data is reset. As a result, Veeam Agent reads the entire data added to the backup scope to detect what blocks have changed since the last job session, and incremental backup requires greater time.
- You cannot back up an entire system image or specific volumes of machines used as cluster nodes. Only snapshot-less file-level backup of cluster nodes is supported. That includes backup of machines that use shared disks, clustered file systems or clustered LVM.
- Certain limitations for EMC PowerPath configuration apply. To learn more, see this Veeam KB article .
- BFQ I/O scheduler is not supported.
- Sparse files are not supported. Veeam Agent backs up and restores sparse files as regular files.
IMPORTANT
Linux user account used to work with Veeam Agent for Linux must have the /bin/bash shell set as the default shell.
- The following packages are not required for CentOS, RHEL and SLES distributions if a pre-built binary veeamsnap package is to be installed.
- dkms
- gcc
- make
- perl
- kernel-headers (for RedHat-based systems)
- kernel-devel (for RedHat-based systems)
- Version of the following packages varies according to the Linux kernel version that you use:
- linux-headers (for Debian-based systems)
- kernel-headers (for RedHat-based systems)
- kernel-devel (for RedHat-based systems)
- linux-image- -dbg (for Debian 11.0)
where — the Linux kernel version that you use
- For openSUSE and SLES distributions, either of the following packages is required: libncurses5 or libncurses6 .
- The dmidecode package is r equired for Veeam Agent management — a valid BIOS UUID must be obtainable either from dmidecode | grep -i uuid or from /sys/class/dmi/id/product_uuid . Each Veeam Agent that consumes a license installed in Veeam Backup & Replication must have a unique BIOS UUID. If a valid UUID cannot be obtained, Veeam will generate it automatically.
- The libmysqlclient package is required to process MySQL database system located on the Veeam Agent server. For details, see Backup of MySQL Database . Package version varies according to the MySQL database system version that you use.
- The libpq5 package is required to process PostgreSQL database system located on the Veeam Agent server. For details, see Backup of PostgreSQL Database .
- The python3 package or another RPM package providing a /usr/bin/python3 binary is required for CentOS, RHEL 7.0 and later distributions if a pre-built binary kmod-veeamsnap package is to be installed.
- The btrfs-progs package version 3.16 or later is required.
Any file systems and devices that are accessible from the host OS. To learn about limitations, see File System .
Backup can be performed to the following types of storage:
- Local (internal) storage of the protected computer (not recommended).
- Direct attached storage (DAS), such as USB, eSATA or Firewire external drives.
- Network Attached Storage (NAS) able to represent itself as SMB (CIFS) or NFS share. Requires cifs-utils or nfs-utils packages to be installed on the Veeam Agent for Linux computer, depending on a network storage type.
- Veeam Backup & Replication 11 or later backup repository (including deduplication appliances).
- Veeam Cloud Connect 11 or later cloud repository.
Consider the following:
- Veeam Agent for Linux should be able to establish a direct IP connection to the Veeam Backup & Replication server. Thus, Veeam Agent for Linux cannot work with Veeam Backup & Replication that is located behind the NAT gateway.
- Domain names of the Veeam Agent computer, Veeam Backup & Replication server and other servers in the Veeam backup infrastructure must be resolvable into IPv4 addresses.
Источник
