Posts by cuchillo

cuchillo · General matters

Is the Unlimited One Site Licenses the one that allow me to backup 4 servers in the same nerwork to a 5ft one?

cuchillo · General matters

You are right. XSIBackup-DC is good and the price is fear as it is. :-)

cuchillo · General matters

That is a very big diference compared to PRO. With pro I can backup up to 20 hosts!!!

cuchillo · General matters

Hi... I have 4 ESXi servers in a local network. One server is just for backup (actually using XSIBackup Pro) and the others are running the VMs to backup. XSIBackup Pro licence allow me to backup the 3 servers with a single licence (in fact allow me to backup up to 20 ESXi servers). Can I bakcup the 3 servers in the 4th server with a XSI Backup DC licence?

cuchillo · General matters

Good point... :-)

cuchillo · Repositories

It would be convenient to have a command to list all the bacups in a repository separated by subfolders. It would also be convenient for a command to delete a certain backup (so remove its exclusive blocks).
This is nothing that currently cannot be done by hand. They are only suggestions.

cuchillo · Feature requests & improvements

I intend to use "replica" to make local backups.
But notice that a folder with the date is not created. It would be interesting if this were possible and that the "rotate" option also worked in this mode.
The reason for using "replica" instead of "backup" is that the deduplication system creates many files and VMFS does not support this. In a local environment I prefer to have replicas and be able to program them in a way that rotates automatically (similar to --backup-prog=xsitools in XSI Pro).

cuchillo · General matters

In Pro there are options to perform cold, warm and hot backups... In DC only hot are allowed. Can U include at least warm mode?

cuchillo · General matters

In XSI Pro i can start a backup of VMs hosted in server B by running xsibackup from server A specifying --host parameter. Is (or will be) an equivalent option on XSI DC?
I have 4 ESXi servers in a factory... They are small servers. Every ESXi only have an unique VM. I have them virtualized because is easy to replace hardware, move to other servers, etc... with XSI Pro y installed a 5ft EXSi server witho no VMs... This is my backup server. And i program all the jobs for backup the other 4 servers in this server using the --host option (intead of programming one job per server). This guarantee no overlaping jobs.
It will be usefull to be able to do this on DC.

cuchillo · General matters

cool! I have tried it and it is working!

cuchillo · General matters

cool! I have tried it and it is working!

cuchillo · General matters

is not that... I'm telling U... it does not work. something changed in version 0.9.5.0 an does not work. I rebooted the server.

cuchillo · General matters

I get "Error code 821 at xsibackup.c at line 821. Error description: Port 7722 is closed at xxx.xxx.xxx.xxx"
when i use the command:
./xsibackup --backup "VMs(TST)" root@xxx.xxx.xxx.xxxg:7722:/vmfs/volumes/BUPNAS/XSIDC --compression --subfolder=TST --rotate=2 --remote-path="/vmfs/volumes/SYSTEM/xsi-dc-dir/xsibackup"

however the command:
./xsibackup --add-key root@xxx.xxx.xxx.xxx:7722

works perfectly.

I have the external port 7722 forwarded to the internal port 22 at my ESXi server IP.
If I forward the external port 22 to to the internal port 22 at my ESXi server IP and replace 7722 by 22 in the coomand it works. But I need to use diferent port that the 22 for secyrity reasons.

cuchillo · General matters

It says "This trial version is limited to 60.00 GB files and 6 hous after reboot" and does nothing.
I go back to verison 0.9.4.3 and the same comand (./xsibackup --backup "VMs(TEST)" /vmfs/volumes/BUPNAS/XSIDC --compression --subfolder=TST --rotate=2 --exclude="TEST_1.vmdk") work fine.
Of course the VM is less than 30 GB and i rebooted the server :-)

cuchillo · General matters

I will use XSIBackup to backup ESXi VMs... the reason because I use a Linux distri is that the PDF says "the ESXi VMFS file system has around 130.000 possible inodes, thus it is not very convenient to store deduplicated backups... we recommend that you use XFS or ext4". I cant mount an ext4 FS on ESXi... so I assumed that a linux installation with OpenSSH is what I need. Do you know any way to mount an ext4 FS at ESXi? Do I need to use an NFS system based on ext4?

Sorry for the confussion

cuchillo · General matters

I understand... but can I trigger the backups of several ESXi servers from one central server?

cuchillo · General matters

UPDATE: "SEGFAULT condition was trapped" occurs at each execution regardless of the command. XSIBackup does not execute any commands in Debian and always returns the error "SEGFAULT condition was trapped". I imagine that something is missing in Debian or that it is a security problem but I have no idea what to do.

cuchillo · General matters

I'm trying to ./xsibackup --add-key root@xxx.xxx.xxx.xxx:22 from a Debian to an ESXi and get "SEGFAULT condition was trapped". It do work in the other way (from ESXi to Debian). I have installed OpenSSH Server on Debian.

cuchillo · General matters

In a scenario of several ESXi servers it would be very useful to have an exclusive server for XSIBackup Datacenter. Backup of the other servers would be saved on this server over IP. To be able to schedule these backup tasks and not overlap, the schedule should be programmed on this dedicated backup server. XSIBackup Datacenter should be able to trigger remote tasks over IP on other servers and should also have the equivalent of the options --on-success and --on-error that exist in PRO.

cuchillo · General matters

Great!!! I just say FYI... Is this the place for that? I am testing the beta version and would like to leave my comments and suggestions to collaborate.

cuchillo · General matters

I was trying a backup over the internet with the command

./xsibackup --backup "VMs(XXX)" root@XXX.XXX.XXX.XXX:22:/vmfs/volumes/BACKUP/XSIDC/ --subfolder=XXX --rotate=2 --exclude"XXX_1.vmdk" --remote-path=/vmfs/volumes/SYSTEM/xsi-dc-dir/xsibackup

Everything was going fine until the internet connection breaks down.

Then STDO start showing

Signal 13 received
-----------------------------------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------------------------------
Signal 13 received
-----------------------------------------------------------------------------------------------------------------

....

and never stops...

XSI proccess left running on the remote server because I got this there

Only one instance of XSIBackup-Datacenter is allowed
-----------------------------------------------------------------------------------------------------------------
Remove /var/run/xsibackup.pid if last execution was abruptly terminated

Is very much important that xsibackup handles nework conection interruptions in a right way for it to be a usefull tool. In the best scenario the connection should be restored and continue. In the worse scenario the remote repository should be corrected, the snapshot on the source VM should be removed, and the xsi proccess should be terminated in both sides.

cuchillo · © XSITools

XSITools in version 11.2.0 should purge the repositories according to the specified parameter with the backup-room option. The backup-room option is specified in GB but the purge considers the value specified in MB.

The backup command is this:
"/vmfs/volumes/SYSTEM/xsi-dir/xsibackup" \
--backup-prog=xsitools:z \
--backup-point="/vmfs/volumes/BACKUP/XSIP/TEST/XSITOOLS/" \
--backup-type=custom \
--backup-vms="GESTION2003" \
--backup-how=warm \
--backup-room=300000 \
--smart-info=yes \
--backup-id=001 \
--description="WL GESTION2003" \
--exec=yes >> "/vmfs/volumes/SYSTEM/xsi-dir/var/logs/xsibackup.log"

Here the logs …

** with backup-room=300

2019-01-04T00:06:04| Needed room: 38 Gb.
2019-01-04T00:06:04| Sparse size: 38 Gb.
2019-01-04T00:06:04| Available room: 299 Gb.

* so far so good, but then

2019-01-04T00:17:31| Checking the size of the (c)XSITools repository...
---------------------------------------------------------------------------------------------------------------------------------
2019-01-04T00:17:39| The (c)XSITools repository is 99615Mb in size
---------------------------------------------------------------------------------------------------------------------------------
2019-01-04T00:17:39| Prune round 1: (c)XSITools repository size: 99615 exceeds --backup-room=300

Pruning exclusive blocks of backup </vmfs/volumes/BACKUP/XSIP/TEST/XSITOOLS/20190103201154>
1/2190 blocks | freed 43 Mb | Processed 0% [0K
2/2190 blocks | freed 58 Mb | Processed 0% [0K
3/2190 blocks | freed 87 Mb | Processed 0% [0K
…
2189/2190 blocks | freed 81775 Mb | Processed 99% [0K
2190/2190 blocks | freed 81813 Mb | Processed 100% [0K
Deleting </vmfs/volumes/BACKUP/XSIP/TEST/XSITOOLS/20190103201154> directory (0 Mb)
Blocks deleted: 2190
Space saved: 81813 Mb
2019-01-04T00:21:22| The (c)XSITools repo </vmfs/volumes/BACKUP/XSIP/TEST/XSITOOLS> was pruned, 81813 Mb were made available
2019-01-04T00:21:22| The size of the repo was reduced to 17802
---------------------------------------------------------------------------------------------------------------------------------
2019-01-04T00:21:22| Prune round 2: (c)XSITools repository size: 17802 exceeds --backup-room=300
---------------------------------------------------------------------------------------------------------------------------------
Pruning exclusive blocks of backup </vmfs/volumes/BACKUP/XSIP/TEST/XSITOOLS/20190104000539>
2019-01-04T00:21:22| -- Nothing to prune
2019-01-04T00:21:44| The ESXi configuration was saved to "/vmfs/volumes/BACKUP/XSIP/TEST/XSITOOLS/20190104000539"
---------------------------------------------------------------------------------------------------------------------------------

** As U can see the older backup was removed and the exclusive blocks has been transferred to the current, but there was room yet. That was not necessary yet.

** Now I set backup-room=300000. XSIBackup take all the available space on my disk as room.
2019-01-04T00:26:17| Needed room: 138 Gb.
2019-01-04T00:26:17| Sparse size: 138 Gb.
2019-01-04T00:26:17| Available room: 3467 Gb.

** It says more needed room because I add a VM to this backup… ignore it.
**The thing is when the first VM backup is ended…
---------------------------------------------------------------------------------------------------------------------------------
2019-01-04T00:38:56| Checking the size of the (c)XSITools repository...
---------------------------------------------------------------------------------------------------------------------------------
2019-01-04T00:39:02| The (c)XSITools repository is 21456Mb in size
---------------------------------------------------------------------------------------------------------------------------------
2019-01-04T00:39:02| There's still 278544 Mb available, no need to prune the repo
---------------------------------------------------------------------------------------------------------------------------------

** As U can see the 278544 MB available are the result of 300000 – 21456. It the set backup room but considered in MB – the repo size.

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

#26 Re: General matters » Licencing » 2019-10-31 20:50:34

#27 Re: General matters » Licencing » 2019-10-31 20:42:33

#28 Re: General matters » Licencing » 2019-10-24 18:30:04

#29 General matters » Licencing » 2019-10-23 16:08:58

#30 Re: General matters » Centralized backup » 2019-09-13 17:42:57

#31 Repositories » Additional commands » 2019-09-03 18:21:57

#32 Feature requests & improvements » Replica for local backups » 2019-09-03 18:11:48

#33 General matters » Backup Types » 2019-09-03 17:27:01

#34 Re: General matters » Centralized backup » 2019-09-02 15:29:29

#35 Re: General matters » Trial 0.9.5.0 does not work at all » 2019-09-02 15:19:04

#36 Re: General matters » Port problem » 2019-09-02 15:17:50

#37 Re: General matters » Trial 0.9.5.0 does not work at all » 2019-09-01 21:46:17

#38 General matters » Port problem » 2019-09-01 07:07:36

#39 General matters » Trial 0.9.5.0 does not work at all » 2019-09-01 05:50:49

#40 Re: General matters » SEGFAULT condition was trapped » 2019-08-12 16:40:03

#41 Re: General matters » Centralized backup » 2019-08-12 16:34:25

#42 Re: General matters » SEGFAULT condition was trapped » 2019-08-10 19:56:23

#43 General matters » SEGFAULT condition was trapped » 2019-08-10 19:24:15

#44 General matters » Centralized backup » 2019-08-10 16:24:30

#45 Re: General matters » Error: Signal 13 received » 2019-08-10 16:15:26

#46 General matters » Error: Signal 13 received » 2019-08-09 22:33:47

#47 © XSITools » backup-room option and prune. Size misunderstood » 2019-01-04 00:45:37

Board footer