Add a New Local Disk Repository on the v13 Backup Server

[jeongkyu]

Configured v13 as a software appliance.

Is there a way to configure Repository by installing additional disks later?

Even if you configure RAID after installing a new disk on the v13 appliance server, the UI only shows the path of the existing /var/lib/veam.

Has anyone added a new Repository?

[Gostev]

This is covered in the sticky FAQ topic.

[luis.felipe]

Veeam Support stated that it is not possible to add a repository to the VSA once it has already been initialized. They provided the following explanation:

The appliance only recognizes disks that are present at the time of installation. Any additional disks must be attached before the first boot of the appliance.

If you plan to use an RDM disk for the repository, make sure it is attached to the VM as a new and unpartitioned disk before powering on the VM for the first time. The installer should detect it and allow you to select it as a repository during the setup process.

There is no supported method to add or expand repository disks after installation. All required disks must be present before the first boot.

Alternatively, you can add external Linux (or Windows, SMB, NFS, or deduplication appliances) servers as additional repositories from the Veeam console; however, these will not be internal repositories of the appliance.

Manually modifying the internal disk or repository configuration of the appliance after installation is not supported, as it would place the system in an unsupported state.

[JulianBlue]

Does the limitation on adding disks also apply to a "simple" Veeam Infrastructure Appliance" with roles of proxy and non-hardened repository?

[Mildur]

Yes. For both Veeam Software Appliance and Veeam Infrastructure Appliance.

Best,
Fabian

[HardWired]

You have got to be kidding that I cant just either enlarge the vm disk holding the repo, or even add another disk to create another repo location on the appliance????????
As if no admin ever would want to add additional space for more backups quickly and easily (if they didnt want to bother booting up yet another linux to to create a nfs nas to point to)
I thought this appliance was supposed to make life that much easier yet something as simple as enlarging the repo vm disk isnt part and parcel of the appliance (as it is just a standard linux vm in the background so adding/resizing lvm disks is a pretty basic thing todo for every other single linux vm ive managed over the years)
Just my rant, which im sure will be agreed by any future admin who decides to move to the appliance and then find this 'feature' out

[Mildur]

Hi HardWired,

This feature (adding disks, expanding storage) is on our roadmap for 2026.

Thanks,
Fabian

[RedVision81]

this is really a pain to be honest that you cant extend or add disks.
nevertheless i deployed the ova as a vm for testing, and before powering on the first time i changed and added an additional disk to the vm:

Hard Disk 1: 240 GB
Hard Disk 2: 255 GB
Hard Disk 3: 111 GB

After the first boot, the appliance created its default backup repository : /var/lib/veeam/backup with 206.9 GB Capacity
But the other disks with 255GB and 111GB are not shown for creating another repository. Is this an usual behavior?

i would have thought, the appliance installs its operating system on disk 1 and the other disks could be used for creating a backup repository??!

Thanks

Peter

[Mildur]

Hi Peter,

Regarding disk sizes:

• Veeam Software Appliance: minimum disk size is 240 GB
• Veeam Infrastructure Appliance: minimum disk size is 120 GB
• Disks smaller than the minimum are ignored by design.

If you deploy the backup server via the ISO, the installer will use the smallest disk > 240 GB for the operating system, Veeam Backup & Replication software and configuration database. All other disks > 240GB will be combined into an LVM group for backup storage and the guest file system catalog. You cannot add additional storage and extend repositories yourself today. You will have to wait for this feature to become available later this year.

Best,
Fabian

[RedVision81]

Hello Fabian,
sorry but i dont get it. i deployed another vm now, and before powering on resized disk 2 and added disk 3:

1. 240 GB
2. 270 GB
3. 280 GB

Default Backup Repository is still the same /var/lib/veeam/backup 206.9 GB
But there is no other backup repo (550GB or 270/280 GB) available to add.

i understood i cannot add or change disk size etc. later (after setup), but before the first time i power on the machine, i would be able to, no?

Regards

Peter

[Mildur]

Hi Peter,

If you need a larger backup repository in your Veeam Software Appliance, please deploy it using the ISO.
With an OVA import, disk size is fixed (as far as I remember), and OVA deployment will not re-initialize disks during first boot.

1.) Create a VM with two virtual disks:
- Disk 1: minimum 240 GB
- Disk 2: size based on your estimated backup storage requirement
2.) Boot the VM from the Veeam Software Appliance ISO.
3.) Run through the installer until you can provide network, NTP, and user settings.

As already confirmed, we will provide the functionality to extend disk size later this year, but right now thats the workflow you have to follow.

Best,
Fabian