This is an old revision of the document!
Table of Contents
Moving Volumes By Move Date
TapeTrack, using Server Utilities, can automatically move Volumes to their Next Repository when the Move Date comes within the scope set.
Moving a Volume automatically in TapeTrack is intentionally a multistep process. This allows you to control both the timing of the individual steps as well as what Volumes are moved in each step, for example you may want to move Volumes that are going offsite once or twice a week, but move Volumes from your racking to the library daily. Or you may want to expire all Volumes offsite daily but only place them into a move once a week.
Prerequisites
All Repositories that are included in the scope of the Volumes that will be targeted for automated must have a Next Repository set in their Properties tab in TapeMaster. This is the Repository that the Volumes will be placed in a move to.
Identifying Volumes To Move
Executing TMSS10ExpireByDate will identify all Volumes within the scope set that qualify to be moved. Any qualifying Volumes will have a p flag added.
Moving Volumes
Executing TMSS10MovePending will identify all Volumes, within the scope set, and place them in a move to that Repository's Next Repository.
Creating Move Lists
Using TMSS10MoveList you can create an output file (text, Excel, CSV or PDF) of all Volumes that are currently in a Move status.
These reports can be filtered to only include the relevant information you require. They can be filtered by:
- Customer-ID
- Media-ID
- Volume-ID
- Current Repository-ID
- Target Repository-ID
- Volume Flags
If required you can also remove columns from the report that are not required, creating a cleaner report with only relevant information required, eg a picking list for Tape staff only may only require the Volume-ID and location.