TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools


planning:introduction

Differences

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

Link to this comparison view

planning:introduction [2019/10/16 21:56] – [Backup Administrators] Scott Cunliffeplanning:introduction [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 51: Line 51:
 At a high level, our suggested objectives are: At a high level, our suggested objectives are:
  
-  To create a completed inventory record of every tape asset owned by the enterprise. +  To create a completed inventory record of every tape asset owned by the enterprise. 
-  To create a consistent tape management process across the enterprise, or where that is not appropriate, a common framework to formalize the different management processes that might exist in each region. +  To create a consistent tape management process across the enterprise, or where that is not appropriate, a common framework to formalize the different management processes that might exist in each region. 
-  To create a chain-of-custody record of each activity related to each and every tape. +  To create a chain-of-custody record of each activity related to each and every tape. 
-  To automate as many tape management processes as possible by leveraging the features of TapeTrack, and by integrating with third-party software products and library hardware. +  To automate as many tape management processes as possible by leveraging the features of TapeTrack, and by integrating with third-party software products and library hardware. 
-  To better organize tape libraries that are in racks and shelving units. +  To better organize tape libraries that are in racks and shelving units. 
-  To implement reporting processes to comply with regulatory requirements. +  To implement reporting processes to comply with regulatory requirements. 
 ===== Obtaining Consensus ===== ===== Obtaining Consensus =====
  
Line 63: Line 63:
 Examples of the kind of disagreements that might arise are: Examples of the kind of disagreements that might arise are:
  
-  The level of integration and automation that is implemented. +  The level of integration and automation that is implemented. 
-  Who is responsible for supporting TapeTrack. +  Who is responsible for supporting TapeTrack. 
-  What level of alerting is enabled within TapeTrack.+  What level of alerting is enabled within TapeTrack.
  
 <note tip>Create a document that outlines what you will setup and deploy TapeTrack, ensure each stake-holder receives a copy, and ask for feedback before moving towards implementation.</note> <note tip>Create a document that outlines what you will setup and deploy TapeTrack, ensure each stake-holder receives a copy, and ask for feedback before moving towards implementation.</note>
Line 98: Line 98:
 These objections can include: These objections can include:
  
-  Why did we have to change from our old system? +  Why did we have to change from our old system? 
-  Why is maintaining the old system no longer part of my duties? +  Why is maintaining the old system no longer part of my duties? 
-  I did not attend the training and I don't know how the system works. +  I did not attend the training and I don't know how the system works. 
-  The system is not the same as our old system. +  The system is not the same as our old system. 
-  Why am I getting messages notifying me that I have made a mistake? +  Why am I getting messages notifying me that I have made a mistake? 
-  Scanning tapes in and out is too time consuming. +  Scanning tapes in and out is too time consuming. 
-  There are discrepancies between what the offsite vendor's system has and TapeTrack.+  There are discrepancies between what the offsite vendor's system has and TapeTrack.
planning/introduction.1571262998.txt.gz · Last modified: 2025/01/21 22:07 (external edit)