Forum ©XSIBackup: ©VMWare ©ESXi Backup Software
MenuYou are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: General matters » error: first 50M mistmatch » 2017-10-25 15:34:01
Yes, it could be related to the VMWare issue that you pointed out. Remove the 500M check with the options flag --options=no-500M-check and see if this helps the problem. Nevertheless, the fact that the resulting VM is not an exact copy of the original one when quiescing, is something to be concerned about. I guess VMWare should solve this issue.
I fully agree. But Vmware do state in this article that this is by design and by that I understand the presence of this partition should not be of any concern. Are you saying that the disks are not identical or could it be an error that happens within the test itself? Could the disks be compared in any other ways?
We are working on this issue. We will offer a solution or workaround in short.
Highly appreciated. Let me know if you need any help testing or debugging. I'll assist with as much as I can.
#2 Re: General matters » error: first 50M mistmatch » 2017-10-25 15:24:00
sistemi wrote:ulfthomas wrote:Long story short:
• I converted the disk to GPT (I can revive the link if needed)
...
I'm interested at the link, can you provide it?
You have a link to a free tool in our Most Common Issues page here: https://33hops.com/xsibackup-most-common-issues.html
That is indeed the link I was using (I'm sorry but I forgot). 
There is a couple of typos in that article:
gptgen.exe -w \.physicaldrive0
bcdboot c:windows /s s: /f UEFI
Needs to be changed to:
gptgen.exe -w \\.\\physicaldrive0
bcdboot c:\windows /s s: /f UEFI
Else it will fail.
#3 Re: General matters » error: first 50M mistmatch » 2017-10-24 18:03:56
A couple of more tests:
- Cleaned out all the snaphosts and folders
- Initiated the first Onediff backup with additional switch --backup-how=warm: Backup successful
- Initiated the second Onediff backup with the same switch: Backup successful
- Initiated the third Onediff backup removing warm switch but adding --snapshot=dontquiesce: Backup successful
- Initiated the forth Onediff backup removing both warm and snapshot switch: failed
Wouldn't this indicate that it could be related to the quiescing of the VM?
#4 Re: General matters » error: first 50M mistmatch » 2017-10-24 17:20:36
Did another test:
- Cleaned out all the snapshots and folders
- Shutdown VM
- Started Onediff backup with --backup-type=warm
- Started the second Onediff backup with the VM still off and that passed the comparisson step
- Restarted the VM
- Started another Onediff backup and now it failed the comparisson step
#5 Re: General matters » error: first 50M mistmatch » 2017-10-24 17:01:10
It shouldn't, as the 500M check is performed once all snapshots are removed from the target VM and the ghost partition is created during the snapshot process. Can you confirm if the ghost partition is persistent after removing the snapshot?, check both the source and target VMs.
Both the VM and its snapshot contains the following partitions:
Partition 1 System 100MB
Partition 4 Unknwon 256KB
Partition 2 Reserved 127MB
Partition 3 Primary 39GB
This is verified after taking the first Onediff backup (with all snapshots and folders empty) and with the VM in an offline state.
#6 Re: General matters » error: first 50M mistmatch » 2017-10-24 16:11:59
Could it be related to this?
#7 Re: General matters » error: first 50M mistmatch » 2017-10-24 15:08:23
Hi.
Just redid the test with your latest version and I am sorry to say the results are the same:
[nonet01] info: comparing first 500M of [nonet01-flat.vmdk]...
[nonet01] error DIFQMSH3: first 500M mistmatch...I am also seeing this in the Vsphere client when selecting the snapshot: (Also noticed this before trying your latest version)
Configuration issues
Virtual machine disks consolidation is needed
#8 Re: General matters » error: first 50M mistmatch » 2017-10-24 14:58:21
That is good news indeed. I will download the updated version at once and report back. Thank you.
I do have a follow-up question to something I mentioned discovering: After cleaning out my snapshot folder and removing all snapshots xsi still complains that it cannot find the .vmxf and .nvram-files for one of the VMs:
[Sophos] info: created dir to host VM backup
[Sophos] info: VMX file copied succesfully
[Sophos] info: VMSD file copied succesfully
[Sophos] info: VMXF file copied succesfully.
[Sophos] info: NVRAM file copied succesfully.[exch02] info: created dir to host VM backup
[exch02] info: VMX file copied succesfully
[exch02] info: VMSD file copied succesfully
[exch02] info: VMXF file copied succesfully.
[exch02] info: NVRAM file copied succesfully.No .vmxf file found for nonet01 (32)
No .nvram file found for nonet01 (32)
[nonet01] info: created dir to host VM backup
[nonet01] info: VMX file copied succesfully
[nonet01] info: VMSD file copied succesfully#9 Re: General matters » error: first 50M mistmatch » 2017-10-24 11:06:54
Excerts from the logfile. (I was not able to post the complete log due to a 404 error)
[nonet01] info: file [nonet01-flat.vmdk]...
[nonet01] info: file size check | OK [ 48318382080 bytes | 48318382080 bytes ]
-------------------------------------------------------------------------------------------------------------------------------------------------------------
[nonet01] info: remote VMX file size 2565
System disk CIDs b0566e59|b0566e59
-------------------------------------------------------------------------------------------------------------------------------------------------------------
OneDiff
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Mirror VM exists and the system disks CID are the same, starting OneDiff...
[nonet01] info: length of .vmx file before OneDiff phase is 2564
-------------------------------------------------------------------------------------------------------------------------------------------------------------
[nonet01] info: Updating CID at 192.168.1.11:22:/vmfs/volumes/RAIDBackup/snapshot/nonet01/nonet01.vmdk
[nonet01] info: finished OneDiff backup, CID updated
-------------------------------------------------------------------------------------------------------------------------------------------------------------
[nonet01] info: performing quick check...
-------------------------------------------------------------------------------------------------------------------------------------------------------------
[nonet01] info: file [nonet01-flat.vmdk]...
[nonet01] info: file size check | OK [ 48318382080B | 48318382080B ]
-------------------------------------------------------------------------------------------------------------------------------------------------------------
[nonet01] info: comparing first 50M of [nonet01-flat.vmdk]...
[nonet01] error DIFQMSH3: first 50M mistmatch...
-------------------------------------------------------------------------------------------------------------------------------------------------------------#10 General matters » error: first 50M mistmatch » 2017-10-24 11:04:57
- ulfthomas
- Replies: 19
Hi.
I’ve tested your script earlier and just recently I bought the PRO version because I find it a very cost-effective and easy way to back up my VMs. Kudos on a great product.
Now, however I’m having a problem but let me just briefly list my environment:
• HP Proliant running ESXi 6, update 3
• 4 VMs (1 Windows Server 2008 R2 Core, 1 Windows Server 2008 R2 and two linux-flavoured servers)
I set up xsi and onedif and everything went smoothly. All was backed up and no problems were seen.
Looking through the logs I did notice the warning about quiescing being disabled due to Windows on MBR partitions and needless to say - I went about solving that. 
Long story short:
• I converted the disk to GPT (I can revive the link if needed)
• Deleted the original VM from inventory
• Recreated VM with UEFI and hardware level 11
• Connected VM to converted disk
• Booted the VM a couple of times
• Everything came up smoothly (YAY!)
It is my AD-controller so I was very pleased when it all came back. I then proceeded to delete the XSIBAK snapshot (and clean out the target snapshot-folder for good meassure) before I manually started my xsi-job. And again - it worked like a carm. It did complain about not finding the .nvram and .nvxm file but looking in the folder they were both there and I have not followed up on this and I am unsure if this is related to my problem.
The problem arrises when I re-run the xsi-job the second time and it only presents itself when backing up the converted disk VM:
• It starts
• Detects the VM
• Quiesces the VM succsessfully
• Compares sizes and CIDs which checks out
• Then it backs up the disks
• When it does the final comparisson it fails with: "error DIFQMSH3: first 50M mistmatch..."
It then cleans up, removes the .xmx to initialize a full backup the next time and then kills itself.
I have attached the log from the second run and hopefully you can help me shed some light on this issue.
Appreciate your answer.
Best regards,
Ulf Thomas
Pages: 1