Has anyone run into this error: "Number of Pages in meta vector exceeds limit (520000) or vector is corrupted. Failed to download disk."
Couldn't find any documentation directly linked to that "number of pages exceeds limit error". Opened a case with Veeam, case# 02257247, just thought I would check here as well.
This job only has one VM in it, and that VM has about 17TB of data on it. Really hate to start all over with a new backup chain if I don't have to.
Thanks for looking
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Jul 25, 2017 11:03 am
- Contact:
-
- Product Manager
- Posts: 20400
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: job failing, meta vector exceeds limit (520000)
Cannot recall anything similar either. So, kindly, keep working with our support team and update the thread, once the resolution is found.
-
- Influencer
- Posts: 19
- Liked: 3 times
- Joined: Jan 11, 2019 7:00 pm
- Full Name: neil pedrosa
- Contact:
Re: job failing, meta vector exceeds limit (520000)
Hello. Hate to bring up a old thread but were you able to resolve this? Im also getting this error.
-
- Chief Product Officer
- Posts: 31804
- Liked: 7298 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: job failing, meta vector exceeds limit (520000)
Hello!
In the original case, the root cause was backup file size being too large for the selected block size.
Try changing Storage Optimization settings to Local, and keep in mind you need to do an Active Full backup for the new setting to take effect.
Thanks!
In the original case, the root cause was backup file size being too large for the selected block size.
Try changing Storage Optimization settings to Local, and keep in mind you need to do an Active Full backup for the new setting to take effect.
Thanks!
Who is online
Users browsing this forum: Jordi.B and 73 guests