©XSIBackup-Free: Free Backup Software for ©VMWare ©ESXi

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


You are not logged in.

#26 2021-07-22 20:25:54

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: Replica XSIBackup-DC versions

We have indeed embraced that type of usage as explained in the above post.

Extended rotation features

I believe that the key matter here is that you probably have not perceived the radical difference between a simple timestamp and a Julian + Mod rotation.

When you use $(( $(date +%j) % N )), the rotation is implicit to the date algorithm. You don't need to use argument --rotate, the date will always produce a fixed rotation from 0 to N-1, thus it will revisit each folder each (N-1) times and produce a differential copy. The first time for each of the integers produced the copy will be full.

When you use the plain time stamp pattern, each folder is new every time and so your VM is fully copied every time, there isn't any kind of differential feature.

Of course it's not possible to generate the data out of thin air. If there isn't any seed data in the target folder, no differential copy can be performed.

Offline

#27 2021-07-22 20:36:20

zarthan
Member
Registered: 2018-02-25
Posts: 37

Re: Replica XSIBackup-DC versions

I do understand what happens with $(( $(date +%j) % N )). It gives me differential replicas. I don't want that at all. I want what I get with /vmfs/volumes/backup/replica/$(date +%Y%m%d%H%M%S) which is discrete dated folders with full vmdks. The link to the Extended rotation feature led me to believe that the rotation option would indeed remove folders based on the different rotation options.

Offline

#28 2021-07-22 21:03:34

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: Replica XSIBackup-DC versions

You can now since version 1.5.0.11. Previous version didn't support rotating sets of replicas.

Offline

#29 2021-07-22 21:28:37

zarthan
Member
Registered: 2018-02-25
Posts: 37

Re: Replica XSIBackup-DC versions

I am using 1.5.0.11 which is why I was reporting it wasn't working or at least --rotate=3 isn't

Offline

#30 2021-07-23 12:40:43

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: Replica XSIBackup-DC versions

It is indeed working for us

 ./xsibackup --replica "VMs(WS2012)" "root@192.168.133.23:22:/volume1/backup/replicas/$(date +%Y%m%d%H%M%S)" --rotate=3

|---------------------------------------------------------------------------------|
||-------------------------------------------------------------------------------||
|||   (c)XSIBackup-DC 1.5.0.11: 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
-------------------------------------------------------------------------------------------------------------

...
...
...
...
...
...
...
Total size:                                                                    100.02 GB    | Done 100.00%
-------------------------------------------------------------------------------------------------------------
*** Snapshot was removed ***
-------------------------------------------------------------------------------------------------------------
Backup end date: 2021-07-23T12:38:10
-------------------------------------------------------------------------------------------------------------
Time taken: 00:06:58 (418 sec.)
-------------------------------------------------------------------------------------------------------------
Total time:      418 sec.
-------------------------------------------------------------------------------------------------------------
Full file speed:                                                                           245.01 mb/s
-------------------------------------------------------------------------------------------------------------
Real data speed:                                                                            33.42 mb/s
-------------------------------------------------------------------------------------------------------------
Item backup completed without errors
-------------------------------------------------------------------------------------------------------------
Final checksum: 10095909563 bytes were sent and confirmed to have been written remotely
-------------------------------------------------------------------------------------------------------------
Data processing completed successfully
-------------------------------------------------------------------------------------------------------------
--rotate option was detected, retrieving backups to prune...
-------------------------------------------------------------------------------------------------------------
- Deleting replica at '/volume1/backup/replicas/20210723091155'
-------------------------------------------------------------------------------------------------------------
Removed host <tmp> dir        OK
-------------------------------------------------------------------------------------------------------------
Removed prog <tmp> dir        OK
-------------------------------------------------------------------------------------------------------------
Unlocked backup               OK
-------------------------------------------------------------------------------------------------------------

Offline

#31 2021-07-23 15:32:53

zarthan
Member
Registered: 2018-02-25
Posts: 37

Re: Replica XSIBackup-DC versions

My apologies. My test script lacked a slash before the date variable and while the documentation did say that, it is NOT clear.

"normally use that string, and not other"

At any rate, thank you. If I might offer a suggestion. Please add some simple scenarios and take a new user through building the script. The documentation is just a list of commands and options but doesn't help with understanding anything. You created it so it is second nature. Some options are available for some situations and not others. It reminds me of Cisco documentation in the early 90s. Start with a stated goal and then show how you developed your choices. I am sure you lose potential customers because you treat many as stupid users. I was a moderator on the VMware forums for many years. It is often difficult for some new users to grasp the concepts. Your ideas and your application can be a very solid solution to protecting VMs.
Again
Thank you

Offline

#32 2021-07-24 10:04:31

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: Replica XSIBackup-DC versions

You are right, taking the user's hand and walking him through all the learning curve is the way to go.

Still, given our current size we can't afford to do so, thus, by now we will have to treat our users as Linux sys admins with a mid knowledge of the Linux command line environment.

Once we reach our goals we can move up the commercial line towards the end user, or at least power users. Take on account that given the nature of the software's purpose, we may never reach end users, it might even be couterproductive.

Offline

#33 2021-07-24 12:38:56

zarthan
Member
Registered: 2018-02-25
Posts: 37

Re: Replica XSIBackup-DC versions

You don't need to lead each user by the hand. I so seldom ask for help with a piece of software, unless it is confusing or undocumented. Give someone like me, clear way to use something and I will figure it out and find innovative ways to use it. Take various scenarios and show how you would build the script and why. Just a list of commands and options doesn't help anyone understand how and where those commands and options are useful. I am sure you have customers who would be willing to put some narratives together to describe their infrastructure and how they came to the scripts they have and why. If you have a few different levels of infrastructure or needs complexity laid out on the website and new users to your product can pick something close to their situation and build from there. The beauty of your product is that it spans simple to very complex. An admin that starts working at a small organization and then gets a job with a more complex situation, can start with something they are already familiar with, knowing that your application can easily grow to suit the situation.

Offline

#34 2021-07-24 13:13:21

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: Replica XSIBackup-DC versions

We totally agree. (c)XSIBackup is a tool, you can use it from a basic approach to a much complex one. We offer a man page and post use cases that we find to be interesting as often as we can. We manufacture a swiss knife, it's up to you how to use it though.

We aren't by now pretending to offer anything beyond that.

Offline

#35 2021-07-25 13:15:19

zarthan
Member
Registered: 2018-02-25
Posts: 37

Re: Replica XSIBackup-DC versions

Ask your customers to describe how they use your product and I am positive some will respond with their very innovative approaches. Have a section on your website to highlight various situations and their solutions. A man page and a command and options page are not enough. You brought this to life so it is easy for you to look at a command string and mentally understand what it is doing and how the whole backup will transpire. A new user at whatever complexity level, will not. Give them something to refer to. An email to your existing customers asking for help putting together these scenarios would be a great way to engage with existing customers.

Offline

#36 2021-07-31 21:36:06

zarthan
Member
Registered: 2018-02-25
Posts: 37

Re: Replica XSIBackup-DC versions

I hate to come back at this but, although I must. In spite of the rotate being acknowledged and seemingly acted upon, the folders are not being deleted.
My script is simple
/scratch/XSI/XSIBackup-DC/xsibackup --replica "VMs(tiny)" /vmfs/volumes/backup/replica/$(date +%Y%m%d%H%M%S) --rotate=3

Item backup completed without errors
-------------------------------------------------------------------------------------------------------------
Data processing completed successfully
-------------------------------------------------------------------------------------------------------------
--rotate option was detected, retrieving backups to prune...
-------------------------------------------------------------------------------------------------------------
- Deleting replica at '/vmfs/volumes/backup/replica/20210729194533'
-
-------------------------------------------------------------------------------------------------------------
SIGTERM (11) condition was trapped: check logs for more details
-------------------------------------------------------------------------------------------------------------
Cleaning up...

Obviously the SIGTERM line indicates a problem.

The error.log file shows
2021-07-31T21:08:33 | Error code 216 at file signal.c, line 216 | Error description: raised SIGTERM (2) (2) in job, total errors: 2, c
2021-07-31T21:08:33 | Error code 2161 at file common.c, line 2161 | Error description: can't remove directory tree, error: 0
, description: No such file or directory

The directory does exist.

[root@ESXI:~] ls /vmfs/volumes/backup/replica/20210729194533
tiny
[root@ESXI:~]

If I am not understanding something correctly, I apologize, but it appears that the removal fails

Offline

#37 2021-08-01 00:10:47

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: Replica XSIBackup-DC versions

The SIGTERM is most probably due to an empty variable, this is a side effect though.
This kind of error happens when the remote FS is not mounted properly or there's some bug in the NFS implementation, there have been some in the ESXi 6 branch regarding the use of NFS 4 from the shell.
Please switch to NFS 3 and try again. NFS 4.1 is indeed useless in this context.

Offline

#38 2021-08-01 12:07:33

zarthan
Member
Registered: 2018-02-25
Posts: 37

Re: Replica XSIBackup-DC versions

I am using NFS 3 in this test. My biggest concern is that the rotate did not remove the old folder. XSIbackup creates the folder and I can manually remove them, so it isn't the share not being properly mounted. It happens with a QNAP NAS and a Synology NAS.

Offline

#39 2021-08-01 18:00:27

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: Replica XSIBackup-DC versions

(c)XSIBackup uses system calls, the same as your manual commands. We haven't been able to reproduce your issue on the other side. If it was a bug I guess we would know by now as some other people would have complained on the same matter. We can't be sure 100% without checking it, it all looks like some sort of misconfiguration or faulty driver/ hardware though.

No such file or directory is a message coming directly from the remote system call. It's not the same to delete a folder manually than doing it right after a heavy load on the NFS share.

Contact us directly to ask for a remote RDP session if you will, but please change your cables/ switch and try to find the problem on your own first.

Offline

#40 2021-08-01 19:02:42

zarthan
Member
Registered: 2018-02-25
Posts: 37

Re: Replica XSIBackup-DC versions

This backup is tiny. This Linux vmdk is 32M (Megabytes). The whole backup takes less than 10 seconds including creating and removing snapshots. Copying the vmdk is 2 to 3 seconds. The failure to delete happens on a local SSD. I can do an rm -rf on half a dozen backups of this tiny VM and I get the prompt back almost instantly; everything gone! Being local eliminates cables and switches.
I posted my backup script and if there is something I have misconfigured, I don't know what but am willing to learn.

/scratch/XSI/XSIBackup-DC/xsibackup \
--replica \
"VMs(tiny)" \
/vmfs/volumes/Local-1/replica/$(date +%Y%m%d%H%M%S)/ \
--rotate="4" \

I can easily remove the folders with find and add it to the script, but both my customer and me, want this to be something he can easily modify himself from the GUI.

Offline

#41 2021-08-02 10:21:25

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: Replica XSIBackup-DC versions

Your job syntax is OK. The error is raised on the remove() system call, the error is coming directly from the FS.

I'm wordering if that really tiny size could be causing some unexpected behaviour, it shouldn't. It could have something to do with the SSD, maybe some driver issue. Can you try to some alternative location?

Prepend strace to have a direct insight into de problem at a system call level, you will most probably just see that the remove() system call returns -1, but there may be some additional info.

From the installation dir:

strace ./xsibackup --replica "VMs(tiny)" /vmfs/volumes/Local-1/replica/$(date +%Y%m%d%H%M%S)/ --rotate="4"

UPDATE:

Just a little detail. Remove that trailing slash, you don't need it. I don't think this will be causing any issue, still, just to remove unneeded variables from the equation.

strace ./xsibackup --replica "VMs(tiny)" /vmfs/volumes/Local-1/replica/$(date +%Y%m%d%H%M%S) --rotate="4"

Offline

#42 2021-08-03 16:08:41

zarthan
Member
Registered: 2018-02-25
Posts: 37

Re: Replica XSIBackup-DC versions

The failure to remove the rotated replica happens with a larger VM, maybe 100GB, on a spinning HD in a NAS. Much easier to test a 32MB VM than 100GB.

Here are the last lines of the strace. I don't see anything obvious. If you need the complete strace I would rather send it than post it.

fstat(10, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xa342906000
read(10, "Get Snapshot:\n", 600)        = 14
read(10, "|-ROOT\n", 600)               = 7
read(10, "--Snapshot Name        : xsi6238"..., 600) = 205
read(10, "", 600)                       = 0
close(10)                               = 0
wait4(2751074, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 2751074
munmap(0xa342906000, 4096)              = 0
pipe([10, 11])                          = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xa30283f910) = 2751081
close(11)                               = 0
fstat(10, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xa342906000
read(10, "Remove Snapshot:\n", 600)     = 17
read(10, "", 600)                       = 0
close(10)                               = 0
wait4(2751081, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 2751081
munmap(0xa342906000, 4096)              = 0
write(1, "*** Snapshot was removed ***\n", 29) = 29
write(1, "\33[90m---------------------------"..., 119) = 119
pipe([10, 11])                          = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xa30283f910) = 2751089
close(11)                               = 0
fstat(10, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xa342906000
read(10, "0;", 600)                     = 2
read(10, "", 600)                       = 0
close(10)                               = 0
wait4(2751089, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 2751089
munmap(0xa342906000, 4096)              = 0
pipe([10, 11])                          = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xa30283f910) = 2751091
close(11)                               = 0
fstat(10, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xa342906000
read(10, "0;", 600)                     = 2
read(10, "", 600)                       = 0
close(10)                               = 0
wait4(2751091, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 2751091
munmap(0xa342906000, 4096)              = 0
stat("/etc/localtime", {st_mode=S_IFREG|0444, st_size=56, ...}) = 0
write(1, "Backup end date: 2021-08-02T14:1"..., 37) = 37
write(1, "\33[90m---------------------------"..., 119) = 119
write(1, "Time taken: 00:00:03 (3 sec.)\n", 30) = 30
write(1, "\33[90m---------------------------"..., 119) = 119
write(1, "Total time:        3 sec.\n", 26) = 26
write(1, "\33[90m---------------------------"..., 119) = 119
write(1, "Full file speed:\t               "..., 96) = 96
write(1, "\33[90m---------------------------"..., 119) = 119
write(1, "Real data speed:\t               "..., 96) = 96
write(1, "\33[90m---------------------------"..., 119) = 119
open("/scratch/XSI/XSIBackup-DC/var/log/backupdb.log", O_WRONLY|O_CREAT|O_APPEND, 0666) = 10
fstat(10, {st_mode=S_IFREG|0644, st_size=9207, ...}) = 0
mmap(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xa342906000
fstat(10, {st_mode=S_IFREG|0644, st_size=9207, ...}) = 0
lseek(10, 9207, SEEK_SET)               = 9207
write(10, "6238059529795125;2750950;--repli"..., 186) = 186
close(10)                               = 0
munmap(0xa342906000, 131072)            = 0
access("/vmfs/volumes/585bd3c7-63c6dc10-a706-001fc69beea0/replica/20210802141508/tiny/.locked", F_OK) = 0
unlink("/vmfs/volumes/585bd3c7-63c6dc10-a706-001fc69beea0/replica/20210802141508/tiny/.locked") = 0
write(1, "\33[32mItem backup completed witho"..., 42) = 42
write(1, "\33[0m\33[90m-----------------------"..., 123) = 123
access("", F_OK)                        = -1 ENOENT (No such file or directory)
write(1, "Data processing completed succes"..., 39) = 39
write(1, "\33[90m---------------------------"..., 119) = 119
write(1, "--rotate option was detected, re"..., 61) = 61
write(1, "\33[90m---------------------------"..., 119) = 119
pipe([10, 11])                          = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xa30283f910) = 2751093
close(11)                               = 0
fstat(10, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xa342906000
read(10, "0;/vmfs/volumes/Local-1/replica/"..., 600) = 227
read(10, "", 600)                       = 0
close(10)                               = 0
wait4(2751093, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 2751093
munmap(0xa342906000, 4096)              = 0
write(1, "\33[90m-\33[0m Deleting replica at '"..., 78) = 78
mknod("/tmp/xsi/2750950/fifo1", S_IFIFO|0666) = 0
mmap(NULL, 528384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_32BIT, -1, 0) = 0xa342906000
mprotect(0xa342906000, 4096, PROT_NONE) = 0
clone(child_stack=0xa3429860b0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0xa3429869d0, tls=0xa342986940, child_tidptr=0xa3429869d0) = 2751101
open("/tmp/xsi/2750950/fifo1", O_RDONLY) = 10
read(10, "Bad port '-q'\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 255) = 255
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
close(0)                                = 0
write(1, "\33[90m-\33[0m\n", 11)        = 11
write(1, "\33[90m---------------------------"..., 119) = 119
write(1, "SIGTERM (11) condition was trapp"..., 64) = 64
write(1, "\33[90m---------------------------"..., 119) = 119
write(1, "Cleaning up...\n", 15)        = 15
write(1, "\33[90m---------------------------"..., 119) = 119
pipe([0, 14])                           = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xa30283f910) = 2751103
futex(0x75a040, FUTEX_WAKE_PRIVATE, 1)  = 1
close(14)                               = 0
fstat(0,

Offline

#43 2021-08-04 08:27:09

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: Replica XSIBackup-DC versions

Well, it turned out to be something that we weren't expecting. This is the relevant part in the strace output.

read(10, "Bad port '-q'\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 255) = 255

For some reason the ssh client is not taking the -q option (quiet), or the call is malformed.
This isn't happening on our tests though. Can you share the exact build number with vmware -v?, so that we can try to install the very same build and again try to reproduce your issue.

Now the weirdest thing of all is that in theory (you didn't post the exact job command that produced the above strace output, we will asume it is the very same as in the previous post) the job was local, thus, there should not be any ssh command tunneling at that point.

Offline

#44 2021-08-04 13:01:05

zarthan
Member
Registered: 2018-02-25
Posts: 37

Re: Replica XSIBackup-DC versions

[root@ESXI:~] vmware -v
VMware ESXi 6.7.0 build-14320388
[root@ESXI:~]


The backup job was run exactly as I posted it. Prior to posting, I ran it with and without the trailing slash. I also ran it with and without the rotate value quoted. I ran the backup job folded as posted and unfolded on a single command line.

I ran the job again and here is the "Bad port" line with the prior line
open("/tmp/xsi/2783805/fifo1", O_RDONLY) = 12
read(12, "Bad port '-q'\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 255) = 255
--- SIGSEGV (Segmentation fault) @ 0 (0) ---

the /tmp/xsi/2783805/fifo1 file does not exist.

[root@ESXI:/vmfs/volumes/585bd3c7-63c6dc10-a706-001fc69beea0/.locker/XSI/XSIBackup-DC] ls -la /tmp/xsi/
total 20
drwx------    1 root     root           512 Aug  4 12:33 .
drwxrwxrwt    1 root     root           512 Aug  4 12:33 ..
drwx------    1 root     root           512 Aug  4 12:30 2783505
drwx------    1 root     root           512 Aug  4 12:31 2783671
drwx------    1 root     root           512 Aug  4 12:33 2783842
[root@ESXI:/vmfs/volumes/585bd3c7-63c6dc10-a706-001fc69beea0/.locker/XSI/XSIBackup-DC] ls -la /tmp/xsi/2783505/
total 8
drwx------    1 root     root           512 Aug  4 12:30 .
drwx------    1 root     root           512 Aug  4 12:33 ..

Another thing I would like to bring to your attention. On the third run-through with the rotate value set at three, xsibackup tried to delete the earliest backup job. Perhaps it is how you define rotate, but I would expect rotate to rotate on the fourth backup run leaving me three copies of the backup. If your definition of rotate=3 is to remove the third, the documentation should make that clear

Offline

#45 2021-08-04 14:14:33

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: Replica XSIBackup-DC versions

--rotate=3 means: keep the three latest timestamped dirs.

Back on the issue.

- The FIFO node is required to use --rotate. Check that you are indeed able to create a FIFO in the /tmp dir by using mkfifo

mkfifo /tmp/fifotest;ls -la /tmp/fifotest

- We just worked an issue around some OpenSSL implementations present in some ESXi builds. Upgrade the main binary and see if this helps your issue, it probably won't, we need to move forward eliminating some uncertainties though.
Issue on spurious error raised by OpenSSL

Offline

#46 2021-08-04 14:32:13

zarthan
Member
Registered: 2018-02-25
Posts: 37

Re: Replica XSIBackup-DC versions

[root@ESXI:~] mkfifo /tmp/fifotest;ls -la /tmp/fifotest
prw-r--r--    1 root     root             0 Aug  4 14:17 /tmp/fifotest
[root@ESXI:~]

--rotate=3 means: keep the three latest timestamped dirs. is not working correctly then. It is trying to remove the first of three which would leave only two,

The 1.5.12 has been installed but makes no difference.

Offline

#47 2021-08-04 14:34:27

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: Replica XSIBackup-DC versions

OK, let's concentrate on the main issue and we can then address the other one.
We'll try to reproduce the problem on the exact same version + build.

Offline

#48 2021-08-04 14:38:55

zarthan
Member
Registered: 2018-02-25
Posts: 37

Re: Replica XSIBackup-DC versions

OK let me know what I can do to help

Offline

#49 2021-08-08 10:39:01

admin
Administrator
Registered: 2017-04-21
Posts: 1,821

Re: Replica XSIBackup-DC versions

We are making tests with your same exact version this weekend, we'll reach you back as soon as we have something.

Offline

#50 2021-08-08 11:20:26

sanyex
Member
Registered: 2017-12-14
Posts: 4

Re: Replica XSIBackup-DC versions

I think same problem here. Backup is done without error but rotate segfaulting.

VMware ESXi 6.7.0 build-14320388
XSIBackup-DC 1.5.0.11
dst: Synology NFS3 drive


command:  /scratch/XSI/XSIBackup-DC/xsibackup --backup "VMs(RUNNING)" "/vmfs/volumes/poseidon/esxi5/repo/daily/"
--block-size=10M --rotate=5

strace:

write(1, "\33[32mItem backup completed witho"..., 42) = 42
write(1, "\33[0m\33[90m-----------------------"..., 123) = 123
access("/scratch/XSI/XSIBackup-DC/tmp/15947810/.blocklog.diff", F_OK) = 0
stat("/scratch/XSI/XSIBackup-DC/tmp/15947810/.blocklog.diff", {st_mode=S_IFREG|0700, st_size=289361, ...}) = 0
access("/vmfs/volumes/poseidon/esxi5/repo/daily/data/.xsitools", F_OK) = -1 ENOENT (No such file or directory)
access("/vmfs/volumes/poseidon/esxi5/repo/daily/.xsitools", F_OK) = 0
pipe([20, 21])                          = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x279f830910) = 15949390
close(21)                               = 0
fstat(20, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x27df91f000
read(20, "1\n", 600)                    = 2
read(20, "", 600)                       = 0
close(20)                               = 0
wait4(15949390, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 15949390
munmap(0x27df91f000, 4096)              = 0
write(1, "Differential blocks were added t"..., 57) = 57
write(1, "\33[90m---------------------------"..., 119) = 119
write(1, "Data processing completed succes"..., 39) = 39
write(1, "\33[90m---------------------------"..., 119) = 119
write(1, "--rotate option was detected, re"..., 61) = 61
write(1, "\33[90m---------------------------"..., 119) = 119
pipe([20, 21])                          = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x279f830910) = 15949396
close(21)                               = 0
fstat(20, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x27df91f000
read(20, "0;/vmfs/volumes/poseidon/esxi5/r"..., 600) = 600
read(20, "211000,/vmfs/volumes/poseidon/es"..., 600) = 62
read(20, "", 600)                       = 0
close(20)                               = 0
wait4(15949396, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 15949396
munmap(0x27df91f000, 4096)              = 0
mknod("/tmp/xsi/15947810/fifo1", S_IFIFO|0666) = 0
mmap(NULL, 528384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_32BIT, -1, 0) = 0x27df91f000
mprotect(0x27df91f000, 4096, PROT_NONE) = 0
clone(child_stack=0x27df99f0b0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x27df99f9d0, tls=0x27df99f940, child_tidptr=0x27df99f9d0) = 15949404
open("/tmp/xsi/15947810/fifo1", O_RDONLY) = 20
read(20, "Bad port '-q'\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 255) = 255
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
close(0)   





Queston: can I delete old folders manually from the repo ?

Offline

Board footer