©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 » SMTP failure » 2022-09-02 15:20:59

terryfryar

Never mind, had to use a different port for STARTTLS and it worked.....so I am ok....

#2 General matters » SMTP failure » 2022-09-02 14:37:40

terryfryar
Replies: 1

Using smtp config of:

1;smtp.ionos.com:465;xsibackup@stcelectronics.com;terry.fryar@stcelectronics.com;xxxxx;yes;TLS;0

and I get this result:

Using stored SMTP server info...
Found conf/smtpsrvs file...
2022-09-02T14:29:34|  Opening port 465 for SMTPout-465 service...
SMTP probe:
TLS Module ::: The e-mail server [smtp.ionos.com] is not reachable at port [465]
Firewall rule SMTPout-465 closed.

However, if I test using an ncat connection, I get this:

ncat --ssl smtp.ionos.com 465
220 perfora.net (mreueus002) Nemesis ESMTP Service ready

which connects to the mail server using SSL/TLS with no problem?  I also verified the esxi firewall rule is enabled to allow 465.  Why is xsibackup failing to connect to the smtp server?

#3 Re: General matters » It looks like you are trying to backup to the root of an (c)ESXi DS » 2022-09-01 18:27:39

terryfryar

Ah, never mind...it appears the command line arguments have changed quite drastically with this newer version?  I am passing some older arguments, and I suspect that's why I"m getting the error.  Sorry to have bothered you!

#4 General matters » It looks like you are trying to backup to the root of an (c)ESXi DS » 2022-09-01 18:11:37

terryfryar
Replies: 2

Using Pro version 1.5.2.1 and I am getting this error when attempting to run a backup job:

It looks like you are trying to backup to the root of an (c)ESXi DS

Here is my command line:

"/scratch/XSI/XSIBackup-DC/xs
ibackup" --backup --backup-prog=vmkfstools --certify-backup=yes --backup-point=/vmfs/volumes/NAS_EX4100/vm_backup/EMTRAC-ESX3/xsibac
kup/ --date-dir=yes --backup-room=3000 --backup-type=Running --backup-how=Hot --remote-xsipath="/scratch/XSI/XSIBackup-DC" --backup-id=001

I have a NAS box mounted on NFS at /vmfw/volumes/NAS_EX4100 that I am attempting to back up to.  We have used this same structure for 4 other ESXi server without any problems using older version of XSI Pro for several years.  Why am I seeing this error on this new version??

#5 General matters » Bad blocks and failed restore? » 2018-12-14 21:12:47

terryfryar
Replies: 1

Using XSIBACKUP-PRO v11.1.9 on ESXi server v5.1.0, here is my command:

"/vmfs/volumes/Server_DS1/xsi-dir/xsibackup" \
--backup-prog=XSITools:z \
--certify-backup=yes \
--backup-point=/vmfs/volumes/NAS_EX4100/vm_backup/EMTRAC-VRH/xsibackup/$( date +%Y%m%d'000' ) \
--backup-room=2000 \
--backup-type=custom \
--backup-vms="WinServer2008x64 Copy7 AUGUSTA" \
--backup-how=Hot \
--remote-xsipath=/vmfs/volumes/Server_DS1/xsi-dir

During this backup, had a large number of bad blocks detected like this:

Please wait while the XSITools repository hash tables are checked...
---------------------------------------------------------------------------------------------------------------------------------
sh: Bad block detected: 0077d9807f9315ec8f951c28413f27b020249378
Bad block detected: 0090f5002a554bac7f10888a4f1511a1688d95f4
Bad block detected: 00a82eaf2f518357191f548b8de8086ef4d7b10a
Bad block detected: 00fdb76aba2be9e3fa2c42b367049258a2ecc12d
...


Then, when I tried to restore this VM, it stopped after a few seconds, with "sh: bad number" and would not restore the VM:

Restoring disk /vmfs/volumes/03cf4264-f23eeb43/vm_backup/EMTRAC-VRH/xsibackup/20181214000000/20181214173302/WinServer2008x64 Copy7 AUGUSTA/WinServer2008x64-flat.vmdk...
---------------------------------------------------------------------------------------------------------------------------------
sh: bad number
sh: bad number
sh: bad number
---------------------------------------------------------------------------------------------------------------------------------
Restore completed


Why is this?  The backup runs ok using "vmkfstools", but I get problems using "xsitools".  Is it the spaces in the vm name?

Thanks!

Pages: 1

Board footer