Veeam Backups & Replication

[mmokrzycki]

Hello,

We are using Veeam b&r ce 6.3.1 and are wondering if creating Veeam recovery media from the backup server supports saving the file to a remote location.

Currently, we can only save the file to the server. When we get to the "specify local folder to create recovery image in:" we can only choose a local path. Is there a way to choose a remote path?

[marina.skobeleva]

Hi Matt, and welcome to the Community!

If I understand correctly, you’re using VBR CE v12 with Veeam Agent for Microsoft Windows 6.3.1.

When creating Veeam Recovery Media in Veeam B&R, the wizard only allows saving the ISO file to a local folder, not directly to a remote UNC path.

Alternatively, Veeam Agent offers more flexibility for recovery media creation, allowing you to save the recovery image either locally or to a network shared folder. You may want to try creating the recovery media directly from the Veeam Agent. More details can be found in our Help Center.

Let me know if you need further details!

[mmokrzycki]

Hi Marina,

Yes correct VBR CE v12 with Veeam Agent for Microsoft Windows 6.3.1. Thank you.

Question about this "Alternatively, Veeam Agent offers more flexibility for recovery media creation, allowing you to save the recovery image either locally or to a network shared folder. You may want to try creating the recovery media directly from the Veeam Agent." If we install Veeam Agent on all our computers that we want to backup but manage the backup from the server, would that allow us to make the recovery media and save it remotely?

[marina.skobeleva]

Unfortunately, Veeam Backup & Replication does not provide native functionality to create recovery media directly onto a network share - only locally on the server.

A possible workaround for your case could be:

• Save the .iso files to a specified local directory, then use a PowerShell script to move them to a network share.

• Add this script to the Windows Task Scheduler to run automatically.

I hope this information helps.

[mmokrzycki]

Thank you Marina,

So even if we upgrade our version to a paid version, that wouldn't help?

Also, another question, this is our current retention policy: 7 days GFS "Keep weekly full backups for: 2 weeks, if multiple full backups exist, use the one from: Saturday". Our goal is to perform a full backup and daily incremental backups. At the end of the month, we will zip the folder and place the backup in another location. Example: Full backup starts 1/1/2026, followed by daily incremental backups for ~30 days. Once the next full backup starts, zip up the folder and place it in a remote location.

Let me know if what we have is correctly configured.

[marina.skobeleva]

Hi Matt,

I have good news for you! In v13.0.1 (which was just released), there’s a workaround for your case with network shared folders.

If you map a network share as a network drive under the appropriate user account, you can then select this mapped drive as the destination when creating recovery media.
You’ll need to launch the VBR console under the same user account that mapped the network drive, because only that user will see the mapped drive. Then, you can save the ISO files directly to the network drive.

Regarding your retention policy, it looks like it is sufficient to configure the Advanced Backup settings for active full or synthetic full backup. Schedule an active full or synthetic full backup to run once a month (for example, on the first day of each month). This will ensure you have a monthly full backup along with daily incremental backups, making it easy to archive the backup chain at the end of each month.

[mmokrzycki]

Noted thank you.

We've noticed that vm backups allow synthetic full backups but non-vms only allow active full backups, is there a reason for this?