You must monitor DIVAdirector daily to insure proper operation, storage capacities, orphaned files, user interaction, successful backups, and general system health. If you discover any anomalies that you are uncertain of or if you are unsure of how to handle them, contact Oracle Support for assistance.
This chapter describes your daily operations routine and includes the following information:
In your initial DIVAdirector configuration you identified system storage locations and the limits for each location. Storage locations will fill up over time during normal use. You must check the remaining available space for each location daily. If a storage location is reaching its limit, you must either migrate some (or all) of the data to another location (for proxy data see Proxy Migration) or configure a new location (see Source/Destination Configuration).
Use the following procedure to check your storage locations and remaining available space:
Navigate to the Storage Location Configuration section under Admin, System, Storage Locations.
Check each location's State to identify the current storage location status.
If the location's state is something other than operational (and you didn't set it that way), you must identify why it is in the current state, and if necessary, resolve the issue. You use the server logs and Drop Folder logs to help identify issues. If you are unable to resolve the issue and need further assistance contact Oracle Support.
Check the Used and Available columns to identify how much of the storage space is filled and how much is left available (respectively) for each location. You will need to decide if additional space is required, if data must be migrated to another location, or if the location is fine the way it is.
If you must add a new storage location refer to Source/Destination Configuration.
If you must adjust the storage space limits refer to Configuring the Proxy Storage Location.
If you must migrate data to another storage location see Proxy Migration for information.
Next you will check for orphaned files.
Throughout daily user interaction with DIVAdirector, you will occasionally get some orphaned files. Orphaned files are files that were placed in a Drop Folder and had the wrong format, had different encapsulation than configured for the folder, or they do not exist in the database. The system identifies the files as unrecognized and moves them to a special Orphan folder. You identified the Orphan folder during your initial configuration (see Drop Folder Configuration).
Use the following procedure to locate and act on orphaned files:
Open Windows File Explorer.
Navigate to the Orphan folder you configured for your first Drop Folder.
Identify the contents of each file inside the folder.
When you identify what the file is, decide whether to:
Repair whatever caused the file to be placed in the orphan folder, and then re-drop it into the Drop Folder for re-processing.
Move the file to another storage location.
Delete the file.
Determine the action you take on each file according to your internal organizational policy and the importance of the file.
Next you will check the user interaction with audit trails.
Audit trails are checked to review system and user activity formed on specific objects. This is useful for general system overview, and to determine if errors occurred while a user was trying to perform an action on a specific object.
The Audit Trail screen displays user interactions with the DIVAdirector system. You can filter the display by Action, User, Time (From and To), Object Name, and Object Category using the options on the right side of the screen. The Object Name and Object Category fields in the filter can contain partial words.
For example, use the following procedure if you are searching specifically for actions performed by a user in the Marketing Department on an object named MySportsVideos and having the object category MOV:
Enter Mark in the Organization field, and select the Organization check box.
Enter My in the Object Name field, and select the Object Name check box.
Enter MO in the Object Category field, and select the Object Category check box.
Click Apply Filter on the bottom right side of the screen to locate the object.
This procedure will locate the object if it exists in the audit trail.
Clicking Export on the top right side of the screen will export the filtered (or unfiltered) audit trail to a file that you can use for tracking general system use or errors.
System backups are necessary and extremely important for disaster recovery. You must confirm that the backups you created during initial configuration are completing successfully and to the proper storage location. You cannot restore a corrupt backup file so you must check them daily.
Use the following procedure to check the backup files:
Open Windows Explorer.
Navigate to the storage location you designated in the initial system configuration.
See Automated Backup Configuration if you need a reminder of where you set the backup storage location.
Check the creation date and time of the latest file in the folder. Confirm that the date and time match the backup schedule.
Check the system log files for errors related to the backup job. See Checking Log Files for the procedure to use.
If a corrupt or unsuccessful backup is discovered, use the procedure described in Performing a Manual Backup to attempt a manual system backup before attempting to troubleshoot any issues.
In the next chapter you will find system maintenance tasks that you must use occasionally.