This chapter describes installation and configuration of SPM. References to installation and configuration procedures of additional software are included only to the extent required to allow interaction of those components with SPM. Refer to the specific additional software documentation in the Oracle DIVArchive documentation library for full installation and configuration instructions for specific additional elements where necessary.
This chapter includes the following information:
There are several prerequisites required before installing SPM as follows:
DIVArchive 7.6 and later only supports the following database packages:
Windows only supports DIVAOracle Database Oracle 12c package OracleDivaDB_3-0-0_12_1_0_2_0_SE2_Windows_64-bit.zip and later. No previous database package will work with DIVArchive 7.6 and later.
The OracleDivaDB_3-0-0_12_1_0_2_0_SE2_Windows_64-bit.zip and later releases no longer include the 32-bit Oracle database client.
Linux only supports DIVAOracle Database package OracleDivaDB_3-0-0_12_1_0_2_0_SE2_OEL7_x86_64.sh and later.
The database user name and password must be the same ones used for the DIVArchive installation.
DIVArchive must be installed and running.
DIVArchive SPM Service must be installed and running.
SPM uses a plain text file to store its configuration parameters. The configuration file, named spm.conf.ini, is supplied with SPM and is located in the %DIVA_HOME%\Program\SPM\bin folder. You must rename the file to spm.conf, and change the parameter values to meet your requirements using a plain text editor (for example, Notepad or Notepad++). Although all parameters are important, some are more important than others, and the following sections describe all parameters.
The following describes the parameters used in the SPM configuration file. You can also set some parameters using the DIVArchive Configuration Utility. However, the settings in the SPM configuration file called METADATA_ARCHIVE_TRANSFORMED_OBJECT_NAME and ALLOW_OBJECT_DELETION will always override any settings created through the Configuration Utility.
The following parameter is for the SPM Windows Service Name:
SERVICE_NAMEThis parameter identifies the DIVArchive SPM Service Name. You use this variable to specify the name of the Windows Service. This is useful when multiple instances of SPM are operational on the same server by giving a different name to each instance.
If you use this variable, the service name will be DIVArchive Spm - <SERVICE_NAME>. If you do not use this variable, the service name will be DIVArchive Spm.
The following parameters are for the DIVArchive Manager:
DIVA_MANAGER_ADDRESSThis parameter identifies the IP address, or DNS Name, of the DIVArchive Manager host computer. The default value is localhost.
DIVA_MANAGER_PORTThis parameter identifies the DIVArchive Manager port number. The default value is 9000.
The following are connection parameters for the DIVArchive Oracle Database:
ORACLE_USERThis parameter identifies the DIVArchive Database user name. There is no default for this parameter, but the typical user name is diva.
ORACLE_PASSWORDThis parameter identifies the DIVArchive Database user password. There is no default for this parameter.
ORACLE_CONNECTIONThis parameter identifies the DIVArchive Database connection string. This is usually the SQL*Net address name declared in the local Oracle client TNSNAMES.ORA file for the DIVArchive Oracle instance. The typical connect string is lib5.
ORACLE_POOL_SIZECaution:
Do not change this value. Reducing the value can lead to database connection issues, and cause SPM to freeze.This parameter identifies the maximum number of database connections allowed by SPM. The default value is 5.
The following are parameters for the SPM Manager Monitor:
DIVA_MANAGER_MONITOR_MAX_REQUESTSSPM will check with the DIVArchive Manager to find out how many requests are currently processing before it sends any requests. This parameter limits the number of requests (processing and pending from all sources) the SPM service will attempt to send to the DIVArchive Manager. If the number of requests already processing on the Manager is greater than this setting, SPM will not send any additional requests at that time. The valid range is 10 to 500, and the default value is 250.
DIVA_DELETE_MAX_REQUESTSSPM will check with the DIVArchive Manager to find out how many requests are currently being processed. If the number is less than the DIVA_MANAGER_MONITOR_MAX_REQUESTS value, SPM will verify how many Delete Object and Delete Instance requests are being processed. If the number is less than this parameter's value, SPM will send additional Delete requests equal to the difference between the number of Delete requests processing, and the value of this parameter.
Example:
DIVA_MANAGER_MONITOR_MAX_REQUESTS = 100 DIVA_DELETE_MAX_REQUESTS = 50
In this example, when SPM checks with the Manager, if the Manager is currently processing 75 requests total, and only 25 of them are Delete requests, SPM will send another 25 Delete requests to Manager, because both numbers are less that the parameter's value in the configuration file. The valid range is 1 to 300, and the default value is 300.
This value identifies how many of this type of request are simultaneously processed from the Action Queue.
This value cannot exceed the value of DIVA_MANAGER_MONITOR_MAX_REQUESTS.
DIVA_RESTORE_MAX_REQUESTS, DIVA_TRANSCODE_ARCHIVE_MAX_REQUESTS, and DIVA_METADATA_ARCHIVE_MAX_REQUESTSThese parameters restrict the number of Restore, Transcode Archived and Metadata Archive requests SPM can submit to the Manager simultaneously.
These parameters must all be enabled or disabled together.
The valid range is 0 to 300 and the default value is -1.
The value you use identifies how many of this type of request are allowed in the Action Queue. Using the default value of -1 disables these parameters. SPM will not execute these actions if the parameter is set to a value of 0.
Example:
DIVA_RESTORE_MAX_REQUESTS=3 DIVA_TRANSCODE_ARCHIVE_MAX_REQUESTS=52 DIVA_METADATA_ARCHIVE_MAX_REQUESTS=100
In this example, SPM will start normally using these configuration settings because they are all enabled, even though the values are different for each parameter (3, 52, and 100).
Example:
DIVA_RESTORE_MAX_REQUESTS=3 DIVA_TRANSCODE_ARCHIVE_MAX_REQUESTS= -1 DIVA_METADATA_ARCHIVE_MAX_REQUESTS= -1
In this example, SPM will fail to start using these configuration settings because the first one is enabled with a value of 3, but the next two parameters are disabled. They must all be either enabled or disabled, not a combination of both.
DIVA_MANAGER_MONITOR_DELAYThis parameter identifies the number of seconds between checks of the number of requests (processing and pending) on the DIVArchive Manager. The valid range is 1 to 600, and the default value is 30.
DIVA_MANAGER_MONITOR_ACTION_DELAYThis parameter identifies the number of seconds to delay an action for execution if the DIVArchive Manager is processing more than the value of the DIVA_MANAGER_MONITOR_MAX_REQUESTS parameter during its execution. The valid range is 1 to 3600, and the default value is 60.
The following are parameters for the SPM Controller:
ACTION_STEP_WATCH_DELAYThis parameter identifies the minimum delay (in seconds) before the next check on the request status. The valid range is 1 to 60, and the default value is 10.
ACTION_QUEUE_SIZEThis parameter identifies the maximum size of the Action Queue, including the number of actions that can be stored in the queue. The valid range is 1 to 300.
The following are rest time parameters for SPM working tasks:
SPM_EXECUTION_THREAD_RESTThis parameter identifies the resting time for the Execution Task in seconds. The valid range is 0 to 600, and the default value is 5. Entering 0 disables the task completely.
SPM_UPDATE_THREAD_RESTThis parameter identifies the resting time for the Update Task in seconds. The valid range is 0 to 600, and the default value is 20. Entering 0 disables the task completely.
SPM_LOAD_THREAD_RESTThis parameter identifies the resting time for the Load Task in seconds. The valid range is 0 to 600, and the default value is 20. Entering 0 disables the task completely.
Note:
The Recovery Load Task will never rest; it stops upon completion of all work.The following are Row Chunk Size parameters that SPM will process simultaneously:
RECOVERY_ACTIONS_CHUNKThis parameter identifies the number of actions SPM will process (from the database) simultaneously during each call of the Recovery Task. The valid range is 1 to 65535, and the default value is 500.
UPDATE_ACTIONS_CHUNKThis parameter identifies the number of actions SPM will process simultaneously during each call of the Update Task. The valid range is 1 to 500, and the default value is 50.
GET_ACTIONS_CHUNKThis parameter identifies the number of actions SPM will process simultaneously during each call of the Load Task. The valid range is 1 to 100, and the default value is 25.
UPDATE_ACTIONS_NEXT_UPDATEThis parameter identifies the time (in minutes) added to the action's date of next update after it has been updated by the Update Task. Current releases of DIVArchive SPM is more dynamic in nature than previous release, and constantly reexamines actions. The date of next update is used internally to sort the actions to be reexamined. The valid range is 10 to 65535, and the default value is 20160 (two weeks).
UPDATE_ACTIONS_RETRY_FAILED_DELAYThis parameter identifies the delay (in minutes) before a long retry of a failed action. After this value is reached, the Update Task will reschedule all actions in the FAILED LONG state to be executed again. This parameter configures the retry of SPM actions and will not retry the action if its corresponding slot is modified after the action is put to a FAILED_LONG state - it will wait for the UPDATE_ACTIONS_NEXT_UPDATE to update the actions according to the latest slot changes before executing the action. The valid range is 10 to 65535, and the default value is 720 minutes.
The following are SPM processing options:
ALLOW_OBJECT_DELETIONCaution:
This parameter causes complete object deletion when enabled!An object can be deleted when a Storage Plan has no slot at a given time. You must manage this feature, and define the Storage Plans, carefully because you can lose many objects according to the Storage Plan.
The valid settings are true or false, and the default value is false.
You set this field to true to enable object deletion. The Storage Plan definition in the database can either allow or deny deletion. If deletion is denied, configuring a Storage Plan to enable deletion will have no effect.
Note:
The setting in the SPM configuration file for this parameter overrides any settings created through the DIVArchive Configuration Utility.For example, if there is slot starting at day 0 and ending at day 30, and another slot starting at day 61 with an unlimited retention, objects will be deleted after 30 days because there are no slots during the second month (days 31 to 60).
DELETE_OBJECT_ONLY_LAST_INSTANCEThis parameter works with the ALLOW_OBJECT_DELETION parameter, and forces SPM to Delete Object at the end of the Storage Slot. Deletion only occurs if this object is the last instance in the entire DIVArchive system, and this last instance exists in the Storage Slot medium that has the highest Slot End Time among all Storage Slots of the Storage Plan. Otherwise, SPM will never perform a Delete Object at the end of the Storage Slot, it will always only do a Delete Instance instead. Refer to SPM Delete Object Behavior for more detailed information.
METADATA_ARCHIVE_TRANSFORMED_OBJECT_NAMEThis parameter defines whether SPM will use the original, or transformed, object name as the target object name in a METADATA_ARCHIVE action. This setting overrides any configuration performed through the DIVArchive Configuration Utility.
The default setting is true. When this value is true, SPM uses the transformed object name. When this value is false, SPM uses the original object name.
The following is a DSM task option:
DSM_DIW_REQUEST_PRIORITYThis parameter identifies the priority of the requests produced by DELETE INSTANCE actions. The valid range is 1 to 100, and the default value is 15.
The following is a Rest Time parameter for DSM working tasks:
DSM_SPACE_MONITOR_THREAD_RESTThis parameter identifies the resting time for the DSM Task in seconds. The valid range is 0 to 600, and the default value is 10. Entering 0 disables the task completely.
The following is a Row Chunk Size parameters that DSM will process simultaneously:
DSM_ACTIVATE_ACTIONS_CHUNKThis parameter identifies the number of actions DSM will process at a given time during each call of the procedure. The valid range is 1 to 65535, and the default value is 50.
The following are parameters for disk arrays being monitored:
ARRAY{number}This parameter specifies watermark values for disk arrays. For each array, you must create an ARRAY{i} parameter, where {i} identifies the array number. The first array number is 1. The {i} must always be increased only by one.
The information for the Array is as follows:
ARRAY_NUMBER = "array name"; "watermark low-level percent"; "watermark high-level percent" ["mounted disk path1", "mounted disk path2", and so on]
ARRAY_NUMBERThis parameter identifies the name known to SPM for this array (for example, ARRAY1).
"array name"This parameter identifies the name of the disk array as it is named in DIVArchive. It is not the SPM medium name.
"watermark low-level percent"This parameter identifies a number from 0 to 100 representing the lower array space setting use percent. DSM will attempt to reach this value when cleaning.
"watermark high-level percent"This parameter identifies a number from 0 to 100 representing the higher array space use percent. DSM will start the cleaning process when the array space use is higher than this level.
["mounted disk path1", mounted disk path2", and so on]This parameter identifies the mounting points of the array disks. Either none, one, or many, separated by a comma.
No spaces are allowed.
If one or many, DSM will access arrays through the file system (old) interface.
If none, DSM will access arrays through the DIVArchive API (new) interface (recommended).
If the monitored array is a password protected network share, the following syntax is allowed as a mount point:
cifs://user:pwd@\\nas\share
When the SPM Service is configured with a CIFS array, the log in of the SPM Service must be changed from the default Local System to a valid Windows user.
Oracle DIVArchive Actors in the Linux operating system do not support UNC paths for CIFS managed disks. However, you can define a local path to a mounted SMB share. UNC paths are supported for SMB managed disks if the UNC path is directly mounted on the Windows Actors.
Use the following steps to change the SPM Service login:
Run the Windows Services application (services.msc).
Select the SPM Service requiring the log in change.
Right-click the SPM Service, and then select Properties.
Select the Log On tab in the Properties window of the SPM Service.
Select the This account option.
Enter a valid Windows user name and password.
Click Apply (or OK) to commit the changes.
Examples:
ARRAY1 = ShortClips;75;90 (this is the recommended syntax)
ARRAY2 = Raid_001;60;85;X:\;Y:\;Z:\ (this is the legacy syntax)
The following is a Trace Log level parameter:
TRACE_LEVELThis parameter identifies the level of tracing to use for the logs. The valid range is 1 to 2, and the default value is 2.
Caution:
Setting this parameter to1 will generate large volumes of trace information, and must be used for debug and validation purposes only!Setting this parameter to 1 will trace entry and exit points in all important functions.
Setting this parameter to 2 will produce a normal, production level, trace.
SPM contains three Request Type Distribution options that are defined in the SPM configuration file. These parameters restrict the number of Restore, Transcode Archived, and Metadata Archive actions that can be executed simultaneously. The default values for the following parameters are -1 in the SPM configuration file:
DIVA_RESTORE_MAX_REQUESTS
DIVA_TRANSCODE_ARCHIVED_MAX_REQUESTS
DIVA_METADATA_ARCHIVE_MAX_REQUESTS
Acceptable values for these three parameters are -1, 0, and positive integers. Leaving the configuration file settings for these parameters to the default (-1) causes SPM to ignore the settings, and the defined behavior will not be changed.
You should set all, or none, of these parameters to a value higher than the default (-1) setting. For example, you cannot set DIVA_RESTORE_MAX_REQUESTS=3, but keep DIVA_TRANSCODE_ARCHIVED_MAX_REQUESTS= -1. If only one or two parameters are defined with other values, SPM will refuse to start because of the incorrect configuration.
Note:
Whenever you change these parameter values, you must restart SPM for the new values to take effect.There are several rules for Request Type Distribution as follows:
SPM must not execute more Restore requests than the DIVA_RESTORE_MAX_REQUESTS value simultaneously. If the DIVA_RESTORE_MAX_REQUESTS=0, SPM will not execute any Restore requests.
SPM must not execute more Transcode Archived requests than the DIVA_TRANSCODE_ARCHIVED_MAX_REQUESTS value simultaneously. If the DIVA_TRANSCODE_ARCHIVED_MAX_REQUESTS=0, SPM will not execute any Transcode Archived requests.
SPM must not execute more Metadata Archive requests than the DIVA_METADATA_ARCHIVE_MAX_REQUESTS value simultaneously. If the DIVA_METADATA_ARCHIVE_MAX_REQUESTS=0, SPM will not execute any Metadata Archive requests.
SPM will attempt to reserve the configured number of actions in the SPM queue to execute the corresponding number of the requests (if available). The number of simultaneous Restore requests may be less than DIVA_RESTORE_MAX_REQUESTS, even if some Restore actions are ready to be executed immediately. This configuration must be observed for less than 50 percent of the execution time.
Example:
DIVA_RESTORE_MAX_REQUESTS=3 DIVA_MANAGER_MONITOR_MAX_REQUESTS=100
Workflow:
If Restore Actions exist and are scheduled, SPM will execute three Restore requests at the same time (most of the time).
SPM will never execute more than three Restore requests.
Sometimes (less than 50 percent of operational time) SPM will execute 0, 1 or 2 Restore requests when Restore Actions exist, and are scheduled.
If no Restore Actions exist, and are scheduled, other actions will be executed so the total amount of requests executed will be 100 (not 97).
By default, the Execute process will perform Delete Actions first, and then other request types by Slot Priority. If this feature is configured, SPM will still perform Delete Actions first, and then decide the number of Copy, Restore, Metadata Archive, and Transcode Archived requests to send, and then for each type of request, sort the actions by Slot Priority.
Example:
Two Copy Slots have the defined priorities 90 and 95, and 1000 Copy Actions are to be executed.
There are two Restore Slots with priorities 30 and 35, and 100 Restore Actions to be executed.
DIVA_RESTORE_MAX_REQUESTS=3
DIVA_MANAGER_MONITOR_MAX_REQUESTS=100
Workflow:
SPM will disregard the priority between the slot types, so 97 Copy requests will be scheduled, and 3 Restore requests will be scheduled.
SPM will schedule Restore requests with the priority of 35 first.
Delete Object and Delete Instance requests always have higher priority.
SPM requires configuration of Storage Plans before execution. You configure the SPM Storage Plans using the DIVArchive Configuration Utility.
There are two tabs in the DIVArchive Configuration Utility related to SPM configuration; Storage Plans and Slots.
The Storage Plans tab in the DIVArchive Configuration Utility has three sections:
Storage Plans
Media Groups
Filters
Each of these sections is configured independently, but associates with other sections to complete the configuration.
Oracle recommends that you use the following order when configuring SPM through the DIVArchive Configuration Utility:
Create the Storage Plans.
Create the Media Groups.
Create the Filters.
Create the slots (using the Slots tab).
The first step in configuring SPM is to create the Storage Plans. Use the following procedure to create a storage Plan:
Click the + in the Storage Plans section of the Storage Plans tab in the Configuration Utility.
When the Add New Row dialog box opens, begin configuring the new Storage Plan. Enter an name in the new Storage Plan Name field.
Use the lists to select the values for the parameter fields as follows:
This parameter identifies the name of the Storage Plan.
Caution:
You must use this parameter with caution. Data loss can occur if set incorrectly.This parameter determines whether SPM is allowed to delete the last instance of an object when there is only one instance remaining on the DIVArchive system. Set to Y or N to allow, or deny, deletion of the last instance of an object.
This parameter only applies to Storage Slots, and is overridden by the configuration of ALLOW_OBJECT_DELETION in the SPM configuration file.
Set to I for internal, or E for external origins. This parameter is typically used for all SPM actions. The internal (I) setting is for objects contained within the DIVArchive system and is the typical selection. The external (E) setting is mainly used during data migration in combination with the SPM API. Only Oracle should use the external setting in this release. For example, for use with DIVArchive Automatic Data Migration from Avalon to DIVArchive.
Select the default media from the list of media managed in the DIVArchive system. The DIVArchive Manager uses the selected media for object placement when a new object is found, and the Storage Plan in use has an active Storage Slot. This placement occurs when an Archive Request is submitted to the Manager without a destination Media, and only a Storage Plan selected in the request.
Click OK to save the Storage Plan. The new Storage Plan will be displayed in the Storage Plans section of the Configuration Utility.
The Media Groups Section has two purposes:
Any medium that is defined in the Media Groups section of the Configuration Utility Storage Plans tab is available for use by SPM. If a new object is placed on a medium not included in the Media Groups list, it will not be managed by SPM and is assigned the SPM_DEFAULT Storage Plan.
To select a medium as the target for actions when creating slots, it must be defined in the Media Groups list.
Use the following procedure to create a Media Group:
Navigate to the Configuration Utility Storage Plans tab.
Click the + icon on the top of the Media Groups section.
When the Add New Row dialog box appears, begin configuring the new mediums.
Enter the information in the appropriate fields, and use the menu lists to select the remaining options as follows:
Enter the Medium Name in the Medium Name field.
Enter the desired Storage Name in the Storage Name field. The recommended Storage Name is DIVA. This value is not currently in use.
Select the Tape Group or Disk Array to be associated with this medium from the list.
The selections available in the list are determined by what media is defined in the DIVArchive system.
Monitors the Medium's usage (available space, used space, and so on). Select Y, N, or M to specify whether to apply watermarking to this medium. Refer to Sections 1.7.1 and 1.8 for detailed information on Watermarking.
In general it is recommended that slots are not deleted, but disabled instead. Deleting a slot does not remove the content from the DIVArchive system.
In the case of a Storage Slot, setting the Slot End Time to 0 will force SPM to delete any contents created by this slot and once all the contents are removed, the Storage Slot can be deleted or disabled. If retaining the content in the Storage Slot is desired, but no further processing of future actions is required, disabling the slot instead of deleting it is the safer way to do this.
The Watermark-Based Disk Cleaning Management options are as follows:
This selection applies watermarking.
This selection does not apply watermarking.
This selection applies a combination of watermarking. The disk cleaning action taken depends on what event occurs first; either the slot reaches it's End Time, or the High Watermark is reached.
Mixed Mode only works if Once Only is set to yes (Y) for the slot.
Watermarks are only used for Storage Slots, and only for disk arrays configured as Mediums.
Defines the cleaning strategy to perform on objects marked for deletion on the Array when the high watermark is reached. See Watermark Based Disk Cleaning Management for detailed information on disk cleaning management.
There are two options available:
Older objects are cleaned up before recently accessed objects.
The largest objects are cleaned up first until the Low Watermark is reached.
Click OK to complete the process.
The new Media Group is now displayed in the Media Groups section of the Storage Plans tab.
Filters determine whether an action must be performed on an object, or if it should be ignored. Filters only functions for mediums defined in the Mediums list and monitored by SPM.
When a new object is archived into DIVArchive, and it matches a defined filter, a Storage Plan is assigned to that object as follows:
If the new object does not meet any filter criteria, the default Storage Plan will be assigned.
If an object satisfies multiple filters, it will be assigned the Storage Plan of the matching filter with the lowest Filter ID.
Use the following procedure to create a filter:
Navigate to the Configuration Utility Storage Plans tab.
Click the + icon on the top of the Filters section.
When the Add New Row dialog box appears, begin configuring the new filter.
Leaving the default * in Object Category, Object Source, and Object Name fields causes no filtering to be identified for these parameters.
Enter the information in the appropriate fields, and use the menu lists to select the remaining options as follows:
Enter the Filter Name in the Filter Name field.
The Filter ID is auto-generated by SPM starting with Filter 0.
Use the menu to select the Mediums you previously created.
Enter any object category filters you require. Leaving the default * will cause no filtering for this parameter.
Enter any object category filters you require. Leaving the default * will cause no filtering for this parameter.
Enter any object category filters you require. Leaving the default * will cause no filtering for this parameter.
Enter the minimum object size.
Enter the maximum object size.
Use the menu to select the size units (B, KB, MB, and GB. The initials refer to Byte, KiloByte, MegaByte, and GigaByte respectively).
Use the menu to select the Storage Plan to associate with this filter.
Click OK to complete the process.
The new Filter is now displayed in the Filters section of the Storage Plans tab.
There are several alternate methods of assigning a Storage Plan to an object including the following:
Assigning a new Storage Plan to an Object using the DIVArchive GUI.
Using a DIVArchive API; C++, Java, Oracle DIVA Enterprise Connect. See the appropriate API documentation in the DIVArchive Additional Features documentation library.
Including a Storage Plan name when submitting an Archive request forcefully applies a Storage Plan to the object and avoid the filters.
Media Mapping enables you to configure and alternate destination media, and to forcefully apply a Storage Plan, avoiding filters, when an object is archived to a specific tape group or disk array.
You configure Media Mapping in the DIVArchive Configuration Utility under the Sets, Groups & Media Mapping tab, in the Media Mapping section as follows:
Open the Configuration Utility and navigate to the Sets, Groups & Media Mapping tab, in the Media Mapping section.
Click the + icon to open the Add new row in Media Mapping dialog box.
Enter the appropriate information in the fields as follows:
This field is automatically system generated and is not editable.
Enter the name to use for this mapping in the Name field.
Use the menu list to select the media to use for this mapping.
Use the menu list to select the Destination Media for this mapping.
Use the menu list to select the Storage Plan to use for this mapping.
For example:
Media Array1 is mapped to Array2. In this scenario, objects archived to the media named Array1 will be transferred to the media named Array2 as its destination. If there is a filter configured with destination media as Array2, the Storage Plan configured in that filter will be assigned to the archived object.
Media Array1 is mapped to the Storage Plan named storagePlan1. In this scenario, objects archived to the media named Array1 will be assigned the Storage Plan named storagePlan1, and avoid filters.
Media Array1 is mapped to Array2, and also the Storage Plan named storagePlan1. In this scenario, objects archived to the media named Array1 will be transferred to the media named Array2 as its destination, assigned the Storage Plan named storagePlan1, and avoid filters.
The following sections describe the process for creating each different type of slot.
The Storage Slot is the only slot that has two actions associated with it. It will create a copy of the object when it starts and delete it when the slot ends, unless the medium used is watermarked. See Watermark Based Disk Cleaning Management for watermarking details.
The copy action will occur only if the slot destination medium does not already have the required number of instances identified in the slot configuration. The Delete Action will only occur if the slot is specifically configured to perform the Delete Action (slot has an ending time defined).
Use the following procedure to configure a Storage Slot:
Open the Configuration Utility, and navigate to the Slots tab.
Click the + icon on the top right of the Slots section.
When the Slot Configuration dialog box opens, configure the options as follows:
Use the menu list to select the Storage Plan to be associated with this slot.
Select the type of request for this slot (Storage, Transcode Archived, Metadata Archive, or Restore). Select STORAGE in this case.
Enter a name for the slot in the Slot Name field.
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 object is archived.
Caution:
If the Slot Begin Time and Slot End Time are both set to zero, then the behavior is unknown, except for Storage Slots.Setting this parameter to -1 indicates that the slot will never end (it is permanent). If set to another number, for example 10 (minutes), the Delete Action will execute 10 minutes after the object is archived.
If a Storage Slot's Slot Begin Time and Slot End Time are the same (for example, 0, 0 or 10, 10), the slot is what may be referred to as an idle slot. SPM creates a Copy and a DeleteInstance Action and these actions get updated but NOT executed.
The only exception is if the medium is watermarked. If the medium is watermarked then the DeleteInstance Action will be executed when a disk clean-up is necessary and it will go through the usual POSTPONED through COMPLETED cycle.
In practice, creating an idle slot is useful for mediums where an external tool creates instances (not SPM), but use of the SPM's watermark-based clean-up mechanism is desired.
Example (typical slot):
Slot Begin Time (Minutes): 10
Slot End Time (Minutes): 20
Workflow:
The original object is archived onto the source medium.
Ten minutes later, the slot actions begin and it is copied to the target medium.
SPM deletes the copy from the target medium 10 minutes later.
Example (idle slot):
Slot End Time (Minutes): 0
Slot Begin Time (Minutes): 0
Workflow:
The object is archived on medium Array1, and the idle slot is defined for medium Array2. An Array2 Copy Action is created, and the status is set to SCHEDULED. Then, an Array2 DeleteInstance Action is created, and the status is set to COMPLETED.
An external tool creates an instance on Array2 using the Copy function. The Array2 Copy Action status is set to COMPELTED, and the Array2 DeleteInstance Action status is set to POSTPONED.
The Array2 hits the High Watermark. The Array2 DeleteInstance Action is executed, and the status is set to COMPLETED.
The Array2 Copy Action status remains as COMPLETED.
Determines whether the slot is active. Selecting Y indicates the slot is enabled, and N indicates it is disabled. When a slot is disabled its actions are not executed, however they are still created, and the status is updated. When the slot is enabled again, pending actions are executed immediately.
Examples:
A new object that is archived and assigned to a Storage Plan with a Tape Storage Slot will have the Tape Slot's Copy Action created, but not executed. Therefore, no Copy request is sent to the Manager.
A DeleteInstance Action reaching its execution time will not send the Delete Instance request to the Manager, but if somebody manually deletes that instance using the Control GUI, the action will be updated to the COMPLETED status.
This field is the slot execution window opening time in 24 hour time. If set to 00:00 the slot opens at the beginning of each day. If set to another time, for example 08:00, it will open at that time (in this case 8:00 am).
This field is the slot execution window closing time in 24 hour time. If set to 24:00 the slot closes after each day. If set to another time, for example 17:00, it will close at that time (in this case 5:00 pm).
Setting the Request Execution Begin Time and Request Execution End Time to something other than an entire 24 hour period will allow for scheduling of different functions through SPM at different times of the day (for example overnight jobs). If an object is archived to the source medium outside of the designated time frame for the slot, even though the object meets the Filter and Storage Plan criteria, no actions from this particular slot will occur.
If the original object was archived to the source medium while the slot was inactive (closed) and has passed the Slot End Time, when the slot finally becomes active (open), no Delete Action will occur.
Note:
This is not the case for Storage Slots. For Storage Slots the DeleteInstance Action will still be executed.Example (non-Storage Slots):
Slot Begin Time (Minutes): 10
Slot End Time (Minutes): 20
Request Execution Begin Time (HH:MM): 08:00
Request Execution End Time (HH:MM): 14:00
Workflow:
A new object is placed onto the source medium at 07:00 (while the slot is closed). If the slot had been open at 07:00 when the new object was created it would be copied to the target at 07:10 and then deleted from the target at 07:20. Because the slot was not open when the new object was created, and the Slot End Time has passed when this slot opens at 08:00, no actions will be taken on the object.
If a new object is created on the source medium at 14:15 today, then tomorrow when this slot opens, no actions will be taken on the object because the Slot End Time has passed.
If an object is created on the source medium at 07:59 (before the slot opens), at 08:09 (10 minutes after the object existed on the source) the object will be copied to the target medium because the Slot End Time has not yet passed. Then at 08:19 (20 minutes after the object existed on the source) the object instance on the target will be deleted.
Example (Storage Slots):
Slot Begin Time (Minutes): 10
Slot End Time (Minutes): 20
Request Execution Begin Time (HH:MM): 08:00
Request Execution End Time (HH:MM): 14:00
Workflow:
A new object is placed onto the source medium while the slot is closed. A Copy Action is created and the status is set to COMPLETED. A DeleteInstance Action is created and the status is set to SCHEDULED. No actions are executed because the slot is closed.
The disk instance expires after 20 minutes.
The slot opens the next day. The DeleteInstance Action is executed, and the status is set to COMPLETED. The Copy Action status remains as COMPLETED.
This field identifies the priority of the request and order of execution when the action is submitted to the DIVArchive Manager.
Select the target medium to associate with the slot from the list.
The number of object instances that should exist on the target medium. If the actual number of instances is less than this setting, additional copies will be created. This parameter is only applicable to Storage Slots.
Example:
Req. Number of Instances: 2
Workflow:
One object instance already exists on the target medium.
Because there is only one instance existing, and this parameter is set to 2, another copy will be made to another disk in the array, or to another tape in the group.
Determines whether the slot can run multiple times. Setting this to N indicates it can run multiple times, while setting this to Y indicates it will only run once.
Note:
This parameter is only applicable for Storage Slots and must be set to Y when using Mixed Mode Watermarking.Example:
Once Only: N
Workflow:
An object was copied to the target medium, but somebody manually deleted the copied instance. This slot will realize the object does not exist on the target medium and run again, resulting in another copy on the target medium being created.
Example:
Once Only: Y
Workflow:
An object was copied to the target medium, but somebody manually deleted the copied instance. This slot will not run again, resulting in no object instance on the target medium (because it had been manually deleted).
If the Slot End Time for deletion has been set, when the Slot End Time is reached, SPM will automatically mark the object instance on the target medium as being deleted because it was manually deleted before the Slot End Time was reached.
Click OK to complete the process. The new slot will be displayed in the Slots tab of the Configuration Utility.
Starting with DIVAdirector 5.3, you can specify two new Quality of Service (QOS) parameters called NEARLINE_ONLY and NEARLINE_AND_DIRECT through the API or the Control GUI in Restore and Multiple Restore requests. The default QOS for a Restore or Multiple Restore request is NEARLINE_AND_DIRECT. The default QOS for all other requests remains DIRECT_AND_CACHE.
See Appendix A for Oracle DIVArchive options and licensing information.
When the Manager receives either of the new QOS values, it will initiate a DIRECT restore from any available disk instance, regardless of whether the disk instance is located on a disk with a DIVArchive Actor-Disk connection that is configured for Nearline. If no disk instance is found, the Manager will not terminate the request; instead it creates a disk instance and proceeds in the following sequence:
Check for NEARLINE disks during disk selection.
If no disks are available, then for QOS:
The workflow will terminate and an error is generated stating No AVAILABLE Actor-Disk connection is configured with Nearline storage.
DIRECT RESTORE will be used.
Reserve space for permanent storage during the restore.
Create a permanent disk instance in memory.
If the disk instance cannot be created, then for QOS:
The workflow will terminate.
DIRECT RESTORE will be used.
If the disk instance can be created, the workflow will proceed to the next step.
Write the disk instance to the database upon success or failure of the Restore.
Save component checksums for the new disk instance.
Update storage capacity.
Update last access date of object instance, if not already updated.
If all disk instances are busy, a delayed solution will be generated.
The Manager will terminate a Restore Instance request with a QOS of NEARLINE_ONLY, or a QOS of NEARLINE_AND_DIRECT, by sending an error message to the Control GUI stating Nearline and Nearline & Direct QOS are not supported for Restore Instance, and sending an Invalid Parameter error code to the API.
Nearline storage is defined using the same technique for defining the disk use. The Nearline type is defined by specifying one of two uses under Actor-Disk Connections called STORAGE_AND_NEARLINE and CACHE_AND_STORAGE_AND_NEARLINE. Any disk defined with one of these uses can be used for any of these operations.
An SPM Storage Slot supports this workflow for purging disk instances created during Restore requests.
If the disk instances are created on the same medium used in the Storage Slot, a Delete Instance action in the Storage Slot will be rescheduled.
If the disk instance is created on a different medium, you must set the Storage Slot's Slot Begin Time and Slot End Time to 0 for the associated medium.
SPM supports purging of disk instances created by the Manager during Restore requests in the following two work flows.
Nearline Instances are stored on the same medium, which is also used in an SPM Storage slot.
In this work flow it is assumed that the medium used for Nearline Storage must also be used in a SPM Storage Slot.
The Storage Slot must have Once Only set to N.
Nearline instances are not copied until the delete instance action is completed for the Storage Slot on the medium.
The medium used must be watermarked.
The disk cleaning strategy for the medium must be based on the Object Last Access Time.
After the action is put into the SCHEDULED state, SPM will start processing and put it into the POSTPONED state until the disk reaches its High Watermark.
After the disk reaches its High Watermark value, all of the Delete Instance Actions in the POSTPONED state will be executed based on the Disk Cleaning Strategy configured for the medium. In this case it will be the Object Last Access Time.
A separate medium is used for Nearline Storage.
In this workflow a Storage Slot is configured on the medium with the Slot Begin Time and Slot End Time is set to 0.
The Storage Slot must have Once Only set to N.
Setting the Slot Begin Time and Slot End Time to 0 causes SPM to generate a Storage Slot Action for this medium. However, it will be in the COMPLETED state by default.
The medium used must be watermarked.
The Disk Cleaning Strategy for the medium must be based on Object Last Access Time.
After the action is put into the SCHEDULED state, SPM will start processing and put it in the POSTPONED state until the disk reaches its High Watermark.
After the disk reaches its High Watermark value, all of the Delete Instance Actions in the POSTPONED state will be executed based on the Disk Cleaning Strategy configured for the medium. In this case it will be the Object Last Access Time.
A medium must not be configured for only one of previously mentioned workflows. Every medium that has a disk used for STORAGE_AND_NEARLINE or CACHE_AND_STORAGE_AND_NEARLINE must be configured with any one of the mentioned workflows for SPM to purge Nearline instances.
Transcode Archived Slots require configuration on the Slots Tab of the DIVArchive Configuration Utility and contain only a single action. This slot will take an existing clip in a DIVArchive Object, transcode it to another format, and archive the resulting clip as a new Object.
Because a Transcode Archived request creates a new object in the DIVArchive System, it requires directions as how to name the new object (Transformation Rules).
Note:
Each Oracle DIVArchive Actor defined as a Transcoder must also be defined as a LOCAL type Source/Destination. Linux based Actors only support Telestream Vantage transcoding operations. See Appendix A for Oracle DIVArchive options and licensing information.Use the following procedure to configure a Transcode Archived Slot:
Open the Configuration Utility and navigate to the Slots tab.
Click the + icon in the Slots section of the screen.
When the Slot Configuration window opens begin configuring the new slot by selecting TRANSCODE_ARCHIVED from the Slot Request Type list, and then continue with the remaining configuration parameters as follows:
Use the menu list to select the Storage Plan to be associated with this slot.
Select the type of request for this slot (Storage, Transcode Archived, Metadata Archive, or Restore). Select TRANSCODE_ARCHIVED in this case.
Enter a name for the slot in the Slot Name field.
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 object is archived.
Caution:
If the Slot Begin Time and Slot End Time are both set to zero, then the behavior is unknown, except for Storage Slots.Setting this parameter to -1 indicates the slot will never end (it is permanent) and the Transcode Archived Action will occur regardless of whether the slot is open or closed.
Example:
Slot Begin Time (Minutes): 10
Slot End Time (Minutes): -1
Workflow:
The original object is archived onto the source medium. Ten minutes later, the slot actions begin and it is transcoded onto the target medium.
Because the Slot End Time is set to -1, this slot will never end. If the slot is called during a period when the slot is closed, then as soon as the slot is open the transcode will take place. If this was set to another number (other than -1), the normal rules will apply as described later in the Request Execution End Time parameter.
Determines whether the slot is active. Selecting Y indicates the slot is enabled, and N indicates it is disabled. When a slot is disabled its actions are not executed, however they are still created, and the status is updated. When the slot is enabled again, pending actions are executed immediately.
This field is the slot execution window opening time in 24 hour time. If set to 00:00 the slot opens at the beginning of each day. If set to another time, for example 08:00, it will open at that time (in this case 8:00 am).
This field is the slot execution window closing time in 24 hour time. If set to 24:00 the slot closes after each day. If set to another time, for example 17:00, it will close at that time (in this case 5:00 pm).
Setting the Request Execution Begin Time and Request Execution End Time to something other than an entire 24 hour period will allow for scheduling of different functions through SPM at different times of the day (for example overnight jobs). If an object is archived to the source medium outside of the designated time frame for the slot, even though the object meets the Filter and Storage Plan criteria, no actions from this particular slot will occur.
If the original object was archived to the source medium while the slot was inactive (closed) and has passed the Slot End Time, when the slot finally becomes active (open), the action taken (or not taken) is determined by the Slot End Time setting.
Example:
Slot Begin Time (Minutes): 10
Slot End Time (Minutes): 20
Request Execution Begin Time (HH:MM): 08:00
Request Execution End Time (HH:MM): 14:00
Workflow:
A new object is placed onto the source medium at 07:00 (while the slot is closed). If the slot had been open at 07:00 when the new object was created it would be transcoded to the target at 07:10. Because the slot was not open when the new object was created, and the Slot End Time has passed, when this slot opens at 08:00, no action will be taken on the object.
If a new object is created on the source medium at 14:15 today, then tomorrow when this slot opens, no actions will be taken on the object because the Slot End Time has passed.
If an object is created on the source medium at 07:59 (before the slot opens), at 08:09 (10 minutes after the object existed on the source) the object will be transcoded to the target medium because the Slot End Time has not yet passed.
Example:
Slot Begin Time (Minutes): 10
Slot End Time (Minutes): -1
Request Execution Begin Time (HH:MM): 08:00
Request Execution End Time (HH:MM): 14:00
Workflow:
A new object is placed onto the source medium while the slot is closed. If the slot had been open at 07:00 when the new object was created, it would have been transcoded to the target at 07:10.
Since the slot was not open when the new object was created, and the Slot End Time is set to never end (-1), when this slot opens at 08:00, the Transcode Action will be completed on the object because the slot never ends.
If a new object is created on the source medium at 14:15 today, then tomorrow when this slot opens, the Transcode Action will be completed on the object because the slot never ends.
This field identifies the priority of the request and order of execution when the action is submitted to the DIVArchive Manager.
Select the target medium to associate with the slot from the list.
The number of object instances that should exist on the target medium. If the actual number of instances is less than this setting, additional copies will be created. This parameter is only applicable to Copy Actions in Storage Slots.
This parameter is only applicable for Storage Slots and must be set to Y when using Mixed Mode Watermarking.
Click OK to complete the process. The new slot is displayed in the Slots tab of the Configuration Utility.
There is a second set of tabs at the bottom of the Slot Configuration screen that contains the following tabs:
Restore, Transcode & Metadata Archive
Storage
The Transcode Archived Slot uses the Restore, Transcode & Metadata Archive tab to configure additional parameters including:
Quality Of Service
Request Options
Request Comments
Object Name Filter
Object Source Filter
Object Category Filter
Cascade Delete Links
Transformation Rules (for renaming)
The object filters allow restricting the Transcode process to particular objects. You can use them if you do not want to transcode all objects belonging to a Storage Plan.
The Transformation Rules are rules associated with the object filters to transform the object name and category for Transcode Archived and Metadata Archived.
Using the Restore, Transcode & Metadata Archive tab at the bottom of the Slot Configuration screen, configure the Object Filters and Transformation Rules as required:
Enter the Object Name filtering criteria you want to use for this filter. An asterisk is a wildcard character and the default entry in this field.
Enter the Object Source filtering criteria you want to use for this filter. An asterisk is a wildcard character and the default entry in this field.
Enter the Object Category filtering criteria you want to use for this filter. An asterisk is a wildcard character and the default entry in this field.
Enter the name for the transcoded clip on the target medium. The caret (^) character indicates the system should use the original name.
Enter the category for the transcoded clip on the target. The caret (^) character indicates the system should use the original name.
If the object matches the Object Filter criteria it will continue to be processed using the Transcode_Archived Slot. If the filter criteria are not matched then no further action is taken on the object for this slot.
Transformation Rules transform the object's name and category during the request, and the Transformation Name and Transformation Category need to be added. At least one of these two values should be changed from the default.
Using the caret (^) in the Target Name Template, or Target Category Template, or both, will cause SPM to use the original clip name, or the original clip category, or both. You can use the caret with additional naming conventions (for example, ^_wm9 or ^_cat).
Using only the caret with no additional characters causes the DIVArchive system to initiate an error stating that an object with that name, or category, or both, already exists. Changing just one of these parameters avoids this error and creates the new transcoded clip on the target.
Similar to the Transformation Rules, the Request Templates parameters are located at the bottom of the Slot Configuration screen in the Restore, Transcode & Metadata Archive tab. Configure the additional parameters as required:
This field is not accessible because the newly created object is always archived from the Actor that performed the transcoding.
Select the appropriate Quality Of Service from the list for this request. The Quality Of Service parameter has seven different levels:
Archiving is performed according to the default Quality Of Service (currently direct and cache for archive operations).
Use cache archive only.
Use direct archive only.
Cached transfers from, or to, a Source/Destination to, or from, DIVArchive are preferred, but direct transfers will occur if it is not possible to process the request in cache mode.
Direct transfers from, or to, a Source/Destination to, or from, DIVArchive are preferred, but cache transfers will occur if it is not possible to process the request in direct mode.
If a Nearline disk instance exists, the data is transferred from Nearline disk to the destination. Alternatively, the data is first transferred entirely to Nearline storage on disk from tape, and then transferred to the destination. If no Nearline service is available, the request will be terminated. See Appendix A for Oracle DIVArchive options and licensing information.
If Nearline transfer is not available (for example, no Actor with Nearline storage is available), a direct transfer is performed instead. See Appendix A for Oracle DIVArchive options and licensing information.
Enter the transcoding options in this field based on the transcoders defined in the Configuration Utility System tab. The available options are as follows:
-tr_namesThis option specifies the transcoder to use as defined in Configuration Utility Transcoders section.
-tr_archive_formatThis option specifies the factory and format to be transcoded to for Archive Slots.
-tr_restore_formatThis option specifies the factory and format to be transcoded to for Restore Slots.
Enter any comments in this field to be sent to the DIVArchive Manager with this action request.
This field is not accessible because the File Path Root for the archive of the transcoded object is generated internally by the Transcode Archived request.
This parameter determines whether to perform a Delete Action on just the original object, or on both the original and the transcoded object. If set to Y, when the original is deleted, the transcoded copy will also be deleted. When set to N, when the original is deleted, the copy remains untouched.
This parameter determines whether to perform a Restore Action on just the original object, or on both the original and the transcoded object. If set to Y, when the original is restored, the transcoded copy will also be restored. When set to N, when the original is restored, the copy remains untouched.
You configure the Metadata Archive Slots on the Slots tab of the DIVArchive Configuration Utility. These slots contain only a single action. This slot will archive a metadata file after an object is archived. The metadata file's file name must be the Object Name with no extension, and must reside on a location (Source/Destination and Path) that is defined in the Slot Configuration window. The Object Name and Object Category used for the metadata file archive are controlled by the Transformation Rule entries.
Use the following procedure to configure Metadata Archive Slots:
Open the Configuration Utility, and navigate to the Slots tab.
Click the + icon on the top right of the Slots section.
When the Slot Configuration dialog box opens, configure the options as follows:
Use the menu list to select the Storage Plan to be associated with this slot.
Select the type of request for this slot (Storage, Transcode Archived, Metadata Archive, or Restore). Select METADATA_ARCHIVE in this case.
Enter a name for the slot in the Slot Name field.
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 object is archived.
Caution:
If the Slot Begin Time and Slot End Time are both set to zero, then the behavior is unknown, except for Storage Slots.Setting this parameter to -1 indicates that the slot will never end (it is permanent), and the Metadata Archive Action will occur regardless of whether the slot is open or closed.
Example:
Slot Begin Time (Minutes): 10
Slot End Time (Minutes): -1
Workflow:
The original object is archived onto the source medium.
Ten minutes later, the slot actions begin and the metadata file is archived onto the target medium.
Because the Slot End Time is set to -1, this slot will never end. If the slot is called during a period when the slot is closed, as soon as the slot is open the archive will take place. If this was set to another number (other than -1), the normal rules will apply as described later in the Request Execution End Time description.
Determines whether the slot is active. Selecting Y indicates the slot is enabled, and N indicates it is disabled. When a slot is disabled its actions are not executed, however they are still created when a new object is archived.
This field is the slot execution window opening time in 24 hour time. If set to 00:00 the slot opens at the beginning of each day. If set to another time, for example 08:00, it will open at that time (in this case 8:00 am).
This field is the slot execution window closing time in 24 hour time. If set to 24:00 the slot closes after each day. If set to another time, for example 17:00, it will close at that time (in this case 5:00 pm).
Setting the Request Execution Begin Time and Request Execution End Time to something other than an entire 24 hour period will allow for scheduling of different functions through SPM at different times of the day (for example overnight jobs). If an object is archived to the source medium outside of the designated time frame for the slot, even though the object meets the Filter and Storage Plan criteria, actions taken on the object are determined but the setting of the Slot End Time parameter.
If the original object was archived to the source medium while the slot was inactive (closed) and has passed the Slot End Time, when the slot finally becomes active (open), the action taken (or not taken) is determined by the Slot End Time setting.
Example:
Slot Begin Time (Minutes): 10
Slot End Time (Minutes): 20
Request Execution Begin Time (HH:MM): 08:00
Request Execution End Time (HH:MM): 14:00
Workflow:
A new object is placed onto the source medium at 07:00 (while the slot is closed). If the slot had been open at 07:00 when the new object was created the metadata file would have been archived to the target at 07:10. Because the slot was not open when the new object was created, and the Slot End Time has passed, when this slot opens at 08:00, no actions will be taken on the object.
If a new object is created on the source medium at 14:15 today, then tomorrow when this slot opens, no actions will be taken on the object because the Slot End Time has passed.
If an object is created on the source medium at 07:59 (before the slot opens), at 08:09 (10 minutes after the object existed on the source) the object will be copied to the target medium because the Slot End Time has not yet passed. Then at 08:19 (20 minutes after the object existed on the source) the metadata file will be archived to the target medium because the Slot End Time has not yet passed.
Example:
Slot Begin Time (Minutes): 10
Slot End Time (Minutes): -1
Request Execution Begin Time (HH:MM): 08:00
Request Execution End Time (HH:MM): 14:00
Workflow:
A new object is placed onto the source medium at 07:00 (while the slot is closed). If the slot had been open at 07:00 when the new object was created, the metadata file would have been archived to the target at 07:10.
Because the slot was not open when the new object was created, and the Slot End Time is set to never end (-1), when this slot opens at 08:00, the Metadata Archive Action will be completed on the object because the slot never ends.
If a new object is created on the source medium at 14:15 today, then tomorrow when this slot opens, the Metadata Archive Action will be completed on the object because the slot never ends.
This field identifies the priority of the request and order of execution when the action is submitted to the DIVArchive Manager.
Select the target medium to associate with the slot from the list.
Similar to the Transformation Rules, the Request Templates parameters are located at the bottom of the Slot Configuration screen in the Restore, Transcode & Metadata Archive tab.
Object Filters allow restricting the Metadata Archive process to particular objects. You can use them if archiving metadata files for all objects belonging to a Storage Plan is not desired.
Transformation Rules are rules associated with the Object Filters to transform the name and category during the request.
If the object matches the Object Filter criteria it will continue to be processed using the Metadata_Archive request type. If the filter criteria are not matched then no further action is taken on the object for this slot.
Transformation Rules transform the object's name and category during the request, and the Transformation Name and Transformation Category must be added. At least one of these two values should be changed from the default.
Using the caret (^) in the Target Name Template, or Target Category Template, or both, will cause SPM to use the original clip name, or the original clip category, or both. You can use the caret with additional naming conventions (for example, ^_wm9 or ^_cat).
Using only the caret with no additional characters causes the DIVArchive system to initiate an error stating that an object with that name, or category, or both, already exists. Changing just one of these parameters avoids this error and creates the new transcoded clip on the target.
Configure the additional parameters as required:
This field is not accessible because the newly created object is always archived from the Actor that performed the transcoding.
Select the appropriate Quality Of Service from the list for this request. The Quality Of Service parameter has seven different levels:
Archiving is performed according to the default Quality Of Service (currently direct and cache for archive operations).
Use cache archive only.
Use direct archive only.
Cached transfers from, or to, a Source/Destination to, or from, DIVArchive are preferred, but direct transfers will occur if it is not possible to process the request in cache mode.
Direct transfers from, or to, a Source/Destination to, or from, DIVArchive are preferred, but cache transfers will occur if it is not possible to process the request in direct mode.
If a Nearline disk instance exists, the data is transferred from Nearline disk to the destination. Alternatively, the data is first transferred entirely to Nearline storage on disk from tape, and then transferred to the destination. If no Nearline service is available, the request will be terminated. See Appendix A for Oracle DIVArchive options and licensing information.
If Nearline transfer is not available (for example, no Actor with Nearline storage is available), a direct transfer is performed instead. See Appendix A for Oracle DIVArchive options and licensing information.
This is only used if a user name and password are required for the Source/Destination, otherwise leave this blank.
Enter any comments in this field to be sent to the DIVArchive Manager with this action request.
Enter the path to the metadata files on the Source/Destination.
Enter the Object Name filtering criteria you want to use for this filter. An asterisk is a wildcard character and the default entry in this field.
Enter the Object Source filtering criteria you want to use for this filter. An asterisk is a wildcard character and the default entry in this field.
Enter the Object Category filtering criteria you want to use for this filter. An asterisk is a wildcard character and the default entry in this field.
This parameter determines whether to perform a Delete Action on just the original object or on both the original and the Metadata Object. If set to Y, when the original is deleted, the Metadata Object will also be deleted. When set to N, when the original is deleted, the Metadata Object remains untouched.
This parameter determines whether to perform a Restore Action on just the original object, or on both the original and the metadata object. If set to Y, when the original is restored, the metadata object will also be restored. When set to N, when the original is restored the metadata object remains untouched.
For a Metadata Archive request, this parameter serves two purposes; it notifies SPM to look for an object with this parameter value on the Source/Destination, and it notifies SPM to create a Metadata Archive file on the target using this parameter value. The caret (^) character indicates the system should use the original name.
Enter the category for the transcoded clip on the target. The caret (^) character indicates the system should use the original category.
Click OK to complete the process. The new slot will be displayed in the Slots tab of the Configuration Utility.
You configure Restore Slots on the Slots tab of the DIVArchive Configuration Utility. Restore Slots only contain a single action. This slot will take an existing DIVArchive Object and restore it onto the designated Source/Destination.
Use the following procedure to configure Restore Slots:
Open the Configuration Utility, and navigate to the Slots tab.
Click the + icon on the top right of the Slots section.
When the Slot Configuration dialog box opens, configure the options as follows:
Use the menu list to select the Storage Plan to be associated with this slot.
Select the type of request for this slot (Storage, Transcode Archived, Metadata Archive, or Restore). Select RESTORE in this case.
Enter a name for the slot in the Slot Name field.
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 object is archived.
Caution:
If the Slot Begin Time and Slot End Time are both set to zero, then the behavior is unknown, except for Storage Slots.Setting this parameter to -1 indicates that the slot will never end (it is permanent), and the Restore Action will occur regardless of whether the slot is open or closed.
Example:
Slot Begin Time (Minutes): 10
Slot End Time (Minutes): -1
Workflow:
The object is found on the mediums monitored by SPM.
Ten minutes later, the slot actions begin and the object is restored to the target Source/Destination.
If the Slot End Time was greater than zero, and if the Restore Action has not executed before the Slot End Time is reached (because the slot remained closed after the Slot End Time was reached) then the Restore Action will never be executed. If this was set to another number (other than -1), the normal rules will apply as described later in the Request Execution End Time description.
Determines whether the slot is active. Selecting Y indicates the slot is enabled, and N indicates it is disabled. When a slot is disabled its actions are not executed, however they are still created when a new object is archived.
This field is the slot execution window opening time in 24 hour time. If set to 00:00 the slot opens at the beginning of each day. If set to another time, for example 08:00, it will open at that time (in this case 8:00 am).
This field is the slot execution window closing time in 24 hour time. If set to 24:00 the slot closes after each day. If set to another time, for example 17:00, it will close at that time (in this case 5:00 pm).
Setting the Request Execution Begin Time and Request Execution End Time to something other than an entire 24 hour period will allow for scheduling of different functions through SPM at different times of the day (for example overnight jobs). If an object is archived to the source medium outside of the designated time frame for the slot, even though the object meets the Filter and Storage Plan criteria, actions taken on the object are determined but the setting of the Slot End Time parameter.
If the original object was archived to the medium while the slot was inactive (closed) and has passed the Slot End Time, when the slot finally becomes active (open), the action taken (or not taken) is determined by the Slot End Time setting.
Example:
Slot Begin Time (Minutes): 10
Slot End Time (Minutes): 20
Request Execution Begin Time (HH:MM): 08:00
Request Execution End Time (HH:MM): 14:00
Workflow:
A new object is placed onto the source medium at 07:00 (while the slot is closed). Because the slot was not open when the new object was created, and the Slot End Time has passed, (20 minutes after the object was placed on the medium, that is 7:20) when this slot opens at 08:00, no actions will be taken on the object.
Note:
If the slot had been opened at 07:00, then when the new object was created it would have been restored to the target at 07:10.If a new object is created on the source medium at 14:15 today, then tomorrow when this slot opens, no actions will be taken on the object because the Slot End Time has passed.
If an object is created on the source medium at 07:59 (before the slot opens), at 08:09 (10 minutes after the object existed on the source) the object will be restored to the Source/Destination because the Slot End Time has not yet passed.
Example:
Slot Begin Time (Minutes): 10
Slot End Time (Minutes): -1
Request Execution Begin Time (HH:MM): 08:00
Request Execution End Time (HH:MM): 14:00
Workflow:
A new object is placed onto the source medium at 07:00 (while the slot is closed). Because the slot is not open when the new object was created, and the Slot End Time is set to never end (-1), when this slot opens at 08:00, the Restore Action will be completed on the object because the slot never ends.
Note:
If the slot had been open at 07:00 when the new object was created, it would have been restored to the Source/Destination at 07:10.If a new object is created on the source medium at 14:15 today, then tomorrow when this slot opens, the Restore Action will be completed on the object because the slot never ends.
This field identifies the priority of the request and order of execution when the action is submitted to the DIVArchive Manager.
Similar to the Transformation Rules, the Request Templates parameters are located at the bottom of the Slot Configuration screen in the Restore, Transcode & Metadata Archive tab.
Object Filters allow restricting the Metadata Archive process to particular objects. You can use them if archiving metadata files for all objects belonging to a Storage Plan is not desired.
Transformation Rules are rules associated with the Object Filters to transform the name and category during the request.
If the object matches the Object Filter criteria it will continue to be processed using the Metadata_Archive request type. If the filter criteria are not matched then no further action is taken on the object for this slot.
Transformation Rules transform the object's name and category during the request, and the Transformation Name and Transformation Category must be added. At least one of these two values should be changed from the default.
Using the caret (^) in the Target Name Template, or Target Category Template, or both, will cause SPM to use the original clip name, or the original clip category, or both. You can use the caret with additional naming conventions (for example, ^_wm9 or ^_cat).
Using only the caret with no additional characters causes the DIVArchive system to initiate an error stating that an object with that name, or category, or both, already exists. Changing just one of these parameters avoids this error and creates the new transcoded clip on the target.
Configure the additional parameters as required:
This field is not accessible because the newly created object is always archived from the Actor that performed the transcoding.
Select the appropriate Quality Of Service from the list for this request. The Quality Of Service parameter has seven different levels:
Archiving is performed according to the default Quality Of Service (currently direct and cache for archive operations).
Use cache archive only.
Use direct archive only.
Cached transfers from, or to, a Source/Destination to, or from, DIVArchive are preferred, but direct transfers will occur if it is not possible to process the request in cache mode.
Direct transfers from, or to, a Source/Destination to, or from, DIVArchive are preferred, but cache transfers will occur if it is not possible to process the request in direct mode.
If a Nearline disk instance exists, the data is transferred from Nearline disk to the destination. Alternatively, the data is first transferred entirely to Nearline storage on disk from tape, and then transferred to the destination. If no Nearline service is available, the request will be terminated. See Appendix A for Oracle DIVArchive options and licensing information.
If Nearline transfer is not available (for example, no Actor with Nearline storage is available), a direct transfer is performed instead. See Appendix A for Oracle DIVArchive options and licensing information.
This is only used if a user name and password are required for the Source/Destination, otherwise leave this blank.
Enter any comments in this field to be sent to the DIVArchive Manager with this action request.
Enter the path to the metadata files on the Source/Destination.
Enter the Object Name filtering criteria you want to use for this filter. An asterisk is a wildcard character and the default entry in this field.
Enter the Object Source filtering criteria you want to use for this filter. An asterisk is a wildcard character and the default entry in this field.
Enter the Object Category filtering criteria you want to use for this filter. An asterisk is a wildcard character and the default entry in this field.
This parameter determines whether to perform a Delete Action on just the original object or on both the original and the Metadata Object. If set to Y, when the original is deleted, the Metadata Object will also be deleted. When set to N, when the original is deleted, the Metadata Object remains untouched.
This parameter determines whether to perform a Restore Action on just the original object, or on both the original and the metadata object. If set to Y, when the original is restored, the metadata object will also be restored. When set to N, when the original is restored the metadata object remains untouched.
For a Metadata Archive request, this parameter serves two purposes; it notifies SPM to look for an object with this parameter value on the Source/Destination, and it notifies SPM to create a Metadata Archive file on the target using this parameter value. The caret (^) character indicates the system should use the original name.
Enter the category for the transcoded clip on the target. The caret (^) character indicates the system should use the original category.
Click OK to complete the process. The new slot will be displayed in the Slots tab of the Configuration Utility.
Caution:
This feature must be managed carefully because you can lose objects.The DELETE_OBJECT_ONLY_LAST_INSTANCE parameter is a configuration parameter that works with the existing ALLOW_OBJECT_DELETION parameter.
ALLOW_OBJECT_DELETION ParameterThis parameter must be enabled for SPM to delete objects. You must enable or disable Delete Object for each Storage Plan separately when configuring them in the Configuration Utility. This configuration method provides additional security and flexibility. Delete Object is enabled only when it is enabled in both the configuration file and also the Storage Plan configuration.
Note:
If this parameter is disabled, allowing it for a Storage Plan will have no effect.Delete Object is executed only when the following conditions are satisfied:
The ALLOW_OBJECT_DELETION parameter must be enabled.
Delete Object must be enabled for the Storage Plan level through the Configuration Utility.
All of the Storage Slots in the Storage Plan associated with the object must have a Slot End Time.
Delete Object will be executed by the Storage Slot that has the highest end time in the Storage Plan.
An object can be associated with only one Storage Plan.
If multiple Storage Slots have a maximum end time in a Storage Plan, the slot with the maximum Slot ID among the slots with maximum end time will perform the delete object.
Just enabling ALLOW_OBJECT_DELETION will not acknowledge a Storage Slot medium Watermark, and the Delete Object is executed at the end of the Storage Slot that has the highest end time in the Storage Plan.
The valid values for this parameter are true or false, and the default is false.
DELETE_OBJECT_ONLY_LAST_INSTANCE ParameterThis parameter adds additional checks and conditions to the SPM Delete Object feature.
Enabling this parameter forces SPM to delete an object at the end of a Storage Slot only if it is the last instance in the entire DIVArchive system, and that last instance exists on the Storage Slot medium with the highest Slot End Time among all Storage Slots of the Storage Plan. Otherwise, SPM will never execute a Delete Object at the end of the Storage Slot, it will always only execute a Delete Instance at the end of a Storage Slot. The following conditions must be satisfied for this to execute correctly:
This parameter requires ALLOW_OBJECT_DELETION to be enabled. Only enabling DELETE_OBJECT_ONLY_LAST_INSTANCE has no effect, and the SPM Delete Object feature will not be enabled.
The parameter DELETE_OBJECT_ONLY_LAST_INSTANCE must be enabled.
You must have Delete Object enabled for the Storage Plan level through the Configuration Utility.
All of the Storage Slots in the Storage Plan associated with the object must have a Slot End Time.
Delete Object will be executed by the Storage Slot that has the highest Slot End Time in the Storage Plan.
An object can be associated with only one Storage Plan.
If multiple Storage Slots have a maximum end time in a Storage Plan, the slot with maximum slot ID among the slots with maximum end time will perform the Delete Object function.
At the end of the Storage Slot, if more than two instances exist in the DIVArchive system or on the medium, only Delete Instance is executed.
Delete Object is executed only if one instance exists on the entire DIVArchive system, and that one instance exists on the medium of the Storage Slot that has the highest Slot End Time among all Storage Slots of the storage plan.
If the medium of the Storage Slot that has the highest Slot End Time is Watermarked, the Delete Object is postponed until the Watermark condition is satisfied.
Storage Plans contain Slots that you can altered if required. You can add slots, and edit, delete, and enable or disable existing slots. These adjustments to Storage Plans must be performed carefully to ensure the results that are desired. Below is an example of adding a slot to a Storage Plan, and changing an existing slot within the same Storage Plan.
Example:
DISK1 = Local DIVArchive Managed Disk
Storage Slot
Slot Start Time = 0
Slot End Time = -1
NEARLINE = Local Tape Group
Storage Slot
Slot Start Time = 0
Slot End Time = -1
OFFLINE = Local Tape Group
Storage Slot
Slot Start Time = 0
Slot End Time = -1
DISK2 = New DIVArchive Managed Disk
This is not an initial slot.
This Storage Slot is added in Step 4 of the following workflow with a Slot Start Time = 0, and Slot End Time = -1.
The company has Storage Plan A, which includes three total instances; one instance on disk and two instances on tape. The following is the workflow for Storage Plan A:
Object1234 is archived to DISK1 under Storage Plan A.
Storage Plan A has slots for the following operations, and Object1234 is copied to both tape groups:
Copy to NEARLINE
Copy to OFFLINE
At some point in the future, the company changes its internal policy for content with Storage Plan A to three total instances; two instances on disks (DISK1 and DISK2), and one instance on the NEARLINE tape group.
The new slot change is added that will copy Object1234 to DISK2 but it is necessary to also delete the object instance from the NEARLINE tape group.
To delete the object instance from the NEARLINE tape group, you must change the Slot End Time to 0 for the NEARLINE Storage Slot (see Disabling and Deleting Slots for more information).
You must add a new Storage Slot on DISK2 with a Slot Start Time = 0 and Slot End Time = -1 (see Adding a Slot for more information).
Storage Plan A is now updated with the Nearline Slot configuration to delete the instance from the NEARLINE tape group. The Slot Begin Time and Slot End Time are both set equal to 0.
Oracle generally recommends that slots are not deleted, but rather disabled instead. Deleting a slot does not remove the content from the DIVArchive system.
For a Storage Slot, setting the Slot End Time to 0 forces SPM to delete any contents created by this slot. You can delete, or disable, the Storage Slot after all the contents are removed. If you want to retain the content in a Storage Slot, but no further processing of future actions is required, you should disable the slot instead of deleting it.
You can add a slot to an existing Storage Plan. However, you must use caution to achieve the desired results.
When adding a slot to an existing Storage Plan, you must ensure that the Slot Start Time and Slot End Time are both valid (see Configuring Storage Slots for valid parameters). New slots are always immediately applicable to new objects, but for existing objects you must ensure that the Slot Start Time and Slot End Time are correct. Otherwise, the action specified in the new slot will not be executed on existing objects.
Example:
A Storage Plan with numerous objects that have been archived 48 hours before the current time. If a new Storage Slot is added, and is configured with a Slot Start Time = 0 and a Slot End Time = 24, the new slot's action will be added but not applied to existing objects because the slot has already expired for all of the existing objects:
((Archive Object Time + Slot End Time (24 hours)) < Current Time)
For existing objects to be affected by the new Storage Slot, they must be immediately copied to the Storage Slot medium, but never deleted. To perform this function, you set the Slot Start Time to 0, and the Slot End Time to -1 (infinite). As a result, all instances will be copied to the Storage Slot medium:
((Archive Object Time + Slot End Time (infinite)) > Current Time)
For non-Storage Slots (for example, Restore Slots), you must configure the Slot Start Time = 0 and the Slot End Time = 100. In this case, SPM will try restoring objects that have existed for less than the Slot End Time (100 hours); that is, the objects whose Slot End Time has not expired:
((Archive Object Time + Slot End Time (100 hours)) > Current Time)
If SPM is not able to complete the restore of the object within 100 hours from the Archive Time, that object is never restored. If the Slot End Time = -1, SPM will try to restore all of the objects.
Disk Array cleaning can be managed by a fixed slot duration, where disk instances or objects are deleted when they expire, or using a Watermark based housekeeping mechanism, where disk instances or objects are only deleted when space must be recovered. This section discusses the details of the second option.
Based on configuration, SPM may attempt to delete instances, or objects. When a Storage Slot's retention for an object is expired, and the object has no more open Storage Slots at the time, SPM will attempt to delete the object if the configuration authorizes it. Otherwise, SPM will only attempt to delete the instance located on the medium referenced in the slot.
You can explicitly specify the order in which array instances, or objects, or both, of content are removed during the DIVArchive Array Housekeeping activities. SPM includes an array monitoring component to manage array space usage called Watermarking.
Array housekeeping is based on a Watermark system monitored by the Disk Space Monitor component. When the array's Storage Slot retention period for an object expires, the instance, or object, or both, becomes eligible for deletion, but stays on the array until there not enough space available.
Note:
Watermarking is only valid for Storage Slots.DIVArchive initiates housekeeping activities and expired instances, or objects, or both are deleted according to the defined policies when this threshold is reached. If no instances or objects are eligible for deletion (for example, the retention period has not expired, or a dependency is not met), used array space can exceed the watermark. It is your responsibility to ensure that the array filling rate matches the system configuration, and to monitor how array use evolves.
DIVArchive stops deleting instances and objects at the Low Watermark. Supported policies and rules for housekeeping include deleting array instances based on Last Access Time or Largest Object Size.
When an array is watermarked in Mixed Mode, both instances and objects marked for deletion, and objects whose slots are still open, are considered. Instances and objects in that array are deleted based on whichever of the following comes first:
Note:
You must set Once Only to Y (Yes) in the associated slot's configuration for proper functionality.Array reached the High Watermark. Even if the object's slot has not ended, instances and objects will be deleted to bring the array to the Low Watermark level.
Storage Slot for that object has ended. Even though the High Watermark is not reached, because the slot ended, the instance, or object, or both will be deleted.
This does not mean the array will be cleaned to the level of Low Watermark.
For SPM to delete an object belonging to a Storage Plan, the ALLOW_OBJECT_DELETION parameter must be set to Y in both the SPM Configuration File and the Configuration Utility.
External Storage Plan functionality allows management of the DIVArchive Object Lifecycle using third party external systems. You can use the SPM Database API to develop integration of third party components with DIVArchive and SPM.
Note:
In this release of SPM, E (External) should only be used by Oracle personnel.You can validate the accuracy of the SPM configuration using the DIVArchive Configuration Utility. Use the following procedure to validate the SPM configuration:
Open the DIVArchive Configuration Utility.
Select any of the tabs across the top of the screen.
From the menu bar, select Tools, and then Validate SPM configuration. Alternatively you can hold Alt+t, and then press the F3 function key.
The DIVArchive Configuration Utility will verify the configuration of SPM and return a dialog box with one of two results:
The DIVArchive Configuration Utility verified the SPM configuration successfully and the dialog box indicates no errors were found.
The DIVArchive Configuration Utility verified the SPM configuration, found errors, and dialog box displays the errors that were discovered.
For example:
ERROR: Slot Test must not be of type STORAGE, Please mention correct request type in Object Filters Configuration.