| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| master:moving_volumes [2017/10/03 14:46] – ↷ Page moved from object:moving_volumes to master:moving_volumes dcumming | master:moving_volumes [2025/01/21 22:07] (current) – external edit 127.0.0.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 ==== | ==== Move Dates ==== |
| Move Dates indicate when a Volume should move next. Batch processes such as [[cli:tmss10expirebydate|TMSS10ExpireByDate]] and [[cli:tmss10movepending|TMSS10MovePending]] use these Move Dates to initiate moves for [[object:volume|Volumes]]. If a Volume does not move before its Move Date, the Volume will be [[common:volume_flags|flagged]] as Overdue. | Move Dates indicate when a Volume should move next. Batch processes such as [[cli:tmss10expirebydate|TMSS10ExpireByDate]] and [[cli:tmss10movepending|TMSS10MovePending]] use these Move Dates to initiate moves for [[object:volume|Volumes]]. If a Volume does not move before its Move Date, the Volume will be [[common:volume_flags|flagged]] as Overdue. |
| |
| ==== Manually Moves in the Inventory Administrative Tab ==== | ==== Manual moves in the Inventory Administrative Tab ==== |
| |
| To manually move Volumes between [[object:repository|Repositories]] in the Inventory Administration Tab, select a Volume or group of Volumes in the [[master:view_volume_list|Volume List]] and click and drag them to a [[object:repository|Repository]] in the Repository List. | To manually move Volumes between [[object:repository|Repositories]] in the Inventory Administration Tab, select a Volume or group of Volumes in the [[master:view_volume_list|Volume List]] and click and drag them to a [[object:repository|Repository]] in the Repository List. |
| 1. Set up [[subsystem:simplemanagement|Simple Management Rules]] so that [[object:volume|Volumes]] are given a move date when moved between [[object:repository|Repositories]]. Automation will only function correctly if Volumes move cyclically between Repositories. For example, from Repository A to Repository B to Repository C and back to Repository A, etc. | 1. Set up [[subsystem:simplemanagement|Simple Management Rules]] so that [[object:volume|Volumes]] are given a move date when moved between [[object:repository|Repositories]]. Automation will only function correctly if Volumes move cyclically between Repositories. For example, from Repository A to Repository B to Repository C and back to Repository A, etc. |
| | |
| 2. Each Repository must have a **Next Repository** set in the ''Options Tab'' of the Repository Properties Window. | 2. Each Repository must have a **Next Repository** set in the ''Options Tab'' of the [[master:repository_properties_window|Repository Properties Window]]. |
| <note tip>If Volumes move to different [[object:repository|Repositories]] at a point in the automation cycle, use the "Home Repository" and specify a Home Repository for each Volume. This can be done in the Options Tab of the [[master:volume_properties_window|Volume Properties Window]] or, for multiple Volumes, by Right-Clicking in the [[master:view_volume_list|Volume List]] and selecting Special Operations, Modify, then Home Repository.</note> | <note tip>If Volumes move to different [[object:repository|Repositories]] at a point in the automation cycle, use the "Home Repository" and specify a Home Repository for each [[object:volume|Volume]]. This can be done in the Options Tab of the [[master:volume_properties_window|Volume Properties Window]] or, for multiple Volumes, by right-clicking in the [[master:view_volume_list|Volume List]] and selecting Special Operations, Modify, then Home Repository.</note> |
| |
| 3. Ask your TapeTrack Server Administrator to run the daily script, located in the scripts folder of the TapeTrack Framework Server Install Directory, on a daily basis using Windows Scheduler. | 3. Ask your TapeTrack Server Administrator to run the daily script, located in the scripts folder of the TapeTrack Framework Server Install Directory, on a daily basis using Windows Scheduler. |
| The Daily script includes two applications: | 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: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. |
| 4. In order for automation to continue, each [[object:volume|Volume]] must be confirmed or scanned at each of its Target [[object:repository|Repositories]]. | 4. In order for automation to continue, each [[object:volume|Volume]] must be confirmed or scanned at each of its Target [[object:repository|Repositories]]. |
| |
| 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 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]]. |
| |
| |
