Running SQL Server and EDM Server on separate machines

Note    The description below does not apply to vaults that use a Hypertrieve database.

For each vault the EDM Server stores different types of information.

• The database files
• The Streams
• EDM Local files
• HyperTrieve files (*.lck, *.che, *.csv)
• For an SQL or Oracle back-end: Write-ahead log files (*.log)

In case of an MS-SQL or Oracle vault, the EDM server and the Database server may be running on separate machines. This means that the database files will not be located on the EDM Server machine. Other information stored by the EDM Server can also be configured to be stored remotely.

Each group of files is discussed below.

The database files

When a new SQL vault is created you can specify the paths for the files used by SQL Server.

These paths are stored in the registry of the EDM server machine at:

HKLM\SOFTWARE\Cyco\<ActiveProduct>\CurrentVersion\Installed DataStores\<Vault Name>\CompoundItemService

String value ‘DataPath’ – The location of the SQL database files

String value ‘IndexPath’ – The location of the SQL index files

String value ‘LogPath’ - The location of the SQL log files

These paths should be valid from the machine running SQL Server.

The streams

The EDM server stores some data types (like the document content) directly to the file system. These ‘streams’ are stored in a special folder structure with single root folder. By default, the root folder for the streams is created in the ‘DataPath’ location. But the streams can be stored at an alternate location. A UNC path for this location can be specified when the vault is created (see below).

This path is stored in a string value called ‘RootPath’, in the registry of the EDM server machine at:

HKLM\SOFTWARE\Cyco\<ActiveProduct>\CurrentVersion\Installed DataStores\<Vault Name>\StreamService

String value ‘RootPath’ – The location of the streams folder.

To change this location:

1. Stop the EDM Service
   Note: Any client that tries to connect to the server will cause the service to be started again. This can be prevented by setting the ‘Startup Type’ for the AutoManager EDM Server service to ‘Disabled’.
2. Move the stream files to their new location.
   Note: The name of the streams root folder has 4 characters, which are the first digits of the DatatstoreID.
3. Change the ‘RootPath’ value to the new location
4. Start the EDM service

EDM Server local files

• HyperTrieve files (*.lck, *.che, *.csv)
• For SQL and Oracle backends: Write-ahead log files (*.log)

By default these files are al created at the location specified as the ‘DataPath’. When the database server and the EDM server are separate machines, the value of ‘DataPath’ must be valid on both machines. This may require an identical drive mapping on both machines. In version 2004d this limitation has been resolved by introducing an extra setting LocalDataPath.

HKLM\SOFTWARE\Cyco\<ActiveProduct>\CurrentVersion\Installed DataStores\<Vault Name>\CompoundItemService

String value ‘LocalDataPath’ – The location of the EDM Local files.

This value has to be created manually. It is ignored unless the vault uses a MS-SQL or Oracle Server running on a separate machine.

Using this setting, the EDM Local files can be moved to any location. This can be:

• A folder on the EDM Server machine, that is not equal to the ‘DataPath’ location used for the SQL database.
• A shared location in the LAN. This is required for clustering or other failover configurations.

Starting with version 2004d, this setting cannot be used during vault creation. Therefore it must be done manually on an existing vault. Please use the following procedure:

1. Perform a prepare for backup
2. Stop the EDM Service.
   Note: Any client that tries to connect to the server will cause the service to be started again. This can be prevented by setting the ‘Startup Type’ for the InnoCielo EDM Server service to ‘Disabled’.
3. Check the original location:
1. If any .LOG files exist, the server still needs to process these. Do NOT delete them. Start the server again to allow the .LOG files to be processed.
2. If the .LCK file still exists, the server was not stopped normally. Restart and stop the service again before continuing.
3. There should be a .CHE file. This can be safely deleted.
4. There can be a .CSV file. This can be safely deleted.
4. Create the folder (or share) that will be used as the new location for these files.
5. Create the ‘LocalDataPath’ string value in the registry and fill in the path to the folder created at step 4.
6. Change the ‘Startup Type’ for the InnoCielo EDM Server service back to automatic and start the service. The server will now use the new location.

Prepare for backup

For SQL vaults, the ‘prepare for backup’ operation will create a folder called ‘backup’ at the location specified for the EDM Local files. In this folder the ‘DataStore.ini’ file will be stored.

The BAK file for the SQL database will be stored in a folder called ‘backup’ at the location specified by the 'DataPath’ value.

When the ‘LocalDataPath’ values is used, the ‘DataStore.ini’ file and the BAK file will be stored in different locations.  

Note: The backup folder for the database BAK file is not created automatically (for the case of a remote server).

When creating the actual backup (to tape) you should include:

• The database .BAK file
• The Streams
• The ‘DataStore.ini’ file

Restart after restore

When restoring a vault from backup, the database BAK file is expected to be present at the same location it was created.

• Retrieve the database BAK file from the backup medium. Copy it to a folder called ‘backup’ at the ‘DataPath’ location on the remote server.
• Retrieve the ‘DataStore.ini’ file from the backup medium.
  Open this text file to check that the following values contain valid paths:
• DataPath, IndexPath, LogPath
• Servername (machine name of the remote server)
• LocalDataPath
• RootPath
• From the ‘restart after restore’ wizard, select the ‘DataStore.ini’ file and complete the wizard.