Hi,
We have quite a few backup and backup copy jobs that are running and i'm finding it difficult to find a window in which to perform server patches.
There is always one or more jobs running, sometimes normal backups other times its maintenance tasks or synthetics/GFS running which can take a long time.
It would be handy to be able to set a maintenance time on the management server so that Veeam won't run a job if it will finish later than the time specified based on previous run times
I have had a look around and can't see anything that relates.
Has anyone else experienced this and found a solution?
Thanks
-
- Enthusiast
- Posts: 39
- Liked: 5 times
- Joined: Jul 04, 2017 12:53 pm
- Full Name: Joe Spirit
- Contact:
-
- Product Manager
- Posts: 20415
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Veeam Primary Backup and Replication Server Maintenance
And what maintenance window should do with already running jobs? Stop them? In this case, it might be worth creating a simple script killing all running activity. Thanks.
-
- Enthusiast
- Posts: 39
- Liked: 5 times
- Joined: Jul 04, 2017 12:53 pm
- Full Name: Joe Spirit
- Contact:
Re: Veeam Primary Backup and Replication Server Maintenance
Thanks for the reply.
What effect will it have on the running tasks? killing them will make the maintenance tasks start from the beginning again surely?
Backups don't usually take too long it's the maintenance tasks that are the issue taking up to 30 hours because of the large jobs which leaves us behind slightly on restore points.
We also try to stagger these tasks so they are not all running at the same time but this usually means a maintenance task is constantly running on one of our jobs.
I think being able to set it an advance a flag that tells veeam not to perform a task that will exceed a specified maintenance start time would be useful
What effect will it have on the running tasks? killing them will make the maintenance tasks start from the beginning again surely?
Backups don't usually take too long it's the maintenance tasks that are the issue taking up to 30 hours because of the large jobs which leaves us behind slightly on restore points.
We also try to stagger these tasks so they are not all running at the same time but this usually means a maintenance task is constantly running on one of our jobs.
I think being able to set it an advance a flag that tells veeam not to perform a task that will exceed a specified maintenance start time would be useful
-
- Product Manager
- Posts: 20415
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Veeam Primary Backup and Replication Server Maintenance
It would be handy to be able to set a maintenance time on the management server so that Veeam won't run a job if it will finish later than the time specified based on previous run times
Preventing backup server from executing certain job will lead to less restore points created, in the meantime that seems to be issue you're trying to deal with. So, I'm slightly confused how the proposed functionality will address the problem of being behind on restore points?Backups don't usually take too long it's the maintenance tasks that are the issue taking up to 30 hours because of the large jobs which leaves us behind slightly on restore points.
Thanks.
-
- Enthusiast
- Posts: 39
- Liked: 5 times
- Joined: Jul 04, 2017 12:53 pm
- Full Name: Joe Spirit
- Contact:
Re: Veeam Primary Backup and Replication Server Maintenance
To be clear we try to run our backups overnight and allow the maintenance tasks to run during the day.
Without editing all the jobs to disable maintenance etc it is difficult to find a quiet period in which to perform windows patching other than killing any current jobs and leaving inconsistent states.
I'm aware that we will lose restore points during the outage however it would be more graceful not to start them rather than terminate them.
Once one job has run and backup resources are available another job may take up these resources leaving a small window in which to stop this. Especially on maintenance tasks where you can only select a day not a time at which they are run.
Having a schedule in place rather than having someone continuously monitor the jobs and disable each when finished would be a better solution.
many thanks.
Without editing all the jobs to disable maintenance etc it is difficult to find a quiet period in which to perform windows patching other than killing any current jobs and leaving inconsistent states.
I'm aware that we will lose restore points during the outage however it would be more graceful not to start them rather than terminate them.
Once one job has run and backup resources are available another job may take up these resources leaving a small window in which to stop this. Especially on maintenance tasks where you can only select a day not a time at which they are run.
Having a schedule in place rather than having someone continuously monitor the jobs and disable each when finished would be a better solution.
many thanks.
Who is online
Users browsing this forum: Bing [Bot] and 98 guests