DS-Client Database (Maintenance)
Creation Date: July 24, 2007
Revision Date: May 20, 2008
Product: DS‑Client
Summary
The DS-Client database is created by the DS-Client Installation. Ideally, no further configurations are required after installation.
This article covers some possible maintenance issues that might arise.
Increasing Disk Space for DS-Client Database
DS-Client is installed with notification levels to alert regarding low disk space on the DS-Client Database. You have the following options:
Windows DS-Client databases (Microsoft SQL Server) |
Option 1: | Free up disk space on the database drive. |
Option 2: | Move the DS-Client database to a larger capacity drive by using any method of backing up and restoring the DS-Client database. • Make sure the Microsoft SQL Server version on the target drive is compatible. It is recommended to use the same version. • Re-configure the DS-Client to point to the new database location. Modify the “Database” registry key on the DS-Client computer (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DS-Client\Parameters). Set the value to the UNC path to the new database instance (e.g. \\servername\instance_name\dsclient). |
Option 3: (NOT Recommended) | Create additional data files for the DS-Client databases on other disks (please refer to the Microsoft SQL Server documentation). NOTE: If the additional data files are located on another drive and those paths do not exist when recovering the DS-Client database to another machine, then DS-Client will report errors and the database recovery will fail. |
Linux / Mac DS-Client databases (PostgreSQL Server) |
Option 1: | Free up disk space on the database drive. |
Option 2: | Move the DS-Client database to a larger capacity drive by using any method of backing up and restoring the DS-Client database. • Ensure the PostgreSQL Server version on the target drive is compatible. It is recommended to use the same version. • Re-configure the DS-Client to point to the new database location. Modify the “Database Host” value in the DS-Client’s configuration file (dsclient.cfg). Set the value to the IP address or UNC path of the server where the new database instance is located. |
DS-Client Database Version (compatibility checking)
On running DS-Clients, you can check the database build number from DS-User > Help > About DS-User... > DS-Client Info.
On startup, DS-Client checks if the database build number is compatible with the executable:
• Standalone DS-Client: For standalone DS-Clients (Windows / Linux / Mac), if the DS-Client database build number is not consistent with the DS-Client executable, the service will not start. If you recovered an old DS-Client database that has a lower build number, upgrade the DS-Client database (Windows) or re-run the latest installation (Linux / Mac).
• Grid DS-Client (Windows): For Grid DS-Clients, if a node has the same software version as the highest version in the Grid, the same database compatibility verification as for standalone DS-Clients applies. Otherwise, for any node that has a lower (software) version, the (database) compatibility checking will be skipped and an auto-upgrade will be issued immediately after the DS-Client service is started. If this auto-upgrade fails, the database compatibility verification will be done after the auto-upgrade.
Backing up the DS-Client Database
Since most of the DS-Client configuration settings (DS-User > Setup > Configuration) are stored in the DS-Client database, it is recommended that you regularly backup this database. This is the default behavior for the DS-Client (Click DS-Client Configuration > Parameters > Database options) during its Daily or Weekly Admin Processes.
NOTE: If you recover an older DS-Client database, remember that any configuration changes that were made after the last database backup (if any) will not be saved. They must be manually re-applied.