Video Screencast Help

BE2012 limiting concurrent jobs to tape library

Created: 26 Feb 2013 | 10 comments

Hello

Is it still possible, like it was in BE2010 to limit the maximum concurrently running jobs on the media server? I see the concurrent write session options for disk based storage but not for a tape library or the media server itself.

Staging the start times of backup jobs is far from ideal.

Thanks

 

Operating Systems:

Comments 10 CommentsJump to latest comment

pkh's picture

The tape library is automatically constrainted by the number of tape drives in it.  It can only run 1 job per drive at a time.  Hence the number of concurrent jobs for the media server is contrainted by the number of tape drives and the number of concurrent writes for each B2D folder.

PCAU's picture

Thanks pkh but I think my point has been missed. Lets say I have a tape library with 4x tape drives however I do not have the data throughput to feed all 4 drives at their minimum data rates. I have the need to artificially restrict the tape library to run fewer jobs concurrently, in BE2010 this wasn't an issue as the option was there.

I am aware that I could stagger the job start times, or manually disable a drive, or reduce the amount of tapes available but none of these are ideal.

pkh's picture

Then you are one of the lucky few who has more media than is required and I don't mean this in a sarcastic way.  If this feature is missing in BE 2012, put it up as an idea in the Idea section.  If enough users agree with you, it might get picked up in some future release of BE.

Larry Fine's picture

re: Thanks pkh but I think my point has been missed. Lets say I have a tape library with 4x tape drives however I do not have the data throughput to feed all 4 drives at their minimum data rates. I have the need to artificially restrict the tape library to run fewer jobs concurrently, in BE2010 this wasn't an issue as the option was there.

What option in BE 2010 are you referring to?  I don't recall an option to limit the number of tape drives in use, although you could achive that with pools and/or job scheduling.  This isn't a common question.

If you find this is a solution for the thread, please mark it as such.

PCAU's picture

It was an option to restrict the concurrent jobs running on the media server, not nessesarily the tape library specifically. However I've installed 2010 on a test server and embarrassingly cannot find the option myself!

RLeon's picture

Not sure if I get the meaning, but you can try using the Storage Pool feature. It lets you group individual tape drives together, which is then available when you setup backup jobs.
So if you only want to use two drives out of four during a backup, then create a Storage Pool with only two drives as members, and point to it in your backup job configuration.

Storage tab > Configure storage button > Storage Pools

PCAU's picture

Thanks, yes pkh it's a rather abnormal situation to have, albiet temporary. I will post this in the ideas section.

RLeon, thanks also for the suggestion That's another way to achieve it, but i'm still targeting jobs to particular devices/pools which i'd rather avoid also.

RLeon's picture

All your backup jobs could target the same artificially-crippled Storage Pool, so that the number of concurrent jobs from any servers/agents would be limited to the number of tape drives you assigned to the pool.

For tape, this has the same effect as the concurrent write session option for disk storage.

For servers that have enough throughput to feed all tape drives, just target the default tape library (not the crippled pool) so that all the drives could be used concurrently.

Donald Eady's picture

PCAU.. Is there any other software that is controlling the tape library?

I hope this posting was helpful