Removing Backup Files From the Repository

By default, Doc-To-Help keeps all versions of all files—including source files, auxiliary files, and the D2H project file—sent to the repository by all team members every time they are checked into the repository. These files are kept in the Backup folder in the repository. They come in handy if someone accidentally removes or overwrites changes made by other team members. The backup files can be used to recover lost data. However, this also means that the disk space occupied by the repository grows rapidly when members check in their changes, especially if the D2H project file is checked in frequently.

To conserve the repository disk space, an administrator should delete unneeded backup files from time to time. This can be done using C1D2HTeamAdmin.exe. The administrator can delete backups manually by deleting all or part of the contents of the Backup folder in the repository. Each version number has its own subfolder inside the Backup folder, so you can delete only particular versions, if necessary. If you wish, back up those folders elsewhere before deleting them.

  1. Double-click C1D2HTeamAdmin.exe. See Team Authoring Administrative Functions.
  2. Select File > Open Team Project to connect to the repository. The Load Remote Project dialog opens.
  3. Select the Repository Type. (If necessary, enter your login credentials.)
  4. Select a team project (or from the drop-down choose Select Team Project to browse for a project) and click OK.
  5. Select Tools > Clear Repository Backup. The Clear Repository Backup dialog opens.
  6. In the lower part of the dialog, select Delete all backup files older than.
  7. Click the drop-down arrow next to the date and select a date from the calendar. Select a time using the up and down arrows in the time box.
  8. Click OK. Backup files prior to the date and time specified are removed from the repository.

The administrator can also use this dialog to change the backup settings specified when the project was first shared. See Changing Repository Settings.

Note For other tasks, see Team Authoring Administrative Functions.