Can I coerce Backup Exec 12.5/2010 (or an alternative) to this approach?
Posted on 2011-02-15
Bit of a ranty, pie-in-the-sky, stab-in-the-dark question, this, but here goes...
It seems that, if I split a single multi-server job into per-server (or per-dept) jobs, all using the same tape library, that the following problems occur:
1. It will always try to pick a new tape for each job, instead of appending to the last-written tape (regardless of the media pool, or the Media Overwrite Protection setting)
2. If the jobs are scheduled for the same time, they will queue and run sequentially provided that they do not take longer than 24 hours to complete, otherwise they fall foul of the 'time window'
I can't seem to find a way around these and am looking for alternative options. In an ideal world, I would like to schedule a set of jobs to run sequentially, without any time window, all appending to the same media set.
I have considered disk-to-disk-to-tape but that throws up its own issue: I can only replicate backup sets, which means I need as much disk storage as I have tape storage, which just isn't viable (economically or physically) in the server I have. I would prefer to define a disk-disk-tape target device that would support the following, as part of the device operation:
1. Writing the BKF files to disk until the disk target reaches its configured limit
2. Then writing the contents of the disk target to the tape library
3. Then emptying the disk target and continuing the job (as per #1)
I've been using Backup Exec in its various forms for years; I really like its interface and agent support and it has never let me down yet but it is starting to get difficult to manage so perhaps it is time to look at alternative software.
1. Have I missed something in Backup Exec that might address the issues/approach I have listed above?
2. Does anyone know of any alternatives (with similar application support) that do work in the way I would like?