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

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


Forum menu Menu

You are not logged in.

Pages: 1

#1 Re: General matters » FIPS mode initialized » 2020-01-16 01:59:52

snackish

Thank you. That was it. I added the following on the ESXi host:

[root@Host:] cat ~/.ssh/config
Host *
        LogLevel QUIET

That fixed the issue and the backups now seem to be running. I did not want to use NFS, as in my previous forum post (2019-12-12) I was having issues with using NFS off our zfs based NAS. I am now trying iSCSI off that NAS to a linux machine, therefore I did not want to add the extra protocol in between.

Thanks again.

#2 General matters » FIPS mode initialized » 2020-01-15 04:46:45

snackish
Replies: 3

I am getting this error with the datacenter version (I tried with 1.0.1.3 and 1.1.0.3). I see you mention that you fixed it in the Pro version(https://33hops.com/xsibackup-most-common-issues.html). Please let me know if this is a known issue with the datacenter version too.

./xsibackup --backup "VMs(RUNNING)" root@X.X.X.X:22:/backups --compression=yes --rotate=30 --html-template=003 --mail-to=admins@domain.com --use-smtp=3 --subject="running on HOST"
-----------------------------------------------------------------------------------------------------------
|---------------------------------------------------------------------------------|
||-------------------------------------------------------------------------------||
|||   (c)XSIBackup-Datacenter 1.1.0.3: Backup & Replication Software             |||
|||   (c)33HOPS, Sistemas de Informacion y Redes, S.L. | All Rights Reserved    |||
||-------------------------------------------------------------------------------||
|---------------------------------------------------------------------------------|
                   (c)Daniel J. Garcia Fidalgo | info@33hops.com
|---------------------------------------------------------------------------------|
System Information: ESXi, Kernel 6 Major 7 Minor 0 Patch 0
-----------------------------------------------------------------------------------------------------------
License: xxxxxxxxxxxxxxxxxxxx
-----------------------------------------------------------------------------------------------------------
SSH: FIPS mode initializedTue Jan 14 22:54:24 EST 2020
-----------------------------------------------------------------------------------------------------------
2020-01-15T04:44:00 | Error code 1581 at file xsibackup.c, line 1581
Error description: cannot access SSH server at root@X.X.X.X:22, response was: FIPS mode initializedlinux
-----------------------------------------------------------------------------------------------------------
Removed /tmp/xsi dir     OK
-----------------------------------------------------------------------------------------------------------
Unlocked backup          OK
-----------------------------------------------------------------------------------------------------------
Removed PID              OK
-----------------------------------------------------------------------------------------------------------

NOTE: with version 1.0.1.3 the line error was line 1440.

On its own ssh works using the ssh key that I copied over:

ssh -i xsibackup_id_rsa X.X.X.X
FIPS mode initialized
Linux HOST

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Jan 14 20:37:03 2020 from X.X.X.X
root@HOST:#

I confirmed no firewall, executable or version issues issues and tested with both older Debian and newer Ubuntu as remote IP machines and I am getting the same issue. I have tried with adding xsibackup to /usr/bin as well as having it in a separate directory and using --remote-path with no luck.

Please let me know if I am missing anything.

Thank you.

#3 General matters » Backup completes with errors, no mail is sent » 2019-12-12 18:01:01

snackish
Replies: 1

Job completes but no mail is sent when the below errors are reported. I have tested when running with VMs that do not cause any errors and mail does get sent, so issue is not with the mail configuration. It just seems to get to the end and decide not to send email when there are errors with the task.

We are using NFSv3 in this case, VMware server has Broadcom nics and storage is off FreeNAS system (sync=standard) with Intel nics.

Is there any way to force the mail to get sent?

With NFSv3 and FreeNAS we currently use the default sync=standard, not sure if we should try with sync=always or sync=disabled.

Thank you for any pointers.

Error logs included below:

2019-12-12T01:38:34 | Error code 456 at file dedup-in.c, line 456
Error description: can't rename temp block: /vmfs/volumes/BACKUPS/vmware/data/116790670784987052.tmp, Input/output error
--
2019-12-12T12:06:58 | Error code 1127 at file common.c, line 1127
Error description: file does not exist: /vmfs/volumes/storage/vmware/20191211164731/hostXX/hostXX.vmx.tmp.map
--
2019-12-12T12:06:58 | Error code 2416 at file xsibackup.c, line 2416
Error description: could not rename .vmx.tmp file: /vmfs/volumes/storage/vmware/20191211164731/hostXX/hostXX.vmx.tmp.map
--
2019-12-12T12:07:12 | Error code 2506 at file xsibackup.c, line 2506
Error description: some error was raised while backing up: VMs(RUNNING), error count is: 3
-----------------------------------------------------------------------------------------------------------
Removed /tmp/xsi dir     OK
-----------------------------------------------------------------------------------------------------------
Unlocked backup          OK
-----------------------------------------------------------------------------------------------------------
Removed PID              OK

Pages: 1

Board footer