snapshot overflow and other questions: Support Case #06102534

[hspindel]

Support Case #06102534

Brand new user evaluating Veeam...

My initial backups fail with Snapshot Overflow. I read the forums and found a suggestion to double the portionSize in /etc/veeam/veeam.ini. Doing so did not fix the issue - still getting snapshot overflow. How to fix?

I setup Veeam to perform a full system backup. If the system has mounted SMB shares from another computer, will Veeam attempt to back those up? If yes, how do I prevent that?

I am accessing veeam through a console window GUI. Is there a real GUI available to manage Veeam? How do I install it?

I used the console GUI to configure my first backup. On the page where I specify the backup target, one of the options is SMB share. But the GUI will not let me access the field for configuring the share. How do I configure it?

I got around the limitation in the previous path by mounting the SMB share and telling Veeam to backup to local storage (the mounted share). Is this the correct way or is there a better option?

Thank you.

[PTide]

Hi,

I setup Veeam to perform a full system backup. If the system has mounted SMB shares from another computer, will Veeam attempt to back those up? If yes, how do I prevent that?

VAL is supposed to automatically skip all network filesystems (SMB/NFS) unless you explicitly include them in the backup scope.

I am accessing veeam through a console window GUI. Is there a real GUI available to manage Veeam? How do I install it?

If by 'real GUI' you mean KDE or Gnome, then no, VAL does not have any desktop environment GUI.

I used the console GUI to configure my first backup. On the page where I specify the backup target, one of the options is SMB share. But the GUI will not let me access the field for configuring the share. How do I configure it?

Please provide more details on what's going on. Is the field inactive, or you cannot select it, or it's not there?

I got around the limitation in the previous path by mounting the SMB share and telling Veeam to backup to local storage (the mounted share). Is this the correct way or is there a better option?

It's also a correct way. However, in this case Veeam won't be able to automatically mount/unmount the share.

My initial backups fail with Snapshot Overflow. I read the forums and found a suggestion to double the portionSize in /etc/veeam/veeam.ini. Doing so did not fix the issue - still getting snapshot overflow. How to fix?

Check whether there is enough space on the device where snapshot storage is placed. You can assign another device manually and see if that changes anything.

Meanwhile, please keep working with the support engineer.

Thanks!

[hspindel]

Thanks for all your clarifying replies.

I solved the problem about the GUI not allowing me to specify a CIFS share as the target. I had to use veeamconfig to create a repository before it showed up as available in the GUI.

There are over 3TB of space free for snapshot storage. Should be plenty. But what I read on the web is that snapshot overflow is related to free space on the protected computer, not free space on the backup target. Doesn't make sense to me as the protected computer has plenty of space too.

I don't know that tech support is going to help me more. I am running Rocky Linux and they claim it isn't supported. But Rocky Linux is exactly RHEL, which is supported. I did notice lots of errors in blksnap.log like this:

[04.06.2023 19:06:04-742407] <18101> | ERR :Cannot get empty storage block
[04.06.2023 19:06:04-742426] <18101> | ERR :Set snapshot device is corrupted for [9:124] with error
code 28
[04.06.2023 19:06:05-565507] <16136> | ERR :Failed to copy data to diff storage with error 14
[04.06.2023 19:06:45-455544] <17825> | ERR :Set snapshot device is corrupted for [253:0] with error
code 28
[04.06.2023 19:06:45-455552] <16136> | ERR :Failed to copy data to diff storage with error 14
[04.06.2023 19:33:25-630299] <17294> | ERR :Set snapshot device is corrupted for [8:82] with error
ode 28
[04.06.2023 19:33:25-630316] <18511> | ERR :Failed to copy data to diff storage with error 14
[04.06.2023 19:36:14-230899] <18562> | ERR :Set snapshot device is corrupted for [9:125] with error
code 28

[PTide]

I solved the problem about the GUI not allowing me to specify a CIFS share as the target. I had to use veeamconfig to create a repository before it showed up as available in the GUI

This does not sound right. VAL is not supposed to show repositories in UI. Please send a picture.

Doesn't make sense to me as the protected computer has plenty of space too.

VAL places snapshot on a local disk. Snapshot is basically a file. 'Snapshot overflow' means that the file is out of space OR the computer does not keep up with creating new portions of the file OR the disk where the file resides is out of space.

I don't know that tech support is going to help me more. I am running Rocky Linux and they claim it isn't supported. But Rocky Linux is exactly RHEL, which is supported. I did notice lots of errors in blksnap.log like this:

Code: Select all

04.06.2023 19:06:04-742407] <18101> | ERR :Cannot get empty storage block
[04.06.2023 19:06:04-742426] <18101> | ERR :Set snapshot device is corrupted for [9:124] with error
code 28
[04.06.2023 19:06:05-565507] <16136> | ERR :Failed to copy data to diff storage with error 14
[04.06.2023 19:06:45-455544] <17825> | ERR :Set snapshot device is corrupted for [253:0] with error
code 28
[04.06.2023 19:06:45-455552] <16136> | ERR :Failed to copy data to diff storage with error 14
[04.06.2023 19:33:25-630299] <17294> | ERR :Set snapshot device is corrupted for [8:82] with error
ode 28
[04.06.2023 19:33:25-630316] <18511> | ERR :Failed to copy data to diff storage with error 14
[04.06.2023 19:36:14-230899] <18562> | ERR :Set snapshot device is corrupted for [9:125] with error
code 28х

Although Rocky is exactly RHEL, maybe it's not quite exactly RHEL afterall : )

I asked our support to escalate your case and we will try to check what's wrong. Please keep in mind that although an exclusion has been made, the case is still not in a high priority queue as Rocky is not yet officially supported.

Thanks!