TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools


reports:reconciliation

Differences

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

Link to this comparison view

reports:reconciliation [2018/04/05 01:11] – [Reconciliation Statistics] Scott Cunliffereports:reconciliation [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 5: Line 5:
 The program runs in 4 sequential phases: The program runs in 4 sequential phases:
  
-  * **Phase 1** Load of the TapeTrack Scan-Map from a Scan File. +  * **Phase 1** Load of the TapeTrack Scan-Map from a Scan-File. 
   * **Phase 2** Reconciliation of the Scan-Map.    * **Phase 2** Reconciliation of the Scan-Map. 
   * **Phase 3** Listing of unreferenced Scan-Map items.   * **Phase 3** Listing of unreferenced Scan-Map items.
Line 16: Line 16:
 {{reports:reports_tmss10reconcile_tapemaster_customer_status.png}} {{reports:reports_tmss10reconcile_tapemaster_customer_status.png}}
  
-==== Scan File ====+==== Scan-File ====
  
 {{reports:reports_tmss10reconcile_tapemaster_scanfile.png}} {{reports:reports_tmss10reconcile_tapemaster_scanfile.png}}
Line 24: Line 24:
 ==== Load of Scan-Map ==== ==== Load of Scan-Map ====
  
-The purpose of this phase is load a [[concepts:scan-file|TapeTrack Scan-File]] and resolved each of the a Scan-File Entries into a [[concepts:fully_qualified_barcode|Fully Qualified TapeTrack Barcode]].+The purpose of this phase is to load a [[concepts:scan-file|TapeTrack Scan-File]] and resolve each of the a Scan-File Entries into a [[concepts:qualified_barcode|Fully Qualified TapeTrack Barcode]].
  
-As the Scan-File is loaded, a [[concepts:scan-map|Scan-Map]] is created.+As the [[concepts:scan-file|Scan-File]] is loaded, a [[concepts:scan-map|Scan-Map]] is created.
  
-Alternatively, rather than loading the Scan-Map from a Scan-File, the [[subsystem:importengine|TapeTrack Import Engine]] can be used to load the Scan-Map. This facilitates loading from Fixed Length Reports, CSV Files and ODBC Data Sources. +Alternatively, rather than loading the [[concepts:scan-map|Scan-Map]] from a Scan-File, the TapeTrack Import Engine can be used to load the [[concepts:scan-map|Scan-Map]]. This facilitates loading from Fixed Length Reports, CSV Files and ODBC Data Sources. 
  
-The Fully Qualified TapeTrack Barcode can be resolved from an [[concepts:unqualified_barcode|Unqualified Barcode]] or an [[concepts:extended_attribute|Extended Attribute]]. +The Fully Qualified TapeTrack Barcode can be resolved from an [[concepts:qualified_barcode|Unqualified Barcode]] or an [[concepts:extended_attribute|Extended Attribute]]. 
-<code>+<code plain;>
              System: TapeTrack              System: TapeTrack
  Report Description: Phase 1: Load Scan-Map from Scan-File  Report Description: Phase 1: Load Scan-Map from Scan-File
Line 51: Line 51:
 ==== Reconcile of TapeTrack Volumes ==== ==== Reconcile of TapeTrack Volumes ====
  
-The purpose of this phase is to list all of the Volumes that are either in, moving to, or unexpected in the specified Repository.+The purpose of this phase is to list all of the [[:object:volume|Volumes]] that are either in, moving to, or unexpected in the specified [[:object:repository|Repository]].
  
 The following statuses may result: The following statuses may result:
  
-  * **Reconciled** if the Volume is in the target repository, is in the Scan-Map and not moving. +  * **Reconciled** if the [[:object:volume|Volume]] is in the Target [[:object:repository|Repository]], is in the [[concepts:scan-map|Scan-Map]] and not moving. 
-  * **Reconciled (Confirmed)** if the Volume is moving into the specified Repository and is in the scan map. The Volume will be Confirmed in the TapeTrack database. +  * **Reconciled (Confirmed)** if the [[:object:volume|Volume]] is moving into the specified [[:object:repository|Repository]] and is in the [[concepts:scan-map|Scan-Map]]. The [[:object:volume|Volume]] will be Confirmed into the [[:object:volume|Volume's]] Target Repository in the TapeTrack database. 
-  * **Absent from Scan-Map** if the Volume is confirmed into the specified Repository and is not present in the Scan-Map. An Audit Flag will be placed on the Volume. +  * **Absent from Scan-Map** if the [[:object:volume|Volume]] is confirmed into the specified [[:object:repository|Repository]] and is not present in the [[concepts:scan-map|Scan-Map]]. An Audit Flag will be assigned to the [[:object:volume|Volume]]
-  * **Pending Confirmation** if the Volume is in a Move Status out from the specified repository and is not overdue at the target repository. +  * **Pending Confirmation** if the [[:object:volume|Volume]] is in a move status out from the specified [[:object:repository|Repository]] and is not overdue at the Target [[:object:repository|Repository]]
-  * **Overdue at Target** if the Volume is in a Move Status to the specified Repository, is not in the Scan-Map and is now overdue at the target repository. +  * **Overdue at Target** if the [[:object:volume|Volume]] is in a move status to the specified [[:object:repository|Repository]], is not in the Scan-Map and is now overdue at the Target [[:object:repository|Repository]]
-  * **Unexpected in Scan-Map** Present in Scan-Map but not present at, or moving to, the target repository.+  * **Unexpected in Scan-Map** Present in the [[concepts:scan-map|Scan-Map]] but not present at, or moving to, the Target [[:object:repository|Repository]].
  
-<note tip>Report headings and spacing have been edited to fit information on web formatting</note>+<note>Report headings and spacing have been edited to fit information on web formatting</note>
  
-<code>+<code plain;>
             System: TapeTrack             System: TapeTrack
  Report Description: Phase 2: Reconcile TapeTrack Volumes against Scan-Map  Report Description: Phase 2: Reconcile TapeTrack Volumes against Scan-Map
Line 83: Line 83:
  
 Following the example data at the top of page we have: Following the example data at the top of page we have:
-  * Volumes 000002L5 and 000009L6 are referenced as **Reconciled** as they are in the scan map, and confirmed in the current repository (Offsite Vault).   +  * [[:object:volume|Volumes]] ''000002L5'' and ''000009L6'' are referenced as **Reconciled** as they are in the [[concepts:scan-map|Scan-Map]], and confirmed in the current [[:object:repository|Repository]] (Offsite Vault).   
-  * Volumes 000003L5, 000004L6 and 000005L6 are referenced as **Pending confirmation** as they are in the scan map, and in a move from the current repository but not yet confirmed at the target repository.   +  * [[:object:volume|Volumes]] ''000003L5''''000004L6'' and ''000005L6'' are referenced as **Pending confirmation** as they are in the [[concepts:scan-map|Scan-Map]], and in a move from the current [[:object:repository|Repository]] but not yet confirmed at the target [[:object:repository|Repository]].   
-  * Volume 000008L6 is referenced as **Absent from Scan-Map** as it appears in TapeTrack as at the current repository but is absent from the scan map.  This shows the volume is either somewhere it shouldn't be or is missing and as such is given a status of **NOT-OK** and is given an audit flag for further investigation. +  * [[:object:volume|Volumes]] ''000008L6'' is referenced as **Absent from Scan-Map** as it appears in TapeTrack as at the current [[:object:repository|Repository]] but is absent from the [[concepts:scan-map|Scan-Map]].  This shows the [[:object:volume|Volume]] is either somewhere it shouldn't be or is missing and as such is given a status of **NOT-OK** and is given an audit flag for further investigation. 
-  *  Volume 000010L6 is referenced as **Unexpected in Scan-Map** as it is present in the scan map as being at the current repository but shown in TapeTrack as being confirmed at another repository. As such is given a status of **NOT-OK** and is given an audit flag for further investigation. +  *  [[:object:volume|Volume]] ''000010L6'' is referenced as **Unexpected in Scan-Map** as it is present in the [[concepts:scan-map|Scan-Map]] as being at the current [[:object:repository|Repository]] but shown in TapeTrack as being confirmed at another [[:object:repository|Repository]]. As such is given a status of **NOT-OK** and is given an audit flag for further investigation.  
 + 
 +<note tip>Status strings may be customized using [[reports:reconciliation_tmssreconciletext|TMSSRECONCILETEXT]] variables.</note>
 ==== Unreferenced Scan-Map Entries ==== ==== Unreferenced Scan-Map Entries ====
-This report shows Volumes that are in the Scan-Map, but are not known to TapeTrack. +This report shows [[:object:volume|Volumes]] that are in the [[concepts:scan-map|Scan-Map]], but are not known to TapeTrack. 
-<code>+<code plain;>
              System: TapeTrack              System: TapeTrack
  Report Description: Phase 3: Unreferenced Scan-Map entries  Report Description: Phase 3: Unreferenced Scan-Map entries
Line 102: Line 104:
  
 Reasons for this error could be: Reasons for this error could be:
-  * Volume does not belong to you but has been included with your volumes by operator error. +  * [[:object:volume|Volume]] does not belong to you but has been included with your [[:object:volume|Volumes]] by operator error. 
-  * Manually produced scan file with a typo on a volume ID. +  * Manually produced Scan-File with a typo on a [[:object:volume|Volume]] ID. 
-  * Volume added to inventory but not entered into TapeTrack.+  * [[:object:volume|Volume]] added to inventory but not entered into TapeTrack. 
 ==== Reconciliation Statistics ==== ==== Reconciliation Statistics ====
 This report shows the final statistics for the Reconciliation process. This report shows the final statistics for the Reconciliation process.
  
-<code>+<code plain;>
              System: TapeTrack              System: TapeTrack
  Report Description: Phase 4: Reconciliation Statistics  Report Description: Phase 4: Reconciliation Statistics
Line 136: Line 139:
 </code> </code>
  
-**Phase 1** Reads in volume ID's from the scan file, parses them (depending on format) into Customer ID, Media ID and volume ID.  Metrics are then displayed as the number of volumes successfully and unsuccessfully loaded ready for reconciliation in phase two.+=== Phase 1 ===
  
-With the example dataall 7 entries were successfully loaded as fully qualified barcodes from the scan file into the scan map ready for reconciliation.+Reads in [[:object:volume|Volume-ID's]] from the Scan-Fileparses them (depending on format) into Customer-ID, Media-ID and [[:object:volume|Volume-ID]].  Metrics are then displayed as the number of [[:object:volume|Volumes]] successfully and unsuccessfully loaded ready for reconciliation in phase two.
  
-**Phase 2**+With the example data, all 7 entries were successfully loaded as fully qualified barcodes from the Scan-File into the Scan-Map ready for reconciliation.
  
- **Reconciled** shows number of volumes present in scan map and confirmed at subject repository. +=== Phase 2 === 
- **Reconciled (Confirmed)** shows number of volumes confirmed into subject repository that were in a move to there and present in scan map.  + 
- **Confirmation Bypass** (set as an attribute in TMSS10Reconcile) shows the number of volumes moving to subject repository and present in scan map but not confirmed. +<note tip>Status strings (Reconciled, Reconciled (Confirmed) etc) may be customized using [[reports:reconciliation_tmssreconciletext|TMSSRECONCILETEXT]] variables </note> 
-**Pending confirmation** shows number of volumes present in scan map, in a move status out of subject repository and yet to be confirmed at target repository.   + 
-**Out of scope** shows the number of volumes in the customers inventory that are not referenced in the scan map and are listed in TapeTrack as being confirmed in a repository other than the subject repository.  +  **Reconciled** shows number of [[:object:volume|Volumes]] present in Scan-Map and confirmed at subject [[:object:repository|Repository]]\\ 
-**Absent from Scan-Map** show the number of volumes expected to be either in, moving to or moving from the subject repository that are not listed in the scan map.   +  **Reconciled (Confirmed)** shows number of [[:object:volume|Volumes]] confirmed into subject [[:object:repository|Repository]] that were in a move to there and present in Scan-Map\\ 
- Unexpected in Scan-Map  +  **Confirmation Bypass** (set as an Attribute in [[cli:tmss10reconcile|TMSS10Reconcile]]) shows the number of [[:object:volume|Volumes]] moving to subject [[:object:repository|Repository]] and present in Scan-Map but not confirmed. \\ 
- Overdue at subject repository  +  **Pending confirmation** shows number of [[:object:volume|Volumes]] present in Scan-Map, in a move status out of subject [[:object:repository|Repository]] and yet to be confirmed at target [[:object:repository|Repository]].  \\ 
- Overdue at target repository +  **Out of scope** shows the number of [[:object:volume|Volumes]] in the customers inventory that are not referenced in the Scan-Map and are listed in TapeTrack as being not confirmed in, moving to or from the subject [[:object:repository|Repository]]\\ 
 +  **Absent from Scan-Map** show the number of [[:object:volume|Volumes]] expected to be either in, moving to or moving from the subject [[:object:repository|Repository]] that are not listed in the Scan-Map.  \\ 
 +  * **Unexpected in Scan-Map** shows the number of [[:object:volume|Volumes]] present in the Scan-Map that, in TapeTrack, are not present in, moving to or moving from the subject [[:object:repository|Repository]]. \\ 
 +  * **Overdue at subject repository** shows the number of [[:object:volume|Volumes]] present in the Scan-Map that are moving to the subject [[:object:repository|Repository]] but have exceeded the time threshold to complete the move. \\ 
 +  * **Overdue at target repository** shows the number of [[:object:volume|Volumes]] present in the Scan-Map that are moving from the subject [[:object:repository|Repository]] but have exceeded the target [[:object:repository|Repository]]'s time threshold to complete the move. 
 + 
 +=== Phase 3 === 
 + 
 +**Unreferenced Scan-Map Items** shows the number of [[:object:volume|Volumes]] that are present in the [[concepts:scan-map|Scan-Map]] but don't exist within the customers target media. 
 + 
 +=== Phase 4 === 
 + 
 +**Total Errors** shows the total accumulated errors from the reconciliation process.
  
 ==== Movement Aging Report ==== ==== Movement Aging Report ====
-This report shows statistics on Volumes that remain in a Move Status after the Reconciliation has completed. 
  
-<code>+This report shows statistics on [[:object:volume|Volumes]] that remain in a move status after the reconciliation has completed. 
 + 
 +<code plain;>
              System: TapeTrack              System: TapeTrack
  Report Description: Phase 4: Movement Aging Report  Report Description: Phase 4: Movement Aging Report
Line 175: Line 191:
  -------------------- -------- --------   -------------------- -------- -------- 
 </code> </code>
 +
 +In the example data, these are the [[:object:volume|Volumes]] 000003L5, 000004L6 and 000005L6 which are in a move status (one day) out of the subject [[:object:repository|Repository]] but not yet confirmed into their target [[:object:repository|Repository]].
 +
 +{{tag> update_doco}}
reports/reconciliation.1522890670.txt.gz · Last modified: 2025/01/21 22:07 (external edit)