You are not logged in.
Error:
-----------------------------------------------------------------------------------------------------------
2020-09-27T03:08:39 | Error code 2221 at file xsibackup.c, line 2221 | Error description: use just letters, dots, numbers, hyphens, parenthesis, spaces and underscores in path names
-----------------------------------------------------------------------------------------------------------
/scratch/XSI/XSIBackup-DC/xsibackup \
--backup \
--backup-type=Running \
"root@10.40.150.37:22:/vmfs/volumes/xsi-backup" \
--remote-path="/vmfs/volumes/datastore1/xsi-dir/xsibackup " \
--backup-how="hot " \
--mail-to="cw@ns.c " \
--subject="esxi_038 " \
>> /scratch/XSI/XSIBackup-DC/var/log/xsibackup.log 2>&1
Overall doing backups has lots of options and scenarios to cover and its tough, thanks for giving it a go, its great.
Few questions:
a.
why not follow the same format at PRO, example the "--backup-type=" and :"--backup-point"??
b.
Does DC support "--on-success=" serial backup jobs?
c.
I couldn't set rotation in DC like "--del-dirs=" from PRO
d.
Does DC copy the exec files to the remote host like PRO did? If yes, then which folder does CD try to copy the exec files too on the remote host? PRO uses ""/vmfs/volumes/datastore1/xsi-dir/xsibackup" \"
e.
What is with not supporting nested?
-----------------------------------------------------------------------------------------------------------
/!\ Running XSIBackup-DC in a nested host is not supported
-----------------------------------------------------------------------------------------------------------
f.
In general I think that the job files should be yml format, it would help to when using editors to edit the code and submit the code to git repos.
DC:
/scratch/XSI/XSIBackup-DC/xsibackup \
--backup \
"VMs(RUNNING)" \
"root@10.240.100.38:22:/vmfs/volumes/xsi-backup" \
--backup-how="hot " \
--description="esxi_038 " \
--mail-to="cw@ns.com " \
--subject="esxi_038 " \
>> /scratch/XSI/XSIBackup-DC/var/log/xsibackup.log 2>&1
PRO:
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-prog=OneDiff \
--backup-point=/vmfs/volumes/xsi-backup \
--backup-type=Running \
--backup-how=Hot \
--del-dirs=+2d \
--use-smtp=2 \
--mail-to=cw@ns.com \
--backup-id=038 \
--description="038oneDiff" \
--on-success="backupId->039" \
--on-error="backupId->039" \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"
Is it plausible to install xsibackup in a VM instead of on the esxi host?
Thanks
I think I purchased a few PRO licenses a few years ago.
May I download the current release of PRO?
I am currently on XSIBACKUP-PRO 11.2.3
Thanks
>>> smtp failed
>>> chained job failed
>>>I ran my job by cut/paste the command line from the crontab:
[root@esxi-38:/vmfs/volumes/5bc410e3-ae8c84a6-07cf-5cf3fc1d7030/xsi-dir] /vmfs/volumes/datastore1/xsi-dir/jobs/038
>>>At the end of the job we see that smtp=2: not found:
The ESXi configuration was saved to "/vmfs/volumes/QNAP-Archive"
--------------------------------------------------------------------------------------------------------------------------------------------------------
No errors detected in backup
--------------------------------------------------------------------------------------------------------------------------------------------------------
Backup finished
Tip: no chained backups scheduled, set --on-success and/or --on-error arguments to chain a backup
--------------------------------------------------------------------------------------------------------------------------------------------------------
Killed
/vmfs/volumes/datastore1/xsi-dir/jobs/038: line 13: --use-smtp=2: not found
[root@esxi-38:/vmfs/volumes/5bc410e3-ae8c84a6-07cf-5cf3fc1d7030/xsi-dir]
>>> Here is my job
[root@esxi-38:/vmfs/volumes/5bc410e3-ae8c84a6-07cf-5cf3fc1d7030/xsi-dir] cat /vmfs/volumes/datastore1/xsi-dir/jobs/038
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-prog=OneDiff \
--backup-point=/vmfs/volumes/QNAP-Archive \
--backup-type=Running \
--backup-how=Hot \
--del-dirs=+2d
--use-smtp=2 \
--mail-to=c@ions.com \
--backup-id=038 \
--description="038oneDiff" \
--on-success="backupId->039" \
--on-error="backupId->039" \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"
[root@esxi-38:/vmfs/volumes/5bc410e3-ae8c84a6-07cf-5cf3fc1d7030/xsi-dir]
>>> Here are my smtp servers
[root@esxi-38:/vmfs/volumes/5bc410e3-ae8c84a6-07cf-5cf3fc1d7030/xsi-dir] cat conf/smtpsrvs
# [TITLE] = SMTP Server
# You can add as many SMTP servers as you want
# Columns are separated by colons as described below
# One server per line pledging to the following format (please, do note that the server IP or FQDN and port are separated by a colon)
# ORDINAL(integer);--smtp-srv(IP or FQDN):--smtp-port;--mail-from;--smtp-usr;--smtp-pwd;--smtp-auth(none|anystring);--smtp-sec(TLS|anystring);--smtp-delay(0-4 sec)
# Do not parse any --smtp-delay unless you need it 0 is OK, only first 8 fields are mandatory
# Example
# 1;smtp.gmail.com:465;youremail@gmail.com;youremail@gmail.com;Y0urpassw0rd;yes;TLS;0
2;ions-com.mail.protection.outlook.com:25;esxi-noreply@ions.com;esxi-noreply@ions.com;none;none;TLS;0
[root@esxi-38:/vmfs/volumes/5bc410e3-ae8c84a6-07cf-5cf3fc1d7030/xsi-dir]
Thanks for the feedback.
Here is what I did:
First problem you have to solve is with snapshot management. Snapshots cannot be deleted. That's an ESXi inner mechanism, so finding why it fails is your main concern.
There all appear to have been created by xsibackupdiff and can be deleted via cli.
[root@esxi-38:~] vim-cmd vmsvc/snapshot.get 3
Get Snapshot:
|-ROOT
--Snapshot Name : xsibackupdiff
--Snapshot Id : 50
--Snapshot Desciption : xsibackupdiff 50
--Snapshot Created On : 3/11/2019 23:22:51
--Snapshot State : powered off
[root@esxi-38:~] vim-cmd vmsvc/snapshot.removeall 3
Remove All Snapshots:
[root@esxi-38:~] vim-cmd vmsvc/snapshot.get 4
Get Snapshot:
|-ROOT
--Snapshot Name : xsibackupdiff
--Snapshot Id : 51
--Snapshot Desciption : xsibackupdiff 51
--Snapshot Created On : 3/11/2019 23:25:6
--Snapshot State : powered off
[root@esxi-38:~] vim-cmd vmsvc/snapshot.removeall 4
Remove All Snapshots:
[root@esxi-38:~] vim-cmd vmsvc/snapshot.removeall 18
Remove All Snapshots:
[root@esxi-38:~] vim-cmd vmsvc/snapshot.get 25
Get Snapshot:
|-ROOT
--Snapshot Name : xsibackupdiff
--Snapshot Id : 1
--Snapshot Desciption : xsibackupdiff 1
--Snapshot Created On : 3/11/2019 23:19:29
--Snapshot State : powered off
[root@esxi-38:~] vim-cmd vmsvc/snapshot.removeall 25
Remove All Snapshots:
[root@esxi-38:~]
[root@esxi-38:~] vim-cmd vmsvc/snapshot.removeall 16
Remove All Snapshots:
Deleted _XSIBAK files for some of the VMs
[root@esxi-38:~] vim-cmd vmsvc/destroy 9
[root@esxi-38:~] vim-cmd vmsvc/destroy 10
[root@esxi-38:~] vim-cmd vmsvc/destroy 11
[root@esxi-38:~]
You have this error on your log: Skipping invalid VM '20'. Its is indicating that your host's registry is not in good condition and that could lead to all sort of errors, including problems with snapshots.
[root@esxi-38:~] vim-cmd vmsvc/getallvms includeConfigNotAvailable
Skipping invalid VM '20'
[root@esxi-38:~] vim-cmd /vmsvc/unregister 20
[root@esxi-38:~]
I have been having problems several problems for a few weeks with xsipro not running as a cron task.
I uninstalled cron today from xsibackup gui
I installed con again today from xsibackup gui
I then ran start of this job from inside the xsibackup gui
This is the email report edited to remove some details in names.
How do I correct all these issues?
Thanks
Mon Mar 11 21:47:07 UTC 2019
XSIBACKUP-PRO 11.2.3 AT HOST:
esxi-38.com IP v4: 10.240..38/ 255.255.255.0
VMware ESXi 6.5.0 build-8294253
Done hot backup (id: 038) using onediff (no compression)
Available room in device /vmfs/volumes/QNAP-Archive before backup: 3797 Gb.
Sparse size on disk of the selected virtual machines: 748 Gb.
Needed room in device /vmfs/volumes/QNAP-Archive for backup: 677 Gb.
(Id)VM Name State Size (Gb) Stop Copy Start Time (min:sec) Speed (mb/s)
(16) 00022028--ssong ON 176.38/ 176.36 NO (hot backup) KO! - 23:12 129/ 129
Last error raised for the above VM:
ERROR DIFQMSH4, details: [00022028--] error: first 500M mistmatch [VM_W2K12_SE_BASE_1-flat.vmdk]
(17) 00022236-- ON 222.29/ 222.28 NO (hot backup) OK - 52:02 72/ 72
(18) 00022237-ms-hyperion- ON 168.78/ 168.76 NO (hot backup) KO! - 16:24 175/ 175
Last error raised for the above VM:
ERROR CLDELSN3, details: [00022237-ms-hyperion-] error: cannot delete snapshot, details: Skipping invalid VM '20' Skipping invalid VM '20'
(25) mist. ON 40.00/ 40.00 NO (hot backup) KO! - 03:23 201/ 201
Last error raised for the above VM:
ERROR CLDELSN3, details: [mist.] error: cannot delete snapshot, details: Skipping invalid VM '20' Skipping invalid VM '20'
(3) 00022028-centos-1- ON 7.82/ 41.30 NO (hot backup) OK - 02:15 59/ 313
(4) 00022028-centos-2- ON 1.10/ 40.16 NO (hot backup) OK - 00:38 53/ 1078
(7) 00022028-centos-3- ON 60.40/ 60.32 NO (hot backup) OK - 00:40 1537/ 1536
Available space in device /vmfs/volumes/QNAP-Archive after backup: 3773 Gb.
Complete backup elapsed time: 98 min
Chained backup --on-success: backupid->039
The ESXi configuration was saved to /vmfs/volumes/QNAP-Archive
• [ Mon Mar 11 22:10:24 UTC 2019 ] ERROR (DIFDELAL), details [00022028--] error: error deleting all snapshots VM [00022028-genesys-ssong_XSIBAK] Id (vim.fault.AlreadyExists) {
• [ Mon Mar 11 22:10:35 UTC 2019 ] ERROR (DIFQMSH4), details [00022028--] error: first 500M mistmatch [VM_W2K12_SE_BASE-flat.vmdk]
• [ Mon Mar 11 22:10:46 UTC 2019 ] ERROR (DIFQMSH4), details [00022028--] error: first 500M mistmatch [VM_W2K12_SE_BASE_1-flat.vmdk]
• [ Mon Mar 11 23:08:59 UTC 2019 ] ERROR (CLDELSN1), details Error: cannot delete snapshot VM Id: 18, details: Skipping invalid VM '20'
• [ Mon Mar 11 23:19:11 UTC 2019 ] ERROR (CLDELSN3), details [00022237-ms-hyperion-] error: cannot delete snapshot, details: Skipping invalid VM '20'
• [ Mon Mar 11 23:19:37 UTC 2019 ] ERROR (CLDELSN1), details Error: cannot delete snapshot VM Id: 25, details: Skipping invalid VM '20'
• [ Mon Mar 11 23:22:34 UTC 2019 ] ERROR (CLDELSN3), details [mist.] error: cannot delete snapshot, details: Skipping invalid VM '20'
• Skipping invalid VM '20'
• faultCause = (vmodl.MethodFault) null,
• faultMessage =
• faultMessage = ,
• msg = "The specified key, name, or identifier '14' already exists."
• msg = "Unable to find a VM corresponding to "(vim.fault.AlreadyExists) {
• name = "14"
• }""
• }, details: (vim.fault.NotFound) {
• }
• [ Mon Mar 11 22:10:46 UTC 2019 ] WARNING (DIFRMVMX), details [00022028--] measure DIFRMVMX: took measure, renamed remote .vmx file to reinitialize OneDiff
the end of the xsibackup.log, but above there is ca chain option set to go to 039.
250 SMTPUTF8
read:errno=0
2019-03-11T23:26:38| Firewall rule SMTPout-25 closed.
2019-03-11T23:26:38| Backup finished
2019-03-11T23:26:38| Tip: no chained backups scheduled, set --on-success and/or --on-error arguments to chain a backup
"Use the crontab does not trigger automatically"
Apologies,
cron is not triggering the xsibackup process automatically
1.
/vmfs/volumes/datastore1/xsi-dir/jobs/038
this command starts the backup process
2.
[root@esxi-38:/vmfs/volumes/5bc410e3-ae8c84a6-07cf-5cf3fc1d7030/xsi-dir] 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'
2271343 2271343 busybox /usr/lib/vmware/busybox/bin/busybox crond
3.
[root@esxi-38:/vmfs/volumes/5bc410e3-ae8c84a6-07cf-5cf3fc1d7030/xsi-dir] ls -al /var/spool/cron/crontabs/root
-rwx------ 1 root root 399 Feb 21 00:23 /var/spool/cron/crontabs/root
[root@esxi-38:/vmfs/volumes/5bc410e3-ae8c84a6-07cf-5cf3fc1d7030/xsi-dir] tail -f /tmp/my-cron-test.txt
Tue Feb 26 20:56:01 UTC 2019
Tue Feb 26 20:57:01 UTC 2019
Tue Feb 26 20:58:01 UTC 2019
Sorry
Use the crontab does not trigger automatically
Thanks
I have removed the cron and added it back in with the xsibackup gui.
I have run the command from the command line directly and it works.
my crontab below.
Thoughts please?
[root@esxi-38:/vmfs/volumes/5bc410e3-ae8c84a6-07cf-5cf3fc1d7030/xsi-dir] cat /var/spool/cron/crontabs/root
#min hour day mon dow command
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 8 * * * "/vmfs/volumes/datastore1/xsi-dir/jobs/038" # Added by XSIBackup
"crash back to cli"
xsibackup application stopped
now I am back at the cli
on the host with the xsibackup pro installed
After starting XSI GUI
Select Link
Select List
crash back to cli
log from remote esxi server doing backup
failed during during cloning
checked job status and status is \[I\]
the time is now Tue Nov 27 17:08:30 UTC 2018
I didnt think it would take over 10 hours to do that clone.
Thanks
2018-11-27T07:34:01| [win02-2008r2] Starting backup (size is 146002M on 146000M file)
2018-11-27T07:34:01| XSIBackup will backup your VMs while they are running and will quiesce guest services too, so that users
2018-11-27T07:34:01| can continue to use the VM while the backup is taking place. You can also run cold and warm --backup-how
2018-11-27T07:34:01| Hot backup selected for VM: [win02-2008r2], will not be switched off
Skipping invalid VM '34'
Skipping invalid VM '34'
2018-11-27T07:34:02| [win02-2008r2] info: boot partition is MBR
2018-11-27T07:34:02| [win02-2008r2] info: Win64 OS (windows7Server64) detected on MBR, applying Windows algorithm
2018-11-27T07:34:03| Remember: --date-dir argument will be ignored in OneDiff backups
Skipping invalid VM '34'
Skipping invalid VM '34'
2018-11-27T07:34:05| [win02-2008r2] info: quick size check...
2018-11-27T07:34:05| [win02-2008r2] info: file [win02-2008r2-flat.vmdk]...
2018-11-27T07:34:05| [win02-2008r2] info: file size check | OK [ 85899345920 bytes | 85899345920 bytes ]
2018-11-27T07:34:05| [win02-2008r2] info: quick size check...
2018-11-27T07:34:05| [win02-2008r2] info: file [win02-2008r2_1-flat.vmdk]...
2018-11-27T07:34:05| [win02-2008r2] info: file size check | OK [ 53687091200 bytes | 53687091200 bytes ]
2018-11-27T07:34:05| [win02-2008r2] (c) OneDiff algorithm
[win02-2008r2] info: OneDiff backup first run, removing snapshots
[win02-2008r2] info: all snapshots removed
2018-11-27T07:46:58| Snapshot & Quiescing
2018-11-27T07:46:58| [win02-2008r2] info: VMWare Tools detected, taking snapshot QUIESCED(false)...
2018-11-27T07:46:58| [win02-2008r2] info: set argument --snapshot=doquiesce to quiesce your VMs
2018-11-27T07:46:58| [win02-2008r2] info: round 1
2018-11-27T07:47:04| [win02-2008r2] info: snapshot taken, quiescing status:
Skipping invalid VM '34'
2018-11-27T07:47:06| Removing snapshots, please wait...
2018-11-27T07:47:08| Error CLDELSN1: cannot delete snapshot VM Id: 5, details: Skipping invalid VM '34'
2018-11-27T07:47:08| Skipping invalid VM '34'
2018-11-27T07:47:08| Syncronizing config files
Skipping invalid VM '34'
Skipping invalid VM '34'
2018-11-27T07:47:14| Backing up virtual disks...
2018-11-27T07:47:14| scsi0:0.fileName = "win02-2008r2.vmdk"
2018-11-27T07:47:14| scsi0:1.fileName = "win02-2008r2_1.vmdk"
Destination disk format: VMFS thin-provisioned
Cloning disk '/vmfs/volumes/port-esx-data-store/win02-2008r2/win02-2008r2.vmdk'...
Clone: 28% done.
New xsibackup install
I added a new host
I tried to list the new host
xsibackup pro gui crashed
I tried to add the host again and I see that is already added.
Enabling port 22 out in the ESXi firewall...
There is already an RSA public key at /vmfs/volumes/datastore1/xsi-dir/xsibackup_id_rsa.pub. We will use the existing one.
Enter the remote server root password when prompted.
2018-11-26T18:08:16| Enter remote systems's password for user root, checking OS type...
Password:
Password:
The local RSA key has already been added to the authorized_keys file at 10.240.100.39:22.
There is no need to add it again, you should be able to connect with XSIBackup to 10.240.100.39:22 without any password.
Killed
Thoughts
Thanks
Thank you very much.
Interesting cron didnt run any jobs Tuesday.
I figured job 041 would run then chain the next jobs until finished, but the same job 041 runs 4 times.
cron:
[root@esx41:/etc] cat /var/spool/cron/crontabs/root
#min hour day mon dow command
1 1 * * * /sbin/tmpwatch.py
1 * * * * /sbin/auto-backup.sh
0 * * * * /usr/lib/vmware/vmksummary/log-heartbeat.py
*/5 * * * * /sbin/hostd-probe ++group=host/vim/vmvisor/hostd-probe
00 1 * * * localcli storage core device purge
*/2 * * * * /usr/lib/vmware/vsan/bin/vsanObserver.sh
* 23 * * 1,2,3,4,5 "/vmfs/volumes/datastore1/xsi-dir/jobs/041"
Jobs:
[root@esx41:/etc] cat /vmfs/volumes/datastore1/xsi-dir/jobs/041
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-prog=OneDiff \
--backup-point=/vmfs/volumes/QNAP-Archive \
--backup-type=Running \
--backup-how=Hot \
--backup-id=041 \
--description="esxi-041-oneDiffBackup" \
--use-smtp=1 \
--mail-to=EMAIL@DOMAIN.com \
--on-success=""backupId->042"" \
--on-error=""backupId->042"" \
--subject="esxi-041-oneDiffBackup" \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"
[root@esx41:/etc] cat /vmfs/volumes/datastore1/xsi-dir/jobs/042
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-prog=OneDiff \
--host=10.240.100.42:22 \
--backup-point=/vmfs/volumes/QNAP-Archive \
--backup-type=Custom \
--backup-how=Hot \
--on-success=""backupId->043"" \
--on-error=""backupId->043"" \
--use-smtp=1 \
--mail-to=EMAIL@DOMAIN.com \
--subject="esxi-042-oneDiffBackup" \
--backup-id=042 \
--description="esxi-042-oneDiffBackup" \
--backup-vms="Sales-Demo2 1_Clean" \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"
[root@esx41:/etc] cat /vmfs/volumes/datastore1/xsi-dir/jobs/043
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-prog=OneDiff \
--host=10.240.100.43:22 \
--backup-point=/vmfs/volumes/QNAP-Archive \
--backup-type=Running \
--backup-how=Hot \
--on-success=""backupId->045"" \
--on-error=""backupId->045"" \
--use-smtp=1 \
--mail-to=EMAIL@DOMAIN.com \
--subject="esxi-043-oneDiffBackup" \
--backup-id=043 \
--description="esxi-043-oneDiffbackup" \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"
[root@esx41:/etc] cat /vmfs/volumes/datastore1/xsi-dir/jobs/045
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-prog=OneDiff \
--host=10.240.100.45:22 \
--backup-point=/vmfs/volumes/QNAP-Archive \
--backup-type=Running \
--backup-how=Hot \
--remote-xsipath=/vmfs/volumes/port-esx-data-store \
--use-smtp=1 \
--mail-to=EMAIL@DOMAIN.com \
--backup-id=045 \
--description="esxi045onediffBackup" \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"
The subject of my email after a job is run is
"✔ XSIBACKUP no errors detected in backup job | esxi-041-oneDiffBackup"
but the vms listed in the job have the following errors:
Last error raised for the above VM:
ERROR CLVMKFS1, details: [ARIASQL2008] error: vmkfstools error, details: Failed to clone disk: The system cannot find the file specified (25).
Last error raised for the above VM:
ERROR DIFQMSH4, details: [TMG] error: first 500M mistmatch [Director-flat.vmdk]
Last error raised for the above VM:
ERROR CLVMKFS1, details: [MAIL2013] error: vmkfstools error, details: Failed to clone disk: The file already exists (39).
Last error raised for the above VM:
ERROR DIFQMSH4, details: [confluence-ChrisW] error: first 500M mistmatch [confluence-ChrisW-flat.vmdk]
I am thinking that the subject of the email should read "many error detected yada yada"
Thanks
This is odd to me, I created the the job, ran the job and then when the cron runs the same job runs into problems.
When I run the job the first time everything is fine.
When the cron runs all these job errors appear.
How do I contact support?
Thanks
Thanks
The /vmfs/volumes/datastotre1 datastore folder was missing
Thanks
Thanks
I dont see what you are saying but I just edited the the jobs in the job folder and added --test-mode=true
Thanks
I was reading the other posts for a maybe a common issue but maybe I have many issues? Maybe I have one big issue?
Your thoughts please.
This is a new deployment over 6 esxi servers
I had these issues consistently for a few days since I have set this up
#10 and #12 appear to okay
The rest of the jobs have different errors.
Fri Nov 2 23:34:13 UTC 2018
XSIBACKUP-PRO 11.1.4 AT HOST:
esx41.DOMAIN.COM IP v4: 10.240.100.41/ 255.255.255.0
VMware ESXi 6.0.0 build-3620759
(Id)VM Name State Size (Gb) Stop Copy Start Time (min) Speed (mb/s)
(1) SQL2008 ON 550/ 550 NO (hot backup) KO! - 0 14449/ 14448
Last error raised for the above VM:
ERROR CLVMKFS1, details: [SQL2008] error: vmkfstools error, details: Failed to clone disk: The file already exists (39).
(10) tomcat-1-jira-ubuntu-16.04-Jar (Cor and Kat) ON 60/ 60 NO (hot backup) OK - 1 635/ 63
(12) salesf-dev-joh ON 350/ 350 NO (hot backup) OK - 1 3349/ 3349
(13) TMG ON 100/ 100 NO (hot backup) KO! - 2 606/ 606
Last error raised for the above VM:
ERROR CLVMKFS1, details: [TMG] error: vmkfstools error, details: Failed to clone disk: The file already exists (39).
(14) DC2012DC ON 89/ 100 NO (hot backup) KO! - 0 2291/ 2560
Last error raised for the above VM:
ERROR CLVMKFS1, details: [DC2012DC] error: vmkfstools error, details: Failed to clone disk: The file already exists (39).
(15) MAIL2013 ON 1469/ 1470 NO (hot backup) KO! - 23 1071/ 1071
Last error raised for the above VM:
ERROR DIFRMVMX, details: [MAIL2013] error: tried to take measure, but could not rename remote .vmx file, delete remote [] VMX file, details: mv: can't rename '/vmfs/volumes/QNAP-Archive/MAIL2013/Windows Server 2012 R2 Partner.vmx': No such file or directory
(6) confluence-ChrisW ON 135/ 135 NO (hot backup) KO! - 0 2433/ 2433
Last error raised for the above VM:
ERROR DIFQMSH4, details: [conf-Chri] error: first 500M mistmatch [conf-Chri-flat.vmdk]
(7) LicenseServer ON 91/ 91 NO (hot backup) KO! - 20 75/ 75
Last error raised for the above VM:
ERROR DIFQMSH4, details: [LicenseServer] error: first 500M mistmatch [LicenseServer-flat.vmdk]
Last error raised for the above VM:
ERROR CLVMKFS1, details: [QL2008] error: vmkfstools error, details: Failed to clone disk: The file already exists (39).
Thoughts
Thanks
Chris
Is cron based on UTC or local time?
My time is scheduled for 11pm every week night.
It appears that the job starts at 44 minutes after the hour
Fri Nov 2 23:44:21 UTC 2018
XSIBACKUP-PRO 11.1.4 AT HOST: