Journal

The TapeTrack Journal is a database containing operational activity recorded by the TapeTrack Framework Server.

Journal entries provide the source data used to create Customer statistics (.ttstats) files for billing.

The Journal records activity occurring within TapeTrack, including Volume storage and movement events. TMSS10LogStatsExtractDB reads the Journal and creates a separate statistics extract for each Customer within the selected date range.

The Journal does not contain the Customer's billing rates or final invoice items. Rates, package assignments and billing calculations are applied later by TMSS10LogStatsProcess.

The Journal provides an authoritative record of TapeTrack activity that may be used for reporting, statistics and billing. The Journal can be used to:

• Record operational activity generated by the TapeTrack Framework Server.
• Filter activity for a defined period.
• Support the extraction of Customer-specific .ttstats files.
• Provide an audit trail between TapeTrack activity and invoice quantities.

The TapeTrack Framework Server writes activity to the Journal as TapeTrack operations occur.

Depending on the installed version and configuration, Journal activity may include Volume movements, storage activity, repository activity, media activity, other operational statistics required for reporting or billing.

The exact billing result depends on:

• The activity stored in the Journal.
• The Customer associated with the activity.
• The selected extraction date range.
• The statistics created by TMSS10LogStatsExtractDB.
• The Package Map and Billing Rules used during processing.

The Journal database is maintained by the TapeTrack Framework Server.

Its physical location depends on:

• The TapeTrack Framework Server installation directory.
• The operating system.
• The installed TapeTrack version.
• The Framework Server configuration.

The Journal database should be accessed using the TapeTrack server utilities rather than edited directly.

The account running the Journal extraction must have sufficient permission to:

• Access the TapeTrack Framework Server installation.
• Read the Journal database.
• Execute TMSS10LogStatsExtractDB.
• Write the generated .ttstats files to the billing extract directory.

TMSS10LogStatsPrintDB can be used to print the contents of the Journal database.

This utility is useful when:

• Confirming that activity exists for a Customer.
• Investigating missing .ttstats records.
• Comparing Journal activity with billing quantities.
• Checking activity within a date range.
• Troubleshooting unexpected invoice items.

Confirm that:

• The correct server utility is being used.
• The Journal database exists.
• The utility account has the required permissions.
• The database is not damaged.
• The installed utility version is compatible with the Framework Server.
• No unsupported direct changes were made to the Journal files.

If the Journal appears damaged or unreadable, contact TapeTrack Support before attempting repairs.

• Treat the Journal as an authoritative operational record.
• Do not manually edit the Journal database.
• Use non-overlapping billing extraction periods.
• Record the exact extraction date range.
• Investigate missing or empty Customer files.
• Retain the extracted TTSTATS files with the billing output if required.
• Restrict database access to authorized administrators.
• Contact TapeTrack Support before attempting Journal repair.

The Journal may contain Customer, Volume, Repository and operational activity information.

Access should therefore be restricted to:

• TapeTrack Framework Server services.
• TapeTrack administrators.
• Authorized billing staff requiring access.
• The account running TMSS10LogStatsExtractDB.
• The account running authorized backup processes.

The Journal should not be publicly accessible or stored in an unsecured shared directory.

• TMSS10LogStatsProcess
• Customer-ID
• Customer TTSTATS File
• Customer Description Map
• Package Map
• Billing Rules
• TapeTrack XML Stylesheet
• Billing Process
• Billing XML
• XMLQuickBooks Mapping