Dell PowerVault ML6000 Dell PowerVault ML6000 SCSI Reference Guide - Page 56

Move Medium – A5h, What the Library Does With This Command, Command Usage

Page 56 highlights

Move Medium - A5h What the Library Does With This Command The library will attempt to physically move a cartridge from the requested source element to the requested destination. The library will make reasonable attempts to retry this operation within the scope of its capabilities, but if unsuccessful, will try to return the cartridge to its source element. If the source element was a drive, the library will attempt to leave the cartridge in either a storage or I/E element if the configuration supports it (not partitioned in the case of the I/E), otherwise it may remain in the picker. If the library includes towers, any required movement of the towers will be provided automatically by the library. When the source and destination addresses are the same, the library will still do a full Get and Put, even if it is a drive (data transfer element). The library will check that the source element is occupied and that the destination element is empty. It will also check for media compatibility between the source and destination elements. Failures in either of these will result in a Check Condition. Command Usage Storage, data transfer, and import/export elements can be used as valid source or destination elements. The medium transport element (picker) cannot be a destination element. It can be a source element to recover stranded media. This is the primary command for the library, and should be used to accomplish any media movement within the system. If the library indicates a failure due to element status problems (source empty, destination full, media incompatible, etc.), element status should be re-initialized and re-synchronized. This would apply to both hardware errors and illegal requests. 46 SCSI Commands

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90

46
SCSI Commands
Move Medium – A5h
What the Library Does With This Command
The library will attempt to physically move a cartridge from the requested source element to the requested
destination. The library will make reasonable attempts to retry this operation within the scope of its
capabilities, but if unsuccessful, will try to return the cartridge to its source element. If the source element
was a drive, the library will attempt to leave the cartridge in either a storage or I/E element if the configuration
supports it (not partitioned in the case of the I/E), otherwise it may remain in the picker.
If the library includes towers, any required movement of the towers will be provided automatically by the
library.
When the source and destination addresses are the same, the library will still do a full Get and Put, even if
it is a drive (data transfer element).
The library will check that the source element is occupied and that the destination element is empty. It will
also check for media compatibility between the source and destination elements. Failures in either of these
will result in a Check Condition.
Command Usage
Storage, data transfer, and import/export elements can be used as valid source or destination elements.
The medium transport element (picker) cannot be a destination element. It can be a source element to
recover stranded media.
This is the primary command for the library, and should be used to accomplish any media movement within
the system. If the library indicates a failure due to element status problems (source empty, destination full,
media incompatible, etc.), element status should be re-initialized and re-synchronized. This would apply to
both hardware errors and illegal requests.