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

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


You are not logged in.

#1 Re: General matters » Understanding the capabilities of XSIBackup » 2019-06-19 17:02:13

What will pricing be like for a small business operating only 1 or 2 physical servers? XSIBackup-Pro was of interest to us since we don't have big money to throw around on very expensive licenses.

#2 Re: General matters » Understanding the capabilities of XSIBackup » 2019-06-18 18:00:11

This seems like a usecase assumption to me. Is there any way to force deduplicating snapshots as well? It seems every backup it copies the same snapshots that were also present in previous backups, thus wasting a lot of space (as our snapshots are >20GB in some instances). I know this is not how most people use vm snapshots, but since this is already the workflow our client already uses we have to run with it as best as we can.

Thank you kindly for your time and responses so far smile

#3 Re: General matters » Understanding the capabilities of XSIBackup » 2019-06-17 17:15:02

I indeed did not delete the .xsitools file as it didn't show up with regular ls (and I did not initially use -a). Thank you for this pointer, all seems to work now.

Can I ask why the snapshots aren't deduplicated when backing up with tool XSITools:z? Is there some reason behind this design choice that I'm not seeing? It's not vital to us, but it would be nice if there's some way to enable this as we have some vm's with large snapshots that are similar/the same between backups.

#4 Re: General matters » Understanding the capabilities of XSIBackup » 2019-06-13 13:31:01

I got this message on the first run where it created the repo itself, hence why I'm asking why it would create a non-compressed repo when I'm explicitly asking it to make a compressed backup.
I'll try making a new backup to a new empty folder to see it that produces different results.

#5 Re: General matters » Understanding the capabilities of XSIBackup » 2019-06-11 17:28:41

Running some tests I'm starting to see some issues with --backup-prog=XSITools:z. I get the following error:
XSITools Error XSITCMP1: /vmfs/volumes/volname/Backup is an uncompressed repository, you cannot backup to it with compression enabled

Everything seems to work fine if I disable compression (by not using :z). I can't find this error in the documentation. The NFS share is mounted as NFS3.

#6 General matters » Understanding the capabilities of XSIBackup » 2019-06-06 12:59:00

fsolsup
Replies: 13

Our setup is this:
- NAS storage host running NFS server
- ESXi free host machine running <10 VM's from local SSD datastore, backup folder from NAS NFS mounted as datastore
- Devices are connected on gigabit LAN, potential upgrade to 10Gbit LAN if gigabit lan doesn't suffice
- VM sizes range from 5GB to about 60GB currently, I don't expect them to grow larger than ~120GB

What we want to achieve:
- Automatic backup every time interval (every week or something)
- Backup should include the snapshots of the VM
- Automatic removal of "old" backups, either by setting maximum size of backup storage, or by setting to keep X previous backups

Nice to have:
- Compression and/or deduplication on the NFS backup store


It seems to me the different "Diff" packages use is only sending delta info over the network/to the backup store as to reduce network traffic and increase backup time. This doesn't seem to be of crucial interest to us (potential nice to have).
It seems to me that XSITools would allow the deduplication that I put down as a nice to have, requiring the Pro version.

I can't for the life of me find if the must have features I described can be achieved on the Free version though. For example: I can't find the documentation that clearly states that ESXi VM snapshots are preserved, even though I see some talk about it on the forum. In one of the videos it shows a backup with Vmkfstools where it states it's deleting all snapshots: this would be unacceptable for us at this moment.

Maybe someone can shed some light on this.

Board footer