| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| master:moving_volumes [2018/04/23 23:44] – [Movement Errors] Scott Cunliffe | master:moving_volumes [2025/01/21 22:07] (current) – external edit 127.0.0.1 |
|---|
| Moving Volumes between [[object:repository|Repositories]] is one of the single most important tasks in TapeMaster. For this reason, there are several options for Moving Volumes. | Moving Volumes between [[object:repository|Repositories]] is one of the single most important tasks in TapeMaster. For this reason, there are several options for Moving Volumes. |
| |
| When a [[object:volume|Volume]] is moving, it is given a Move [[common:volume_flags|Flag]] and said to be in a **Move Status**. [[object:volume|Volumes]] move from a Current [[object:repository|Repository]] to a Target [[object:repository|Repository]]. Volumes can be confirmed at a Target [[object:repository|Repository]] in TapeMaster by right-clicking in the Volume List, selecting Special Operations, and then confirm or by using a barcode scanner in [[desktop:lite|TapeTrack Lite]] or [[desktop:checkpoint|TapeTrack Checkpoint]]. | When a [[object:volume|Volume]] is moving, it is given a Move [[common:volume_flags|Flag]] and said to be in a **Move Status**. [[object:volume|Volumes]] move from a Current [[object:repository|Repository]] to a Target [[object:repository|Repository]]. Volumes can be confirmed at a Target [[object:repository|Repository]] in TapeMaster by right-clicking in the Volume List, selecting Special Operations, and then confirm or by using a Barcode scanner in [[desktop:lite|TapeTrack Lite]] or [[desktop:checkpoint|TapeTrack Checkpoint]]. |
| |
| ==== Move Dates ==== | ==== Move Dates ==== |
| There are several types of movement errors. Here are the two most common: | There are several types of movement errors. Here are the two most common: |
| |
| * **Warning Flag**: A [[object:volume|Volume]] will receive a Warning [[common:volume_flags|Flag]] (which appears as a orange highlight in the [[master:view_volume_list|Volume List]] and on the Customer Tree) when it is confirmed at its Current [[object:repository|Repository]] before first reaching its Target Repository. In TapeMaster this will evoke the **Failed Operations** window, displaying the volume ID's in error and listed as **Update OK but marked for followup**. In command line interface, the volumes will be marked in the same way but listed in the stderr output. | * **Warning Flag**: A [[object:volume|Volume]] will receive a Warning [[common:volume_flags|Flag]] (which appears as a orange highlight in the [[master:view_volume_list|Volume List]] and on the Customer Tree) when it is confirmed at its Current [[object:repository|Repository]] before first reaching its Target Repository. In TapeMaster this will evoke the **Failed Operations** window, displaying the Volume-ID's in error and listed as **Update OK but marked for followup**. In command line interface, the volumes will be marked in the same way but listed in the stderr output. |
| * **Audit Flag**: A [[object:volume|Volume]] will receive an audit [[common:volume_flags|Flag]] when inventory documents between TapeTrack and other software (such as the software for an offsite vendor) do not match-up. For more information, see [[subsystem:certification|Certification]]. | * **Audit Flag**: A [[object:volume|Volume]] will receive an audit [[common:volume_flags|Flag]] when inventory documents between TapeTrack and other software (such as the software for an offsite vendor) do not match-up. For more information, see [[subsystem:certification|Certification]]. |
| |
| |
