Both sides previous revisionPrevious revisionNext revision | Previous revision |
daytoday:moving_volumes [2018/04/06 16:17] – [Copy and Paste] dcumming | daytoday:moving_volumes [2025/01/21 22:07] (current) – external edit 127.0.0.1 |
---|
====== Moving Volumes ====== | ====== Moving Volumes ====== |
| |
Moving volumes between repositories so that they remain in sycronisation with the physical movement of the actual volumes between locations would be the most important function with TapeTrack. | Moving [[object:volume|Volumes]] between [[object:repository|Repositories]] so that they remain in synchronisation with the physical movement of the actual [[object:volume|Volumes]] between locations would be the most important function with TapeTrack. |
| |
Volumes can be moved manually via drag and drop, using a barcode scanner, set move dates, synchronization scripts or a combination of these methods. | Moving a [[object:volume|Volume]] from one [[object:repository|Repository]] to another involves several processes: |
| * Updating the [[object:volume|Volume's]] Target [[object:repository|Repository]] to place it in a move status. |
| * Scanning the [[object:volume|Volume]] out of the Current [[object:repository|Repository]] (optional but recommended). |
| * Confirming the [[object:volume|Volume]] in the Target [[object:repository|Repository]] . |
| |
===== Manually Moving Volumes ===== | [[object:volume|Volumes]] can be moved manually via drag and drop, using a Barcode scanner, set move dates, synchronisation scripts or a combination of these methods. |
| |
While manually moving volumes is, essentially, the simplest way of moving a volume from one repository to another the method best suited is dependent on factors such as: | The method best suited to moving the [[object:volume|Volumes]] is dependent on the number of [[object:volume|Volumes]] to be moved, how the information |
* how many volumes need to be moved. | is received on which [[object:volume|Volumes]] need to be moved and access to hardware such as scanners, keyboard or mouse. |
* how the information is received on which volumes need to be moved. | |
* access to hardware such as mouse, keyboard or scanners. | |
| |
==== Drag and Drop ==== | ===== Putting Volumes Into A Move ===== |
| |
Drag and Drop selected volumes is a quick method for moving small groups of easily identified volumes. Simply select the volume (or range of volumes by Ctrl + click and/or Shift + click) and drag them to the required target repository and release the mouse. | Updating a [[object:volume|Volumes]] Target location to a [[object:repository|Repository]] other than its' Current [[object:repository|Repository]] will place the [[object:volume|Volume]] into a move status. The [[object:volume|Volumes]] Target location can be updated: |
| * [[:master:moving_volumes_manually|Moving Volumes Manually]]. |
| * [[technote:excel_import|Excel Data Importation]]. |
| * [[:master:moving_volumes_sync|Via Synchronization]]. |
| |
{{:master:tapemaster_volume_drag_drop.png}} | ===== Scanning Volumes Out ===== |
| |
The selected volumes will now have a target repository of the repository you dropped the volume/s on. | While scanning a [[object:volume|Volume]] out of its' Current [[object:repository|Repository]] is an optional step in the movement process it has the added benefits of |
| * Ensuring the correct [[object:volume|Volumes]] are being moved as any incorrect [[object:volume|Volumes]] will be alerted. |
| * Maintains a more accurate chain of custody as TapeTrack records the operator scanning out the [[object:volume|Volume]] as well as the date and time. |
| * Enables filtering of [[object:volume|Volumes]] that have been scanned out from other [[object:volume|Volumes]] in a move status. |
| |
{{:master:tapemaster_volume_drag_drop_moving.png}} | ===== Confirming Move ===== |
| |
==== Copy and Paste ==== | Confirming [[object:volume|Volumes]] into their Target [[object:repository|Repository]] updates the [[object:volume|Volume's]] Current [[object:repository|Repository]] to that of the Target [[object:repository|Repository]] . This removes the [[object:volume|Volumes]] move status and verifies its arrival at the specified [[object:repository|Repository]] . |
| |
Copy the volume ID's to your clipboard from text file, csv, email or other format. | [[object:volume|Volumes]] can be confirmed: |
| * [[:master:confirm_volumes_manually|Manually]]. |
| * [[lite:function_reconciliation|Via Reconciliation]]. |
| * [[:master:confirm_volumes_sync|Via Synchronization]]. |
| |
Right click the repository you want the volumes to move to and select ''Scan'' -> ''To Move''. | |
| |
{{:master:tapemaster_scan_to_move.png}} | ===== Move Errors ===== |
| |
From the scan in window click the **Clipboard** icon to paste in the volume ID's. | ==== Moving Volumes Back To Current Repository Before Confirming At Target Repository ==== |
| |
Close the scan in window by clicking th ''X'' at the top right. | Moving a [[object:volume|Volume]] that is currently in a move status back to it's Current [[object:repository|Repository]] before confirming at it's Target [[object:repository|Repository]] will: |
| * Move [[object:volume|Volume]] back to it's Current [[object:repository|Repository]] . |
| * Set Target [[object:repository|Repository]] to it's Current [[object:repository|Repository]] . |
| * Remove ''M'' (move) flag. |
| * Throw an error ''Update OK but marked for followup''. |
| * Add a ''W'' (warning) [[common:volume_flags|flag]] to the [[object:volume|Volume]] and highlight that [[object:volume|Volume]] in an orange background. |
| |
The volumes will now have a target repository displayed. | The [[object:volume|Volume]] is highlighted with the orange background and ''W'' [[common:volume_flags|flag]] added to allow the operator to easily identify [[object:volume|Volumes]] that have been moved back before Confirmation. This allows the operator to investigate why this has happened and make adjustments to [[object:volume|Volume]] movement processes if required. |
| |
| [[:daytoday:moving_volumes_error_w|Move back error examples]] |
| |
| |
| |
| {{tag> update-doco}} |
| |
| |
| |