Standalone backup agents for Linux, Mac, AIX & Solaris workloads on-premises or in the public cloud
Post Reply
ta_yoshizumi
Enthusiast
Posts: 62
Liked: 3 times
Joined: Jun 18, 2018 12:29 am
Contact:

Parameters of Veeam.ini

Post by ta_yoshizumi »

Hello,

Backup failed with snapshot overflow in our customer environment, so I was investigating. I contacted Veeam support and support number is '03243753'.
However, as there was not much progress on this matter, I asked a question here.

When I got a log and executed cat '/etc/veeam/veeam.ini', I found that there were differences in parameters and values that do not exist in my environment.
Below is our customer environment 'Veeam.ini'.

Code: Select all

# veeam.ini, v2.0.1.665 2018-10-17 06:04:22
# This is the veeamservice system-wide configuration file.
# The strategy used for options in the default veeam.ini shipped with
# Veeam Agent for Linux is to specify options with their default value where
# possible, but leave them commented. Uncommented options override the
# default value.

[backup]
# Backup cluster alignment logarithm
# clusterAlign= 3

# Ignore inactive LVM logical volumes during backup
# ignoreInactiveLvm= false

# IO rate limit, from 0.01 to 1.0
# ioRateLimit= 0.9

# CPU priority for veeamagents, from 0 to 19
# priority= 10


[bitlooker]
# Enable BitLooker
# enabled= true

# Exclude the specified devices from BitLooker processing (e.g. /dev/sda1, /dev/sdb3)
# exclude= 

# BitLooker timeout per device, ms
# timeout= 900000


[db]
# Veeam database path
# path= /var/lib/veeam/veeam_db.sqlite

# Veeam database scheme path
# schemePath= /usr/share/veeam/lpb_scheme.sql

# Veeam database upgrade scheme path
# schemeUpgradePath= /usr/share/veeam/lpb_upgrade_scheme.sql


[general]
# Root folder path for mount file systems of backup disks
# backupDisksFsMountFolder= /mnt/backup

# Root folder path for mount backup disks
# backupDisksMountFolder= /mnt/backup

# Force FUSE mount on kernels 4.0.0-4.1.33 (for file level restore)
# ignoreFuseBug= false

# Logs path
# logsFolder= /var/log/veeam

# Logs rotation period, days
# logsRotateDays= 14

# Temp directory path
# temporaryDirectory= /tmp/veeam


[job]
# New job default retries count
# retriesCount= 3

# Job retry delay interval (seconds)
# retriesInterval= 600

# Retry all errors, set to 'false' to enable retries only for 'snapshot overflow'
# retryAllErrors= true


[reconnects]
# Time to wait before each reconnect attempt, ms
# attemptInterval= 5000

# Enable reconnect
# enabled= true

# Reconnect attempts timeout, ms
# overallTimeout= 300000


[scripts]
# Ignore freeze and thaw scripts result
# ignoreFreezeThawFailures= false

# Timeout for freeze and thaw scripts
# timeoutFreezeThaw= 600

# Timeout for pre- and post-backup scripts
# timeoutPrePost= 600


[service]
# Service socket
# socket_path= /var/tmp/veeam/socket/veeam.sock


[snapshot]
# Free percent of storage. Used for calculate optimal snapshot data size and determinate snapshot data location, not for stretch snapshot
freePercent= 99

# Percent of free space on block device can be used for snapshot data allocating
# limitFreePercent= 50

# Location folder for snapshot data, only for 'stretch' and 'common' snapshot
# location= 

# Maximum possible snapshot data size, not for stretch snapshot
maxSize= 68719476736

# Minimal possible snapshot data size, not for stretch snapshot
minSize= 68719476736

# Snapshot data type, can be 'stretch' (default) or 'common'
# type= 

# Used percent of storage. Used for calculate optimal snapshot data size and determinate snapshot data location, not for stretch snapshot
usedPercent= 99


[stretchsnapshot]
# Stretch snapshot data portion
portionSize= 8589934592

# Free percent of storage. Used for determinate snapshot data location. Only for stretch snapshot
storageFreePercent= 50


[veeamsnap]
# Kernel log logging level. 7 - list all messages as an error, 4 or 0 - all messages as a warning, 2 - all message as a trace (use only if veeam works perfectly on your system)
# debuglogging= 0
It seems that not only parameters but maxSize and minSize are the same capacity, the # indicated by default is not our customer environment.
Please tell me if you know about this cases.

Thank you for reading to the end.
PTide
Product Manager
Posts: 6428
Liked: 729 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Parameters of Veeam.ini

Post by PTide »

Hi,

minSize and maxSize are intended to be used with 'common' snapshot algorithm, while the portionSize is for 'strecth' only.

That is, if the customer's setup uses 'stretch', maxSize and minSize are ignored. As far as I understand, the engineer has tuned the portionSize, is that correct?

Thanks!
ta_yoshizumi
Enthusiast
Posts: 62
Liked: 3 times
Joined: Jun 18, 2018 12:29 am
Contact:

Re: Parameters of Veeam.ini

Post by ta_yoshizumi »

Hi, Thank you for comment to my post.

Sorry to forget about the details about the parameters.
An error occurred and Veeam engineer's instructions did not change the parameters.
Our customers also said they never made changes to veeam.ini since introducing the Agent in August.

I also installed the Agent for verification and checked the default 'veeam.ini', and all the parameters were preceded by a # and the values of minSize and maxSize were also different from our customer's parameters.
PTide
Product Manager
Posts: 6428
Liked: 729 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Parameters of Veeam.ini

Post by PTide »

In case of an overflow Veeam Agent for Linux attempts to auto-tune the snapshot parameters. That is the reason why you can see different values in the veeam.ini. Sometimes auto-tune does not help much and manual tuning is required. If you feel that the support case could have been handled better, then please ask the support engineer to escalate the case.

Thanks!
ta_yoshizumi
Enthusiast
Posts: 62
Liked: 3 times
Joined: Jun 18, 2018 12:29 am
Contact:

Re: Parameters of Veeam.ini

Post by ta_yoshizumi »

Do you know the following three parameters that do not exist in default?

Code: Select all

※For details, please refer to attached code.
=================================================
# Free percent of storage. Used for calculate optimal snapshot data size and determinate snapshot data location, not for stretch snapshot
freePercent= 99

# Used percent of storage. Used for calculate optimal snapshot data size and determinate snapshot data location, not for stretch snapshot
usedPercent= 99

# Free percent of storage. Used for determinate snapshot data location. Only for stretch snapshot
storageFreePercent= 50
=================================================
I think that these codes were automatically added because our customers did not add them manually.

When I contacted with Veeam support, there was no answer for information about these parameters.
PTide
Product Manager
Posts: 6428
Liked: 729 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Parameters of Veeam.ini

Post by PTide »

By default veeam uses 'stretch' algorithm. The parameters that you see are related to 'common' algorithm and are not shown unless a failover from 'stretch'' to 'common' took place and the default values have been altered. Does the backup job work now, or it still shows 'overflow'?

Thanks
ta_yoshizumi
Enthusiast
Posts: 62
Liked: 3 times
Joined: Jun 18, 2018 12:29 am
Contact:

Re: Parameters of Veeam.ini

Post by ta_yoshizumi »

The backup success failure is summarized below.
------------------------------
10/17 (Wed) Failed
10/18 (Thu) Success
10/19 (Fri) Success
10/20 (Sat) Success
10/21 (Sun) Failed
10/22 (Mon) Failed
------------------------------

In both cases, the following message was output to the HTML report, the backup failed.
=================
Backing up Volume00
Snapshot overflow
Snapshot overflow
Failed to perform managed backup
=================

I also make inquiries at Case # 03243753, but they have no replies.

Currently, in our customer environment snapshot type is 'stretch', can I see improvement by adjustmenting 'maxSize' and 'minSize' after changing to 'common'?

Thank you.
PTide
Product Manager
Posts: 6428
Liked: 729 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Parameters of Veeam.ini

Post by PTide »

Currently, in our customer environment snapshot type is 'stretch', can I see improvement by adjusting 'maxSize' and 'minSize' after changing to 'common'?
I don't have the information what snapshot size worked for that particular environment, but you can try to set it to 'common', set 'location' parameter to a volume that has plenty of space, and set values for 'minSize' and 'maxSize' and see how it goes. However, I would wait for the support engineer to respond - they reported that the case has been escalated, so please wait for their findings.

Thanks!
Post Reply

Who is online

Users browsing this forum: No registered users and 11 guests