You are not logged in.
Pages: 1
The ESXI is using an Intel on-motherboard NIC.
<<DD test from ESXI to MyCloud Mirror>>
[root@elevation:~] time dd if=/dev/zero bs=1000000 count=4000 of=/vmfs/volumes/NAS1/testfile
4000+0 records in
4000+0 records out
real 6m 5.43s
user 0m 2.24s
sys 0m 0.00s
Approx. 10.9 MB/s
<<DD test from ESXI to external disk drive on Mac Pro - (Gdrive 7200, ~=255MB/s R/W)>
[root@elevation:~] time dd if=/dev/zero bs=1000000 count=4000 of=/vmfs/volumes/macpro/testfile
4000+0 records in
4000+0 records out
real 1m 9.10s
user 0m 2.16s
sys 0m 0.00s
Approx. 57.9 MB/s
XSIBackup to External (usb 3) Gdrive 7200 on macpro, ~=255MB/s R/W)
Backup end date: 2021-07-06T06:13:35
-------------------------------------------------------------------------------------------------------------
Time taken: 02:10:42 (7842 sec.)
-------------------------------------------------------------------------------------------------------------
Total time: 7842 sec.
-------------------------------------------------------------------------------------------------------------
Full file speed: 19.60 mb/s
-------------------------------------------------------------------------------------------------------------
Real data speed: 30.67 mb/s
During the above backup the cpu triplet was approx. 39, 30, 37 - The memory overcommit you mentioned was always 0.
The XSI Backups/restores to the myCloud get approx 10MB/s and less.
-------------------------------------------
Now I'm completely confused.
I just did a restore (same one I did before to the esxi ssd that took 8 hours)
I did it again from the myCloud mirror, but this time to the esxi's vmdata disk drive (not the ssd).
It processed at 63MB/s. Maybe there's a problem with my esxi's ssd. It's the common denominator with all the very slow backups and restores.
I thought I explained the topology in previous replies. But here it is:
ESXI ------------- NAS
NET = 1gb, same subnet
ESXI = 3930K 6 core - 32G mem - SSD (spec 550r, 530w).
NAS = MYCloud Mirror, 5400rpm,
I think it may be the myCloud as the bottleneck (I'm going to do dd tests). I am also considering backing up in two phases (headache), by backingup/restoring from a network fast disk (repo on the fast disk) and then only archiving repos on the NAS. Basically what you talked about as the enterprise scheme. But I'm a bit concerned about the window of risk where the repo is sitting on a single drive without the raid 1 of the NAS.
I get what you're saying about XSI not affecting the contents of files (at least things like changes to a single data field - but corruption maybe). I'll change the .vmdk field in the .vmx to point to the most recent snapshot after restoring again and see if it comes up with more current data. Although there seems to be data problems as the ESXI UI under manage snapshots hangs when trying to enumerate snapshots, so there seems to be corruption ostensibly from the backup/restore as it was fine before the backup. That doesn't mean it's XSIBackup's fault, just that it likely occured during the backup/restore process.
There is no raid controller nor raid controller cache on the ESXI server.
XSIBackup restore has restored it to a very old state (like a year ago). I had backed it up with XSIbackup less than a month ago. There were snapshots on it and it's like after restore the snapshots are being ignored and it comes up on the base revision of the vmdk.
VM files participating in the restore are 71GB
All VMs (3) are running on ESXI on SSD on their dedicated host 3930K cpu, 32G ram.
Yes triplet parts were like .03 or less.
I don't recall overcommit numbers, but I'll watch for that going forward. There was no paging.
Now when I tried to bring up the restored VM it brought up a really old version of the vm. The XSIbackup backup was only a few days ago.
I did notice this backup has multiple vmdk's and snapshots. It's like it came up on the wrong one or something.
In the ESXI web console under manage snapshots it just hangs looking for snapshots.
The VM came up using JAKWEB_2.vmdk
Here's an ls -la of the vm files.
drwxr-xr-x 1 root root 3780 Jul 4 22:43 .
drwxr-xr-t 1 root root 2520 May 4 03:29 ..
-rw-r--r-- 1 root root 2147483648 Jul 4 07:12 JAKWEB-Snapshot1.vmem
-rw-r--r-- 1 root root 5772757 Jul 4 00:43 JAKWEB-Snapshot1.vmsn
-rw-r--r-- 1 root root 28762 Jul 4 07:12 JAKWEB-Snapshot2.vmsn
-rw-r--r-- 1 root root 107374182400 Jul 3 22:48 JAKWEB-flat.vmdk
-rw-r--r-- 1 root root 8684 Jul 4 22:43 JAKWEB.nvram
-rw-r--r-- 1 root root 589 Jul 3 22:48 JAKWEB.vmdk
-rw-r--r-- 1 root root 671 Jul 4 03:48 JAKWEB.vmsd
-rw-r--r-- 1 root root 671 Jul 4 07:12 JAKWEB.vmsd.tmp
-rw-r--r-- 1 root root 3345 Jul 4 22:43 JAKWEB.vmx
-rw-r--r-- 1 root root 3353 Jul 4 07:12 JAKWEB.vmx.tmp
-rw-r--r-- 1 root root 150 Jul 4 03:48 JAKWEB.vmxf
-rw-r--r-- 1 root root 107374182400 Jul 4 00:43 JAKWEB_1-flat.vmdk
-rw-r--r-- 1 root root 591 Jul 4 00:43 JAKWEB_1.vmdk
-rw-r--r-- 1 root root 22246797312 Jul 4 06:56 JAKWEB_2-000001-delta.vmdk
-rw-r--r-- 1 root root 379 Jul 4 06:56 JAKWEB_2-000001.vmdk
-rw-r--r-- 1 root root 107374182400 Jul 4 22:43 JAKWEB_2-flat.vmdk
-rw-r--r-- 1 root root 644 Jul 4 22:24 JAKWEB_2.vmdk
-rw-r--r-- 1 root root 246829 Jul 4 07:12 vmware-48.log
-rw-r--r-- 1 root root 258347 Jul 4 06:56 vmware-49.log
-rw-r--r-- 1 root root 713218 Jun 27 05:05 vmware-50.log
-rw-r--r-- 1 root root 610720 Jul 3 20:28 vmware-51.log
-rw-r--r-- 1 root root 205432 Jul 3 20:30 vmware-52.log
-rw-r--r-- 1 root root 651121 Jul 4 07:12 vmware-53.log
-rw-r--r-- 1 root root 211475 Jul 4 22:43 vmware.log
-rw-r--r-- 1 root root 115343360 Jul 4 06:56 vmx-JAKWEB-812182546-2.vswp
[root@elevation:/vmfs/volumes/588366f8-5f993700-3530-902b3451b465/JAKWEB]
I'm now trying to create a new VM using an OVF backup from April 2021.
I was restoring a VM to the SSD from a repository on our NAS across our internal 1gb network. 3 Vm's share this SSD as their primary drive.
During the entire time of the restore (some 8 hours), our Windows server on another VM (same ESXI) was unusable. services wouldn't start. A command on the Window's UI or Windows command prompt (even just hitting enter) took 20-30 seconds to be even recognized.
Completely unusable.
As soon as the restore completed, the Windows machine returned to normal.
I ran ESXTOP.
CPU was low (surprised me - I expected it to be high).
SSD Disk was active, but not crazy high.
Network was high (between 70-90% utilization).
I'm obviously concerned, if I essentially can't have other VMs on the box functional when doing a restore.
Maybe I should nice the restore, but then it's going to take much longer.
Ok thanks - so even though one backs up config with the --config-backup switch when backing up a vm(s), the backed up config isn't stored within the VM's backup hierarchy or attached to a vm in any way. The config backup was just created at the same time.
I guess it would be missing the source argument, something like:
./xsibackup PATH_TO_REPO --config-backup
But I'm not sure it will like arg 1 for the source being missing? Or maybe there's some appropriate placeholding null arg for Source?
I'm upgrading ESXI and am thinking I don't want my esxi backup buried with the backup for a specific VM.
It worked to add a repo after the nfs mount point (/vmfs/volumes/NAS1/elevation_repo) to successfully backup and info the smaller VM (couldn't try my larger VM again because my trial just expired).
More problems with --info and apparently the backup that said it was successful without errors.
[root@elevation:/vmfs/volumes/588366f8-884c8d8c-ff51-902b3451b465/XSI/XSIBackup-DC] ./xsibackup --info /vmfs/volumes/NAS1
|---------------------------------------------------------------------------------|
||-------------------------------------------------------------------------------||
||| (c)XSIBackup-Free 1.5.0.8: 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 5 Minor 0 Patch 0
-------------------------------------------------------------------------------------------------------------
PID: 1910182, Running job as: root
-------------------------------------------------------------------------------------------------------------
Deduplicated repository information
-------------------------------------------------------------------------------------------------------------
Compression: 1
Block size: 1048576
Block count: 115476
-------------------------------------------------------------------------------------------------------------
Retrieving block information...
-------------------------------------------------------------------------------------------------------------
2021-06-20T06:53:39 | Error code 165 at file info.c, line 165 | Error description: can't get blockhash, bad .blocklog format?, details: No such file or directory
-------------------------------------------------------------------------------------------------------------
2021-06-20T06:53:39 | Error code 174 at file info.c, line 174 | Error description: can't get blocksize, bad .blocklog format?, details: No such file or directory
-------------------------------------------------------------------------------------------------------------
2021-06-20T06:53:39 | Error code 174 at file info.c, line 174 | Error description: can't get blocksize, bad .blocklog format?, details: No such file or directory
<<<<<
<<<<<Hundreds of these lines>>>>>
<<<<<
-------------------------------------------------------------------------------------------------------------
2021-06-20T06:53:59 | Error code 174 at file info.c, line 174 | Error description: can't get blocksize, bad .blocklog format?, details: No such file or directory
-------------------------------------------------------------------------------------------------------------
2021-06-20T06:53:59 | Error code 174 at file info.c, line 174 | Error description: can't get blocksize, bad .blocklog format?, details: No such file or directory
-------------------------------------------------------------------------------------------------------------
2021-06-20T06:53:59 | Error code 174 at file info.c, line 174 | Error description: can't get blocksize, bad .blocklog format?, details: No such file or directory
-------------------------------------------------------------------------------------------------------------
2021-06-20T06:53:59 | Error code 174 at file info.c, line 174 | Error description: can't get blocksize, bad .blocklog format?, details: No such file or directory
-------------------------------------------------------------------------------------------------------------
2021-06-20T06:53:59 | Error code 174 at file info.c, line 174 | Error description: can't get blocksize, bad .blocklog format?, details: No such file or directory
-------------------------------------------------------------------------------------------------------------
| Real data | Hosted data |
-------------------------------------------------------------------------------------------------------------
Block number | 115476 | 679 |
Data volume | 51.37 GB | 671.84 MB |
Compression | -7729.73% | - |
-------------------------------------------------------------------------------------------------------------
Removed host <tmp> dir OK
-------------------------------------------------------------------------------------------------------------
Removed prog <tmp> dir OK
-------------------------------------------------------------------------------------------------------------
[root@elevation:/vmfs/volumes/588366f8-884c8d8c-ff51-902b3451b465/XSI/XSIBackup-DC]
I got the backup to work by outputting to a nas.
However after finishing the backup, when I try to do an --info on the repository. No matter how I escape the spaces in the path (double or single quote enclosed or back-slash escaped spaces) --info blows up. Apparently the code isn't passing the path with spaces as one unit.
>>> I renamed the mount to NAS1 to eliminate the spaces and --info now works. But it should really be able to handle names with spaces if escaped or quoted. Right?
Here's the output. I also included the original --backup command output afterwards:
-------------------------------------------Info----------------------------------------
[root@elevation:/vmfs/volumes/588366f8-884c8d8c-ff51-902b3451b465/XSI/XSIBackup-DC] ./xsibackup --info /vmfs/volumes/nas\ 1\ john
|---------------------------------------------------------------------------------|
||-------------------------------------------------------------------------------||
||| (c)XSIBackup-Free 1.5.0.8: 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 5 Minor 0 Patch 0
-------------------------------------------------------------------------------------------------------------
PID: 1909763, Running job as: root
-------------------------------------------------------------------------------------------------------------
Deduplicated repository information
-------------------------------------------------------------------------------------------------------------
Compression: 1
Block size: 1048576
Block count: 115476
-------------------------------------------------------------------------------------------------------------
Retrieving block information...
-------------------------------------------------------------------------------------------------------------
sh: can't create /vmfs/volumes/nas: Operation not permitted
sort: /vmfs/volumes/nas: No such file or directory
2021-06-20T05:15:53 | Error code 3577 at file common.c, line 3577 | Error description: error ordering .blocklog file: /vmfs/volumes/nas 1 john/data/.blocklog
-------------------------------------------------------------------------------------------------------------
2021-06-20T05:15:53 | Error code 67 at file info.c, line 67 | Error description: error ordering .blocklog file at: /vmfs/volumes/nas 1 john/data/.blocklog
-------------------------------------------------------------------------------------------------------------
Removed host <tmp> dir OK
-------------------------------------------------------------------------------------------------------------
Removed prog <tmp> dir OK
-------------------------------------------------------------------------------------------------------------
[root@elevation:/vmfs/volumes/588366f8-884c8d8c-ff51-902b3451b465/XSI/XSIBackup-DC]
-------------------------------------------Orig bckup --------------------------------
./xsibackup --backup "VMs(Black)" "/vm
fs/volumes/nas 1 john"
|---------------------------------------------------------------------------------|
||-------------------------------------------------------------------------------||
||| (c)XSIBackup-Free 1.5.0.8: 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 5 Minor 0 Patch 0
-------------------------------------------------------------------------------------------------------------
License: unlicensed trial version, remaining trial time: 15:37:32 | (c)XSIBackup-Free
-------------------------------------------------------------------------------------------------------------
PID: 1905571, Running job as: root
-------------------------------------------------------------------------------------------------------------
LZJB compression has been enabled
-------------------------------------------------------------------------------------------------------------
Block size is 1.00 MB (1048576 bytes)
-------------------------------------------------------------------------------------------------------------
Performing --backup action
-------------------------------------------------------------------------------------------------------------
(c)XSIBackup-Free setting repository at /vmfs/volumes/nas 1 john
-------------------------------------------------------------------------------------------------------------
Remote 'data' folder does not exist, creating it...
-------------------------------------------------------------------------------------------------------------
Item number 1 in this job
-------------------------------------------------------------------------------------------------------------
Black Hardware Version is: 13
-------------------------------------------------------------------------------------------------------------
Virtual Machine Name: Black
-------------------------------------------------------------------------------------------------------------
Creating snapshot VM : Black (powered on)
-------------------------------------------------------------------------------------------------------------
*** Snapshot was successfully created ***
-------------------------------------------------------------------------------------------------------------
Virtual Machine: Black
-------------------------------------------------------------------------------------------------------------
Backup start date: 2021-06-19T20:22:33
-------------------------------------------------------------------------------------------------------------
2021-06-19 20:22:33 | Backing up 23 files, total size is 162.24 GB
-------------------------------------------------------------------------------------------------------------
NUMBER FILE SIZE PROGRESS
-------------------------------------------------------------------------------------------------------------
1/23 Black.vmx 3.30 KB | Done 0.00%
-------------------------------------------------------------------------------------------------------------
2/23 Black_0-flat.vmdk 150.00 GB | Done 0.00%
-------------------------------------------------------------------------------------------------------------
::: detail ::: 100.00% done | block 153600 out of 153600 | Done 92.46%
-------------------------------------------------------------------------------------------------------------
3/23 Black_0.vmdk 551.00 B | Done 92.46%
-------------------------------------------------------------------------------------------------------------
4/23 Black.vmsd 435.00 B | Done 92.46%
-------------------------------------------------------------------------------------------------------------
5/23 Black.nvram 8.48 KB | Done 92.46%
-------------------------------------------------------------------------------------------------------------
6/23 Black.vmx~ 3.29 KB | Done 92.46%
-------------------------------------------------------------------------------------------------------------
7/23 Black.vmxf 3.08 KB | Done 92.46%
-------------------------------------------------------------------------------------------------------------
8/23 vmware-2.log 463.94 KB | Done 92.46%
-------------------------------------------------------------------------------------------------------------
9/23 vmware-3.log 983.66 KB | Done 92.46%
-------------------------------------------------------------------------------------------------------------
10/23 vmware-4.log 1.23 MB | Done 92.46%
-------------------------------------------------------------------------------------------------------------
11/23 vmware-7.log 2.79 MB | Done 92.46%
-------------------------------------------------------------------------------------------------------------
12/23 vmware-6.log 508.62 KB | Done 92.46%
-------------------------------------------------------------------------------------------------------------
13/23 vmx-Black-1838801243-2.vswp 110.00 MB | Done 92.46%
-------------------------------------------------------------------------------------------------------------
14/23 vmware-5.log 347.73 KB | Done 92.53%
-------------------------------------------------------------------------------------------------------------
15/23 vmx-Black-1838801243-1.vswp [open excluded]
-------------------------------------------------------------------------------------------------------------
16/23 Black.vmx.lck [skipped excluded]
-------------------------------------------------------------------------------------------------------------
17/23 vmware.log 546.27 KB | Done 92.53%
-------------------------------------------------------------------------------------------------------------
18/23 Black-6d99e15b.vswp [open excluded]
-------------------------------------------------------------------------------------------------------------
19/23 Black.vmsd.tmp 43.00 B | Done 92.53%
-------------------------------------------------------------------------------------------------------------
20/23 Black.vmx.tmp 3.29 KB | Done 92.53%
-------------------------------------------------------------------------------------------------------------
21/23 Black-Snapshot3.vmsn 31.04 KB | Done 92.53%
-------------------------------------------------------------------------------------------------------------
22/23 Black_0-000001-delta.vmdk [skipped excluded]
-------------------------------------------------------------------------------------------------------------
23/23 Black_0-000001.vmdk [skipped excluded]
-------------------------------------------------------------------------------------------------------------
Total size: 150.11 GB | Done 100.00%
-------------------------------------------------------------------------------------------------------------
*** Snapshot was removed ***
-------------------------------------------------------------------------------------------------------------
Backup end date: 2021-06-20T04:28:36
-------------------------------------------------------------------------------------------------------------
Time taken: 08:06:03 (29163 sec.)
-------------------------------------------------------------------------------------------------------------
Total time: 29163 sec.
-------------------------------------------------------------------------------------------------------------
Full file speed: 5.27 mb/s
-------------------------------------------------------------------------------------------------------------
Real data speed: 7.77 mb/s
-------------------------------------------------------------------------------------------------------------
Item backup completed without errors
-------------------------------------------------------------------------------------------------------------
Differential blocks were added to the .blocklog database
-------------------------------------------------------------------------------------------------------------
Data processing completed successfully
-------------------------------------------------------------------------------------------------------------
Removed host <tmp> dir OK
-------------------------------------------------------------------------------------------------------------
Removed prog <tmp> dir OK
-------------------------------------------------------------------------------------------------------------
Unlocked backup OK
-------------------------------------------------------------------------------------------------------------
Removed PID OK
-------------------------------------------------------------------------------------------------------------
Yes it is vmfs-5. Outputting locally to VMDATA (it is only 4% full). I'm trialing so I can only output to the local drive (my understanding).
It is backing up a smaller vm (80G thin) ok to same location. Made me think it was maybe your trial limit doing this. Thinking it may be something else I didn't want to just license the trial and have it not resolve the issue. Also when this failed, I tried to run a smaller vm backup and it failed with "out of disk space" error, even though there was still almost 4TB of space available (maybe out of inodes is throwing same exception). I could only backup another vm after deleting the repository from the failed backup.
Currently trying again with the ouput going to an nfs mounted nas.
[root@elevation:/vmfs/volumes/588366f8-884c8d8c-ff51-902b3451b465/XSI/XSIBackup-DC] ./xsibackup --backup "VMs(Black)" /vmf
s/volumes/VMDATA/Backups
|---------------------------------------------------------------------------------|
||-------------------------------------------------------------------------------||
||| (c)XSIBackup-Free 1.5.0.8: 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 5 Minor 0 Patch 0
-------------------------------------------------------------------------------------------------------------
License: unlicensed trial version, remaining trial time: 31:35:42 | (c)XSIBackup-Free
-------------------------------------------------------------------------------------------------------------
PID: 1898025, Running job as: root
-------------------------------------------------------------------------------------------------------------
LZJB compression has been enabled
-------------------------------------------------------------------------------------------------------------
Block size is 1.00 MB (1048576 bytes)
-------------------------------------------------------------------------------------------------------------
Performing --backup action
-------------------------------------------------------------------------------------------------------------
(c)XSIBackup-Free setting repository at /vmfs/volumes/VMDATA/Backups
-------------------------------------------------------------------------------------------------------------
Item number 1 in this job
-------------------------------------------------------------------------------------------------------------
Black Hardware Version is: 13
-------------------------------------------------------------------------------------------------------------
Virtual Machine Name: Black
-------------------------------------------------------------------------------------------------------------
Creating snapshot VM : Black (powered on)
-------------------------------------------------------------------------------------------------------------
*** Snapshot was successfully created ***
-------------------------------------------------------------------------------------------------------------
Virtual Machine: Black
-------------------------------------------------------------------------------------------------------------
Backup start date: 2021-06-19T04:24:23
-------------------------------------------------------------------------------------------------------------
2021-06-19 04:24:23 | Backing up 23 files, total size is 162.24 GB
-------------------------------------------------------------------------------------------------------------
NUMBER FILE SIZE PROGRESS
-------------------------------------------------------------------------------------------------------------
1/23 Black.vmx 3.30 KB | Done 0.00%
-------------------------------------------------------------------------------------------------------------
2/23 Black_0-flat.vmdk 150.00 GB | Done 0.00%
-------------------------------------------------------------------------------------------------------------
::: detail ::: 19.48% done | block 29917 out of 153600 | Done 18.01%2021-06-19T06:39:11 | Error code 389 at file dedup-in.c, line 389 | Error description: can't open temp block file: /vmfs/volumes/VMDATA/Backups/data/34269407511556112.tmp
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
2021-06-19T06:39:11 | Error code 214 at file signal.c, line 214 | Error description: raised SIGTERM (11) (28) in job, total errors: 11, check error.log
-------------------------------------------------------------------------------------------------------------
Removed current target dir: /vmfs/volumes/5894f2f4-1995ab20-7898-902b3451b465/Backups/20210619042418/Black
-------------------------------------------------------------------------------------------------------------
SIGTERM (11) condition was trapped: check logs for more details
-------------------------------------------------------------------------------------------------------------
Cleaning up...
-------------------------------------------------------------------------------------------------------------
*** Snapshot was removed ***
-------------------------------------------------------------------------------------------------------------
Removed host <tmp> dir OK
-------------------------------------------------------------------------------------------------------------
Removed prog <tmp> dir OK
-------------------------------------------------------------------------------------------------------------
Unlocked backup OK
-------------------------------------------------------------------------------------------------------------
Log file unmapped OK
-------------------------------------------------------------------------------------------------------------
Removed PID OK
-------------------------------------------------------------------------------------------------------------
[root@elevation:/vmfs/volumes/588366f8-884c8d8c-ff51-902b3451b465/XSI/XSIBackup-DC]
I had been really excited about this software.
Installed fine, ran backup fine to local drive. Got 30% through the backup and errored out.
I'm running as root - /tmp is 777
/vmfs/volumes/VMDATA/data/33938929867210700.tmp does not exist.
/vmfs/volumes/VMDATA/data/ is root:root 755
2021-06-17T22:03:20 | Error code 209 at file signal.c, line 209 | Error description: raised SIGTERM (2) in job, num of errors: 2, check error.log
2021-06-17T22:03:20 | Error code 214 at file signal.c, line 214 | Error description: raised SIGTERM (2) (2) in job, total errors: 2, check error.log
2021-06-17T22:03:55 | Error code 1058 at file common.c, line 1058 | Error description: .lock on '/tmp/xsibackup.pid' after 30 s
2021-06-17T22:03:55 | Error code 133 at file signal.c, line 133 | Error description: can't remove PID from /tmp/xsibackup.pid
2021-06-18T01:57:57 | Error code 389 at file dedup-in.c, line 389 | Error description: can't open temp block file: /vmfs/volumes/VMDATA/data/33938929867210700.tmp
2021-06-18T01:57:57 | Error code 214 at file signal.c, line 214 | Error description: raised SIGTERM (11) (28) in job, total errors: 11, check error.log
Pages: 1