Veeam backup mysql linux

Содержание

Specifying MySQL Processing Settings
MySQL Backup
System Requirements

Specifying MySQL Processing Settings

You can enable MySQL processing settings in the properties of a volume-level backup job configured in Veeam Agent for Linux .

IMPORTANT

To process the MySQL database system, the MySQL account must have the following privileges:

SELECT for all tables. If you do not have the SELECT privilege for the table, Veeam Agent does not process the table.
LOCK TABLES. If you do not have the LOCK TABLES privilege, Veeam Agent does not process MyISAM tables.

RELOAD. This privilege is required to allow the MySQL account to perform FLUSH operations.

To obtain information about privileges that are assigned to the account, use MySQL functionality, for example, the SHOW GRANTS statement. To learn more, see MySQL documentation .

To enable MySQL processing settings for the backup job, use the following command:

veeamconfig aap set mysql —jobId

veeamconfig aap set mysql —jobName

— ID of the backup job for which you want to enable MySQL processing settings. You should look up the job ID in advance, before configuring MySQL processing settings , for example, with the veeamconfig job list command. To learn more, see Viewing List of Backup Jobs .

— name of the backup job for which you want to enable MySQL processing settings.

— MySQL processing settings for the backup job. To learn more, see MySQL Processing Settings .

TIP

To view IDs or names of all existent backup jobs, you can press the Tab key right after you type the —jobId or —jobName option.

You can specify the following MySQL processing settings for the backup job:

Description and values

Defines that Veeam Agent must continue the backup process if errors occur when processing the MySQL database system. If you do not specify this option, Veeam Agent will stop the backup process if an error occurs when processing the MySQL database system.

Name of the MySQL account. Veeam Agent can connect to the MySQL database system in one of the following ways:

If you specify account name ( —usrMysqlDb option) only, Veeam Agent will prompt you to specify a password to access the MySQL database system.
If you specify account name and password ( —usrMysqlDb and —password options), Veeam Agent will access the MySQL database system.
If you do not specify account credentials ( —usrMysqlDb and —password options), Veeam Agent will use a password file to connect to the MySQL database system. To learn more about password file configuration, see Preparing Password File for MySQL Processing .

Password of the MySQL account. If you do not specify the —password value, Veeam Agent will prompt you to specify a password to access the MySQL database.

Keep in mind, if you specify the password using the —password option, password is stored in terminal in plain text.

Path to a password file. You must specify a full path to a password file if you want Veeam Agent to use a password file located in specific directory. Specifying relative paths is not supported.

With this method selected, you do not need to specify account credentials in the backup job settings.

You do not need this option in the following cases:

Veeam Agent uses account name and password that are specified in the backup job settings to connect to the MySQL database.
Veeam Agent uses account credentials that are stored in the password file in /root/.my.cnf .

Authentication with password:

$ veeamconfig aap set mysql —jobId 29bc2e1a-e35c-4efb-8d37-b7177b8ea75 —tryProcess —usrMysqlDb root —password P@ssw0rd

Источник

MySQL Backup

You can use Veeam Agent for Linux to create transactionally consistent backups of Veeam Agent machines that run the MySQL database system.

How MySQL Processing Works

To ensure that the backed-up data is in the consistent state, Veeam Agent for Linux performs the MySQL database system processing. To process the database system, Veeam Agent performs the following operations:

When the backup job starts, Veeam Agent connects to the MySQL database system and obtains the list of tables.
Veeam Agent locks base tables that are based on the MyISAM storage engine. Veeam Agent changes the table state using the MySQL functionality. Tables based on the InnoDB storage engine do not require locking.

Keep in mind that Veeam Agent supports processing of tables based on the MyISAM and InnoDB storage engines only. Veeam Agent does not support tables that use other storage engines.

Creates a snapshot of the volume.
Unlocks tables locked at the step 2.

After Veeam Agent unlocks tables , Veeam Agent proceeds to the next step of the backup process. To learn more, see How Backup Works .

IMPORTANT

To process the MySQL database system, the MySQL account must have the following privileges:

SELECT for all tables. If the MySQL account does not have the SELECT privilege for the table, Veeam Agent cannot access table metadata. As a result, Veeam Agent does not process the table. To learn more, see MySQL documentation .
LOCK TABLES. If the MySQL account does not have the LOCK TABLES privilege, Veeam Agent does not process tables based on the MyISAM storage engine.

To obtain information about privileges that are assigned to the account, use MySQL functionality, for example, the SHOW GRANTS statement. To learn more, see MySQL documentation .

Veeam Agent for Linux can connect to the MySQL database system using one of the following methods:

Password — Veeam Agent uses the MySQL account credentials that you specify in the backup job settings.
Password file — Veeam Agent uses the MySQL account credentials that are stored in the .my.cnf password file. To learn more about password file configuration, see Preparing Password File for MySQL Processing .

Requirements and Limitations for MySQL Processing

Veeam Agent for Linux supports processing of MySQL database system version 5.6 – 8.0.

Configurations with multiple MySQL installations and/or instances on the same machine are not supported.
MySQL Cluster versions are not supported.

Источник

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

Читайте также: Linux add ftp user

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.

Источник