Posts by Dennis

Dennis · General matters

solved it myself. Got rid of the '^M' characters in conf/root-crontab. :-)

Dennis · General matters

Dear Forum,

Cannot get cron to work with newest free version 11.0.1. Although the jobs run fine out their own, and the syslog.log shows launches at the correct times, cron works, still nothing happens: no mail and no log entries. Would anybody know how to resolve this issue? This is just too curious...what is wrong here? Are we missing something? Thanks so much!

Dennis

Syslog shows crond doing its job:

cat /var/log/syslog.log
...
2019-02-19T01:00:01Z crond[2098971]: crond: USER root pid 2826075 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001"
...
2019-02-19T02:00:01Z crond[2098971]: crond: USER root pid 2826530 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/002"
...
2019-02-20T01:00:01Z crond[2841383]: crond: USER root pid 2846127 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001"

Running from command line works very well:

/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001
/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/002

Xsibackup logfile shows no entries:

cat /vmfs/volumes/gc0_ssd1/scripts/xsi-dir/var/logs/xsibackup.log
...
<nothing for those cron times only when running manually>
...

Main log directory /var/log also shows nothing:

[:/var/log] grep -i -I -r -n -s /001 *
syslog.log:2566:2019-02-18T01:00:01Z crond[2098971]: crond: USER root pid 2769648 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001"
syslog.log:3651:2019-02-19T01:00:01Z crond[2098971]: crond: USER root pid 2826075 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001"
syslog.log:4761:2019-02-20T01:00:01Z crond[2841383]: crond: USER root pid 2846127 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001"
[:/var/log] grep -i -I -r -n -s 2826075 *
syslog.log:3651:2019-02-19T01:00:01Z crond[2098971]: crond: USER root pid 2826075 cmd "/vmfs/volumes/gc0_ssd1/scripts/xsi-dir/jobs/001"

@REF: https://33hops.com/xsibackup-cron-troubleshooting.html

The Troubleshooting Step 2 works: Question: could it be that this should be done after --update-cron?

[root@gc0:/var/log] for p in $(ps -c | grep -v grep | grep 'busybox crond' | awk '{print $1}'); \
> do kill -9 $p;done; \
> /usr/lib/vmware/busybox/bin/busybox crond; \
> ps -c | grep -v grep | grep 'busybox crond'
2840345  2840345  busybox                         /usr/lib/vmware/busybox/bin/busybox crond

The Troubleshooting Step 3 works:

[root@gc0:/var/spool/cron/crontabs] cat root
#min hour day mon dow command
*/1  *    *   *   *   echo "$(date)" >> /tmp/my-cron-test.txt
1    1    *   *   *   /sbin/tmpwatch.py
1    *    *   *   *   /sbin/auto-backup.sh
0    *    *   *   *   /usr/lib/vmware/vmksummary/log-heartbeat.py
*/5  *    *   *   *   /bin/hostd-probe.sh ++group=host/vim/vmvisor/hostd-probe/stats/sh
00   1    *   *   *   localcli storage core device purge
 # Added by XSIBackupmes/datastore1/xsi-dir/jobs/001"
 # Added by XSIBackupmes/datastore1/xsi-dir/jobs/002"

*** ^NOTE: Bottom 2 entries are not logical! ***

[root@gc0:/var/spool/cron/crontabs] cat /tmp/my-cron-test.txt 
Tue Feb 19 14:09:01 UTC 2019
Tue Feb 19 14:10:01 UTC 2019
Tue Feb 19 14:11:01 UTC 2019
Tue Feb 19 14:12:01 UTC 2019
Tue Feb 19 14:13:01 UTC 2019
Tue Feb 19 14:14:01 UTC 2019
Tue Feb 19 14:15:01 UTC 2019

However, in text editor, things are shown correctly:

#min hour day mon dow command
*/1  *    *   *   *   echo "$(date)" >> /tmp/my-cron-test.txt
1    1    *   *   *   /sbin/tmpwatch.py
1    *    *   *   *   /sbin/auto-backup.sh
0    *    *   *   *   /usr/lib/vmware/vmksummary/log-heartbeat.py
*/5  *    *   *   *   /bin/hostd-probe.sh ++group=host/vim/vmvisor/hostd-probe/stats/sh
00   1    *   *   *   localcli storage core device purge
0 1 * * * "/vmfs/volumes/datastore1/xsi-dir/jobs/001"^M # Added by XSIBackup
0 2 * * * "/vmfs/volumes/datastore1/xsi-dir/jobs/002"^M # Added by XSIBackup

*** ^Question: What doe "^M" Stand for? ***

We would really appreciate help from anybody! Thanks so kindly!
Dennis

Dennis · General matters

Dear 33 hops team,

Thanks for making such a great tool. Running a job from command line gives some errors: rsync and grep

/<path>/scripts/xsi-dir/jobs/002
sh: rsync: unknown operand
grep: invalid option -- '*'
BusyBox v1.22.1 (2018-07-23 19:34:44 PDT) multi-call binary.

Usage: grep [-HhnlLoqvsriwFEz] [-m N] [-A/B/C N] PATTERN/-e PATTERN.../-f FILE [FILE]...

Search for PATTERN in FILEs (or stdin)

	-H	Add 'filename:' prefix
	-h	Do not add 'filename:' prefix
	-n	Add 'line_no:' prefix
	-l	Show only names of files that match
	-L	Show only names of files that don't match
	-c	Show only count of matching lines
	-o	Show only the matching part of line
	-q	Quiet. Return 0 if PATTERN is found, 1 otherwise
	-v	Select non-matching lines
	-s	Suppress open and read errors
	-r	Recurse
	-i	Ignore case
	-w	Match whole words only
	-x	Match whole lines only
	-F	PATTERN is a literal (not regexp)
	-E	PATTERN is an extended regexp
	-z	Input is NUL terminated
	-m N	Match up to N times per file
	-A N	Print N lines of trailing context
	-B N	Print N lines of leading context
	-C N	Same as '-A N -B N'
	-e PTRN	Pattern to match
	-f FILE	Read pattern from file

grep: invalid option -- '*'
BusyBox v1.22.1 (2018-07-23 19:34:44 PDT) multi-call binary.

Usage: grep [-HhnlLoqvsriwFEz] [-m N] [-A/B/C N] PATTERN/-e PATTERN.../-f FILE [FILE]...

Search for PATTERN in FILEs (or stdin)

	-H	Add 'filename:' prefix
	-h	Do not add 'filename:' prefix
	-n	Add 'line_no:' prefix
	-l	Show only names of files that match
	-L	Show only names of files that don't match
	-c	Show only count of matching lines
	-o	Show only the matching part of line
	-q	Quiet. Return 0 if PATTERN is found, 1 otherwise
	-v	Select non-matching lines
	-s	Suppress open and read errors
	-r	Recurse
	-i	Ignore case
	-w	Match whole words only
	-x	Match whole lines only
	-F	PATTERN is a literal (not regexp)
	-E	PATTERN is an extended regexp
	-z	Input is NUL terminated
	-m N	Match up to N times per file
	-A N	Print N lines of trailing context
	-B N	Print N lines of leading context
	-C N	Same as '-A N -B N'
	-e PTRN	Pattern to match
	-f FILE	Read pattern from file

Killed

[root] cat <path>/scripts/xsi-dir/jobs/002
# This is a backup job file example. It starts with the path to your
# xsibackup file and ends with the redirection to the log file. Please
# do make sure that you keep first and last lines, changing paths to
# match your working environment.

"<path>/scripts/xsi-dir/xsibackup" \
--certify-backup=yes \
--backup-point=<path>/vm \
--backup-type=custom \
--backup-vms="example!exclude_tester.vmdk;exclude_example.vmdk;exclude_1.vmdk;exclude_2.vmdk;exclude_3.vmdk;exclude_4.vmdk;exclude_5.vmdk;exclude_6.vmdk;exclude_7.vmdk;exclude_8.vmdk,tester!tester_files.vmdk,intranet,mini-web" \
--backup-how=hot \
--use-smtp=1 \
--mail-to=name@<domain>.info \
--backup-id=002 \
--description="XSITools backup of production VMs from <path>" \
--exec=yes >> "<path>/scripts/xsi-dir/var/logs/xsibackup.log"

Thanks you,
Dennis

Dennis · General matters

Thanks for your friendly answer.

Dennis · General matters

Still waiting...

Dennis · General matters

Could you please make this make this "XSIBackup tutorial - part 3" at the top of your index? Thanks so kindly. D/

Dennis · General matters

Yes; we understand this. And yes, we do not want to backup independent disks. However, we:

[1] We -do- want your produced backup vmx's also to access these “independent” service vmdk disks and -not !!! - be excluded from the vmx file!! Is this possible?

[2] Don't have this error message at the top. E.g. perform calculation first.

Dennis · General matters

Yes; thanks; understood that now from the hidden "things have changed page". However, in that example, I don't get:

--on-success="backupId->005" \
--on-error="backupId->005" \

Maybe it could help to put two more simple example jobs 001 and 002 on that page.

Dennis · General matters

Yes; of course, we had read the man page; however, we cannot find an appropriate solution.

To repeat myself, it is not an issue of all / running / custom!

These VMs reside on multiple datastores and we wish to backup from each one uniquely to another datastore. To simplifly: storeA to storeC and storeB to storeD. --- without having to specify the names or expressions since that is too tedious and too much work to change all the time.

Dennis · General matters

We get error message:

Needed room: 9619 Gb.
Sparse size: 9630 Gb.
Available room: 4412 Gb.

All VMs together are only 542G. We suspect that this error is due to service vmdks residing at other datastores.

[tesla] info: boot partition is EFI
---------------------------------------------------------------------------------------------------
[tesla] Info: attempting to free 4337664 mb at [ /vmfs/volumes/gc0_hdd3 ]
---------------------------------------------------------------------------------------------------
Removing snapshots, please wait...
---------------------------------------------------------------------------------------------------
Syncronizing config files
---------------------------------------------------------------------------------------------------
At least one independent disk was detected
Tip: perform a [cold] backup to copy independent disks
---------------------------------------------------------------------------------------------------
This independent disks will be excluded:
---------------------------------------------------------------------------------------------------
tesla.vmdk
---------------------------------------------------------------------------------------------------
[tesla] info: VMWare Tools detected, taking snapshot QUIESCED(false)...
[tesla] info: set argument --snapshot=doquiesce to quiesce your VMs
---------------------------------------------------------------------------------------------------
Backing up virtual disks...
---------------------------------------------------------------------------------------------------
sata0:0.fileName = "tesla.vmdk"
sata1:0.fileName = "/vmfs/volumes/572d1e61-cd94fa28-d1f8-0cc47a8e1078/vm-ext/tesla/tesla.vmdk"
---------------------------------------------------------------------------------------------------
Disk ["tesla.vmdk"] excluded
---------------------------------------------------------------------------------------------------
Disk ["/vmfs/volumes/572d1e61-cd94fa28-d1f8-0cc47a8e1078/vm-ext/tesla/tesla.vmdk"] excluded
---------------------------------------------------------------------------------------------------
Excluded disks removed from backup .vmx file

Excluded disks removed from backup .vmx file

Excluded disks removed from backup .vmx file
---------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------
| Backup of ESXi configuration is not available in XSIBACKUP-FREE |
| Get XSIBACKUP-PRO at https://33hops.com |
--------------------------------------------------------------------------------------------

Errors detected in backup, check logs

It is OK that these service drives are not backed up; however,
We -do- want these backups also to access these “independent” service vmdk disks and -not- be excluded from the vmx file!! Is this possible?

Thanks for any assistance in the matter,

Dennis

Dennis · General matters

We get "Errors detected in backup, check logs"

However, we cannot find log:

cat cat var/logs/xsibackup.log is empty ?!?

Dennis · General matters

E.g., need to backup VMs from datastoreA/vm/* to clonof_datastoreA/vm/* and datastoreB/vm/* to cloneof_datastoreB/vm/*
Each datastore has a varying amount of vms that we cannot always specify with "--backup-vms” since this would be very tedious to change all the time.
We tried expressions but there is no reference to any source datastore.
Do you have a solution for this?

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

#1 Re: General matters » Cron on XSIBackup 11.0.1 does not work for us. Please help. » 2019-02-21 14:59:03

#2 General matters » Cron on XSIBackup 11.0.1 does not work for us. Please help. » 2019-02-20 09:12:07

#3 General matters » Small Errors from jobs/002 » 2019-02-18 11:47:15

#4 Re: General matters » Problem: Cannot specify source datastore » 2019-02-15 15:58:22

#5 Re: General matters » Problem: Cannot specify source datastore » 2019-02-14 16:51:08

#6 Re: General matters » Where is the cron tab » 2019-02-13 08:38:44

#7 Re: General matters » Problems with "Sevice" VMDK Disks. » 2019-02-12 21:20:41

#8 Re: General matters » Where is the error log? » 2019-02-12 21:17:59

#9 Re: General matters » Problem: Cannot specify source datastore » 2019-02-12 21:15:57

#10 General matters » Problems with "Sevice" VMDK Disks. » 2019-02-12 18:03:53

#11 General matters » Where is the error log? » 2019-02-12 18:00:45

#12 General matters » Problem: Cannot specify source datastore » 2019-02-12 17:58:53

Board footer