Troubleshoot seeding to your on-premises environment
Who is this article for?
Code42 for Enterprise, yes.
CrashPlan for Small Business, no.
This article applies to on-premises authority servers.
Overview
This article provides solutions for any issues that may arise during the process of seeding archives to your on-premises environment.
Affects
Any Code42 server used for seeding archives
Diagnose
Code42 server sends an email notification
Issue
If there is a problem during the seeding process, the Code42 server sends an email to the address configured in that server's c42.seed.email system property. The affected seed archive is renamed <GUID>.SEED_FAILED.<timestamp> and placed in the seeding directory that was used for the seeding process. For example:
CrashPlanArchive_SEED/578290134123758901.SEED_FAILED.1358867950197
Recommended solution
The recommended solution depends on the type of message included in the notification:
| Error Message | Cause | Solutions |
|---|---|---|
| Computer not found | The device does not exist within the authority server's database. Backup archives created under another Code42 environment (with a different authority server) cannot be seeded. |
|
| Destination not offered | The device being seeded is not allowed to back up to the destination that is being seeded. | Enable backup to the destination via the organization level or system-wide level destination settings. |
| Unknown destination error | The authority server cannot gather information about the destination where the seeded archive has been placed. | Confirm network connectivity between the authority server and the destination. |
| Unreadable file |
The Code42 server cannot read the seed archive. |
|
| System error | The seeding process has failed for another reason. System errors also include a stack trace for additional diagnostic information. |
Contact our Customer Champions for Code42 for Enterprise support. |
Seeded archives do not move
Issue
Archives placed in the seeding directories are not immediately processed by the Code42 server.
Cause
The Code42 server checks every five minutes for archives in each seeding directory. A backup archive in the seeding directories is moved only after the backup archive remains the same size for two consecutive seed checks. This ensures that the archive has been completely copied into the seeding directory before the Code42 server moves it to the store point.
Recommended solution
Wait up to ten minutes before the seeding job begins moving a seeded backup archive from the seeding directory to the associated store point.
If the archive has not moved after ten minutes, contact our Customer Champions for Code42 for Enterprise support.
Seeded archives do not exist on the store point
Issue
Seeded archives are not present on the store point after seeding is complete.
Cause
If data balancing is enabled on the store point the archive is being seeded to, the data balancing process may move a seeded archive to another store point immediately after seeding is complete.
Solution
Use the Code42 console to search for the archive's GUID on all store points:
- Sign in to your Code42 console.
- Enter the archive's GUID in the search box.
- Select the result listed under Devices.
- Select the device entry to view its details, including the destination and store point on which the archive is stored.
Seed performance is slow
Issue
Seeding archives takes longer than expected.
Cause
Archive maintenance occurs on an archive immediately after the completion of the copy operation.
Solution
In order to speed up archive maintenance, you may choose to allocate more of your Code42 server's processing resources to archive maintenance.
- Sign in to your Code42 console.
- Navigate to Storage > Servers.
- For each server that is being used to seed archives:
- Click the server entry to view its details.
- From the action menu, select Edit.
- Increase the slider for Maintenance Rate, User Jobs to allocate more processing resources for archive maintenance.
Changing this setting affects the maintenance jobs that the Code42 server runs daily. If you change this setting, we recommend reverting the change when your seeding process is complete.