Who is this article for?
CrashPlan for Enterprise, yes.
Code42 for Enterprise, yes.
CrashPlan for Small Business, no.
This article applies to on-premises authority servers.
This article explains how to interpret and respond to the following alert.
The table below displays where the alert appears and where it can be configured.
|"Database backup db.bak exists on server Code42 server name at /sample/path. Confirm database import success, then safeguard or remove database backup."||Delivered by email and to the Alerts Overview of the Code42 console|
|"Database restore cleanup needed"||Settings > Notifications of the Code42 console|
Low - this alert indicates a condition that should ideally be corrected, although it does not pose an immediate threat to user data, system security, or service availability.
When you use the database import function to import a database into your Code42 server, the Code42 environment backs up the current database before importing the new database. The backed up database is stored as the file db.bak. This file, if present, will trigger the alert Database restore cleanup needed until the file is removed or safeguarded to another location.
Unnecessary database backups take up space.
To resolve this alert:
- Confirm that the database import was successful, and that you can log into the Code42 console.
- Move the database backup, db.bak, to a safe location, or delete it. The path to the file db.bak is included in the notification.
Acknowledge the alert
An alert appears in the Code42 console's list of active alerts until someone dismisses it. To dismiss an alert:
- (Version 6.5 and later) Go to Active Alerts, select the alert, then go to the action menu and choose Dismiss.
- (Before version 6.5) Go to Alerts Overview, select the alert, then go to the action menu and choose Acknowledge.