Differences

This shows you the differences between two versions of the page.

--- master:moving_volumes [2017/11/10 20:44] – dcumming
+++ master:moving_volumes [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-===== Moving Volumes =====
+====== 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**.
+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.
-==== Overview ====
+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 ====
@@ Line 28: / Line 26: @@
 The Daily script includes two applications:
   * **[[cli:tmss10expirebydate|TMSS10ExpireByDate]]**: Locates [[object:volume|Volumes]] with a Move Date of today or greater and adds a **Move Pending [[common:volume_flags|Flag]]**.
-  * **[[cli:tmss10movepending|TMSS10MovePending]]**: Puts [[object:volume|Volumes]] with a **Move Pending [[common:volume_flags|Flag]]** into a move status to the [[object:volume|Volume's]] current [[object:repository|Repository's]] Next Repository, as set in the ''Options Tab'' of the Repository Properties Window. If the [[object:volume|Volume's]] current Repository has no Next Repository, the **Move Pending [[common:volume_flags|Flag]]** will be added, but no move will be initiated.
+  * **[[cli:tmss10movepending|TMSS10MovePending]]**: Puts [[object:volume|Volumes]] with a **Move Pending [[common:volume_flags|Flag]]** into a move status to the [[object:volume|Volume's]] current [[object:repository|Repository's]] Next Repository, as set in the ''Options Tab'' of the [[master:repository_properties_window|Repository Properties Window]]. If the [[object:volume|Volume's]] current Repository has no Next Repository, the **Move Pending [[common:volume_flags|Flag]]** will be added, but no move will be initiated.
 . In order for automation to continue, each [[object:volume|Volume]] must be confirmed or scanned at each of its Target [[object:repository|Repositories]].
@@ Line 35: / Line 33: @@
 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 green 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.
+  * **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 off-site 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]].