Skip to main content
Solved

Too many levels of redo logs

  • April 25, 2025
  • 7 comments
  • 1015 views
F
Hi everyone, I have again encountered a problem related to backup using veeam backup, the error message is below.

“Processing VM Linux Error: An error occurred while saving the snapshot: Too many levels of redo logs. (An error occurred while saving the snapshot: Too many levels of redo logs., An error occurred while taking a snapshot: Too many levels of redo logs.)
Failed to create VM snapshot. Error: CreateSnapshot failed, vmRef 11, timeout 1800000, snName VEEAM BACKUP TEMPORARY SNAPSHOT, snDescription Please do not delete this snapshot. It is being used by Veeam Backup., memory False, quiesce False
Error: An error occurred while saving the snapshot: Too many levels of redo logs. (An error occurred while saving the snapshot: Too many levels of redo logs., An error occurred while taking a snapshot: Too many levels of redo logs.)”

 

Detail disk

VM Disk : 1 TB

Datastore Free : 300 GB

 

I really appreciate the advice given..

 

Best answer by matheusgiovanini

The snapshot tree could have reached its limit, and Veeam cannot create new snapshots. The solution is to remove old snapshots and perform consolidation. If removal fails, cloning the VM might be necessary. Be aware that consolidation can impact performance.

A full datastore can also cause this issue. Veeam needs extra space for redo logs and temporary data. If the datastore is full, Veeam cannot create or consolidate snapshots. To fix this, free up space or move the VM to another datastore.

7 comments

Marcel.K
Forum|alt.badge.img+9
  • Marcel.K
  • Veeam Legend
  • 297 comments
  • April 25, 2025

you don't have enough space on datastore

Marcel Kačmár | VCSP Partner 2022 | VMCE 2024 | VMCA 2024 | Veeam Legend 2025 |
MarkBoothman
Forum|alt.badge.img+7
  • MarkBoothman
  • Influencer
  • 258 comments
  • April 25, 2025

How many open snapshots are there on the VM being backed up?

 

VMCA2022 | VMCE2021/5 | VUG UK Leader
Chris.Childerhose
Forum|alt.badge.img+21
  • Chris.Childerhose
  • Veeam Legend, Veeam Vanguard
  • 9587 comments
  • April 25, 2025

Check datastore capacity as mentioned. Also is this job running just once or more than once per day.  If this is being run every so often it could be an issue.  Increase the backup window and see.

Also what version of Veeam are you using?  What SQL version?  More details helps here.

Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
matheusgiovanini
Forum|alt.badge.img+6
  • matheusgiovanini
  • Veeam Legend
  • 388 comments
  • Answer
  • April 26, 2025

The snapshot tree could have reached its limit, and Veeam cannot create new snapshots. The solution is to remove old snapshots and perform consolidation. If removal fails, cloning the VM might be necessary. Be aware that consolidation can impact performance.

A full datastore can also cause this issue. Veeam needs extra space for redo logs and temporary data. If the datastore is full, Veeam cannot create or consolidate snapshots. To fix this, free up space or move the VM to another datastore.

Matheus Giovanini | Senior Backup Analyst | Veeam Legend | Blog: techdirectarchive.com
F
  • fakhri11
  • Author
  • Not a newbie anymore
  • 5 comments
  • April 28, 2025
I have a task to backup using veeam backup that runs every 3 hours using incremental and full backup every 3 days.for information about snapshots on esxi I make sure there are no snapshots that I make in exsi, all run on veeam backup.
D
Forum|alt.badge.img+3
  • ddomask
  • Comes here often
  • 192 comments
  • April 30, 2025
I have a task to backup using veeam backup that runs every 3 hours using incremental and full backup every 3 days.for information about snapshots on esxi I make sure there are no snapshots that I make in exsi, all run on veeam backup.

https://knowledge.broadcom.com/external/article/310765/determining-if-there-are-leftover-delta.html

Check the datastore. Very likely the snapshots are not registered in the snapshot manager, and you’ll need to check the datastores directly.

 

0x0D 0x0A
AndrePulia
Forum|alt.badge.img+9
  • AndrePulia
  • Veeam Vanguard
  • 603 comments
  • April 30, 2025

Sometimes the array may be experiencing  some overload and the snapshop can be affcted by the array, try take a snapshot manually and also monitor the IOPS and Latency on the array.
Is it the first time you are running this job?

I had already the situation that the snapshot manager doesn’t report the snapshot, I would suggest you to check the VM folder on the respective Datastore to see if therre are some snapshots files there.

Is this situation happen only in one VM? 

You can try to run bkp from another VM that resides on the same datastore

André Pulia - VMCA | VMCE | VMCT |Veeam Vanguard | VUG Leader Brazil | ObjectFirst ACE | HPECI | VCI | Nutanix Certified Instructor | Twitter: @andrepulia | Blog Site – https://pulia.com.br | https://www.credly.com/users/andre-pulia


Terms & ConditionsAccessibility statement