Skip to main content

Who is this article for?

Code42 for EnterpriseSee product plans and features
CrashPlan for Small Business 

CrashPlan for Small Business, no.

Code42 for Enterprise, yes.

Link: Product plans and features.

This article applies to Code42 cloud environments.

Code42 Support

Resolve extreme scale from large manifest files

Who is this article for?

Code42 for EnterpriseSee product plans and features
CrashPlan for Small Business 

CrashPlan for Small Business, no.

Code42 for Enterprise, yes.

Link: Product plans and features.

This article applies to Code42 cloud environments.

Overview

Extreme scale due to large manifest files can cause issues such as slow loading of file restore options, file restores that take a long time to complete, restores that time out, and problems with synchronization. This article describes what a file manifest is, what causes extreme scale, and what you do to resolve these issues. 

About large manifests

A manifest file is a binary file that stores the file paths in the archive. A history data file is a binary file that stores the version information of all backed up files. During the restore process, Code42 checks the manifest file to identify the path to use when restoring a file. Code42 also checks the history data file to confirm that the file exists and fetches the file for you.

Causes of extreme scale

Backup archives can reach extreme scale due to large manifest files as a result of:

  • Backing up file versions at a high frequency 
  • Retaining more file versions than necessary 
  • Backing up system or application files (like app data, temp data, system files, and so on) that the Code42 app is not designed to back up. For more information, see What should you back up?.

Recommended solution

You can manage the size of the manifest file and the history data file by updating your file selection, updating frequency and version settings, and changing the Remove deleted files setting. See Recommended Code42 console settings for full details on how to optimize your settings.

Step 1: Change the file selection

Remove files and folders from your file selection: 

  1. Open the Code42 app. 
  2. Go to Manage files
  3. Uncheck the box next to:
    • Windows: C:
    • Mac: / or Macintosh HD 
  4. Verify any external drives you want backed up are selected. 
  5. Navigate to the folders and files you want backed up. User files are typically stored in a User directory or Home folder. 
  6. Select the check box next to the files and folders you want backed up. 

For detailed instructions, see Change the file selection.

Step 2: Update frequency and versions settings 

Updating the frequency and version settings for your backups can help reduce the size of your manifest file and the history data file, resolving issues with file restores and synchronization.

You can update frequency and version settings from the Code42 app or from the Code42 console. When adjusting these settings: 

  • Decrease the number of file versions that are backed up
  • Change the Remove deleted files setting to 90 days

Step 3: Start archive maintenance

To reduce the size of your backup archive, manually start archive maintenance:

  1. Sign in to the Code42 console. 
  2. Select Administration > Devices > Active from the left navigation menu. 
  3. Select the device for which you want to start archive maintenance.
  4. From the device details, select the Archive Options icon Archive Options icon.
  5. Select Maintain Archive.
    A message informs you that running archive maintenance may cause the archive to become unavailable for restore or backup until maintenance finishes. 
  6. Click OK.
    Your job is added to the queue.

Next steps

  • You can confirm the issue is resolved when you can navigate the restore files options (from the Code42 app or the Code42 console) without experiencing any slowness. From a technical standpoint, the manifest file should be around 300 MB or less, and the manifest file should be 1 GB or less. 
  • For more information about how to configure your environment for optimal performance, see Recommended Code42 console settings
  • Was this article helpful?