Free disk space on datastore

[guitarfish]

I understand that there should be around 25% free space on a datastore for Veeam to use for snapshots and other purposes. On my Veeam server itself, I have a couple 4TB disks that are solely used as repositories for Veeam backups. These disks are not backed up, there's no VMs there. Is it OK to expand the size of the datastore to use the entire disk? I'd like to maximize the amount of backup space.

[foggy]

Could you please clarify on whether you're after space on backup repository or source datastore, where VM disks reside?

[guitarfish]

I am looking to maximize space on the backup repository. I'd like a config like this, no free space on Disks 2 & 3:

Example:
ESXi Host "BKP"
Disk 1 - 300GB
Disk 2 - 4TB
Disk 3 - 4TB

VM "VM-BKP":
Disk 1 - Datastore 1 - 100GB Drive C: - has VM files, Windows OS, Veeam B&R application. 200GB free space
Disk 2 - Datastore 2 - 4TB - Repository for backup files (no free space)
Disk 3 - Datastore 3 - 4TB - Repository for backup files (no free space)

[foggy]

If you're talking about formatting the entire host disk as NTFS and presenting it to Veeam B&R through iSCSI, then this can be done.

[guitarfish]

Not iSCSI. It's DAS, just drives in a tower. So I don't have to worry about slack space for disks used as repositories, correct?

[PTide]

Hi,

I am looking to maximize space on the backup repository. I'd like a config like this, no free space on Disks 2 & 3:

Example:
ESXi Host "BKP"
<...>

Ok, and how does you current config look like?

[guitarfish]

The current config is the same as the example, except Disks 2 & 3 have a around 500GB free space. I'd like to expand the datastores to use that space for backups.

[foggy]

You can expand disks to the entire drive size, no issues with that.

[guitarfish]

Thank you for this feedback. In my scenario, it seems like the repository drives should be Independent - Persistent. This way they wouldn't be included in snapshots which I would make of the C: drive (OS) when patching, etc.

[foggy]

Yes, I'd note, however, that your design implies storing backups on the same physical host where your source VMs reside and, in addition to that, on VMFS. Both are strictly against best practices.

[guitarfish]

Yes, I'd note, however, that your design implies storing backups on the same physical host where your source VMs reside and, in addition to that, on VMFS. Both are strictly against best practices.

No. VMs are on different hosts.

Drive C: in my example above is Windows OS and Veeam B&R 8.0. Nothing else on this box. All other drives are Veeam repositories. I have 3 other hosts that have the production VMs. It's their data that is being backed up. I only snapshot Drive C: to patch my VM running Veeam.

[foggy]

Ah, ok, for some reason I thought you're backing up VMs residing on the same ESXi host. Then just the VMFS note applies.