Regular File Maintenance

This document covers the normal file maintenance that should addressed from within DAD and within the network as a whole.  As always, please use caution when deleting files. Verify that the file you wish to remove is not needed elsewhere.

The following are items that should be done on a regular schedule. This schedule might be monthly or perhaps every five to six weeks or perhaps even every week. The frequency is dependent upon the amount of cuts being added and deleted from the Library.

Getting a Unique Rebuild [aka UR]:

A Unique Rebuild [also called a UR for short] is a time that all ENCO software applications are not connected the Library Database [..\DAD\Files\CUTS.DBF]. This means that DAD, Gateway and other applications such as CutServer or DropBox would not be running.

A Unique Rebuild will happen when only ONE machine starts DAD. When DAD starts it will run the Rebuild application. Rebuild will check, organize and clean up the Library database.

When one runs Rebuild, a screen will display information about the process taking place. This screen lists what files are being backed up and rebuilt. The screen can be 'held' by pressing the HOLD button to view the information in the screen. 

When Rebuild is able to get exclusive access to the database one will see the line:

Opened [path]\DAD\FILES\CUTS.dbf database for rebuild!
Uniquely rebuilding a cuts database..
[path]\DAD\FILES\CUTS.dbf database has been rebuilt

If Rebuild can NOT get access to the database one would see the line:

Could not get exclusive access to [path]\DAD\FILES\CUTS.dbf
Could NOT open [path]\DAD\FILES\CUTS.dbf database for rebuild!

 

CAUTION: Only one machine can get access and perform Rebuild at a time. If two different DAD programs are started at the same time, they both could get access and cause problems.

 

Additional information about Rebuild:

Rebuild does the following:

Process Action Other Details
FIX Mode When run, Rebuild will compare the audio file header information with what is in the database and make corrections as necessary.  Rebuild runs in this mode - the first time it can get exclusive access. It then creates <datadir>\DAD\progs\has_run as a semaphore.

If one deletes the has_run file - then the next unique rebuild will run in FIX mode. One can also specify the "FIX" parameter on the rebuild command line
Backups of Library databases Makes a copy of CUTS.dbf (and other Library databases) in the \Files\Backup folder.  This copy is done only once each day when Rebuild is run. The backup file name is: LIB_<LibDrive>_<LibName>_<DayofWeek>
Backup of Groups database Makes a copy of GROUPS.dbf in the \Files\Backup folder.   
Rebuild of Library databases Opens the Library database and performs normal maintenance routines.   
Re-indexing of Library database Re-indexes the database and creates the <LibraryName>.CDX file.   
Backup of Cut Security database Makes a copy of CUTSEC.dbf in the \Files\Backup folder.   
Re-indexing of Cut Security database Re-indexes the database and creates the CutSec.CDX file.   
Backup of Playlist database Makes a copy of PLIST.dbf in the \Files\Backup folder.   
Backup of Search database Makes a copy of SEARCH.dbf in the \Files\Backup folder.  See notes below for more information about the Quick Search database. 
Re-indexing of Groups database Re-indexes the database and creates the Groups.CDX file.   
Re-indexing Playlist database Re-indexes the database and creates the Plist.CDX file.   
Re-indexing MLIB database Re-indexes the database and creates the MLib.CDX file.   
Re-indexing MLIBWS database Re-indexes the database and creates the MLibWS.CDX file.   

 

 

Quick Search:

The Quick Search database is a database of all the cuts in the Library containing only the fields specified in the [path]\DAD\Files\SCONTROL.DAT file. 

Any time a cut is recorded, added or one of the fields being 'watched' is modified, the Quick Search is updated. Because of this, this file can grow in size over time. Administrators should regenerate the Quick Search database at the same time they are performing their Unique Rebuild.  One MUST have exclusive access to the SEARCH.dbf file in order to regenerate the database. 

NOTE: In current versions of DAD (from DAD v5.1d+) the Quick Search database is regenerated when you do a Unique Rebuild and get Unique Access to the Library database.

To regenerate the Quick Search: 

Once the first and only DAD application is up and running after a Unique Rebuild, one should go to SETUP and press the GEN QUICK SEARCH button [shown highlighted at right]. 

This will display a message stating that it could take a few moments. Press OK and allow the process to continue. Once finished, other DAD applications can be started. 
 
   

 

 

 

Defragging Drives and other workstation / server related items:

There are several items that administrators should check on a regular basis. This section lists these items. 

Defragging Drives:

In general administrators who are using Windows based servers should be defragging the DATA and AUDIO drives. Fragmented files can cause poor performance of database queries and audio playback. 

NOTE: Administrators should exercise some caution when considering defragging server drives. There are many variables that can come into play. The size of the drive, amount of fragmented files, overall system usage when defragging, overall server performance (total drive space available etc) all will effect the performance of the system while the defrag is being done.

 

 

Event Logs:

Both workstation and servers should have the Event Logs checked. Many times problems can be found before they become a major issue. Often the operating system will log disk problems to the Event log before the drive dies. 

Both Application and System Event logs should be checked. 

 

For other general system advice, please read: Preventative Maintenance