Host-based backup of VMware vSphere VMs.
Post Reply
rezafathi
Influencer
Posts: 10
Liked: never
Joined: Feb 11, 2024 5:35 pm
Full Name: Reza fathi
Contact:

cannot find layout information for disk

Post by rezafathi »

Hi
Recently, I moved a vm from vmware workstation to my esxi 8 server and it is working fine. But when i want to take backup it shows an error: cannot find layout information for disk 3000 and backup fails. Would you please help?
david.domask
Veeam Software
Posts: 2863
Liked: 657 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: cannot find layout information for disk

Post by david.domask »

Hi Reza,

Thanks for your post, however, sounds like a technical issue, so please open a Support case as is required when creating a topic. Please include logs from the affected job for Support to be able to review; use the 1st radio option, select the job backing up that virtual machine, and then complete the export.

Please note in the case as well that you had done a migration from Workstation to ESXi, as the migration process may be relevant -- you might want to check the disk sizes in the vCenter/ESXi host UI and see if the sizes are full integers or if they have fractional sizes (e.g., check that the disks all show as 10 GiB, not 10.112929292 GiB or some other value with decimals. If this is the case, expand the disk by 1 GiB so it shows as an integer, then try the backup again)

But if all looks good with the disk sizes, a Support Case is the way to go.
David Domask | Product Management: Principal Analyst
danmrls
Lurker
Posts: 1
Liked: never
Joined: Sep 10, 2024 6:55 pm
Full Name: Daniel Mireles Estrada
Contact:

Re: cannot find layout information for disk

Post by danmrls »

I am having the same problem with some vm's, did you get any response from veeam technical team or were you able to solve it?

Thanks.
Regards.
david.domask
Veeam Software
Posts: 2863
Liked: 657 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: cannot find layout information for disk

Post by david.domask »

Hi Daniel, welcome to the forums.

Regrettably the topic creator (tc) never responded back so not sure if a case was opened.

So please open a Support case as is required when creating a topic. Please include logs from the affected job for Support to be able to review; use the 1st radio option, select the job backing up that virtual machine, and then complete the export.

Also please check on the point I mentioned -- it should be a pretty fast check and sometimes is the culprit, but there can be other causes. If the non-integer size is not relevant for you, then please continue with a Support case as requested.

Thanks!
David Domask | Product Management: Principal Analyst
trackstar
Expert
Posts: 177
Liked: 4 times
Joined: Mar 11, 2013 9:47 pm
Contact:

Cannot find layout information for disk: 2000

Post by trackstar »

Good morning,

We added a new datastore this week (purchased a new SAN from Pure Storage). The same night our entire Veeam backup jobs failed with the following error below. We were advised from Pure Storage support to stop the VAAI service on each VMware host (VAAI from Pure Storage) to troubleshoot the issue. Subsequent backups were mostly successful. Most VMs that failed were the ones powered off. The few VMs that were powered on that failed, we "vmotion" (migrate) to another datastore. Then backup would be successful on those VMs. We are trying to figure what caused this issue :mrgreen:

We are planning to upgrade to the latest VMware in the coming weeks so we want to make sure we have stable backup jobs.

Error:
Cannot find layout information for disk: 2000 (some with disk 2001)

Environment:
vCenter 7.0.3.01700
Veeam 12.3.2.3617
david.domask
Veeam Software
Posts: 2863
Liked: 657 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: cannot find layout information for disk

Post by david.domask »

Hi trackstar,

I've moved your topic to an existing topic with similar errors; I'd ask you please quickly check the previous advice, and if it doesn't apply, please open a Support Case as advised above, as likely this will require a deeper review of the logs.

vMotion back and forth between datastores _can_ help as well, so you may want to try migrating the VMs back to the new datastore, but if that doesn't work, a Support Case is the way to go.
David Domask | Product Management: Principal Analyst
Post Reply

Who is online

Users browsing this forum: Semrush [Bot] and 12 guests