I realize this is more vmware question than veeam... but the advice I can find requires either twice the space for temp files or 4x the time to use the converter
I used VBRfree9.5 to copy the vmdk + vmdk descriptor files form an old host to a new host. On the old host they were vRDM. On the new host they should be VMDK.
This is NOT an Operating System bootable drive. Purely file storage. No lingering manual Snapshots ever anywhere!
VBRfree9.5 copied the 2.7TB of old vRDM vmdk pointer beautifully mercifully fast! (the resultant = proper sized 1.8 TB and 1 TB vmdk's and vmdk descriptor files)
But I cannot attach the resultant files to any vm because the descriptor vmdk is 'not right'. and (FWIW) the data vmdk doesn't end in the usual "-flat.vmdk" either
Yes I found this: ( https://kb.vmware.com/s/article/1002511 ) but I only have 4 TB of storage
Can someone help me crack this nut?
Do I need to start all over and spend a whole week with vmware converter?
-
- Enthusiast
- Posts: 65
- Liked: 2 times
- Joined: Mar 19, 2016 5:39 pm
- Full Name: Hari Seldon
- Contact:
-
- Enthusiast
- Posts: 65
- Liked: 2 times
- Joined: Mar 19, 2016 5:39 pm
- Full Name: Hari Seldon
- Contact:
Re: fix vmdk descriptor
Never Mind (-:
after I had my coffee I figured it out
all good!
after I had my coffee I figured it out
all good!
-
- VP, Product Management
- Posts: 7081
- Liked: 1511 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: fix vmdk descriptor
anyway... for migration reasons you could use „quick migration“
https://helpcenter.veeam.com/docs/backu ... tml?ver=95
https://helpcenter.veeam.com/docs/backu ... tml?ver=95
Who is online
Users browsing this forum: Bing [Bot], Google [Bot], Semrush [Bot] and 18 guests