- Code42 CrashPlan (previously CrashPlan PROe)
There are several tools available to help an administrator identify devices that may need attention. This article describes how to use the administration console and the Code42 Reporting web app to identify devices that may require intervention.
Reporting web app
Code42 CrashPlan (previously CrashPlan PROe) version 5.1.x and later
Use the Reporting web app to gather information about backup health and storage in your Code42 environment, including finding devices that require administrator action. The Reporting web app can identify devices that may need attention by displaying key indicators like:
- Device alert status
- Completed backup percentage
- Date of last completed backup
- CrashPlan app version
For more information, see Viewing Device Backup Status By Using The Reporting web app.
The Code42 server sends out warning emails if a client isn't able to reach any backup destinations after a certain time period. The default is to send a warning message after three days and a critical message after five days. A warning email indicates that further investigation is needed.
You can configure the number of days that trigger either warning or critical emails in the Server Settings (Code42 CrashPlan) or from Settings > Reporting (CrashPlan for Small Business (previously CrashPlan PRO)).
User and device overview
Each user can have multiple devices, and each device can back up to multiple destinations. The Users and Devices overview screens combine the information for multiple backups into one progress bar. Progress bars can be found in the following locations:
- User details
- Device details
- User overview (version 5.1 and earlier only)
- Device overview (version 5.1 and earlier only)
The color of the progress bar denotes the state of the backup. By default, if the color is:
- Green - the destination has received new data within the past three days.
- Yellow - signals a warning state, meaning the destination hasn't received any new data in three days.
- Red - signals a critical state, meaning no new data in seven days.
Version 5.1 and earlier only
Clicking Users displays the Users Overview. The user progress bar shows the state of the device that is furthest along in the backup progress. If a user has multiple devices, the progress bar does not reflect the status of all the user's devices. Select a user to see status for all of the user's devices.
Version 5.1 and earlier only
Click Devices to show the Devices Overview, which displays the progress of devices in your Code42 environment.
If the device backs up to multiple destinations, then the progress bar combines information about the device's destinations. If the device's progress bar is green, at least one backup is progressing normally. Investigate further if the progress bar is yellow or red.
Connection and backup statistics
The administration console displays a device as online when it’s turned on and authenticated with the server. Use the Last Backup Activity, Backup Progress, and Completed fields to identify issues with the backups.
Last backup activity
The Last Backup Activity column of the Devices Overview displays the amount of time since any backup activity was detected on the device.
Click a device to open the device details and view Last Activity statistics. The Last Activity field displays the time elapsed since the device sent backup data to the destination. If there hasn't been activity for multiple days:
- Verify that the computer has been turned on and connected to the Internet.
- Access the client device to verify that it’s connected to the Code42 server or to the PRO Cloud and is operational.
- Run a Telnet test over port 4282 to the destination's IP Address to verify connectivity.
Open the device details to view Completed statistics. The Completed field represents the time elapsed since the device reached 100% backed up. If this field shows that the last 100% backup happened many days or weeks ago, the device is likely sending new files, but a small number of files may be locked and preventing backup.
For troubleshooting these situations, follow these articles: