You are not logged in.
Pages: 1
Thank you for the answer, appreciated!
Since you need every cent (and I totally support that) I'm not suggesting a free DC version but rather a DC version for non-commercial/home user e.g. shareware or something.
I am happy to pay a home user fee if you ever decide to go that way. I just love to have a block based copy.
Regardless good work on this product, you are one of the very few backup solution out there that doesn't require a dedicated cumbersome VM just to run a backup.
Thank you.
Hi there, I was wondering...
Could the DC version may be made available to home users like me?
Personally I have 4 VMs in total on my home network and essentially only 1 VM needs remote backup, that's all :-)
I appreciate there's the free version but I would be really interested in the additional features only DC offers.
Not looking for a give away here but was genuinely wondering if you would consider either:
- like many other vmware commercial software, release a unrestricted version for e.g. max 2 VM
- change the charging model and charge per number of VM?
Ultimately home users can help you in the usage in different scenario and with bug reporting.
Just an idea.
Many thanks!
Due to the limitation documented in this post:
https://33hops.com/forum/viewtopic.php?id=48
I've now developed xsi-backup within a custom made script. Essentially rather than backing up remotely (as I'm not willing to do this as root), I'm doing a hot copy of the VM in the same datastore, then I'm manually calling rsync to transfer the file with --inplace parameter to speedup things.
Just one question: xsibackup doesn't allow you to be called it within the script as the end of the procedure the it terminates with:
echo "XSIBACKUP_EXIT_STATUS=$ERR_FILE_SIZE"
xsib_shutdown
drawline
that xsib_shutdown kills the script itself. I'm not sure what is the reason for calling such a function at the very end but I just wanted to report that to be able to use e.g. the following script:
#!/bin/sh
/vmfs/volumes/boot/xsi-dir/xsibackup --backup-point=/vmfs/volumes/boot/xsi-dir/BACKUPS/ --backup-type=custom --backup-vms="Centos7" && /vmfs/volumes/boot/xsi-dir/rsync -aP --inplace /vmfs/volumes/boot/xsi-dir/BACKUPS/Centos7/* backupuser@backupsystem:/media/2TB/home/backupuser/vmware/Centos7/
that last occurrence of xsib_shutdown within xsibackup needs to be quoted.
Regards
You can backup to a datastore or you can create a script that deletes your old snapshots after the backup cycle has finished.
I'm sorry if I insist, but I personally think it is conceptually wrong that I go and run my own script (and schedule) beside xsibackup to keep control of the storage.
Xsibackup creates the data, so it would be (once again in my opinion) a good idea to a control implement within the script itself similar to the one I provided in my example above.
my 2 cents
XSIBackup makes use of the snapshot options available in the ESXi system, it does not decide anything in regards to how big the snapshots will be, with the exception of the includememory option: https://33hops.com/xsibackup-help-man-p … l#snapshot. Thus, the size of the snapshot will depend on your VM config and how you use your data.
The way snapshots are managed by XSIBackup depends on the type of backup you are performing, please, provide some minimum information to get a concrete response. If you are performing an Rsync backup, XSIBackup will preserve the snapshots on the remote end. Some people might find it extremely useful to keep the snapshots on the backed up VM, you can consolidate them by deleting the snapshots.
About the second point: Ok understood. My point (I think) is still valid.
If I run the backup e.g. daily, I will get 1 additional snapshot file every 24 hours. I understand the answer as per above, but this in my case is unwanted and eventually use lots of precious storage.
I'm wondering if the script itself could force a control to remove all the snapshops files on the destination apart from the last N where N is a number of snapshots (e.g. 3) or a timeframe (anything older than 30 days).
N=30
ssh root@BACKUPHOST 'find /vmfs/volumes/3TB/BACKUP/213w -type f -name '*.vmsn' -mtime +30 -exec rm {} \;'
Thanks
I'm trying to get my head around on different issues:
- I have a running VM with Centos7, the disk is literally 40Gb and the VM has very little activity.
As part of the differential backup it appears like a min of 10GB snapshot file is created hence 1/4 of the VM needs to be retransferred which is not a massive issue but just to understand as I would expect the snapshot file to be way smaller.
- I can see the Snapshot created on source, transferred on destination and removed from the source once the backup is completed. However the destination folder retains the snapshot file(s) after the backup is completed. Is there any way to consolidate the snapshot on destination?
There's otherwise a serious storage consideration to be address.
Thanks
You cannot espeficy a username in the --backup-point argument by now.
Compatibility with other *NIX systems has been introduced only in the latest versions of XSIBackup and support by now is limited to the implicit user you are logged in at the ESXi system. Due to the nature of ESXi, only the root user or other user with basically the same set of permissions would be able to run all XSIBackup commands.A workaround by now would be creating a user with the needed permissions to execute XSIBackup successfully (as commented above only a user with a full set of permissions could work), and then run XSIBackup under that user's security context. XSIBackup would then use that user to authenticate against the remote system.
Ok thanks. I suppose a minor modification to the core xsibackup script (while parsing the --backup-point) would do the trick, but I appreciate this is not available right now.
Thank for the answer!
Thanks that did the trick!
I suppose I will have to modify this again once a new version is released.
Thanks again.
I have a linux box I'd like to back up my VM into.
When I try to specify the backup-point in the form user@address:22:/home/mysuer the script complain about the user@ not bein a hostname.
[root@BLUE:/vmfs/volumes/53bfff9d-7c46de0d-9c45-00e081d04c38/xsi-dir] cat backup_lan.sh
./xsibackup --backup-point="backupuser@cisono-2016:22:/media/2TB/home/cisono/vmware/Centos7" --backup-type="custom" --backup-vms="Centos7" --date-dir=yes --backup-prog=rsync
[root@BLUE:/vmfs/volumes/53bfff9d-7c46de0d-9c45-00e081d04c38/xsi-dir] ./backup_lan.sh
#####################################################################################
# #
# (c) XSIBACKUP-FREE 9.0.2 | Backup for (c) VMWARE ESXi Hypervisor by 33hops.com #
# #
#####################################################################################
XSIBackup PID: 110657 BLUE
Sun, 02 Jul 2017 17:13:00 +0000 IPv4: 10.10.9.98/255.255.255.0
VMware ESXi 6.5.0 build-5310538 (c) Rsync 3.1.0 as opt. dependency
-----------------------------------------------------------------------------------------------------------------------------
getaddrinfo() for "backupuser@cisono-2016" failed (-2: Name or service not known)
The --backup-point is not a directory and can't be evaluated as a server either
backupuser@cisono-2016 can't be evaluated as an IPv4 address
It appears like the script assumes the existence of a "datastore1"
[root@BLUE:/vmfs/volumes/53bfff9d-7c46de0d-9c45-00e081d04c38/xsi-dir] cat ./backup.sh
./xsibackup --backup-point="10.10.10.98:22:/vmfs/volumes/3TB/BACKUP/213w" --backup-type="custom" --backup-vms="Centos7" --date-dir=yes --backup-prog=rsync
[root@BLUE:/vmfs/volumes/53bfff9d-7c46de0d-9c45-00e081d04c38/xsi-dir] ./backup.sh
#####################################################################################
# #
# (c) XSIBACKUP-FREE 9.0.2 | Backup for (c) VMWARE ESXi Hypervisor by 33hops.com #
# #
#####################################################################################
XSIBackup PID: 101145 BLUE
Sun, 02 Jul 2017 09:33:02 +0000 IPv4: 10.10.9.98/255.255.255.0
VMware ESXi 6.5.0 build-5310538 (c) Rsync 3.1.0 as opt. dependency
-----------------------------------------------------------------------------------------------------------------------------
Service OpenSSH ready at server 10.10.10.98:22
-----------------------------------------------------------------------------------------------------------------------------
Mirroring to server 10.10.10.98 port 22
Checking Rsync exists on the other side...
xsibackup-rsync needs to be copied/updated in the remote server
mkdir: can't create directory '/vmfs/volumes/datastore1/': Operation not permitted
scp: /vmfs/volumes/datastore1/xsi-dir/bin/xsibackup-rsync: No such file or directory
Done!
Can this remote xsibackup-rsync path location be customised?
Thanks
Pages: 1