Agent-based backup of Windows, Linux, Max, AIX and Solaris machines.
Post Reply
parneye
Enthusiast
Posts: 38
Liked: 1 time
Joined: Oct 28, 2011 12:58 am
Full Name: James
Contact:

Veeam Agent Job Volume Exclusions

Post by parneye »

Veeam B & R 11
Job Mode: Type - Server, Mode - Managed by backup server.
Backup Mode: Volume level backup.

Apologies if this is answered somewhere else, but I cannot seem to find it.

We use volume exclusions for our Veeam Job
Veeam B & R 11
Job Mode: Type - Server, Mode - Managed by backup server.
Backup Mode: Volume level backup.
Objects -> "Backup all volumes except the following".

These exclusions apply to all the VMs that are part of the job, but I was wondering if there is a way to exclude the volumes for only some of the VMs, like you can in a Veeam backup job for vSphere.
We don't want to have to create separate Veeam jobs, and we don't want to have to destroy this job and remake it.
Is it possible to do it via registry or some other way on the actual servers, or something that is easy enough?

Thanks
Mildur
Product Manager
Posts: 9848
Liked: 2607 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Veeam Agent Job Volume Exclusions

Post by Mildur »

Hi James

Can I ask why you do not want to backup the vm’s with a vm backup job? Why are you using an agent? Are there certain requirements on your site to use the agent?

Volume exclusion for a specific agent in a single job is not possible yet.
I have already created a feature request in this topic:
post423144.html#p423144

But there is a possibility to use the registry (FilesNotToSnapshot Key) to exclude certain paths or files. I have never used it by myself:
https://www.veeam.com/kb3236
Product Management Analyst @ Veeam Software
parneye
Enthusiast
Posts: 38
Liked: 1 time
Joined: Oct 28, 2011 12:58 am
Full Name: James
Contact:

Re: Veeam Agent Job Volume Exclusions

Post by parneye »

Hi Mildur

I appreciate the reply. Thanks!.
The customer used to be an on-premise vSphere network, but now they are in the cloud running Azure VMs.
We did have a play around with the hypervisor type jobs that hooks in to the Veeam azure appliance, but we had certain issues and decided to go with a Veeam agent based job.
Hope that makes sense.

As we are currently covered by excluding the drive letters for all servers, and there is currently no overlap, we will wait for the feature request to be filled.
That link for the registry stuff seems rather tedious and difficult to keep track of.

Thanks!

Kind Regards
James
Post Reply

Who is online

Users browsing this forum: No registered users and 5 guests