Posts by jayce

jayce · General matters

Hi,

Just to point out that this is still an issue. At least with backup to remote host.
I agree with Int, since we put a parameter to explicitly exclude it, we shouldn't be warned at execution it was excluded.

jayce · © OneDiff

Just tested with 10.0.3 and last ESXi updates and problem is still here.

<code>[root@XServe3-ESXi:/] lsof |grep ZeusSrv
35346 vmx FILE 3 ZeusSrv.nvram
35346 vmx FILE 50 /vmfs/volumes/55785226-1e682e1a-0f8c-001e52f3e01c/ZeusSrv/ZeusSrv.vmx.lck
35346 vmx FILE 51 /vmfs/volumes/55785226-1e682e1a-0f8c-001e52f3e01c/ZeusSrv/ZeusSrv.vmx
35346 vmx FILE 52 /vmfs/volumes/55785226-1e682e1a-0f8c-001e52f3e01c/ZeusSrv/ZeusSrv.vmx~
35346 vmx FILE 53 /vmfs/volumes/55785226-1e682e1a-0f8c-001e52f3e01c/ZeusSrv/vmware.log
35346 vmx FILE 77 /vmfs/volumes/55785226-1e682e1a-0f8c-001e52f3e01c/ZeusSrv/ZeusSrv-000002-delta.vmdk
35346 vmx FILE 82 /vmfs/volumes/55785226-1e682e1a-0f8c-001e52f3e01c/ZeusSrv/ZeusSrv-flat.vmdk
35346 vmx FILE 83 /vmfs/devices/deltadisks/5f9bead-ZeusSrv-000002-delta.vmdk
[root@XServe3-ESXi:/] esxcli vm process list
ZeusSrv
World ID: 35351
Process ID: 0
VMX Cartel ID: 35346
UUID: 56 4d 66 f3 34 97 8a 64-d5 22 9f c1 89 bc 57 bb
Display Name: ZeusSrv
Config File: /vmfs/volumes/55785226-1e682e1a-0f8c-001e52f3e01c/ZeusSrv/ZeusSrv.vmx
</code>

jayce · © OneDiff

sistemi wrote:

So the problem has moved to the NFS datastore created linking the NAS RAID volume, don't know if could be the NAS hardware, firmware, or something else, but i thing nothing related to XSIBackup itself.

My onediff backups are not related to any NFS datastore , so in my case it's not linked to any of that.

jayce · © OneDiff

admin wrote:

Maybe some other process is holding the .vmdk file, running
lsof /path/to/your-flat.vmdk
Would offer information about the process accessing the file.
We are trying to replicate this issue, but will remove that check, or at least offer an argument to deactivate it if we can't find a permanent solution valid for all ESXi builds.
That 50M check is mainly useful with Linux disks, which will host the superblock in the first sectors. That check allows to know if the superblock has changed, and thus the contents of the disk. A positive check does not ensure disks are exact mirrors, but combined with the CID check offers a more than reasonable insight.

Sorry for the delay, i had some other urgent issues to manage... Here are the results of the lsof :

<code>[root@XServe3-ESXi:~] lsof |grep ZeusSrv-flat
281135 vmx FILE 82 /vmfs/volumes/55785226-1e682e1a-0f8c-001e52f3e01c/ZeusSrv/ZeusSrv-flat.vmdk

[root@XServe3-ESXi:~] esxcli vm process list
ZeusSrv
World ID: 281136
Process ID: 0
VMX Cartel ID: 281135
UUID: 56 4d 66 f3 34 97 8a 64-d5 22 9f c1 89 bc 57 bb
Display Name: ZeusSrv
Config File: /vmfs/volumes/55785226-1e682e1a-0f8c-001e52f3e01c/ZeusSrv/ZeusSrv.vmx

[root@XServe3-ESXi:~] grep vmdk /vmfs/volumes/XServe3-500SSD-1/ZeusSrv/ZeusSrv.vmx
scsi0:0.fileName = "ZeusSrv-000002.vmdk"
</code>

jayce · © OneDiff

So, i identified why it worked on some and not on others.

If the VM is not in use, dd will work fine with the bs=50M parameter.
If the VM is in use, dd will throw the error, even if there is a snapshot and a delta file that should allow the use of dd.

My ESXi version is 6.0.0 Update 3 (Build 5572656).

jayce · © OneDiff

You're right about the 500M, i juste wanted to try to have at least the full GPT partition to test if it was the issue.
I will do more tests today and give you details about builds. What annoys me is that on my 3 server i am supposed to have the same build number of ESXi and on 1 of them dd is working well.

Also this is not the M issue, i thought about that and tried even a simple bs=50 without more success.

jayce · © OneDiff

The first backup doesn't do the 50M test.
The second backup does it and may throw the error if dd is acting weird (or if the VM has empty block at beginning).
When throwing the error it remove the vmx file that cause the reset of the onediff backup.
So the 3rd backup doesn't do the 50M test because it does nearly a full backup like the first one.
4th backup will raise the error, etc.

jayce · © OneDiff

Hmmm... I checked on another server and i don't have this issue on the other server... They both are on same ESXI version...

jayce · © OneDiff

Ok, so it looks like dd isn't working as expected :

[root@XServe3-ESXi:/xserve3/xsibackup] dd if="/vmfs/volumes/XServe3-500SSD-1/ZeusSrv/ZeusSrv-flat.vmdk" conv=notrunc  count=1 seek=0
???
   ????????U?1+0 records in
1+0 records out
[root@XServe3-ESXi:/xserve3/xsibackup] dd if="/vmfs/volumes/XServe3-500SSD-1/ZeusSrv/ZeusSrv-flat.vmdk" conv=notrunc count=1 seek=0 bs=50M
dd: /vmfs/volumes/XServe3-500SSD-1/ZeusSrv/ZeusSrv-flat.vmdk: Function not implemented
[root@XServe3-ESXi:/xserve3/xsibackup] dd if="/vmfs/volumes/XServe3-500SSD-1/ZeusSrv/ZeusSrv-flat.vmdk" conv=notrunc count=1 seek=0 bs=5000
dd: /vmfs/volumes/XServe3-500SSD-1/ZeusSrv/ZeusSrv-flat.vmdk: Invalid argument

Using bs argument in dd just make it go boooo.

jayce · © OneDiff

Ok, there must be another issue...
I tried to change the 50M test to 500M test. I wanted to circumvent this error waiting for next version of xsibackup...
So i changed the 50M by 500M in onediff script and tried...

And you know what ? I still have the error.... Checking further to see what really happens...

jayce · © OneDiff

I have the exact same problem, but my OS is not *that* old... (Windows 2008 Server R2)

But i have an idea why first 50M blocks are empty...
Partitions Screenshot...

The first 300Mo on the disk are for the GPT/EFI partition...

jayce · General matters

It was always slow to display help from xsibackup by using --help parameter, but the greater the versions are, the longer the time to display help is.

With 10.0.1, each time i launch xsibackup --help, it takes between 60 and 70 seconds to display.

Looking quickly at the code, i can't understand why it's been so slow...

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

#1 Re: General matters » Mail report gives warning for excluded disks » 2020-08-18 13:29:54

#2 Re: © OneDiff » error: first 50M mistmatch » 2017-09-25 11:34:19

#3 Re: © OneDiff » error: first 50M mistmatch » 2017-09-25 08:31:53

#4 Re: © OneDiff » error: first 50M mistmatch » 2017-09-25 08:07:02

#5 Re: © OneDiff » error: first 50M mistmatch » 2017-09-05 09:16:18

#6 Re: © OneDiff » error: first 50M mistmatch » 2017-09-05 06:46:43

#7 Re: © OneDiff » error: first 50M mistmatch » 2017-09-01 10:32:28

#8 Re: © OneDiff » error: first 50M mistmatch » 2017-09-01 06:43:58

#9 Re: © OneDiff » error: first 50M mistmatch » 2017-08-31 15:45:53

#10 Re: © OneDiff » error: first 50M mistmatch » 2017-08-31 13:54:16

#11 Re: © OneDiff » error: first 50M mistmatch » 2017-08-31 09:44:45

#12 General matters » Very long to prepare help... » 2017-08-24 09:45:12

Board footer