3.2

Table Of Contents
Moving a Database to Another Server (Clustered Systems)
74
All clients are disconnected from the source server.
3. Deactivate the database using the Manage Databases view (see “Deactivating a Database” on
page 64
).
4. Make sure the database is unloaded by using the Cluster Administrator on one of the cluster
nodes:
a. Select Programs > Administrative Tools > Cluster Administrator.
b. Open the Avid Workgroup Server resource group.
c. In the list of resources, select Avid Workgroup Engine Monitor and change the state to
“Offline.
c
Make sure that you change the state to offline for the Avid Workgroup Engine Monitor
resource only, not the entire Avid Workgroup Server group.
d. Close the Cluster Administrator.
5. Locate the database folder on the active node of the source server.
The default path is \\virtual_cluster_name\WG_Database$\AvidWG (or AvidAM for an
Archive Manager). By default, the administrative share WG_Database$ refers to
S:\Workgroup_Databases. For more information, see
“Identifying the Root Folder of the
Interplay Server Database” on page 85
.
n
If the S drive is not available on the machine, either this is the offline node or the entire Avid
Workgroup Server group was taken offline instead of only the resource.
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
S:\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
S:\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, a 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) using the Manage Databases View.
9. On the target server, rename the existing database folder, for example, rename AvidWG to
AvidWG_old.