I'm new to the whole Veeam world and have been trying to work out exactly how to get my jobs done with low impact on user performance. We're still running backup to tape nightly with our old Symantec product and as soon as I can figure this whole thing out we're going to retire the magnetic media for good. That being said, there seems to be a very under-developed job scheduling feature in Veeam that I can't believe isn't a problem for the majority of Veeam customers.
Here's the problem I see with current scheduling options in Veeam:
You can only choose BETWEEN one type of schedule or another, and none of the available options allow for different run times for the same job.
Here's what I mean by that. We have very large databases, file server repositories and Exchange mail stores that change daily, so even an incremental backup looks much more like a full backup. These jobs generate a LOT of internal network traffic copying from the VMWare cluster to the Veeam server and impact network latency to the point that users will notice if we try to run them during production hours. The way we dealt with this in the past was to run a full backup starting sometime Saturday morning and just let that run until it finished. During the weekdays we would run the same job (incremental instead of full) after hours, starting around 7pm (after our ODBC queries ran and a few other network jobs finished).
It blows my mind that there's no way to run a job at different times on different days. What about Holidays? If I have a holiday, I want to run a full backup starting in the morning and then resume normal schedules after the holiday. In our old backup software this was easy to do using their calendar scheduling features. You would setup the days you want to run the job at a specific time (create a recurring schedule at whatever interval you wanted) then create another schedule with a different starting time (again as a recurring schedule) then you could set exclusions to not run the job. You could even set one time jobs (like Christmas eve, etc.)
This is a serious show stopper for me. I'm now going to have to either spend hours figuring out how to do this using a powershell script or I'm going to have to manually change the start time every Friday/Monday so I can run these jobs differently on the weekend than the weekday. If I forget on a Monday morning to change that schedule back, then come 1pm my full backups are going to run during a production day (not good).
I spoke to support about this and they completely understood my logic/reasoning behind wanting this feature, but they told me that it had actually never been brought up before! This is really the most basic function of job scheduling, and it looks to me like most Veeam customers either do what I'm going to do and figure out a workaround or they've just accepted the limitation and decided to deal with it (even if it impacts their network, or more likely they just run it after hours even on weekends).
So, I'm not sure how readable that is, but I hope I got my concerns across coherently. What do the rest of you think? Wouldn't a calendar based scheduling option (or at the very least, being able to choose more than one type of schedule per job) make sense?
I think the main difference I'm seeing is that the schedule for Veeam is set on the job whereas what my old software allowed was a schedule to be set and then assign the job to the schedule (which to me makes more sense).
So, Veeam... pretty please... with sugar on top... will you consider enhancing your scheduling features? I just need to be able to run the same job at different times on different days... Please.