> We are using Omniback II 2.55 with a DLT library.
> When a (particular) backup is initiated, the job selects a tape from
> the pool (say ABC123), and the library is requested to select the tape
> from slot 25. This turns out to be an empty slot (the tape is actually
> in slot 44). Omniback II does know that this tape is in slot 44
> if I go scan slot 44, it reads the tape. Indeed if I look at the media
> pool, it tells me ABC123 is in slot 44.
> Can someone tell me why the backup is attempting to load from slot 25
> when the tape is in 44?
OmniBack selects medium for backup according to allocation policy.
First of all you have to know what allocation policy is selected for
your media pool. If the policy is Strict, OmniBack will only use valid
OmniBack media from that pool and will not try to iniaitlize new media.
However, if you have Loose policy, depending on "Allocate unformatted
media first" option, OmniBack will also try to initialize new media.
Candidates for initialization are all library slots marked as Blank or
BTW, you can always view the order in which OmniBack will try to
allocate media with the following commands:
# allocation from pool
omnimm -show_pool_alloc <Pool>
# allocation from pool fro particular library
omnimm -show_repository_alloc <Library> <Pool>
If I try to explain what happened in your case:
1. your ABC123 pool has Loose policy with "Allocate unformatted media
first" option enabled,
2. Slot 25 was marked as Blank/Unknown in OmniBack database (OmniBack
was not aware that the slot was not empty) or
3. OmniBack was not aware that you have valid medium from ABC123 pool
in slot 44,
4. OmniBack probably selected slot 25 because it wanted to initialize
How to overcome such behaviour: change pool policy to Loose
with "Allocate unformatted media first" set to Off or use Strict pool
policy. Also, ensure that OmniBack database is up-to-date with actual
repository of the library (perform rescan of library or enter/eject
media to/from library only with OmniBack commands).
> And what is the way to force the backup to go ask the database for the
> correct slot number?
If you want to force OmniBack to use particular media (which can
implicitly mean the slot too), you should look for OmniBack
Preallocation list (specified list of media that should be used for
> Rescan the library?
> Thanks in advance, Andy.
Sent via Deja.com