Forum ©XSIBackup: ©VMWare ©ESXi Backup Software
MenuYou are not logged in.
- Topics: Active | Unanswered
#1126 Re: Speed » Achieving maximum speed » 2019-08-26 17:29:33
LZJB compression is almost RAM fast.
There isn't any menu in XSIBackup-Datacenter, it's all command line driven. In any case it's use is much simpler than XSIBackup, thus incorporating a menu wouldn't be as useful as in the case of XSIBackup-Pro
#1127 Re: © OneDiff » Takes forever to remove snapshots » 2019-08-26 17:03:35
That has nothing to do with SSH ciphers. By what you describe there's something which is not working quite well, or something you are not taking into account.
As you say, the delta snapshot should not be 100 GB unless you are generating that amount of data in between backups. We don't know if you posted this before activating the cache in your disk controller, in any case that would never explain why the delta snapshot is that big.
Check whether you are adding memory to the snapshot ([b]--snapshot=includememory[/b]), which you shouldn't do unless you have some very good reason to. Nonetheless I don't think your memory is 100 GB for that VM.
What you describe seems to be an anomaly on its own. Even if you were not using XSIBackup the snapshot should not be that big.
#1128 Re: General matters » Unable to enumerate all disks » 2019-08-26 16:31:21
This is one of those annoying things that HP does (apart from rejecting their own ink cartridges).
In many HP servers the disk controller has a cache that, for some obscure reason comes turned off. Unfortunately many people never realize and end up using their servers at a fraction of the disk speed they are able to achieve.
#1129 Re: General matters » Error NOVM2BAK with REGEX and that doesn´t work » 2019-08-21 17:52:38
Sorry Helga, we didn't realize that this is a Pro feature, the REGEXP module is in the [b]src/pro/vmsregexp[/b] file.
#1130 Re: © XSITools » XSITools fails to create backup repo » 2019-08-21 17:51:10
This issue has been solved today, version 11.2.9 is already available to all Pro users. If you don't want to update everything, you may just overwrite the src/xsitools file to fix it. You may want to overwrite the src/version file to to update the version number.
#1131 Re: © XSITools » XSITools fails to create backup repo » 2019-08-21 17:19:04
The exact cause of this bug is that the function [b]getSha1Zero[/b] at around line 50 in the src/xsitools module is returning an empty string in some circumstances, still determining...
Thus, although the check of the SHA1 50M zero block (49886561f8e26ed5e2ae549897a28aaab44881bd) should be skipped, as zeros are not saved, it's existence is still being checked, returning the missing block information.
This is not a real problem, apart from the inconvenience of the wrong error itself.
Hebasto, if you can't restore backups contact support, yours is a different issue.
#1132 Re: © XSITools » XSITools fails to create backup repo » 2019-08-21 16:56:44
We have been able to reproduce the error when checking individual map files. This is a bug only since zero blocks should not be checked, we'll fix it in next release.
Hebasto, it seems to be indeed copying every block to the repo.
Please especify what you mean by "Restoring from a backup repo fails as well"
Post the log from the restore or contact support, plain comments are not of great help.
Blocksize is 52428800 bytes
----------------------------------------------------------------------------------------------------------------------------------
Compression has been set
----------------------------------------------------------------------------------------------------------------------------------
Backing up via XSITools
----------------------------------------------------------------------------------------------------------------------------------
File name: Abso_1-flat.vmdk, File size: 107377328128
Block size: 52428800, Block count: 2049
Disk usage: 2209349632
-------------------------------------------------------------------------------------------------------------------------------------------
2049/2049 blocks | Processed 100%
Previous block count: 1476
Current block count: 1550
----------------------------------------------------------------------------------------------------------------------------------
Time taken: 311 seconds
Avg speed: 329 mb/s#1133 Re: © XSITools » Problem backup performed 7 times in one scheduled job » 2019-08-21 16:43:08
Thank you for the feedback, yes, that was for sure the issue in your case.
Best
#1134 Re: General matters » Doing warm backup does not report about VM start » 2019-08-21 16:30:07
We'll treat this as a feature request, thank you for your feedback.
#1135 Re: General matters » Unable to enumerate all disks » 2019-08-19 14:40:43
Just a quick advice: if you use HP servers, don't forget to turn your controller cache on, it comes off by default.
Don't use Vmkfstools to make historical backups, unless you have plenty of room and time to do it. [b](c)XSITools[/b] was conceived just to do that, it will use deduplication and is zero aware, so it will multiply the amount of available space by many times.
Yes, [b](c)Onediff[/b] uses a snapshot to hold the differential data between backups. If you backup the result of a Onediff mirror, you should get a regular working VM, as the resulting mirrored image is consolidated into a single -flat.vmdk file per disk.
XSIBackup tries to handle most of the situations and tweak the paths, so that the resulting VMs are directly usable. In any case, depending on what is the layout of your original VM and what might have happened during the backup, you might have a .vmx file that is not pointing to a bootable disk. Just as long as your main [b]-flat.vmdk[/b] files and the descriptor files (plain .vmdk) are there, you can easily fix that situation by editing the .vmx file.
[url=https://33hops.com/esxi-snapshot-errors-and-solutions.html](c)XSIBackup: snapshots, errors and solutions[/url]
#1136 Re: © XSITools » xsitools backup failing » 2019-08-19 14:25:53
That looks like a full or broken disk. This kind of message [b]Input/output error[/b] usually means that the storage layer is not able to handle the request for some reason, as said, that usually has to do with full or faulty disks.
If the datastore [b]/vmfs/volumes/Backup[/b] is some kind of external device (NFS, iSCSI) it could also mean some cable got disconnected.
#1137 Re: © XSITools » Problem backup performed 7 times in one scheduled job » 2019-08-19 14:22:57
The ESXi crond daemon is very primitive, it lacks any initialization control, thus you could have loaded it 7 times into memory without noticing.
You may use the Tools menu in the GUI to reinitialize the crond binary.
[img=Reinitilize crond]https://33hops.com/images/reinitialize-crond.png[/img]
#1138 Re: © XSITools » XSITools fails to create backup repo » 2019-08-19 14:14:04
We'll check that, it could be a bug. Nevertheless that is the SHA1 hash of a 50M block of zeros. So XSIBackup will rebuild the VM without issue.
dd if=/dev/zero bs=$(( 1024*1024 )) count=50 2>/dev/null | openssl sha1#1139 Re: General matters » SEGFAULT condition was trapped » 2019-08-13 10:16:46
Well, that's right, Linux file systems (ext4, XFS) are much more suitable to host deduplicated backups than VMFS, which has been mainly thought to do the opposite, namely host huge virtual disk files.
Nonetheless to use a Linux OS as the target of your backups you would add the public key in the ESXi box to the Linux host, not the other way around, which is what you are trying to accomplish.
On addition, ff you use CentOS, RHEL, Fedora, you will have the advantage of being using an OS which has previously been tested by us.
#1140 Re: © OneDiff » ERROR: cannot locate .ERR file at ... » 2019-08-11 14:59:55
You are having too much problems, there must be something wrong in your setup or in the way you are trying to use XSIBackup.
Contact support and provide access to your system for revision, if you are going to request some further help.
#1141 Re: © OneDiff » ERROR: cannot locate .ERR file at ... » 2019-08-11 14:58:05
VMFS versions must be coherent both VMFS5 or VMFS6 same for HW versions, you can't use HW version 13 on ESXi 5.5 per instance, you can use HW version 8 on ESXi 6.5.0 though
#1142 Re: General matters » Internet access required? » 2019-08-11 10:53:23
Thank you for your feedback.
The block of code that manages this is at aprox line 275
if [ "${keyvalstr//--install-cron/}" != "${keyvalstr}" ]
then
drawline
installCron ${cronuser}
drawline
xsib_shutdown
fiSo when you use the [b]--update-cron[/b] argument, this code is invoked really early and then the program exits, XSIBackup does not even print the header for this task and the version check function is not even called.
The only network function that could be interfering in your case is maybe the hostname lookup, just wondering...
The thing is that we have blocked the HTTP client in different hosts and we can't reproduce your issue. The [b]--update-cron[/b] functionality works as expected with no delay.
#1143 Re: General matters » Centralized backup » 2019-08-11 10:32:01
Since XSIBackup-Datacenter is a binary it's a lot easier to manage backup chaining by just inspecting the exit codes.
#1144 Re: General matters » Error: Signal 13 received » 2019-08-11 10:30:12
Thank you for your comments, we will improve that behaviour in next versions.
#1145 Re: General matters » SEGFAULT condition was trapped » 2019-08-11 10:28:31
Add the key manually.
We don't announce XSIBackup to be compatible with any Linux distro out of the box. Our set of reference distros, the ones we do test Linux functionaly on is: RHEL, CentOS, Fedora and with a high probabilily any derivative distro, unless it has diverged too much.
#1146 Re: General matters » Error: Signal 13 received » 2019-08-10 09:21:57
Kill the process manually, you are using a beta trial version, we will improve these issues in future versions.
#1147 Re: General matters » Internet access required? » 2019-08-10 09:20:00
Have you set checkver=no in the conf/xsiopts file?
#1148 Re: General matters » Internet access required? » 2019-08-09 18:13:22
The only process that connects to the outside world is the new version check. It works over HTTP port 80, that should not cause that much delay though.
You might be observing two issues simultaneously and assuming that they are one. If you run a user job and kill it, it might take some time (some seconds) for all subprocesses to unload from memory. If you then run a new user job, you will see that message, as the new user job will kill any previously launched user job.
#1149 Re: General matters » error: XSIDiff error, details: rekeyed outbound cipher » 2019-08-09 10:29:01
That is an OpenSSH error that has to do with the SSH tunnel keying
Contact support, there's always a chance that it's a combination of OpenSSH versions that causes it but it looks more like some issue with your job.
#1150 Re: General matters » Error NOVM2BAK with REGEX and that doesn´t work » 2019-08-09 10:24:08
XSIBackup uses grep regex engine. Practice with it in the command line before using your regexp.
echo "Ubuntu-VM" | grep -E "^Ubuntu"