3.2
Table Of Contents
- Title Page
- Contents
- Using This Guide
- Getting Started with the Interplay | Administrator
- Database Settings
- Creating an Interplay Database
- Interplay Databases, Folders, and Files
- Creating and Restoring Database Backups
- Types of Interplay Administrator Backups
- Recommendations for Backup Configuration
- Setting the Number of Database Backups to Keep
- Scheduling Automatic Database Backups
- Starting a Backup Manually
- Using an Archiving Tool for Backup
- Restoring an Earlier Version of a Database
- Performing a Partial Restore of an Interplay Production Database
- Creating a Metadata-Only Backup for Customer Support
- Performing a Consistency Check
- Viewing Database Information
- Locking and Unlocking Databases
- Managing Databases: Deactivating, Activating, and Migrating
- Moving a Database to Another Server (Non-Clustered Systems)
- Moving a Database and Users to Another Server (Non-Clustered Systems)
- Moving a Database to Another Server (Clustered Systems)
- Moving a Database and Users to Another Server (Clustered Systems)
- Moving a Database Under Low Disk Space Conditions
- Renaming a Database
- Running Database Maintenance Tools
- Identifying the Root Folder of the Interplay Server Database
- Server Settings
- User Management
- Understanding the Central Configuration Server
- Adding Users to a Central Configuration Server
- Setting User Authentication Providers and Importing Users
- Managing Users, User Groups, and User Rights
- Understanding Default User Groups, Users, and Roles
- Adding User Groups
- Adding Users Manually
- Viewing and Setting Attributes
- Understanding Standard Roles and Default Rights
- Viewing and Changing Roles
- Viewing and Setting Authentication Providers for Individual Users
- Deleting Users and User Groups
- Removing Users from User Groups
- Managing Database Roles
- Guidelines for User Management
- Site Settings
- Defining Property Layouts
- Setting the Resolutions Available for Display
- Creating Custom Properties
- Configuring Remote Workgroups
- Configuring Categories
- Setting Server Hostnames and the Workgroup Name
- Interplay Media Services View
- Interplay Transfer Status View
- Interplay Transfer Settings View
- Workgroup Transfer Presets View
- Specifying Remote Servers for Asset Tracking
- Specifying Archive Settings
- Setting the Ownership for New Database Folders
- Enabling Interplay Synced Projects
- Setting Options for Deletion
- Viewing and Setting the Metadata Override Status
- Production Engine Bus Connector
- Application Settings
- Application Database Settings View
- Setting Options in the Editing Settings Tab
- Setting Audio Mixing Defaults for Access, Assist, and MediaCentral | UX
- Sending a Source to Playback in Interplay Assist
- Setting the Shotlist Start Timecode for Interplay Access and Interplay Assist
- Setting an Automatic Timeout for Interplay Assist and Avid Instinct
- Configuring the Frame Locators Display
- Configuring the Restrictions Display
- Media Composer | Cloud Settings
- Setting Instinct/Assist User Options
- Pro Tools Plug-Ins Settings
- Application Database Settings View
- Interplay Services
- Troubleshooting
- Reuniting a Split Database
- Installed Components and Services
- Interplay Engine Configuration Files
- Valid and Invalid Characters in Interplay
- System Metadata Properties
- Server Error Codes
- Consistency Check Codes
- Index
Setting Options for Deletion
185
Starting in Interplay v2.4, the Orphan Clips folder includes the following subfolders:
• Kept Media folder: You can select an option to include deletion of online media in the
scheduled deletion (“Permanently delete assets and associated online media from the
Orphan Clips folder”). If you do not select this option, the scheduled deletion moves any
links with online media to a subfolder in the Orphan Clips folder named “Kept Media.” This
option to delete is not selected by default, so even if you do not enable custom deletion, the
Interplay Engine creates a Kept Media folder when needed. You can manually delete clips
and media from this folder at a time that is appropriate for your workflow.
• Failed to Delete folder: If the deletion process is not able to delete a clip or its media (for
example, if a clip is corrupted), the Interplay Engine creates a subfolder in the Orphan Clips
folder named “Failed to Delete” and moves assets it could not delete to this folder. You can
try to manually delete clips and media from this folder as well, but you might need to
determine a different method of deleting these clips and media. For example, check the
shared-storage system workspace to make sure the Server Execution User has delete rights.
These folders are useful in two ways:
• It is easier to browse and search a large Orphan Clips folder for assets with online media and
assets that cannot be deleted.
• The scheduled deletion process ignores both of these folders, resulting in improved
performance.
You can manually delete assets from the Orphan Clips folder at any time.
How Asynchronous Deletion Works with the Orphan Clips Folder
During the scheduled time spans, the Interplay Engine reviews the objects in the Orphan Clips
folder and deletes the links, the database assets, and the media (if the option “Permanently delete
assets and associated online media from the Orphan Clips folder” is selected). At the end of a
time span, the Interplay Engine keeps a record of where it stopped. If not all eligible assets were
deleted, it continues from this position at the start of the next time span. This process also takes
place if the scheduled deletion is interrupted, such as for system maintenance.
Logs for Deleted Media and Metadata
Deletions are logged in two files:
• AvDeletes.log. This log lists information about media deleted from shared storage.
• AvMetaDataDelete.log This log lists information about assets (metadata) deleted from
Orphan Clips or any other folder. Scheduled deletions are noted.