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
Moving a Database to Another Server (Non-Clustered Systems)
70
c
If you move a database to a server that points to a different CCS, all the old CCS
information that was stored, including users, user settings, and local administration
settings for the database, will be lost because you will have to migrate the database (see
“Migrating a Database” on page 67). If you move a database to another server and also
move the CCS, however, this information is preserved. To move both a database and a
CCS, see “Moving a Database and Users to Another Server (Non-Clustered Systems)” on
page 71.
To move a database to another server (non-clustered systems):
1. Install the Interplay Engine on a new server (the target server).
Make sure the configuration is the same on both systems. For example, if you are moving an
AvidWG database, create an AvidWG database on the new server.
2. On the source server, lock the database by using the Lock/Unlock Database view (see
“Locking and Unlocking Databases” on page 62).
All clients are disconnected from the source server.
3. Deactivate the database by using the Manage Databases view (see
“Deactivating a Database”
on page 64
).
4. Make sure the database is unloaded from the server by opening the Restart Server view and
clicking Restart.
5. Locate the database folder on the source server.
The default path is \\server_name\WG_Database$\AvidWG (or AvidAM for an Archive
Manager). By default, the administrative share WG_Database$ refers to
D:\Workgroup_Databases.
6. Pack the database folder into a zip file or use Robocopy from the Microsoft Windows
Resource Kit for path names longer than 256 characters.
To save time and storage, you do not need to copy all the backups in the
D:\Workgroup_Databases\AvidWG\_Backup folder. One complete backup and the most
recent Fast backup are sufficient.
If you are moving a split database, create two zip files, one for
D:\Workgroup_Databases\AvidWG and the other for
\\server_name\\workspace_name\\AvidWG.
n
Split databases are no longer recommended. See “Reuniting a Split Database” on page 234.
7. Copy the zipped file or files to a network server, removable media, laptop, or directly to the
target server.
8. Open the Interplay Administrator, log on to the target server, and deactivate the database
(AvidWG or AvidAM) if one is active, using the Manage Databases View.