Question

Snapshot overflow error when backing up Ubuntu volume


Userlevel 3
Badge
  • Comes here often
  • 8 comments

Hi, my first experience backing up a volume on my Ubuntu 20.04.6 LTS Linux machine is resulting in a Snapshot overflow error.  I use Veeam B&R Community Edition Build 12.1.2.172.  Here are some details:

  • Veaam R&D machine: Dell PowerEdge R7515
  • OS: Windows Server 2022 Standard.
  • CPU: AMD EPYC 7232P 8-Core Processr 3.09GHz
  • RAM: 32 GB
  • Backup Disk E: has 65.5 TB capacity with 9 TB free (This disk is the default backup repository)
  • Protected computer: Dell PowerEdge R550
  • OS: Ubuntu 20.04.1
  • CPU: Intel Xeon Gold 5317 12-Core Processor 3GHz
  • RAM: 64 GB
  • Backup Mode: Volume level backup
  • Objects: /mnt/data as the only mount point (ext4 with about 7.7 TB of content with total capacity of 65 TB, which means it is 87% free)

Multiple backup attempts were made and they all failed with the same Snapshot overflow error. 

Furthermore, I have studied the protected computer requirements referenced here and my system seems to comply.

I appreciate any feedback and suggestions.

Thank you,

-sul.


13 comments

Userlevel 7
Badge +21

Can you check the backup logs and post some of the errors?  Located here - C:\ProgramData\Veeam\Backup\Jobname

You might need to create a case for this one as this is the community not support.  We help as best we can.

Userlevel 3
Badge

Can you check the backup logs and post some of the errors?  Located here - C:\ProgramData\Veeam\Backup\Jobname

You might need to create a case for this one as this is the community not support.  We help as best we can.

Hi Chris,

thanks for your post and comment.  I have attached a log file for the backup job in question.  Happy to send more details if needed.

 

Thank you!

 

-sul.

Userlevel 7
Badge +21

I am not seeing anything in this log about a failure unfortunately.  The drive that is the repo drive on your server - are you able to free up more space on there as the free of 9TB is close to the size of data from the Linux machine 7.7TB and you always want some working room for transforms, etc.

It is hard to say what the issue is without a deeper log dive but that would be a support ticket at this point.

Maybe search the Veeam Forums for the same issue to see if there are any others that fixed it - https://forums.veeam.com

 

Userlevel 3
Badge

Hi Chris,

thank you for studying the log file and for your suggestion for allocating more working room on the repo.  The default repo is now cleaned out and I was able to reclaim 65.2 TB of space.  I just ran the job again and let’s see what happens.  If it fails with the same error, I will open a ticket.

Thanks again,

-sul.

Userlevel 7
Badge +21

Sounds like a plan and I hope the backup works this time.  Keep us posted.

Userlevel 3
Badge

Sounds like a plan and I hope the backup works this time.  Keep us posted.

So, unfortunately even after freeing up more than ample amount of disk space, the back up of the volume still crashes with a “Snapshot overflow” error.  I will open a support ticket and I intend to share my experience with support. 

thank you,

-sul.

Userlevel 7
Badge +21

Sounds like a plan and I hope the backup works this time.  Keep us posted.

So, unfortunately even after freeing up more than ample amount of disk space, the back up of the volume still crashes with a “Snapshot overflow” error.  I will open a support ticket and I intend to share my experience with support. 

thank you,

-sul.

Best approach now for this issue as they can look at the logs better.  Keep us posted on the solution.

Userlevel 3

Hello

 

12.1.2.172 Faulty version please tested, I recommend you to switch to 12.1.1.56

Userlevel 3
Badge

Hello

 

12.1.2.172 Faulty version please tested, I recommend you to switch to 12.1.1.56

Thank you for the tip.  Unfortunately, I am not familiar with how to rollback Veeam to a prior version in a way that is not too disruptive, e.g., fully uninstalling and then re-installing Veeam.  Hopefully Veeam tech support will consider taking on my open case soon. 

Thank you,

-sul.

Userlevel 7
Badge +12

Sounds like a plan and I hope the backup works this time.  Keep us posted.

So, unfortunately even after freeing up more than ample amount of disk space, the back up of the volume still crashes with a “Snapshot overflow” error.  I will open a support ticket and I intend to share my experience with support. 

thank you,

-sul.

Freeing up space on the backup repository doesn‘t solve anything related to a „snapshot overflow“ warning.

 

This message usually means, that there is not enough space in the source machine (where you have installed your Linux Agent) to temporarily store snapshot files while the backup is running. Snapshots are not stored on your backup repository disks.

 

I suggest to check with our support team if anything can be tweaked on your Linux machine to solve this situation.

 

Best,

Fabian

 

 

 

Userlevel 3
Badge

Sounds like a plan and I hope the backup works this time.  Keep us posted.

So, unfortunately even after freeing up more than ample amount of disk space, the back up of the volume still crashes with a “Snapshot overflow” error.  I will open a support ticket and I intend to share my experience with support. 

thank you,

-sul.

Freeing up space on the backup repository doesn‘t solve anything related to a „snapshot overflow“ warning.

 

This message usually means, that there is not enough space in the source machine (where you have installed your Linux Agent) to temporarily store snapshot files while the backup is running. Snapshots are not stored on your backup repository disks.

 

I suggest to check with our support team if anything can be tweaked on your Linux machine to solve this situation.

 

Best,

Fabian

 

 

 

Thank you for your post. The source machine’s volume has about 87% of space free with over 65 TB  of free capacity. Furthermore, and unfortunately, tech support just decided to close my case (#07312406 opened 6/22/2024) with no resolution.  They claim they are low on support staff--which, IMHO should never be a reason to close a case, but rather delay it, if anything.  Very disheartening.  Any way, I will likely be moving on from Veeam as a viable tool to backup my Ubuntu machine.

Thanks!

-sul.

Userlevel 7
Badge +12

Furthermore, and unfortunately, tech support just decided to close my case (#07312406 opened 6/22/2024) with no resolution.  They claim they are low on support staff--which, IMHO should never be a reason to close a case, but rather delay it, if anything.  Very disheartening.  Any way, I will likely be moving on from Veeam as a viable tool to backup my Ubuntu machine.

Thanks!

-sul.

Hi Sul

I’m sorry to hear that. It looks like you are a user of our free product offering.
Support on our free products is on a best effort level. If there is free capacity in our support team, free cases will also be processed. Please see our support policy for more information (chapter 4.3): https://www.veeam.com/support-policy.html 

You may try again with a new case.

 

Best,

Fabian

 

 

Userlevel 3
Badge

Furthermore, and unfortunately, tech support just decided to close my case (#07312406 opened 6/22/2024) with no resolution.  They claim they are low on support staff--which, IMHO should never be a reason to close a case, but rather delay it, if anything.  Very disheartening.  Any way, I will likely be moving on from Veeam as a viable tool to backup my Ubuntu machine.

Thanks!

-sul.

Hi Sul

I’m sorry to hear that. It looks like you are a user of our free product offering.
Support on our free products is on a best effort level. If there is free capacity in our support team, free cases will also be processed. Please see our support policy for more information (chapter 4.3): https://www.veeam.com/support-policy.html 

You may try again with a new case.

 

Best,

Fabian

 

 

Unfortunately, it seems impossible to get free-tier support.  It was closed twice.  I just requested a third time and let’s see.  Crossing fingers, but sadly I’m running out of time before I give up on Veeam.

Thanks!

-s.

Comment