©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 General Matters » Would --del-dirs do deletion before start making backup? » 2022-04-13 08:57:07

alexa
Replies: 1

Here is my backup job:

[root@localhost:~] cat /vmfs/volumes/datastore1/xsi-dir/jobs/prod
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-prog=Rsync \
--date-dir=yes \
--snapshot=doquiesce \
--backup-point={IP address removed}:22:"/vmfs/volumes/datastore2/vm-backups" \
--backup-type=Custom \
--backup-vms="firewall-pfsense,sbc-freepbx,fusionPBX,dialer,stunnel-proxy" \
--backup-how=Hot \
--del-dirs=+20d \
--use-smtp=2 \
--mail-to={email address removed} \
--backup-id=prod \
--description="Production VMs weekly backup" \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"


Question 1 - would the --del-dirs do deletion before start making a new backup job?

Question 2 - For the --del-dirs=+20d from above, what would be the last date for deletion, I want to delete just 20220318000006 from here:

[root@esxi2:~] ls -lah /vmfs/volumes/datastore2/vm-backups
drwxr-xr-x    1 root     root       72.0K Mar 18 02:28 20220318000006
drwxr-xr-x    1 root     root       72.0K Mar 25 02:28 20220325000007
drwxr-xr-x    1 root     root       72.0K Apr  1 02:29 20220401000007
drwxr-xr-x    1 root     root       72.0K Apr  8 02:29 20220408000007

Sorry, couldn't find the answers in the documentation.

Thanks.

#2 Re: General matters » XSIBackup job change - accepted automatically? » 2022-04-13 08:30:48

alexa

root-crontab is scheduled already

# cat /vmfs/volumes/datastore1/xsi-dir/conf/root-crontab
0 0 * * 5 "/vmfs/volumes/datastore1/xsi-dir/jobs/prod

and root crontab is

# cat /var/spool/cron/crontabs/root
.
.
.
0 0 * * 5 "/vmfs/volumes/datastore1/xsi-dir/jobs/prod"


so, nothing more to do i.e. I can make changes to the backup job in the /vmfs/volumes/datastore1/xsi-dir/jobs/prod and it'll be executed regularly on Thursday midnight?

Please confirm.

Thanks.

#3 General matters » XSIBackup job change - accepted automatically? » 2022-04-12 08:25:54

alexa
Replies: 3

I've changed backup job /vmfs/volumes/datastore1/xsi-dir/jobs/prod

I'm wondering do I need to do anything else to make the changed job active, restart / reload some service etc.

#4 Re: © XSITools » SHA1 chunk hashes check failed error » 2022-04-08 10:31:41

alexa

Also we got this error in the email report:

Fri Apr 1 00:01:32 UTC 2022
XSIBACKUP-PRO 11.2.10 AT HOST:
localhost.localdomain
IP v4: 188.117.105.67/ 255.255.255.248
VMware ESXi 6.5.0 build-8294253


Done hot backup (id: prod) using rsync (no compression)
Backing up to folder 188.117.105.66:22:/vmfs/volumes/datastore2/vm-backups/20220401000007
Mirroring following VMs to 188.117.105.66:22:/vmfs/volumes/datastore2/vm-backups...
(Id)VM Name    State    Size (Gb)    Stop    Copy    Start    Time (min:sec)    Speed (mb/s)
(1) firewall-pfsense    ON    10.00/ 10.00    NO (hot backup)    sha1 CERTIFIED    -    04:51    35/ 35
(2) sbc-freepbx    ON    30.00/ 30.00    NO (hot backup)    sha1 CERTIFIED    -    13:49    37/ 37
(3) fusionPBX    ON    150.00/ 150.00    NO (hot backup)    sha1 CERTIFIED    -    69:23    36/ 36
(8) dialer    ON    67.81/ 67.81    NO (hot backup)    sha1 CERTIFIED    -    41:09    28/ 28
(9) stunnel-proxy    ON    20.00/ 20.00    NO (hot backup)    KO!    -    09:49    34/ 34
Last error raised for the above VM:
ERROR CLNCERT0, details: [stunnel-proxy] error: sha1 hashes are different [stunnel-proxy-flat.vmdk], details: 0
--del-dirs | deleted folders older than 22 days:
/vmfs/volumes/datastore2/vm-backups/20220304000007
Complete backup elapsed time: 139 min
The ESXi configuration was saved to 188.117.105.66:22:/vmfs/volumes/datastore2/vm-backups
• [ Fri Apr 1 02:20:39 UTC 2022 ] ERROR (CLNCERT0), details [stunnel-proxy] error: sha1 hashes are different [stunnel-proxy-flat.vmdk], details: 0

#5 Re: © XSITools » SHA1 chunk hashes check failed error » 2022-04-08 10:30:41

alexa

now it floods our hdd, look

-rwx------    1 root     root       18.3K Mar 11 02:37 1646965165-188.117.105.67-config.tgz
-rwx------    1 root     root       18.5K Mar 18 02:37 1647569974-188.117.105.67-config.tgz
-rwx------    1 root     root       18.5K Mar 25 02:37 1648174781-188.117.105.67-config.tgz
-rwx------    1 root     root       18.3K Apr  1 02:39 1648779657-188.117.105.67-config.tgz
-rwx------    1 root     root       18.3K Apr  8 02:39 1649384469-188.117.105.67-config.tgz
drwxr-xr-x    1 root     root       72.0K Mar 18 02:28 20220318000006
drwxr-xr-x    1 root     root       72.0K Mar 25 02:28 20220325000007
drwxr-xr-x    1 root     root       72.0K Apr  1 02:29 20220401000007
drwxr-xr-x    1 root     root       72.0K Apr  8 02:29 20220408000007
[root@esxi2:/vmfs/volumes/5d404b0f-df13b95c-7836-2c44fd83e520/vm-backups] df -h ./
Filesystem   Size   Used Available Use% Mounted on
VMFS-6       1.1T 934.7G    183.1G  84% /vmfs/volumes/datastore2


so, I need fast help, please tell me how to contact support

#6 © XSITools » SHA1 chunk hashes check failed error » 2019-09-25 07:47:38

alexa
Replies: 4

I get this error: "SHA1 chunk hashes check failed error "  when doing a backup on VMware ESXi 6.5.0 with --backup-point set to another Vmware ESXi 6.5.0 via ssh and --certify-backup=yes. xsibackup-pro is installed on both machines. How to troubleshoot this problem?

Pages: 1

Board footer