| |
planning:introduction [2018/02/21 17:41] – dcumming | planning:introduction [2025/01/21 22:07] (current) – external edit 127.0.0.1 |
---|
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 ==== |
| |
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 ===== |
| |
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> |
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. |