How can I backup a case? How do I restore that case?
This article describes how to use the DBConfig utility to backup and restore cases. DBConfig will backup all the database and case information necessary to restore that case. It DOES NOT, however, back up the evidence. This should be done manually if a backup of the evidence is required.
Note: Project backups in eDiscovery using DBConfig do not backup the collections performed in that Project.
1. Open the DBConfig utility by navigating to its install directory (i.e., "[drive]:\Program Files\AccessData\DBConfigTool") >> right-click on DBConfig.exe >> choose Run as administrator.
2. When the DBConfig window opens, make sure the correct connection is checked and select it.
3. Click Backup.
4. Enter (or check) and confirm the following information
a. Backup Path
b. Application Database (confirm the Server Name and port are correct)
c. Check the case(s) to be backed up
5. Click Backup Selected Cases. (Note: A progress bar should appear)
6. When the backup completes, a new window will appear confirming completion.
7. The destination folder should contain the files and folders as shown below.
1. Follow steps 1 and 2 of the Backup Case section above.
2. Click Restore.
3. Enter (or check) and confirm the following information
a. Backup Path
b. Restore to a separate database (choose this from the drop-down menu)
c. Application Database (confirm the Server Name and port are correct)
d. Case Folder (optional) - this is where you can choose to put the new case folder. Leaving this blank will restore the case folder to its original location, seen under the Path column.
4. Select each case (one at a time) to be restored and click Map User IDs
5. Confirm that each user in Previous User Name column has a User Name. These can be mapped by clicking on a user in the left side and then clicking ">>" to add the user to the mappings. Once completed, click Dismiss.
6. Click Restore.
7. When the restore completes, a new window will appear confirming completion.
8. The case should now show up in the case list in the UI.
9. If the backup was made in an older version than currently being used (Ex. Backup from v6.1 being restored into v7.1) you will need to use the dbcontrol command line utility to update the schema of the restored case.
- Example Syntax: dbcontrol.exe dbtype=Postgres host=localhost -updatecases <FTK ID>
- Example Syntax: dbcontrol.exe dbtype=MSSQL host=MSSQLSERVER -updatecases <FTK ID>
(IMPORTANT: After restoring a case, the evidence paths will be the same as they were when the case was backed up. If the evidence location has changed, please use the article Change Evidence Path to update the path to each evidence item in the case. This procedure requires FTK, Enterprise, or Lab to be installed.)
NOTE: When restoring a case to a new location, the chosen case folder will be deleted when the restore first starts, and then re-created later on in the process.
Alternate Backup Solutions
Database backups can also be taken through SQL Server Management Studio (SSMS), or other backup tools, manually or through Maintenance Plan(s). However, it should be noted that if these database backups are to be restored to a different SQL instance, the database users and permissions will not be restored, rendering the restore incomplete.
In addition, using SSMS (or other tools) to perform backups DOES NOT backup the case or evidence data. If this or other tools are to be used for backups, an alternate strategy to backup the case and evidence files should be included.
Backing up and restoring cases can be useful in a variety of situations and is a key component of disaster recovery.