Duplicate to tape job automatically gets skipped if the source job fails
This is a feature request. This is the scenario; If a backup to disk job fails for any reason whatsoever, even if it's only missing one file or directory, it automatically causes a duplicate to tape job to get skipped and then it requires creating a manual duplicate to tape job for that backup set just to get your data backed up. If you're backing up multi-terabytes worth of information and a backup fails for a single missing directory, I still want/need that data to be duplicated to tape regardless! The software needs to be smart enough to do this because I can't babysit backup jobs that sometimes take four or five days to complete by themselves, not including verification. Even if the job failed entirely, I would still want whatever data that actually was backed up to be duplicated to tape.Job priorities are not granular enough
This is a feature request. As verified with support, job priorities are all linked at the server level, which is definitely not granular enough for my needs. For example,if you have multiple stages or sub-jobsfor eachserver, such as backup to disk full/incremental based on daily/weekly/monthly schedule, duplicate to disk/tape, or separate verify jobs, you cannot prioritize anything beyond the main server job over other entire server jobs. Theproblem becomes much more apparentwhen you have multi-terabyte jobs that take most of the week to complete. Add on another dozen or so servers that need backed up (some of those comprised of multiple terabytes of data as well) and you have an extremelyfinite backup window and this is where better job priorities would play a huge role. For instance, it would be nice to be able to prioritizelarge verify jobs lower than thesmaller ones since they take much less time to complete, but still have the actual backup to disk job be a higher priority level. Or to be able to prioritize certain full backup to disk jobs in one order, but have a linked duplicate to tape job be a different priority level entirely. I don't think I need to try and recreate all of the different scenarios of why this feature would be beneficial. It seems like this should already be part of the software, but it isn't for some reason.