Differences

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

--- technote:moving_volumes_by_movedate [2020/09/24 02:10] – [Example Execution] Scott Cunliffe
+++ technote:moving_volumes_by_movedate [2025/02/05 01:29] (current) – Scott Cunliffe
@@ Line 3: / Line 3: @@
 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 TMSS10Sync, Simple Management Rules or manually via TapeMaster.
+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.
@@ Line 11: / Line 11: @@
 ==== Server Utilities  ====
-TapeTrack 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.
+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 Server Utilities are installed on your computer you can either:
+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 [[http://mirror-us.tapetrack.com/Windows-x64/utils/setup.exe|here]].
+  * 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/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".
@@ Line 42: / Line 42: @@
 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]].
-<sxh>
+<code>
 TMSS10ExpireByDate -S username:-password@localhost -V "US01.*.*" -R "*-100:*"
-</sxh>
+</code>
 See [[cli:tmss10expirebydate|TMSS10ExpireByDate]] for more detailed information.
@@ Line 64: / Line 64: @@
 Move all [[object:volume|Volumes]] for [[object:customer|Customer-ID]] US01, [[object:media|Media-ID]] LTO.
-<sxh>
+<code>
 TMSS10MovePending -S user:-password@localhost -V "US01.LTO.*"
-</sxh>
+</code>
 See [[cli:TMSS10MovePending|TMSS10MovePending]] for more detailed information.
@@ Line 89: / Line 89: @@
 Report all LTO [[object:volume|Volumes]] for Customer US01, moving from [[object:repository|Repository]] OFFS to [[object:repository|Repository]] SCRA.
-<sxh>
+<code>
 TMSS10MoveList -S user:-password@server -V US01.LTO.* -C OFFS -T SCRA
-</sxh>
+</code>
-See [[cli:TMSS10MoveLis|TMSS10MoveLis]] for more detailed information.
+See [[cli:TMSS10MoveList|TMSS10MoveList]] for more detailed information.
-{{tag> technote move}}
+{{tag> technote tapemaster cli move}}