Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

Hello,

I have seen a topic where the issue was the same as mine but i still have the problem with the last version of xsibackup-pro-10.1.4

The first onediff copy has taken a LOT of time but the email and the end of the initial copy has informed me that everything worked perfectly.
Since then, each differential backup, using exactly the same options, fails with this error: ERROR DIFQMSH3 error: first 500M mistmatch

Each of my VMs has this error ( linux and windows )

My source is an ESXi v6.5, my target is an ESXi v6.0.

I read in your blog that you advise us to use same version on each side, which is not possible to me due of the complexity of my local infrastructure ( storage compatibility constraints ), do you think this could be the source of my problems?

Please find below a part of the informations i have when i launch the task, the part where the errors are.

Removing hot snapshot & merging data
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[Debian_desktop] info: OneDiff backup differential data (100) merged with base data
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[Debian_desktop] info: the backup mirror VM [Debian_desktop_XSIBAK] Id (vim.fault.AlreadyExists) {
   faultCause = (vmodl.MethodFault) null,
   name = "17",
   msg = "The specified key, name, or identifier '17' already exists."
} has been created
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
./xsibackup: eval: line 1: syntax error: unexpected "("
[Debian_desktop] info: diff mirror VM reloaded
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[Debian_desktop] info: deleting snapshot at [Debian_desktop_XSIBAK] Id (vim.fault.AlreadyExists) {
   faultCause = (vmodl.MethodFault) null,
   name = "17",
   msg = "The specified key, name, or identifier '17' already exists."
}...
./xsibackup: eval: line 1: syntax error: unexpected "("
[Debian_desktop] error DIFDELAL: error deleting all snapshots VM [Debian_desktop_XSIBAK] Id (vim.fault.AlreadyExists) {
   faultCause = (vmodl.MethodFault) null,
   name = "17",
   msg = "The specified key, name, or identifier '17' already exists."
}, details:
./xsibackup: eval: line 5: specified: not found

[Debian_desktop] error DIFQMSH3: first 500M mistmatch...

Thank you in advance for your help,
Regards

Alex

Hello,
Case 1: I am using your free xsibackup solution v6.0.7 on an ESX v6.0 to an ESX v6.0 for a year and i am very satisfied of it.
Case 2: Now i have to backup a second ESX v6.5 with free xsibackup v9.1.9 to an ESX v6.0 but i have an issue.

First, when the target is not local, man page tells me xsibackup uses rsync, while if i do not precise in the command "--backup-prog:rsync" it uses vmkfstools in case 2.
I don't know what am i doing wrong because in case 1, i do not use the --backup-prog option and i uses rsync to my remote backup esx site.

Second, when i use "--backup-prog:rsync", in the mail i receive at the end of the job, i can see "(no compression") whereas in case 1 it is not present.

The errors i have are no left space on device but i have already dedicated 500Go for only less than 300Go of VMS to backup ( according to the size your mail mentionned ).

I guess the issue is linked to the " no compression ".

I have read many many post of your blog and i do not find the solution to my problem, when i run my command with "--test-mode=true" option, evrything is fine so i can guess there is no problem with my configuration.

I hope i gave you enough details, thank you very much in advance,
Best