Agent-based backup of Windows, Linux, Max, AIX and Solaris machines.
Post Reply
Jason_Ryan
Lurker
Posts: 1
Liked: never
Joined: May 11, 2020 2:53 pm
Full Name: Jason Ryan
Contact:

Skipping a VM in a backup job for one iteration

Post by Jason_Ryan »

Hi guys!

I'm looking to prevent a VM/Server from being backed up for one iteration of a Veeam backup job. The Scenario is:

"Backup Job 1" contains three servers:
1. "SQL Server"
2. "Application Server"
3. "File Server"

"Backup Job 1" runs daily at 20:30

What I am looking to do it to let this backup job continue running but exclude "Application Server" from Friday night's run and have it re-included on Saturday's run. Is there a way to achieve this without affecting/deleting the current backups of "Application Server"?
dalbertson
Veeam Software
Posts: 492
Liked: 175 times
Joined: Jul 21, 2015 12:38 pm
Full Name: Dustin Albertson
Contact:

Re: Skipping a VM in a backup job for one iteration

Post by dalbertson »

Not within the gui. Even if you used powershell to add it to the exclusion list for that night and add it back i think it would confuse the chain and take another full.

Best bet would be to create a job just for the App server and have its schedule. You could link these jobs to kick off after one finished.
Dustin Albertson | Director of Product Management - Cloud & Applications | Veeam Product Management, Alliances
PetrM
Veeam Software
Posts: 3229
Liked: 520 times
Joined: Aug 28, 2013 8:23 am
Full Name: Petr Makarov
Location: Prague, Czech Republic
Contact:

Re: Skipping a VM in a backup job for one iteration

Post by PetrM »

Hello,

The job will not take another active full automatically if you just exclude and then re-add a VM because the backup set already contains full point of the corresponding object.

However, there are some cases when active full will be triggered:
1) You enabled this option in job settings and full point of an excluded VM falls out of the specified time period
2) The VM reference at the level of source infrastructure was changed (for example you re-registered VM at the level of vSphere), such VM is considered as completely new object by Veeam
3) The full run is triggered according to job schedule settings :)

You can exclude VM in UI if you add VMs by containers, please find the instructions here.
In case of agent management jobs you could try to remove a server at this step of job creation wizard.

If you decide to achieve this goal using PowerShell, you may take a look at this cmdlet.

Would you be so kind to clarify why would you like to exclude your Application server for specific runs?
Basically, I agree with Dustin that the best option is to have a dedicated job with its own schedule.

Thanks!
Post Reply

Who is online

Users browsing this forum: No registered users and 5 guests