Hey,
I extented my Partitions on our Fileserver. As a result, our VBK Files created by our daily veeam backups fails due to os limitations of filesize...
Is there any way to tell Veeam Backup&Replication 7 ( 7.0.0.871 ) to split backups?
I tried to make multi-Backups per Server per DISK, but veeam does not accept this settings or I am doing it wrong
May some1 of you could verify this?
I think the Red Bubbles are matching together. But when I do it like this, my Backup Size is caclulated without any change...
Hi tschulian and welcome to the community!
You can backup volumes separately. By the way, version 7 is more than 3 years old now. I would definitely suggest you to upgrade, since newer version are much more scalable and work fine even with 90TB VMs.
Thanks!
as a personal best practice I always create one vmdk per guest OS partition. That way I'm always able to expand the VMDKs and the partitions in the guest without the need of using third party software to expand partitions inside the guests. Or how would you now expand your C:, D:, and E: if they are full?
If this is a p2v converted VM, then you used the default options of the VMware converter, which does not split the partitions on a single physikal disk (or virtual drive in a raid). But its always worth to do the extra work before converting by assigning seperate vmdks to the partitons.
That being said, the red bubble in your right screenshot presents the same as the left red screenshot, because Veeam uses the VMDKs in its GUI, not the partitions inside the guest. Thats why you see the total size of 2.1TB... its the size of the VMDKs, not the size of the data inside the guest.
If you have enough space I would advise you to do a v2v convert to have seperate VMDKs per Windows partition.
You spoke about 2TB limitations of the os. WHich OS do you mean? The one which is hosting the backup repository?
I tried to make exlusions but this wont take affect....
I am getting this Error
"Creating snapshot Error: Datei <unspecified filename> ist größer als die vom Datenspeicher '<unspecified datastore>' unterstützte maximale Größe."
File <unspecified filename> is bigger as the supported maximum size of the Datastorage.
yes my vmdks are truely 2.1TB I just checked it. OK, so the red bubbles match together ...
Yeah, I am new in this company and they are still using version 7.
I need a workaround to backup my 2TB++ disks. Any ideas other than upgrading to 9 ...
regards, and have a nice day!
I think all relevant information is within this VMware KB article: https://kb.vmware.com/selfservice/micro ... Id=2058287
However I'll PM you to find the solution (as we both speak german this could be easier for us). If we'll find a solution I'll post it here for all
I think I've found the reason:
He might be using the VM on an upgraded VMFS5 (former VMFS3) volume, or its a native VMFS5 volume wich has been created under vSphere 5.0 / 5.1 resulting in not being able to create files larger than 2 TB. As his VMDK is already at 2TB vSphere won't be able to create a snapshot (which could get as big as its source VMDK) plus the size of the snapshot-metadata resulting in a file bigger than 2TB.
In my opinion he has only some options:
Move all the VMs to another datastore over the weekend and recreate the datastore under native vSphere 5.5, or combine this method with mentioned VMware converter to split his VMDK in several VMDKs to overcome future problems inside the guest (further expanding), or he has to save the snapshots on another datastore which is created under vSphere 5.5
