Checklist for recovery
- If both original DS-Client and new hardware available
o Install new DS-Client, do not start the service.
o Move the database to the DS-Client:
- Look for the most recent dump files. They are located at the buffer location. Usually in C:\windows\temp\ folder.
- If they exist, make sure the timestamp on them is recent, during a time when there were no backups running.
- If a fresh copy is needed, run a daily admin process.
– If space is an issue, change the Buffer location (setup à configuration à parameters).
- Move the files to the new hardware
- Perform the Restore
- Using Management Studio
– Make sure the DS-Client service is NOT running.
– Open studio and locate the database:
- dsclient
- dsdelta
- dslanfiles (this one will not be restored)
- any expand databases (expand0001 and on),
– Right click on the database name à Tasks à Restore à Database
– Change the location to “From Device”
– Click the browse button and locate the dump files and click “Add”
– Select the database to restore
– In the Restore Option panel (on the left), check the “Overwrite the existing database” box.
– Restore the database
– Do this for both dsclient and dsdelta databases and dump files accordingly.
- Using sqlcmd
– Use this: https://www.howtogeek.com/50295/backup-your-sql-server-database-from-the-command-line/
– Or this: http://www.sqlservergeeks.com/restore-sql-server-database-from-bak-file-command-line/
– To overwrite, use “RESTORE WITH REPLACE”
o Once both databases are restores, start the DS-Client service
o Open DS-User and check the DS-Client’s health
o Re-register the hardware if needed
o (CRI file not needed in this scenario)
- In case a fresh dump file cannot be created, use “Detach / Attach” to move the databases to the new hardware.
- If the new DS-Client is installed before you attach the databases, the new databases (empty) should be deleted before the attach takes place.
- If the original DS-Client is unavailable
o Perform DS-Client database recovery
- Check the data and time of the last successful Daily Admin. If any backup occurred after that data/time, backup sets will need to synchronize after the recovery.
- Install the DS-Client on the new hardware
- Apply the CRI file and connect to the DS-System
- Allow auto-updates to finish, and other auto-update downloads.
- Perform the DS-Client database recovery (with dsdelta)
- Wait until the monitor window requests the DS-Client service to be restarted.
- Restart the DS-Client service
- DO NOT restart again during the database recovery.
- Open the Windows Event Viewer à windows logs à application log
- Check for messages regarding the SQL restore running in the background.
- When the final DS-Client Recovery Successful message appears, you can connect with the DS-User to the service.
- Check for other messages, if there are any issues.
o If the recovery fails, Recover Orphaned Backup Sets
- The DS-Client is installed, there are no backup sets but there is data on the cloud. If the recovery fails, the only way to connect to the existing data is to recover orphaned backup sets.
- Do not create new backup sets
- Run daily admin. It will show a messages that it found X backup sets that do not exist in the DS-Client database.
- Go to setup à system activities à repair à orphaned backup sets to repair.
- Select the backup sets (or all of them) to recover
- Backup sets will be created and synchronized, to populate the data in the local database.
- The sets do not have the “items” or any other settings in the backup set properties. To configure this:<
