TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace:
master:remove_volume_container_auto

Differences

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

Link to this comparison view

Next revision		Previous revision
master:remove_volume_container_auto [2018/08/28 02:38] – created Scott Cunliffemaster:remove_volume_container_auto [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== Automate Volume Removal From Containers ======+====== Automate Volume Movement Based On Container Movement ======
  
 Volumes can be removed from the assigned container automatically when the container move is confirmed into a selected repository.  This function can be useful in situations where returning volumes assigned to a container are always removed and placed in a library or racking, saving an operator from having to complete this procedure manually. Volumes can be removed from the assigned container automatically when the container move is confirmed into a selected repository.  This function can be useful in situations where returning volumes assigned to a container are always removed and placed in a library or racking, saving an operator from having to complete this procedure manually.
Line 5: Line 5:
 This function is set at a repository level and thus can be limited to movements to only one repository, or as many as required. This function is set at a repository level and thus can be limited to movements to only one repository, or as many as required.
  
-An example to illustrate the process and which repositories to set:+===== Example =====
  
-Business ACME writes data to tape, packs the volumes into a container and sends them to an offsite vault.  The vault confirms arrival of the container when it arrives and places it, still sealed, into their storage rack.+Business ACME writes data to tape, packs the volumes into a barcoded container, seals it, and sends it to an offsite vault.  The vault confirms arrival of the container and places it, still sealed, into their storage rack.
  
 When the container is recalled the vault ships it back to ACME.  On delivery the container is opened and the volumes are placed back in racking for scratch volumes to be re-used.  The container, empty, is then placed back in storage until required again. When the container is recalled the vault ships it back to ACME.  On delivery the container is opened and the volumes are placed back in racking for scratch volumes to be re-used.  The container, empty, is then placed back in storage until required again.
Line 15: Line 15:
 We set any container in a move status to OFFS to move any volumes contained within it and as the vault does not open the containers we also set OFFS to confirm any volumes when it is itself confirmed. We set any container in a move status to OFFS to move any volumes contained within it and as the vault does not open the containers we also set OFFS to confirm any volumes when it is itself confirmed.
  
-We set the SCRA repository to automatically remove volumes from a container on confirmation of delivery. The volumes are scanned in to the scratch racking, so are not automatically confirmed as they were at the vault.+We set any container in a move status to SCRA repository to move any volumes contained within it and to 
 + automatically remove those volumes from the container on confirmation of delivery. The volumes are scanned in to the scratch racking individually, so are not automatically confirmed as they were at the vault. 
 + 
 +===== Settings ===== 
 + 
 +Offsite (OFFS) repository 
 + 
 +{{daytoday:d2d_tapemaster_move_confirm_container.png}} 
 + 
 +Scratch (SCRA) repository 
 + 
 +{{daytoday:d2d_tapemaster_move_empty_container.png}} 
 + 
  
master/remove_volume_container_auto.1535423901.txt.gz · Last modified: 2025/01/21 22:07 (external edit)