Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

mfwiniberg

Member

Registered: 2020-01-09

Posts: 1

11.2.16 shows error but VMs appear OK

Hi

I've just upgraded to Pro 11.2.16. I am backing up using XSIDiff via TCPIP from one host to an identical machine on the network.
The upgrade has removed all the hundreds of "rekeyed" messages I used to get (as illustrated below):

"Last error raised for the above VM:
ERROR CLXSIDF1, details: [CALEXCH16] error: XSIDiff error, details: rekeyed outbound cipher rekeyed inbound cipher rekeyed outbound ..."

But I am still seeing this at the end of the email report (this text also appears individually under each VM report, which is therefore marked "KO!":

"• [ Thu Jan 9 00:00:54 UTC 2020 ] ERROR (CLXSIDF1), details [CALDCB] error: XSIDiff error, details:
• [ Thu Jan 9 00:14:05 UTC 2020 ] ERROR (CLXSIDF1), details [SAGELink] error: XSIDiff error, details:
• [ Thu Jan 9 00:27:14 UTC 2020 ] ERROR (CLXSIDF1), details [CALDC14] error: XSIDiff error, details:
• [ Thu Jan 9 03:45:30 UTC 2020 ] ERROR (CLXSIDF1), details [CALDC14] error: XSIDiff error, details:
• [ Thu Jan 9 04:46:01 UTC 2020 ] ERROR (CLXSIDF1), details [CALSQL14] error: XSIDiff error, details:
• [ Wed Jan 8 23:48:57 UTC 2020 ] ERROR (CLXSIDF1), details [CALEXCH16] error: XSIDiff error, details:
• [ Wed Jan 8 23:51:31 UTC 2020 ] ERROR (CLXSIDF1), details [3cx] error: XSIDiff error, details:
• [ Wed Jan 8 23:55:33 UTC 2020 ] ERROR (CLXSIDF1), details [CAL19SQL] error: XSIDiff error, details: "

All the VMs appear, as before, to be backing up OK and I can start them etc with no problem.

On the destination host there is a *.vmsn file left behind after each backup, so these tend to build up over time. Deleting these doesn't seem to cause any problems. Is this expected behaviour?

Is there actually any problem here?

Thanks

Mike

admin

Administrator

Registered: 2017-04-21

Posts: 2,057

Re: 11.2.16 shows error but VMs appear OK

Edit the file src/functions with vi and replace line 11

echo "$O"

by

echo -n "$O"

That should not affect error collection, but given the fact that different ESXi versions incorporate a wide variety of busybox components with a wide range of bahaviours, that "-n" will not hurt.

Given the fact that the "details" variable is not printed nor added to the ERR file unless it contains some value, it looks like something is not working as expected in your host. Reboot when you have the chance and retry. We will ad some additional code to double check that the variable printed in "details" is not empty.