Description
Standard practice is to keep a minimum of three backup copies.
- Active cases should be backed up daily as well as backed up prior to and after new data ingestion.
- Active Legal Hold and Collections should be backed up daily
- Node/Appliance backups should be performed weekly as well as prior to and after major or minor upgrades.
Backups are used for multiple reasons.
The most common is the deletion of a case/matter. If for whatever reason the 'old' case/matter becomes relevant again, then the 'old' case/matter can be restored from the backup.
Backups are also used in the event of case failure or server failure where a restore of the case or server is required.
The newest backup prior to failure is always preferred. Sometimes the timing of failure is uncertain, so it is always recommended to have multiple backup copies available. The main concern is to always have at least one backup copy of even the oldest cases.
NOTE: Source Data is not backed-up
- Xcopy or use a third party backup for the contents of the \convertedFiles and \containedPstNsf folders
NOTE: For more details about particular backups, please read the 'About Backups' section within the System Administration Guide
BACKUP PROCESS LOCATIONS:
Case Backups (All Processing > Cases > Backup...)
- Scheduled Case Backups can be set at (System > Schedules > Add > Backups)
- Keep at least three backup copies
- Backup prior to ingestion new data
- Backup post new data ingestion
- When new data is ingested, backup the \convertedFiles and \containedPstNsf folder contents after the case backup
System Backups (System > Backups > System Backups)
- Not a complete backup of all information
Node/Appliance Backups (Clearwell Utility > 1. Backup Appliance)
- used for full recovery
- used to move the product to a new appliance
Legal Hold and Collections Backups (System > Backups > Legal Hold and Collections Backups)
- This option is an independent backup of the Legal Hold and Collection module.
- The Node/Appliance backup will also include this data.
- Restoration of this module must be executed on the original appliance or through a Node/Appliance restore for a new appliance.