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

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


You are not logged in.

#1 Re: General matters » Replica XSIBackup-DC versions » 2021-08-10 19:11:22

The 15.0.13 version seems to be working as it advertizes. Many thanks and I am sure there are lots of users that would echo that. Thanks again to your and your crew.

#5 Re: General matters » Replica XSIBackup-DC versions » 2021-08-04 14:32:13

[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.

#6 Re: General matters » Replica XSIBackup-DC versions » 2021-08-04 13:01:05

[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

#7 Re: General matters » Replica XSIBackup-DC versions » 2021-08-03 16:08:41

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,

#8 Re: General matters » Replica XSIBackup-DC versions » 2021-08-01 19:02:42

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.

#9 Re: General matters » Replica XSIBackup-DC versions » 2021-08-01 12:07:33

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.

#10 Re: General matters » Replica XSIBackup-DC versions » 2021-07-31 21:36:06

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

#11 Re: General matters » Replica XSIBackup-DC versions » 2021-07-25 13:15:19

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.

#12 Re: General matters » Replica XSIBackup-DC versions » 2021-07-24 12:38:56

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.

#13 Re: General matters » Replica XSIBackup-DC versions » 2021-07-23 15:32:53

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

#14 Re: General matters » Replica XSIBackup-DC versions » 2021-07-22 21:28:37

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

#15 Re: General matters » Replica XSIBackup-DC versions » 2021-07-22 20:36:20

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.

#16 Re: General matters » Replica XSIBackup-DC versions » 2021-07-22 20:06:47

I truly appreciate the usefulness of your application. Telling people that it doesn't work like that or what you want to do isn't a backup really sells your program short. That smaller organizations or simpler needs can use your application and have it work as the classic program does and you should embrace it. Someone can start with a simple, point-in-time copy and move themselves to something far more complex. The true beauty of your application is that it runs all within the ESXi host, and with a little bit of encouragement can suit almost everyone froe the single server with a handful of VMs to a Datacenter.

#17 Re: General matters » Replica XSIBackup-DC versions » 2021-07-22 19:27:10

admin wrote:

In any case, the perfect solution to your requirement has always been possible and is indeed commented in this very same thread.

/scratch/XSI/XSIBackup-DC/xsibackup \
--replica[=cbt] \
"VMs(VM1,VM2, VM3...)" \
/vmfs/volumes/backup/replica/$(( $(date +%j) % N )) \
--use-smtp="1" \
--mail-to=mail-from \
>> /scratch/XSI/XSIBackup-DC/var/log/xsibackup.log 2>&1

The mod operator of the Julian date $(( $(date +%j) % N )) will generate a rotating pattern 0 to N-1
If there's something that you don't get about it, please let us know what it is.

This is absolutely NOT what I want. I can get what I want with the /vmfs/volumes/backup/replica/$(date +%Y%m%d%H%M%S) however the --rotate=3 does not remove older folders.

/vmfs/volumes/585bd3c7-63c6dc10-a706-001fc69beea0/XSIBackup-DC/xsibackup \
--replica \
"VMs(tester)" \
/vmfs/volumes/backup/replica/$(date +%Y%m%d%H%M%S) \
--rotate=3

#18 Re: General matters » Replica XSIBackup-DC versions » 2021-07-22 15:16:48

This is why I wanted clarification on the statement "all replicas will be differential from the second pass". That seems to indicate there is something other than a straight copy of the VM. Other than in this thread, where is that documented and how would someone use that from the GUI. I prefer doing things without the GUI, but I know someone that does use it from the GUI

#19 Re: General matters » Replica XSIBackup-DC versions » 2021-07-22 12:16:10

I understand the two pieces of software are different. I was asking for clarification. I have read the somewhat confusing manual.
There are people that want the instantly available copy of a VM. It may not be the best backup, but it is perfect for the dozens of small Linux servers that I have. They may have a bunch of changes throughout the day but are unchanged during the night. I don't need long-term data recovery points, because the data is collected separately. I need an oops copy and I want one from last night, and for the previous two days back. I take a weekend copy of some that I want some historical record. These servers are small and perform a dedicated task. Each of them takes 6 or 7 minutes to back up, they don't take much room. The 3-day backup rotation is convenient as hell. The deduplicated backups or differential replicas, overly complicate a very simple need.  Your software obviously knows how to make a copy of the VM. Add some settings that provides the simple functionality that was available in the Clasic version. A simple point in time copy of a VM.

#20 Re: General matters » Replica XSIBackup-DC versions » 2021-07-21 16:48:37

https://33hops.com/xsibackup-vmware-esxi-backup.html shows 1.5.0.10 even when I access the page on another computer that has never accessed the site. But that same URL shows 1.5.0.11 when coming from other links. I have had the same issue with other pages. Under "Resources & help" on the main menu sometimes shows Index of docs as well as forums but from other links only shows Forums. Page refreshes or deleting site data does no clear things up.

#21 Re: General matters » Replica XSIBackup-DC versions » 2021-07-21 15:37:44

I have been following this because I am looking for the same functionality as the earlier version where I could do a simple backup of the complete VM in date isolated folders. I am not interested in deduplicated anything. I just want a complete VM that can be turned on in the event of a failure. I don't want any form of "recovery". I just want to register the VM and turn it on. I think that is what the OP wanted as well. Some of the things that have been indicated here have led me to believe that that may be possible with 1.5.0.11 which I have seen show up on the website but that appears to have disappeared, only showing 1.5.0.10. Clicking another link on the website does now show 1.5.0.11, so you have links pointing to old pages mixed in with links pointing to new pages.
Also, I would like clarification on the following.

admin wrote:

all replicas will be differential from the second pass

This seems to indicate that a simple replica is not like I and I am sure others, would like to see a replica, a standalone dated folder with a complete operational VM. Could you please clarify.

#22 General matters » License key file not generated after 24 hours (solved) » 2021-07-08 21:36:36

zarthan
Replies: 1

I have been helping someone get XSIBacup Pro installed and running. After generating the request.key yesterday, the license file has not been generated. What is the best way to get this matter taken care of?
I will pose a question, would the fact that they have an IPV6 address cause issues?

#23 General matters » Is DC a trial? » 2019-06-26 14:00:14

zarthan
Replies: 3

Since this isn't yet a shipping version does the 6-hour limitation still apply? I am running this in my home lab but I really don't want to shut down all the running VMs just to run a few tests. There isn't much documentation and it will take a lot of trial and error just to figure out how everything works.

#24 Re: General matters » Welcome to the (c)XSIBackup-Datacenter forum » 2019-06-25 22:16:07

I have downloaded and installed the DC version. I would like to test this but I'm not sure what a command line should look like to back up a single VM to an attached NFS datastore.

#25 Re: General matters » Welcome to the (c)XSIBackup-Datacenter forum » 2019-06-25 20:56:52

Is the Datacenter version a new distinct product or an upgrade to the pro version. I did not see pricing.

Board footer