====== Moving Volumes Automatically By Move Date ======

TapeTrack, using Server Utilities, can automatically move [[object:volume|Volumes]] to their [[options:repository:next_repository|Next Repository]] when the Move Date comes within the scope set.

Move dates can be set via [[cli:TMSS10Sync|TMSS10Sync]], [[object:simple_management|Simple Management Rules]] or [[master:next_move|manually via TapeMaster]].

Moving a [[object:volume|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 [[object:volume|Volumes]] are moved in each step, for example you may want to move [[object:volume|Volumes]] that are going offsite once or twice a week, but move [[object:volume|Volumes]] from your racking to the library daily.  Or you may want to expire all [[object:volume|Volumes]] offsite daily but only place them into a move once a week.

===== Prerequisites =====

==== Server Utilities  ====

TapeTrack [[cli:introduction|Server Utilities]] must be installed on the computer that will run the scheduled commands, the Server Utilities are installed alongside the Framework Server, but can be installed on any computer that has access to the  Framework Server installation.

To check if the [[cli:introduction|Server Utilities]] are installed on your computer you can either:
  * Open a command prompt and run the command ''TMSS10ExpireByDate'', if no parameters are used it will simply run the program and report the missing parameters, no database updates will be made, if this is displayed, the Server Utilities are installed.  If you get 'TMSS10ExpireByDate' is not recognized as an internal or external command, operable program or batch file, the Server Utilities are not installed or registered.  You can download the executable from [[https://mirror-us.tapetrack.com/releases/Windows-x64/utils/setup.exe|here]].
  * Check the installation directory, the default locations is C:\Program Files\TapeTrack\TapeTrack Server Utilities
  * From a command prompt, run the command ''set'' and check the Path variable for the value "C:\Program Files\TapeTrack\TapeTrack Server Utilities\bin\tapetrack";.  If your installion is in another location, look for the end of the variable location to match "TapeTrack\TapeTrack Server Utilities\bin\tapetrack".

==== Next Repository Setting ====

All [[object:repository|Repositories]] that are included in the scope of the [[object:volume|Volumes]] that will be targeted for automated movement must have a [[options:repository:next_repository|Next Repository]] value set in their Properties tab in TapeMaster.  This is the [[object:repository|Repository]] that the [[object:volume|Volumes]] will be placed in a move to.

To check or set the ''[[options:repository:next_repository|Next Repository]]'' in the [[object:repository|Repository]] options, right-click the required [[object:repository|Repository]] and select properties or double click the [[object:repository|Repository]] and select the options tab.

See [[options:repository:next_repository|Next Repository Options]] for more information.

{{options:repository:tapemaster_repository_option_next_repository.png}}

<note important>If ''[[options:repository:next_repository|Next Repository]]'' is set to ''<No Selection>'' the [[object:volume|Volumes]] will have a ''p'' [[common:volume_flags|Flag]] assigned during the following process but will not be placed into a move.</note>

===== Identifying Volumes To Move =====

Executing [[cli:tmss10expirebydate|TMSS10ExpireByDate]] will identify all [[object:volume|Volumes]] within the scope set that qualify to be moved.  Any qualifying [[object:volume|Volumes]] will have a ''p'' [[common:volume_flags|Flag]] added.

{{technote:p_flag.png}}

==== Example Execution ====

Identify all [[object:volume|Volumes]] for Customer US01 with a Next Move Date range of 100 days ago until today.

Using the date range -100 to today means as log as you execute the program more than once every 100 days, all [[object:volume|Volumes]] with a Next Move Date up to the day it is run will have a ''p'' [[common:volume_flags|Flag]] added.  The date range can be set to any range required, as well as into the future allowing you to place [[object:volume|Volumes]] into a move status that will compensate for return time delays.  This means if it takes two days for your offsite provider to action the physical return of [[object:volume|Volumes]] from the time they are recalled, expiring the [[object:volume|Volumes]] two days in advance so they are shipped on the required day, saving the added expense of unnecessary storage costs and faster reuse of Scratch [[object:volume|Volumes]].

<code>
TMSS10ExpireByDate -S username:-password@localhost -V "US01.*.*" -R "*-100:*"
</code>

See [[cli:tmss10expirebydate|TMSS10ExpireByDate]] for more detailed information.

===== Moving Volumes =====

Executing TMSS10MovePending will identify all [[object:volume|Volumes]], within the scope set, and place them in a move to that [[object:repository|Repository's]] [[options:repository:next_repository|Next Repository]].

<note important>[[object:volume|Volumes]] in a [[object:repository|Repository]] with No [[options:repository:next_repository|Next Repository]] value set will not be placed in a move.

See [[options:repository:next_repository|Next Repository Options]] for more information.</note>

{{m_flag.png}}

Once the [[object:volume|Volumes]] are placed in a Move Status, the Next Move Date is reset to Permanent (no Next Move Date).  If you require a Next Move Date to be set, this can be done via Simple Management Rules based off Data Cluster Assignment or Repository values.

==== Example Execution ====

Move all [[object:volume|Volumes]] for [[object:customer|Customer-ID]] US01, [[object:media|Media-ID]] LTO.

<code>
TMSS10MovePending -S user:-password@localhost -V "US01.LTO.*"
</code>

See [[cli:TMSS10MovePending|TMSS10MovePending]] for more detailed information.
===== Creating Move Lists =====

While [[cli:TMSS10MovePending|TMSS10MovePending]] will give you a report of all [[object:volume|Volumes]] that were placed into a move when executed, [[cli:TMSS10MoveList|TMSS10MoveList]] gives you the ability to produce a movement report that contains all [[object:volume|Volumes]] currently in a move status.  This can be useful to supply to Library staff as picking/packing list at the end of the week rather than supplying daily lists or manually combining separate reports.

Using [[cli:TMSS10MoveList|TMSS10MoveList]] you can create an output file (text, Excel, CSV or PDF) of all [[object:volume|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:
  * [[object:customer|Customer-ID]]
  * [[object:media|Media-ID]]
  * [[object:volume|Volume-ID]]
  * [[object:repository|Current Repository-ID]]
  * [[object:repository|Target Repository-ID]]
  * [[common:volume_flags|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 [[object:volume|Volume-ID]] and location.

==== Example Execution ====

Report all LTO [[object:volume|Volumes]] for Customer US01, moving from [[object:repository|Repository]] OFFS to [[object:repository|Repository]] SCRA.

<code>
TMSS10MoveList -S user:-password@server -V US01.LTO.* -C OFFS -T SCRA
</code>

See [[cli:TMSS10MoveList|TMSS10MoveList]] for more detailed information.


{{tag> technote tapemaster cli move}}