©XSIBackup-Free: Free Backup Software for ©VMWare ©ESXi

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


You are not logged in.

#1 Re: © XSITools » XSITools fails to create backup repo » 2019-08-16 17:28:01

I am having the same issue with the missing Block. I am running on 11.2.7 and I tried to perform Hot and Warm Backup. It is still the same behaviour :-/

1 bad blocks detected
49886561f8e26ed5e2ae549897a28aaab44881bd
Block 49886561f8e26ed5e2ae549897a28aaab44881bd is missing

Any Ideas or news at this issue?

#2 Re: © XSITools » chunk hashes check always failed » 2019-08-11 07:20:30

no problem. Thanks for your answer and your support.
with --check-repo=yes it is working fine for me.

#3 Re: © XSITools » chunk hashes check always failed » 2019-08-05 12:51:01

I have this issue with "fast" and with "yes"

#4 © XSITools » chunk hashes check always failed » 2019-08-02 09:32:51

joergnestler
Replies: 4

Hi,

I am running backups from 1 host to another host and vice versa within the same network.

I use XSIBACKUP 11.2.7 on VMware ESXi 6.0.0 build-3620759
and XSIBACKUP 11.2.3 on VMware ESXi 6.7.0 build-8169922

The behavior is identical in both directions and so I think it is not linked to a Version of ESX or XSIBACKUP.
For me it seems a general issue, but I dont know how to solve.

I tried to use the certify option in my job and it always return the same kind of error.
I tested: yes and fast - it is still the same.

Sample:
-------------------------------------------------
2019-08-01T17:55:18|  Please wait while the remote (c)XSITools hash tables are fast checked...
--------------------------------------------------------------------------------                                             -------------------------------------------------
2019-08-01T17:55:56|  [SRV-PK] error: chunk hashes fast check failed, detail:
--------------------------------------------------------------------------------         



It returns the check failed, but I dont know the reason.
There are no details.
So I dont know is it maybe a timeout issue or whatever.

Restoring of these backups are always working and the machines seems working properly.


Any ideas?

Thanks in advance

#5 Re: General matters » --on-error / --on-success » 2019-04-25 07:59:58

thanks a lot for your great support - works fine

#6 Re: General matters » --on-error / --on-success » 2019-04-24 09:14:05

so far so good - but how can I solve my problem?

name of the jobfile to run on success is "2"

and in the former Job I settet up:

--on-success="backupId->002" \

What I did wrong?
I have to rename the Jobfile from 2 into 002 ?

Thanks for you answer in advance

#7 General matters » --on-error / --on-success » 2019-04-24 07:26:39

joergnestler
Replies: 4

I have issues to setup my Job. In the GUI I never succeeded to set the option for "on success" thats why I edited the Job File manually. I also looked for this topic in other posts here, but all the samples I found doesnt work for me. Is there an FAQ or a sample for a JOB-File where I can see how to write the Arguments for "on success".

I tried in my File:
--on-success="backupId->002" \

and

--on-success=""backupId->002"" \

In the Log I always get the result:

"Backup job 002 is not present in the local /jobs directory"

In the jobs subfolder the ID (Name of the Jobfile) for the Job is "2".
Must I setup my Jobfiles also with 3 digits numeric?

Thanks for your help

#9 Re: General matters » (c)XSITools over IP to a remote ESXi server return broken pipe » 2019-04-12 07:16:14

both ESX Machines are on VMware ESXi 6.7.0 build-8169922
on both ESX Machines XSIBACKUP-PRO 11.2.3 is running


here the part of the Log include the broken Pipe error:

---------------------------------------------------------------------------------------------------------------------------------
sending incremental file list
FileSRV.vmdk

            551 100%    0.00kB/s    0:00:00 
            551 100%    0.00kB/s    0:00:00 (xfr#1, to-chk=0/1)

sent 641 bytes  received 35 bytes  450.67 bytes/sec
total size is 551  speedup is 0.82
---------------------------------------------------------------------------------------------------------------------------------
2019-04-01T12:31:19|  Info: transfering file | /vmfs/volumes/HDD_R5/MARX-FILESRV/FileSRV-flat.vmdk
---------------------------------------------------------------------------------------------------------------------------------
[32m(c) XSIDiff 1.1.1.4 licensed:
[0mWriting to file /vmfs/volumes/Datastore2/Marx/FILESRV/20190401123006/FileSRV/FileSRV-flat.vmdk
---------------------------------------------------------------------------------------------------------------------------------
2019-04-02T07:52:37|  [FileSRV] CLXSIDF1 error: file transfer error: packet_write_wait: Connection to XX.XXX.XXX.XXX port 5006: Broken pipe
---------------------------------------------------------------------------------------------------------------------------------



In The Email after I get:

Done hot backup (id: 2) using xsidiff (no compression)
Backing up to folder XX.XXX.XXX.XXX:5006:/vmfs/volumes/Datastore2/Marx/WWS/20190405123006
Mirroring following VMs to XX.XXX.XXX.XXX:5006:/vmfs/volumes/Datastore2/Marx/WWS...
(Id)VM Name    State    Size (Gb)    Stop    Copy    Start    Time (min:sec)    Speed (mb/s)
(5) MARX-WWS    ON    160.00/ 160.00    NO (hot backup)    KO!    -    6287:08    0/ 0
Last error raised for the above VM:
ERROR CLXSIDF1, details: [MARX-WWS] error: XSIDiff error, details: packet_write_wait: Connection to XX.XXX.XXX.XXX port 5006: Broken pipe
Complete backup elapsed time: 6287 min
The ESXi configuration was saved to XX.XXX.XXX.XXX:5006:/vmfs/volumes/Datastore2/Marx/WWS
• [ Tue Apr 9 21:06:24 UTC 2019 ] ERROR (CLXSIDF1), details [MARX-WWS] error: XSIDiff error, details: packet_write_wait: Connection to XX.XXX.XXX.XXX port 5006: Broken pipe

#11 Re: General matters » (c)XSITools over IP to a remote ESXi server return broken pipe » 2019-04-11 10:57:15

yes the server is reachable and I can confirm the backup is running close to the end. It means I backup 2 vmdk disks and I am able to rund the virtual machines too after the backup on the backup-location. the broken-pipe error seems to appear exactly at the moment when the job is finished. I runned the job very often in the past and it returns always this error at the end.

#12 General matters » (c)XSITools over IP to a remote ESXi server return broken pipe » 2019-04-10 08:14:23

joergnestler
Replies: 8

In the BugTracker it was announced this issue will be solved in 11.2.3

I am running on 11.2.3 and have still this issue.
It means the Job is running until the end.
the Size of the backuped vmdk Files also seems ok, but I got always this error in one of my backup Jobs:

CLXSIDF1 error: file transfer error: packet_write_wait: Connection to 87.139.234.106 port 5006: Broken pipe



I would like to know was the detected issue solved in the Version 11.2.3 or is it still pending.

Thanks for your answers in advance

Board footer