Recovering the DS-Client database
If you replace the DS-Client computer, you must recover the DS-Client database to the new machine. By default, it is backed up with the Daily Admin. For more information, see
“Configuring the parameter settings”.
NOTE: If you do not have a DS‑Client database backup, you must recover each backup set that is on the DS‑System individually to recreate the database. You will not be able to recover the backup schedules or any of the logs. Do not create any new backup sets until you finish reconstructing the DS‑Client database to the point it can synchronize successfully with DS-System. For more information, see
“Synchronizing a backup set”.
To recover the DS-Client database:
1. Assemble the hardware required for the replacement DS‑Client computer.
2. Install the same operating system version as the old DS-Client and recreate the user accounts (including the DS-Client service account).
3. Reinstall the DS-Client software.
4. Start the DS-Client service and connect with DS-User.
5. Verify the DS-Client database patch level:
a) On the Help menu, click About DS-User, and then click DS-Client Info.
b) In the DS-Client Version Info dialog box, check the Database Build value. You need to compare this value with the one that appears after recovering the database.
6. On the Setup menu, click System Activities.
7. Click Repair. The Repair DS-Client dialog box appears.
8. Select either DS-Client & delta databases or DS-Client database, and then click OK. A recovery message appears instructing you to restart the DS-Client service.
NOTE: The delta database contains delta information for all files. If this database is not recovered, the next backup requires DS-Client to send a new master (full file). This can significantly increase the time for the next backup.
9. To activate the recovered database, stop and restart the DS-Client service.
The recovered database contains data up to the time of its last backup. On startup, DS-Client checks if the database build number is compatible with the executable. If it is not, the DS-Client service stops or runs in a suspended mode that prevents connection or activity. If this occurs, check the operating system event log for details. Apply the missing patches up to the same database build number that you verified at the beginning of this procedure.
For Grid DS-Clients, any node that has a lower software version than what is compatible with the current database build is auto-upgraded immediately after the DS-Client service starts.
10. Run a Weekly Admin process:
a) On the Setup menu, click System Activities.
b) In the System Activities Administration dialog box, beside Last Weekly Admin run on, click Run Now.
11. Check to event log to ensure that no data exists on the DS-System that is not in the DS-Client database. If more data exists, you must synchronize the affected backup sets before any further backup or restore activities can be performed. For more information, see
“Synchronizing a backup set”.
NOTE: If the recovered DS-Client database data is missing backup sets, you must recover the orphaned backup sets. For more information, see
“Recovering an orphaned backup set”.)
NOTE: In the Select User dialog box, if you see two users with the same name it is because the DS‑Client searches by Security ID (SID). Select the lower one because the current user is closest to the bottom of the list.
13. Verify the DS-Client’s database patch levels again. (On the Help menu, click About DS-User, and then click DS-Client Info.)
IMPORTANT: When you recover a DS-Client database, any configuration changes made after the last database backup must be manually reapplied.