This appendix describes SPM configuration parameters, and sample configuration files. The following information is included:
The following sections describe the default SPM parameters.
This parameter is the name given to the Storage Plan.
Y deletes the object.
N only deletes the instance.
This parameter can be overridden in the configuration file.
The Disc Cleaning strategy is not applicable when set to Y.
This parameter is the given medium name (it is better if you provide the same name as DIVArchive Group/Array Name).
This parameter is the name of the Storage Manager. This value is not used and Oracle recommends keeping the default value (DIVA).
This parameter is the DIVArchive group or array name.
This parameter is only applicable to Storage slots, and only for disk arrays configured as mediums. It monitors the medium's use (available space, used space, and so on). Select Y (applies watermarking), N (does not apply watermarking), or M (a combination of watermarking that is event dependent) to specify whether to apply watermarking to this medium. See Actions, Action Steps, and Action States, and Watermark Based Disk Cleaning Management for detailed information on watermarking.
In general Oracle recommends that slots are not deleted, but rather disabled. Deleting a slot does not remove the content from the DIVArchive system.
For Storage slots, setting the Slot End Time to 0 forces SPM to delete any content created by this slot, and after all of the content is removed, the Storage slot can be deleted or disabled. If you want to retain the content in a Storage slot, but no further processing of future actions is required, disabling the slot instead of deleting it is the safer way to do this.
See Watermark Based Disk Cleaning Management for details on watermarking.
This parameter is the disc cleaning strategy to use:
Last Access Time
Size
This parameter is the name given to the slot.
This parameter is the name given to the Storage Plan.
This parameter is automatically generated by SPM and not editable.
This parameter is the medium associated with the slot.
This parameter is the type of request as follows:
A Copy request is initiated at the beginning of the slot, and then a Delete request is initiated at the end of the slot.
This request is initiated at the beginning of the slot.
This request is initiated at the beginning of the slot.
This request is initiated at the beginning of the slot.
This parameter identifies when the action will occur. If set to zero, the action is initiated as soon as the object is archived. If set to another number, for example 10 (minutes), the action will execute 10 minutes after the original object is archived.
This parameter is the time (in minutes) from the object creation, and points to the slot end.
This parameter is the time in HH:MM format (00:00 to 24:00), and points to the time of the day when execution can start.
This parameter is the Time in HH:MM format (00:00 to 24:00), and points to the time of the day after which execution cannot start.
If the Request Execution Begin Time and Request Execution End Time are 00:00 and 24:00 respectively, there are no limitations on execution time. If the begin time is greater than end time, then the execution interval is taken from the begin time of the first day to the end time of the second day (including midnight).
This parameter is the priority of operations for SPM and the DIVArchive Manager.
This parameter is the name you want to call the filter.
This parameter is automatically generated by SPM and not editable.
This parameter is the name of the media to monitor.
This parameter is the object category to display. Leaving this field blank performs no filtering and all objects are displayed regardless of the category. You can use any combination except abc*def.
This parameter is the source to display. Leaving this field blank performs no filtering and all objects are displayed regardless of the source. You can use any combination except abc*def.
This parameter is the object name to display. Leaving this field blank performs no filtering and all objects are displayed regardless of the name. You can use any combination except abc*def.
This parameter is the minimum object size. A value of zero indicates no restrictions from the Maximum Object Size.
This parameter is the minimum object size. A value of zero indicates no restrictions from the Minimum Object Size.
This parameter is the object size units filter (KB, MB, GB).
This parameter is the name of the Storage Plan to filter.
The following sections describe action definitions that are only used with Transcode Archived, Metadata Archive, and Restore slots.
This parameter is the name you want to call the filter.
This parameter is the name of the Storage Plan to filter.
This parameter is automatically generated by SPM and not editable.
This parameter is only used with Transcode Archived, Metadata Archive, and Restore slots.
This parameter is the object category to display. Leaving this field blank indicates this parameter is not usable. You can use any combination except abc*def.
This parameter is the source to display. Leaving this field blank indicates this parameter is not usable. You can use any combination except abc*def.
This parameter is the object name to display. Leaving this field blank indicates this parameter is not usable. You can use any combination except abc*def.
The following rules are only used with Transcode Archived and Metadata Archive slots.
This parameter is the name of the transcoded object. The ^ character results in using the original object name, and can be added to. For example, ^.txt.
This parameter is the category of the transcoded object. The ^ character results in using the original object category, and can be added to. For example, ^.txt.
This parameter is the name of the transcoded object. The ^ character results in using the original object name, and can be added to. For example, ^.txt.
This parameter is the category of the transcoded object. The ^ character results in using the original object category, and can be added to. For example, ^.txt.
Always leave this parameter set to the default ^ character.
Always leave this parameter set to the default ^ character.
This parameter is only used with Transcode Archived, Metadata Archive, and Restore requests.
This parameter indicates to use an existing transformation rule.
This parameter is automatically generated by SPM and not editable.
For Metadata Archive this parameter is the Source/Destination to archive. For Restore this parameter is the Source/Destination to restore.
This parameter is the Pathroot to use for Metadata Archive or Restore.
This parameter is any additional options necessary for Transcode Archived, Metadata Archive, or Restore.
This parameter is comments for Transcode Archived, Metadata Archive, or Restore.
This parameter is the DIVArchive Quality of Service.
This parameter is only used for Transcode Archived and Metadata Archive.
This parameter is only used for Transcode Archived and Metadata Archive.
spm.conf.ini)
#####################################################################
# SPM4 Configuration File
#
# Front Porch Digital, Inc. (C) 2005, 2006, 2007
# All rights reserved.
#
# $Source: src/main/conf/spm.conf.ini $
# $Date: 2015/01/09 17:21:34EST $
# $Revision: 1.2 $
# $Author: Ramachandran, Prakash (PRamachandran) $
#####################################################################
# DIVA SPM service name
# This variable can be used to specify the name of the windows service. This is
# usefull when multiple SPM are running on the same server by giving
# different names for each SPM
# If this variable is used, the service name will be "DivaSpm-<SERVICE_NAME>".
# Default: If this variable is unset, the service name will be "DivaSpm".
#SERVICE_NAME=
#####################################################################
# MANAGER: Parameters for DIVArchive Manager
#####################################################################
# The ip address and port of DIVA Manager for SPM to connect to.
# Address default is "localhost". Port valid range is 1..65535. Default is 9000.
DIVA_MANAGER_ADDRESS = localhost
DIVA_MANAGER_PORT = 9000
#####################################################################
# ORACLE: Connection parameters for the database
#####################################################################
# NB! For the following "ORACLE" parameters no defaults will be assumed!
ORACLE_USER = diva
ORACLE_CONNECTION = lib5
# Maximum number of simultaneous DB connections. Valid range is 1..20.
# Default is 5.
ORACLE_POOL_SIZE = 5
#####################################################################
# MANAGER MONITOR: Parameters
#####################################################################
# Limit of requests (running+pending) on DIVA Manager, entire SPM service will
# try (see docs) no to surpass. Valid range is 10..500. Default is 250.
DIVA_MANAGER_MONITOR_MAX_REQUESTS = 250
# Maximum number of DIVA delete instance and delete object requests.This number is
# checked before sending new Delete Requests. This value is internaly calculated
# (it's not received by Request to Manager). Therefore it's approximation and sometimes
# we can temproraly have Number of Delete requests grate than total number of request
# (until the next refresh ).
# Valid range is 1..300. Default is 300.Disable (no any limitations) is 0.
DIVA_DELETE_MAX_REQUESTS = 300
# The following parameters are used to restrict how many RESTORE, TRANSCODE and METADATA requests SPM will
# submit to manager simultaneously.
# Kindly note that all the below three parameters must be enabled or disabled together.
# For instance DIVA_RESTORE_MAX_REQUESTS is enabled and DIVA_TRANSCODE_ARCHIVE_MAX_REQUESTS
# and DIVA_METADATA_ARCHIVE_MAX_REQUESTS is disabled.
# Example:
# DIVA_RESTORE_MAX_REQUESTS = 3
# DIVA_TRANSCODE_ARCHIVE_MAX_REQUESTS = -1
# DIVA_METADATA_ARCHIVE_MAX_REQUESTS = -1
# In the above case SPM service will fail to start.
# Valid range is 0..300. Value -1 will disable this feature. Default value is -1.
DIVA_RESTORE_MAX_REQUESTS = -1
DIVA_TRANSCODE_ARCHIVE_MAX_REQUESTS = -1
DIVA_METADATA_ARCHIVE_MAX_REQUESTS = -1
# Minimum delay in seconds between two checks of number of requests (running+
# pending) on DIVA Manager. Checks are opportunistic. Valid range is 1..600.
# Default is 30.
DIVA_MANAGER_MONITOR_DELAY = 30
# Number of seconds that an action will be delay for, if the Manager Monitor
# finds Manager at >= DIVA_MANAGER_MONITOR_MAX_REQUESTS during its execution.
# Valid range is 1..3600. Default is 60.
DIVA_MANAGER_MONITOR_ACTION_DELAY = 60
#####################################################################
# SPM: Parameters for the SPM Controller
#####################################################################
# Total number of "short" failures per action. Next "short" failure will be
# translated into a "long" failure. Valid range is 1..50. Default is 5.
ACTION_SHORT_FAILURE_LIMIT = 5
# Total number of "short" failures per step. Next "short" failure will be
# translated into a "long" failure. Valid range is 1..50. Default is 2.
ACTION_STEP_SHORT_FAILURE_LIMIT = 2
# Minimum delay in seconds before next check on request status.
# Valid range is 1..60. Default is 10.
ACTION_STEP_WATCH_DELAY = 10
# Maximum size of the ACTION QUEUE. Valid range is 1..300. Default is 100.
ACTION_QUEUE_SIZE = 100
#####################################################################
# SPM: "Rest" time for working threads
#####################################################################
# NB! The "RECOVERY" and "RECOVERY LOAD" threads never rest - they stop upon
# completion of all work.
# Rest time for the "EXECUTION" thread in seconds. Valid range is 0..600. Zero
# "0" will disable the thread completely. Default is 5.
SPM_EXECUTION_THREAD_REST = 5
# Rest time for the "UPDATE" thread in seconds. Valid range is 0..600. Zero "0"
# will disable the thread completely. Default is 20.
SPM_UPDATE_THREAD_REST = 20
# Rest time for the "LOAD" thread in seconds. Valid range is 0..600. Zero "0"
# will disable the thread completely. Default is 20.
SPM_LOAD_THREAD_REST = 20
#####################################################################
# SPM: Sizes of chunks of rows it will process at a time
#####################################################################
# Number of rows SPM will process at a time in each call of the RECOVER_ACTIONS
# procedure. Valid range is 1..65535. Default is 500.
RECOVER_ACTIONS_CHUNK = 500
# Number of rows SPM will process at a time in each call of UPDATE_ACTION_LIST
# procedure. Valid range is 1..500. Default is 50.
UPDATE_ACTIONS_CHUNK = 50
# Number of rows SPM will process at a time in each call of the GET_ACTION_LIST
# procedure. Valid range is 1..100. Default is 25.
GET_ACTIONS_CHUNK = 25
# Time before next action update inside the UPDATE_ACTION_LIST procedure,
# in minutes. Valid range is 10..65535. Default is 20160 (two weeks = 60*24*7*2)
UPDATE_ACTIONS_NEXT_UPDATE = 20160
# Delay before "long" retry of a failed action inside the UPDATE_ACTION_LIST
# procedure, in minutes.
# Valid range is 10..65535. Default is 720 (one day = 60*24).
UPDATE_ACTIONS_RETRY_FAILED_DELAY = 720
#####################################################################
# SPM: Processing Options
#####################################################################
######### --> CAUTION! COMPLETE OBJECT DELETION! <-- #########
# This feature must be managed carefully, since we can lose objects. This parameter must be enabled for SPm to delete objects.
## Additionally delete object must be enabled or disabled for each storage plan separately during
# its configuration in configuration utility for additional security & flexibility.
# Delete object is enabled only when it is enabled both here and also Storage plan configuration.
# Note that, if this parameter is disabled here, allowing it for a storage plan will have no effect.
# Delete object is executed only in the following condition satisfy
# 1) This parameter ALLOW_OBJECT_DELETION must be enabled
# 2) Delete object must be enabled for the storage-plan level through configuration utility.
# 3) All The storage slot(s) in the storage-plan associated with the object must have an slot end time.
# 4) Delete object will be executed by the storage slot that has the highest end time in the storage plan.(Please note an object can be associated with only one storage plan)
# If multiple storage slots have max end time in a storage-plan, the slot with max slot id among the slot with max end time will do the delete object.
# 5) Just enabling ALLOW_OBJECT_DELETION will not acknowledge Storage slot medium water mark and Delete object is execute at the end of storage slot that has the highest end time in the storage plan.
# Valid range is [true,false]. Default is "false".
ALLOW_OBJECT_DELETION = false
# The below parameter DELETE_OBJECT_ONLY_LAST_INSTANCE added the following additional conditions to the SPM delete Object feature
# This parameter forces SPM to delete object at the end of a storage slot only it is the last instance in the entire DIVArchive system and that last instance exist on the storage slot
# medium that has the highest slot end time among all storage slots of the Storage plan otherwise SPM will never do a delete object at the end of the storage slot it will always only do delete instance
# at the end of a storage slot.
# The following condition needs to satisfied for this feature to work.
# 1) This parameter requires ALLOW_OBJECT_DELETION also be enabled. Just enabling DELETE_OBJECT_ONLY_LAST_INSTANCE will have no effect and SPM delete object feature will not be enabled.
# 2) This parameter DELETE_OBJECT_ONLY_LAST_INSTANCE must be enabled.
# 3) Delete object must be enabled for the storage-plan level through configuration utility.
# 4) All The storage slot(s) in the storage-plan associated with the object must have an slot end time.
# 5) Delete object will be executed by the storage slot that has the highest end time in the storage plan.(Please note an object can be associated with only one storage plan)
# If multiple storage slots have max end time in a storage-plan, the slot with max slot id among the slot with max end time will do the delete object.
# 6) At the end of the storage slot if more than 2 instances exist in the DIvarchive system or on the medium, only delete instance is executed.
# 7) Delete object is executed only if one instance exist on the entire DIVArchive system and that one instance exist on the medium of the storage slot that has the
# Highest slot end time among all storage slots of the storage plan.
# 8) If the medium of storage slot that has the highest end time is water marked the delete object is postponed until watermark condition is satisfied.
DELETE_OBJECT_ONLY_LAST_INSTANCE = false
# Defines wether SPM will use original or transformed object name as "target"
# object name in METADATA_ARCHIVE step (Default is "true):
# - true: use transformed object name
# - false: use original object name
METADATA_ARCHIVE_TRANSFORMED_OBJECT_NAME = true
#####################################################################
# DSM: Processing Options
#####################################################################
# Priority of the requests produced by DELETE INSTANCE (W) actions.
# Valid range is 1..100. Default is 15.
DSM_DIW_REQUEST_PRIORITY = 15
#####################################################################
# DSM: "Rest" time for working threads
#####################################################################
# Rest time for the "SPACE_MONITOR" thread in seconds. Valid range is 0..600.
# Zero "0" will disable the thread completely. Default is 10.
DSM_SPACE_MONITOR_THREAD_REST = 10
#####################################################################
# DSM: Sizes of chunks of rows it will process at a time
#####################################################################
# Number of Actions DSM will process at a given time.
# procedure. Valid range is 1..65535. Default is 50.
DSM_ACTIVATE_ACTIONS_CHUNK = 50
#####################################################################
# DSM: Disk Arrays to be monitored
#####################################################################
# Description of disk arrays. For each array, an ARRAY<i> parameter has to be
# created, with <i> indicating the array number. The first array number is 1.
# <i> has to be increased always by one.
#
# The information on array is the following:
#
# "array name";"watermark low-level percent";"watermark high-level percent"
# [[;"mounted disk path"] ...]
## where:
# "array name" - name of the disk array, as it named in
# DIVA (It is not the SPM "medium" name!)
# "watermark low-level percent" - number from 0 to 100 - lower disk space
# usage percent: DSM will try to reach this
# percent when cleaning
# "watermark high-level percent" - number from 0 to 100 - higher disk space
# usage percent: DSM will start cleaning
# process when disk space usage is higher
# than this level
# ["mounted disk path"]... - mount points of array disks. None, one or
# many, separated by ";". No spaces allowed.
# If one or many, DSM will access arrays via
# filesystem ("old") interface.
# If none, DSM will access arrays via DIVA
# API ("new") interface (recommended).
#
# Windows specific: If the monitored disk is a password protected network
# share, the following syntax is allowed as a mount point:
# cifs://user:pwd@\\nas\share
# When SPM service is configured with CIFS disk, The login of the SPM service must be changed from the
# default "Local System" to a valid Windows User.
#Following are the steps to change the spm service login.
# Step 1: Start -> run
# Step 2: Type services.msc in the rum prompt and press enter.
# Step 3: This should open the Windows service Control Manager
# Step 4: Select the SPM service to which you want to change the login.
# Step 5: Right click on the SPM service and select properties.
# Step 6: Select the Log on tab in the properties window of the SPM service.
# Step 7: Select the radio button next to "This account".
# Step 8: Enter a valid windows user and password
# Step 9: Click apply or ok button to commit the changes.
#ARRAY1 = FastDisk;75;90;/home/diva;/usr/bin
#ARRAY2 = SlowDisk;60;75;/tmp
#ARRAY3 = SlowDisk2;60;99
#ARRAY4 = FullDisk;50;80
#####################################################################
# SPM/DSM: Additional parameters
#####################################################################
# Level of tracing. Valid range is 1..2. Default is 2.
# "1" - will trace "entry" and "exit" points in all important functions.
# WARNING! Will generate big volume of trace! Must be used for 'debug'
# and 'validation' purposes only!
# "2" - will produce normal, 'production' trace.
#
TRACE_LEVEL = 2
spm.trace.ini)################################################################### # SPM Trace Configuration File # # Front Porch Digital, Inc. (C) 2005, 2006, 2007 # All rights reserved. # # $Source: spm.trace.ini $ # $Date: 2007/12/13 15:43:35EST $ # $Revision: 1.8 $ # $Author: Ramachandran, Prakash (PRamachandran) $ ################################################################### # uncomment the following lines to trace ################################################################### ################################################################### # Global parameters ################################################################### @timestep=60 @sizelimit=200 @timetolive=10 @tracelevel=3 @tracemanagerlog=0 ################################################################### # Daemon and Managers ################################################################### !SPMService !Config !DBManager !CommManager !FSManager !ManagerMonitor !TraceWrapper ? ################################################################### # DivaOracle Interface ################################################################### !Oracle #DbConnectionPool #DbConnection ################################################################### # SPM Controller ################################################################### !RecoveryThread !RecoveryLoadThread !LoadThread !UpdateThread !ExecutionThread !ActionQueue ################################################################### # DSM Controller ################################################################### !SpaceMonitorThread !ArrayContainer ################################################################### # Action Processing Level ################################################################### !RestoreAction !MetaDataArchiveAction !TranscodeArchiveAction !ArchiveRequestAction !DeleteObjectAction !DeleteInstanceAction !CopyAction !RequestAction !Action !ActionRecord ################################################################### # Action Step Processing Level ################################################################### !RESTORE_STEP !ARCHIVE_STEP !TRANSCODE_ARCHIVE_STEP !LINK_OBJECTS_STEP !DELETE_OBJECT_STEP !DELETE_INSTANCE_W2_STEP !DELETE_INSTANCE_W1_STEP !DELETE_INSTANCE_STEP !COPY_STEP !RequestActionStep !ActionStep ################################################################### # Method Tracer ################################################################### #MethodTracer