Forum ©XSIBackup: ©VMWare ©ESXi Backup Software
MenuYou are not logged in.
- Topics: Active | Unanswered
#1 Repositories » Pruning is not possible » 2023-01-11 12:43:52
- cuchillo
- Replies: 1
I can't prune any backup. It says Segmantation fault. Any ideas?
|---------------------------------------------------------------------------------|
||-------------------------------------------------------------------------------||
||| (c)XSIBackup-Pro 1.5.2.1: 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
-------------------------------------------------------------------------------------------------------------
Shell binary pool memory size: 800 MB
-------------------------------------------------------------------------------------------------------------
Total available memory: 28048 MB (~1GB is always kept as a security margin)
-------------------------------------------------------------------------------------------------------------
PID: 81020, Running job as: root
-------------------------------------------------------------------------------------------------------------
- Pruning '/vmfs/volumes/BUPNAS/XSI-DC/20221213030000'...
Segmentation fault
#2 Re: General Matters » Upgrade from 2.0 to 2.1 » 2022-12-06 20:08:25
I tried that... go to "Local Voumes & remote shares" / "Set File Share Protocols"... but after selecting the volume, XSINas formats it
#3 General Matters » Upgrade from 2.0 to 2.1 » 2022-12-04 15:31:49
- cuchillo
- Replies: 3
Hi... I downloaded the new version 2.1. Is a VM, so i register it in my ESXi. The old version has a volume mounted and shared. That volume is a Virtual Disk. I have attached that disk to the new VM (version 2.1)... No problem so far... But, how can I get it mounted and shared without losing the data. The repositories of the backups made with version 2.0 are there.
In other hand, what's new in 2.1 version???
Tnx,
Dani
#4 General matters » Log format » 2022-05-10 18:04:25
- cuchillo
- Replies: 1
Hi... XSI-DC log looks like this
Performing a [1mwarm[0m backup as per the [1m--backup-how[0m argument.
[90m-------------------------------------------------------------------------------------------------------------[0m
[90m|---------------------------------------------------------------------------------|[0m
[90m||-------------------------------------------------------------------------------||[0m
[90m|||[0m[1m (c)XSIBackup-Pro 1.5.1.15: Backup & Replication Software [0m [90m|||[0m
[90m|||[0m[1m (c)33HOPS, Sistemas de Informacion y Redes, S.L. | All Rights Reserved[0m [90m|||[0m
[90m||-------------------------------------------------------------------------------||[0m
[90m|---------------------------------------------------------------------------------|[0m
(c)Daniel J. Garcia Fidalgo | info@33hops.com
[90m|---------------------------------------------------------------------------------|[0m
System Information: ESXi, Kernel 6 Major 5 Minor 0 Patch 0
[90m-------------------------------------------------------------------------------------------------------------[0m
I think that there are escape characters to give it some format... which application do you recomend to see them correctly in Windows?
#5 Re: General matters » The license.key file is more than 1 year older than the binary » 2022-05-10 18:02:21
Yes... Done... All solved :-)
#6 General matters » The license.key file is more than 1 year older than the binary » 2022-05-09 18:39:55
- cuchillo
- Replies: 2
When I run XSI Backup DC it says
"The license.key file is more than 1 year older than the binaryYou can use your key with binaries released within 1 year from purchase"
and then it works with no license.
I downloaded the key again but still says the same.
Im my user panel says End of Support: 2023-05-06T00:00:00+00:00
#7 Re: General matters » XSIBackup-DC 1.5.1.4: Information or warning treated as error » 2021-12-08 17:06:09
I get Error code 1547 too. The target of backup is XSI-NAS... It seems like XSI-Backup-DC can not get free space from XSINAS. How to solve this?
#8 General matters » Disk full notification » 2021-08-25 03:26:07
- cuchillo
- Replies: 1
When there is no space left in the datastore where the backups are made, the .locked file cannot be created and the backup fails. Beyond the maintenance of the repository on which I made a separate post, it would be useful if this failure was notified by email. Currently this is not the case since with this error the execution is interrupted. Additionally, in each email that is sent when the backup is successful, it would be useful to indicate the amount of free space in the repository's datastore.
#9 Repositories » Delete unmapped blocks » 2021-08-25 03:10:58
- cuchillo
- Replies: 1
Hi ... My backup datastore got full so I had to manually delete some dated folders containing the .map files in a repository to make room.
What I want to do now is check the repository so that those blocks that are not referenced in any existing .map are deleted.
#10 Re: General matters » XSIBackup-Pro and XSIBackup-DC combination » 2021-08-03 00:54:34
Great!!! i can rotate replicas and use only XSIBackup-DC, right?
#11 General matters » Renamed VMs » 2021-08-03 00:52:53
- cuchillo
- Replies: 4
when I use the --backup option with a VM that has been renamed (it is not named the same as the folder that contains it in the datastore) the bakcup is performed but I get errors like this
· VM: 2021-07-27T20:12:09 | Error code 4054 at file xsibackup.c, line 4054 | Error description: could not rename .vmx.tmp file to .vmx, error:
· VM: 2021-07-27T20:12:11 | Error code 4063 at file xsibackup.c, line 4063 | Error description: could not rename .vmsd.tmp file to .vmsd, error:
· VM: 2021-07-27T20:12:14 | Error code 4294 at file xsibackup.c, line 4294 | Error description: some error/s were raised while backing up: VMs(VM), error count is: 2
I understand that XSIBackup-DC somehow uses a combination of interpretation of the directory structure and the existence and content of the .vmx file to determine whether or not it is a VM and in the positive case to determine which files to copy.
It seems to me that it would be much less susceptible to errors in cases of particular configurations if, when using VMs (....), it based the decision of what to make a backup by interpreting the .vmx and that if you use a folder as a source it is limited to copying whatever is inside. (links with my post XSIBackup-Pro and XSIBackup-DC combination)
#12 General matters » XSIBackup-Pro and XSIBackup-DC combination » 2021-08-03 00:40:54
- cuchillo
- Replies: 3
Hi...
My goal is to do local backups the way XSIBackup-PRO did. In other words, get a dated folder with the VMs folders inside and ready to attach and turn on. Then, using XSIBackup-DC make a remote copy of this folder obtained with XSIBackup-PRO to a remote deduplicated repository. However, when doing the latter, XSIBackup-DC detects that the contents of the folder is a VM, tries to shut it down and take a snapshot and everything completes.
I don't know if this is the best way to do it but my goal is clear. Ready-to-use local backups that can be rotated according to the available space as was done with XSIBackup-PRO and remote backups in a deduplicated repository to take advantage of this technology to speed up copying over the internet (since duplicate blocks are not transferred).
#13 Re: General matters » XSIBACKUP-DC error for replica on 2 hosts esxi » 2020-11-05 11:27:36
Hello ... I don't know if it will be the same problem but it seems that when installing XSIBackup-DC 1.4.2.3 the directory "mail" is not created in the path "var/spool/". Try creating it manually.
#14 Repositories » XSIBACKUP NAS vmware tools » 2020-11-04 13:48:27
- cuchillo
- Replies: 1
Hi... I'm trying XSIBackup-NAS, see (c)XSIBackup-NAS Help Man Page. When the appliance is implemented ESXi says "VMWare tools not installed". I installed open-vm-tools using the command sudo yum install open-vm-tools. It was installed bun the (c)ESXi still says "VMWare tools not installed". My objetive is to saftely shutdown the OS when i restart the server (OS shutdown).
#15 Re: General matters » XSIBackup-DC GUI » 2020-08-29 13:54:50
I try to use the new GUI but when I run xsibackup-gui it says "Only one instance of the GUI is allowed at a time". I have restarted the ESXi server and I get the same result.
#16 General matters » ESXi version and XSI-BackupDC version » 2020-08-28 22:08:56
- cuchillo
- Replies: 1
Should I use v1.4.0.0 with ESXi 6.x or only with ESXi 7?
#17 Repositories » Interrupted network copies » 2020-01-14 12:38:46
- cuchillo
- Replies: 1
When a copy across the network (LAN or WAN) is interrupted, the server side (where the copy is being stored) cleans. This is not convenient in all cases. Suppose I am copying a 200 GB virtual disk and it is interrupted at 70%. When I copy the VM again, being that the cleaning removed all the blocks from the incomplete disk, I must copy them all again.
It would be very useful to enable an option such as --no-clean that leaves the blocks in the .blocklist file. You should also enable a repair option such as --clean-no-mapped to erase those blocks (which do not belong to any .map)
#18 Re: Repositories » Prune do not work » 2020-01-04 14:20:14
I have restored the backup despite the double folder and the VM has been restored successfully. So it does not seem to be a major problem but a matter of prolixity that happens with renamed VMs.
As for the use of --prune together with --subfolder, the behavior expected by me is that the purge be for each subfolder. This would allow to have a different number of backups per server (each with its own --rotate)
#19 Re: Repositories » Prune do not work » 2020-01-04 12:45:41
Since it is not possible to use --prune together with --subfolder, I have renamed the VMs including the server name on them. With 2 VMs called FILE_SERVER (one on a server called S1 and the other on a server called S2), the new names are S1_FILE_SERVER and S2_FILE_SERVER. This way the backups would be identifiable within the dated folders. When I make the backups of each of them, in this case we take as an example S1_FILE_SERVER, within the dated folder 2 folders are created: an empty one called S1_FILE_SERVER and a FILE_SERVER call with the .map files.
#20 Re: General matters » scratch » 2019-12-02 20:45:37
Great! Tnx
#21 Re: Repositories » Prune do not work » 2019-12-02 20:40:41
Ah... Ok tnx
#22 General matters » mail subject » 2019-12-02 20:38:23
- cuchillo
- Replies: 1
It would be useful that the mail subject indicates fail, warning or success like xsi pro.
#23 General matters » scratch » 2019-12-02 15:54:41
- cuchillo
- Replies: 2
I've read https://33hops.com/xsibackup-datacenter … ckups.html. I have XSI-DC installed on the prymary datastore of ESXi6 (datastore1) which is an SSD. If I understood correctly the tmp files of XSI-DC are already at this location and have 4GB of space. No corrections or tunning is needed. Am I right?
#24 Re: Repositories » Prune do not work » 2019-12-02 15:24:53
A manual prune using --prune REPO/[SUBFOLDER]/[YYYYMMAAhhmmss] produces the same result
#25 Repositories » Prune do not work » 2019-12-02 15:10:35
- cuchillo
- Replies: 6
Im doing backups in a repo... the repo is locates at REPO/ folder. I use the --subfolder option. So there is a REPO/data folder and a REPO/[SUBFOLDER] folder. Inside [SUBFOLDER] there are folders like [YYYYMMAAhhmmss] (one by backup). i have 3 and use the option --rotate=2. XSI says Pruning backup: .../REPO/[SUBFOLDER]/[YYYYMMAAhhmmss] and then says "It looks like there's only one backup folder left, you can't prune the last folder Delete the repository manually instead, this is to prevent you from accidentally removing it" which is not true.