Delete files and versions from your backup

CrashPlan's default version settings and scheduled archive maintenance handle routine cleanup automatically, thinning out older versions and removing deleted files. You can delete files and versions from a CrashPlan backup archive yourself when a requirement calls for it, such as a request to erase personal data or a data retention policy, or when data no longer needs to be backed up. CrashPlan technical support may also recommend deleting files or versions to keep a backup archive healthy.

Files you remove from the file selection or exclude from backup, and versions and deleted files beyond what the version settings keep, are deleted at the next archive maintenance run, or sooner if you run archive maintenance yourself.

Before you delete files or versions from a backup, confirm that you will not need to restore them. Once they are deleted from the backup, they cannot be restored.

To delete everything a device has backed up to one destination, delete the backup archive instead. On most CrashPlan plans, an archive deleted from a cloud destination is held in cold storage, and its data is deleted when the archive is purged from cold storage or the cold storage retention period ends.

Stop backing up folders and files

Files removed from the CrashPlan file selection or excluded from backup are deleted from the backup, with all their versions, at the next archive maintenance run. Folders whose files can be reinstalled, downloaded again, or rebuilt, such as application files, software dependency and build folders, and caches, are the safest to leave out of a backup.

Stop CrashPlan from backing up files in either of these ways:

Administrators can keep operating system and application files out of every device's backup by updating the organization's global exclusions to the current default list, including on devices whose file selection is the whole drive.

Keep fewer versions and deleted files

CrashPlan keeps versions of each file, and keeps files deleted from the device, according to the device's version settings. Versions and deleted files that the settings no longer keep are deleted from the backup at the next archive maintenance run.

Files that change often add the most versions. Three settings determine how often versions are created and how they are kept. They are under Frequency and versions in the device's backup settings in the CrashPlan console:

  • Backup changes every: A longer interval creates fewer versions of files that change often, and leaves fewer points in time to restore them from.
  • Version retention: The settings from For one week, keep a version to After one year, keep a version decide how many versions of older changes are kept. Keeping fewer leaves fewer earlier versions to restore.
  • Remove deleted files: A shorter period removes deleted files from the backup sooner, so they can be restored for less time after they are deleted.

CrashPlan always keeps at least the most recent version of each file it backs up. To delete a file from the backup entirely, stop backing it up.

On a device with more than one backup set, each set has its own version settings. Where sets back up to the same destination, the highest-priority set's version retention and Remove deleted files settings apply to every file at that destination, as described in How exclusions and retention settings apply across backup sets.

To change the CrashPlan version settings for a device:

  1. Sign in to the CrashPlan console.
  2. Select Administration > Environment > Devices.
  3. Select the name of the device.
  4. Select the action menu settings-gear-console.png, then select Edit.
  5. Select the Backup tab. The tab is labeled Backup Sets if backup sets are enabled for the device.
  6. Under Frequency and versions, move the slider for each setting you are reducing.
    When you change a version retention setting to keep fewer versions, the console changes each setting for older versions that kept more, so that it matches.
  7. Click Save.

If you cannot change these settings, they are managed by your organization, and your CrashPlan administrator needs to make any changes. Administrators can change them for an organization in its Device Backup Defaults, and use Push to apply the change to existing users.

Delete files and versions sooner with archive maintenance

CrashPlan deletes the files, versions, and deleted files that a backup no longer keeps at the next scheduled archive maintenance run. To delete them sooner, start maintenance yourself. Users can start maintenance for their own devices.

Archive maintenance can take from several hours to several days, depending on the size and state of the destination's backup archive. Backup to and restore from that destination wait until maintenance finishes, so restore any files you need soon before you start it. While maintenance runs, the Home screen of the CrashPlan app shows an estimate of the time remaining.

Where you start CrashPlan archive maintenance depends on the destination:

  • CrashPlan cloud destination: Start maintenance from the CrashPlan console or from the CrashPlan app.
  • Local destination, such as an external drive: Start maintenance from the CrashPlan app.

Run archive maintenance from the CrashPlan console

To run archive maintenance for a CrashPlan cloud destination from the CrashPlan console:

  1. Sign in to the CrashPlan console.
  2. Select Administration > Environment > Devices.
  3. Select the name of the device.
  4. If you removed files from the file selection or added exclusions, wait for the file verification scan that starts after the change to finish. Administrators can check the device's History in the console to confirm that the scan has completed.
  5. Select the Archive Options icon Archive_Options_Icon-415-export.png for the destination.
  6. Select Maintain Archive.
  7. Click OK.
    The maintenance job is added to the queue.

Each destination keeps its own archive, so if the device backs up to more than one cloud destination, repeat Step 5 to Step 7 for each one.

Run archive maintenance from the CrashPlan app

To run archive maintenance from the CrashPlan app on the device:

  1. Open the CrashPlan app.
  2. If you removed files from the file selection or added exclusions, wait until the Home screen no longer shows Scanning. The file verification scan that starts after the change has to finish first.
  3. Select Settings > Destinations.
  4. Select the destination.
  5. Click Run maintenance.

If the device backs up to more than one destination, repeat Step 4 and Step 5 for each one.

Delete specific files immediately

To remove specific files from a CrashPlan backup promptly, such as malware or data covered by an erasure request, stop backing them up and then run archive maintenance.

At CrashPlan cloud destinations, administrators can also delete specific files and folders immediately, with the purge.path command in the CrashPlan console command-line interface. The command deletes the files and folders at a path from every cloud archive of the device in which they are found, without waiting for archive maintenance. Check that the path names only files and folders you will not need to restore.

The command deletes what is already backed up and leaves the file selection as it is, so files that remain on the device and in the file selection are backed up again. Delete the files from the device, or stop backing them up, before you run the command.

The command acts on cloud destinations only. To delete files from a local destination, stop backing them up and run archive maintenance from the CrashPlan app.

Running purge.path requires an administrator role, such as Customer Cloud Admin or Cross-org Admin. The command's syntax, the other roles that can run it, and the switch for a path that is also in a legal hold archive are described in CrashPlan console command-line interface reference.

The deleted paths disappear from the CrashPlan console at once. The CrashPlan app may still list them until it next synchronizes with the destination, but the files cannot be restored.

Was this article helpful?
0 out of 0 found this helpful