Differences

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

--- cookbook:simplemanagement [2017/06/02 16:48] – [Every 2nd Wednesday of the month] jthatcher
+++ cookbook:simplemanagement [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Simple Management Cookbook ======
-The purpose of this section is to provide guidance on how to configure Simple Management to automate the scheduled movement of media from one repository to another.
+The purpose of this section is to provide practical examples on how to configure Simple Management to automate the scheduled movement of [[object:media|Media]] from one [[object:repository|Repository]] to another.
-The prerequisites being that the following option would be set in properties for the required repositories associated with the intended Simple Management rule, as per the example image below.
+See the [[subsystem:simplemanagement|Simple Management section]] for a detailed description.
-  * Force Simple Management option is set to True.
+===== Enabling Simple Management =====
-  * Next Repository option is set to the next repository in the topology as the intended rule would dictate.
-{{::sm-rep-fsm-nxtrep.png}}
+Simple Management can be enabled for a [[object:volume_target|Target]] [[object:repository|Repository]], or for a specific [[object:volume|Volume]].
-===== Every 2nd Wednesday of the month =====
-First of all check and confirm that the properties of the required repositories have had the Force Simple Management option set to True, and the Next Repository option is set to the repository as per the intended rule.
+When enabled at a [[object:repository|Repository]] level, a matching Simple Management Rule must exist with a matching scope for every [[object:volume|Volume]] moved to that [[object:repository|Repository]].
-Select the Simple Management tab above the Inventory window to the right of the Customer tree view.  Click with the right hand mouse button and select Add.
+When enabled for a specific [[object:volume|Volume]], a Simple Management Rule must exist with a matching scope that for every [[object:repository|Repository]] that the [[object:volume|Volume]] will move to.
-{{::sm-addsmrule.png}}
+==== Enabling at a Repository level ====
+  * ''Force Simple Management'' option is set to ''True''.
+  * As Simple Management sets a Next Move Date, and [[object:volume|Volumes]] are traditionally moved using the [[cli:TMSS10MovePending|TMSS10MovePending]] program, it is recommended that the ''Next Repository'' option is set to an appropriate value.
-This will open the Edit New Simple Management window and display the Identity tab.  On this tab enter an appropriate description into the Description field.  In this example 'Return 2nd Wednesday' has been entered.
+{{:tapemaster:simple_management_repository_options.png}}
-{{::sm-rtn2ndwed-id.png}}
-Next select the Options tab, and set the following.
-  * Expand the Exclusion Days and set to True for Wednesday.
+===== Recipes =====
-  * Set Movement Direction from sending repository (SITE) to receiving repository (OFFS).
-  * Set Volume Attributes, Media-ID Filter to your container ID
+[[cookbook:simplemanagement:restore_previous_date|Restore or Maintain Next Move Date]]
-===== The 2nd last day of each month =====
+[[cookbook:simplemanagement:every_second_wednesday|Every 2nd Wednesday Of The Month]]
+[[cookbook:simplemanagement:second_last_day_month|2nd last day of each month]]
+<- ^ :cookbook:introduction|Cookbook ^ cookbook:volume_id_building|Volume-ID Building ->
+{{tag> cookbook}}