Filter
Top Products
API Guide
601355 Rev A API Functions 2-963
Functins
If there is no drive/medium pair associated with the same
archive, VolServ then selects a drive/medium pair where the
drive and medium are associated with different archives. If
there are multiple drive/medium pair candidates, VolServ
selects a drive/medium pair from the archive with a free drive,
if possible. If all archives contain the same number of drives
with no drives available, VolServ then selects a drive/medium
pair from the archive with the largest number of media.
When specifying a mount by MediaClass group associated
across more than one archive, no inter-archive medium/drive
pairing is permitted. The medium selected from the MediaClass
group must be in the same archive as the selected drive;
otherwise the Mount request fails.
When a medium is ejected (as a result an Export or Checkout
request), no check is made to determine if a Mount request
exists in the queue for the ejected medium. As a result, the
Mount request remains queued until a drive is freed. At that
time, the Mount request fails because the medium is not
available. In other words, the request queue is not checked for
impact on pending requests each time a resource changes its
availability and after a medium/drive pair is identified. VolServ
does not attempt re-pairing based on changed availability of
resources.
A queued Mount request (awaiting drive or medium) can be
cancelled.
The
VSID_CRITERIA_GROUP_HANDLE parameter require that
two arguments be passed instead of one.
• The first argument passed is the number of criteria groups
handles to be used in selecting the medium to be mounted.
• The second argument is the list of criteria group handles to
be used in selecting the medium to be mounted.