TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace: • delete_volumes
planning:introduction

Differences

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

Link to this comparison view

planning:introduction [2017/08/03 22:54] – [Mapping the Existing Environment] dcummingplanning:introduction [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Implementation and Planning Guide ====== ====== Implementation and Planning Guide ======
  
-Let me start this section by saying nobody ever knows how complex their existing tape management processed are until they start implementing TapeTrack.+Let me start this section by saying nobody ever knows how complex their existing tape management processes are until they start implementing TapeTrack.
  
 There are many factors that result in this realization, but above all, is the fact that prior to the TapeTrack implementation, the majority of management processes are manual, and unmanaged, and have been created with no consideration of ever formalizing the process. There are many factors that result in this realization, but above all, is the fact that prior to the TapeTrack implementation, the majority of management processes are manual, and unmanaged, and have been created with no consideration of ever formalizing the process.
Line 10: Line 10:
   - [[planning:complex_processes|Existing processes that are unnecessarily complex and based on unsound logic]].   - [[planning:complex_processes|Existing processes that are unnecessarily complex and based on unsound logic]].
   - [[planning:warnings_and_oversight|Implementing software that will warn of mistakes that previously went unnoticed]].   - [[planning:warnings_and_oversight|Implementing software that will warn of mistakes that previously went unnoticed]].
-  - [[planning:inconsistant_use|Not realizing that Tape Management is an ongoing process and using TapeTrack inconsistently]].+  - [[planning:inconsistent_use|Not realizing that Tape Management is an ongoing process and using TapeTrack inconsistently]].
   - [[planning:tapetrack_design|The design of TapeTrack, which shows tapes in all locations, not just one]].   - [[planning:tapetrack_design|The design of TapeTrack, which shows tapes in all locations, not just one]].
  
 +<note important>Understanding each of these challenges in detail is a good investment in the future success of your TapeTrack deployment.</note>
 ====== Implementation Phases ====== ====== Implementation Phases ======
  
Line 28: Line 29:
 Operations staff will almost always be key participants in the TapeTrack implementation and day-to-day usage. These staff will be involved in: Operations staff will almost always be key participants in the TapeTrack implementation and day-to-day usage. These staff will be involved in:
  
-  - Entering and removing tapes from robotic libraries. +  * Entering and removing tapes from robotic libraries. 
-  - Slotting tapes in racking systems. +  * Slotting tapes in racking systems. 
-  - Scratch tape management. +  * Scratch tape management. 
-  - Scanning tapes in and out of the system. +  * Scanning tapes in and out of the system. 
-  - Working with third parties such as offsite vendors to transfer custody of each tape. +  * Working with third-parties such as offsite vendors to transfer custody of each tape. 
-  - Auctioning any alerts issued by TapeTrack.+  * Actioning any alerts issued by TapeTrack.
 ==== Backup Administrators ==== ==== Backup Administrators ====
  
 When integrating TapeTrack with backup software and robotic tape library equipment the cooperation and assistance of the backup administrators is usually necessary. Backup Administrators will be responsible for: When integrating TapeTrack with backup software and robotic tape library equipment the cooperation and assistance of the backup administrators is usually necessary. Backup Administrators will be responsible for:
  
-  - Ensuring tape management processes align with backup requirements. +  * Ensuring tape management processes align with backup requirements. 
-  - Installing TapeTrack software. +  * Installing TapeTrack software. 
-  - Setting up backup software and library integration.+  * Setting up backup software and library integration.
 ==== Auditors ==== ==== Auditors ====
  
-Auditors are often involved in setting the high level requirements for a TapeTrack implementation and for later validating the efficacy of the implementation, but it is rare for auditors to be involved during the planning for, or implementation of TapeTrack. +Auditors are often involved in setting the high-level requirements for a TapeTrack implementation and for later validating the efficacy of the implementation, but it is rare for auditors to be involved during the planning for, or implementation of TapeTrack. 
 ===== Identifying Tape Management Objectives ===== ===== Identifying Tape Management Objectives =====
  
Line 50: 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 62: 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>
 ===== Mapping the Existing Environment ===== ===== Mapping the Existing Environment =====
  
Line 75: Line 78:
   - What backup software is being used in each environment that uses tapes.   - What backup software is being used in each environment that uses tapes.
   - Who is responsible for tape management in each location.   - Who is responsible for tape management in each location.
-  - Are there any third parties handling the tapes, such as offsite vendors or outsourced tape operations. +  - Are there any third-parties handling the tapes, such as offsite vendors or outsourced tape operations.
  
 +<note tip>Consider drawing a map of your current tape environment in Video or Google Draw so that you can better visualize your tape management topography and workflow.</note>
 ===== Identifying Key Staff ===== ===== Identifying Key Staff =====
  
-Identifying keys staff who will be responsible for the implementation and day-to-day operation of TapeTrack is critical.+Identifying key staff who will be responsible for the implementation and day-to-day operation of TapeTrack is critical.
  
 These key staff may include those who are directly responsible for implementing and using the product, but they may also be staff who have no direct involvement with TapeTrack. These key staff may include those who are directly responsible for implementing and using the product, but they may also be staff who have no direct involvement with TapeTrack.
 ===== Creating a Project Plan ===== ===== Creating a Project Plan =====
  
-It is recommended that a formal project plan be created for the implementation. GazillaByte can provide a template implementation plan upon request. +It is recommended that a formal project plan be created for the implementation.  
 + 
 +<note tip>GazillaByte can provide a template implementation plan upon request.</note>  
 + 
 +===== Planning for Objections ===== 
 + 
 +It is inevitable that you will receive some level of push-back from one or more employees when TapeTrack is deployed.  
 + 
 +These objections can include: 
 + 
 +  * Why did we have to change from our old system? 
 +  * 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. 
 +  * The system is not the same as our old system. 
 +  * Why am I getting messages notifying me that I have made a mistake? 
 +  * Scanning tapes in and out is too time consuming. 
 +  * There are discrepancies between what the offsite vendor's system has and TapeTrack.
planning/introduction.1501800873.txt.gz · Last modified: 2025/01/21 22:07 (external edit)