Thursday, July 18, 2024
Thinware Forums
ForumsForumsThinware vBacku...Thinware vBacku...DiscussionsDiscussionsBackup without double the spaceBackup without double the space
Previous Previous
Next Next
New Post
 4/6/2016 7:49 PM
 Modified By smbecker3673  on 4/6/2016 5:56:25 PM

I tried using this to backup a free esxi in ssh mode. The issue I had is Thinware vBackup seems to create a snapshot on the esxi host first. The exsi server has about 2 TB total. About 1.5 TB is provisioned for the VM I am trying to do an image backup of. 250 Gig is used by another VM. So when it tried to create a snaphot for the VM, without a warning BTW, it tried to use more than what is available and shutdown both VMs, until I deleted the snapshot that never finished. Also, the VM that has 1.5 TB provisioned is not even using 25% of that 1.5 TB. Creating the a snapshot seems to require double the space that is provisioned, which seems stupid especially since most of it is free space and the backup is being saved on an entirely different machine and this would mean you have to keep the same amount free on the esxi host as you have provisioned for VMs. Is there anyway to create a backup image without have the esxi storage location losing 1/2 of it storage space to acomidate for a snapshot? I would really like to use this as Veeam will not work on free esxi since they not longer support the ssh and only use api, might even have the same issue with that as I have been unable to try it, but at this point trying to create an image backup using Thinware vBackup just breaks the entire esxi host until the snapshot is deleted and never actually backs anything up.

New Post
 4/7/2016 2:03 PM
Accepted Answer 
vBackup is a "snapshot-based" backup utility. Being snapshot-based, the ability to create a snapshot of the VM in order to perform a backup is required. This is just like all other agentless VM backup products.

The reason vBackup (and the other agentless VM backup products) use snapshots is because this is the only way to remove the read lock on the VM disk files that need to be backed up. If you were using an agent-based backup solution this would not be required because the backup process runs inside the guest OS of the VM.

To ease your concerns though you need to understand that all of the snapshot operations are managed and performed by the ESXi host server. vBackup simply requests the host server to perform the snapshot operations at the proper times during the backup process.

Also, the provisioned space scenario you explained is simply how snapshots work in vSphere. Given the situation you have described you should get the same result if you were to use Snapshot Manager in vSphere Client to create a snapshot. Here are some links to VMware KBs that explains snapshots and how they work.

Hope this helps.
New Post
 4/7/2016 7:42 PM
 Modified By smbecker3673  on 4/7/2016 5:42:50 PM

Thats what I thought. Wasn't a bash on the software here. Was just hoping there was another way. Hopfully, I can figure out how to use a USB drive to become a datastore in esxi to hold the snaphot.

Previous Previous
Next Next
ForumsForumsThinware vBacku...Thinware vBacku...DiscussionsDiscussionsBackup without double the spaceBackup without double the space

Thinware Community
Membership Membership:
Latest New User Latest: eklipa
New Today New Today: 0
New Yesterday New Yesterday: 1
User Count Overall: 41211

People Online People Online:
Visitors Visitors: 42
Members Members: 0
Total Total: 42

Privacy Statement  |  Terms Of Use
Copyright 2007-2019 Thinware, Inc.