How do I restore files from my tape backup on Linux?

If you are just interested in testing the readability or listing the contents of a tape, you may perform a table of contents listing (aka readback):

tar -tzf /dev/st0

To restore a single file (CONTROL) to a temporary directory (/esupport/restore):

mkdir -p /esupport/restore
cd /esupport/restore
tar -xzvf /dev/st0 ./u2/eclipse/CONTROL

To restore an entire directory (/u2/eclipse) to it’s original location (/u2/eclipse) for a full system recovery:

Warning: As always, please exercise caution when performing system maintenance, especially when initiating processes that can potentially overwrite data.
cd /
tar -xzvf /dev/st0 ./u2/eclipse

How do I troubleshoot tape backups on Linux?

Here are a few helpful procedures for troubleshooting tape backup problems under Linux.

  • First, test the tape drive by attempting to rewind the tape:
mt -f /dev/st0 rewind
    • If there are no problems issuing the rewind command, you’ll be returned to the command prompt.
    • If there are any issues, you will be presented with a descriptive error message.
  • Next, try to perform a manual backup of a few small files:
tar -czvpf /dev/st0 /etc
    • If there are no problems performing the test backup, you’ll see a number of files scroll by and then be returned to the command prompt.
    • If there are any issues, you will presented with a descriptive error message.
  • If there were errors with either of the above tests, please run the Dell Hardware diagnostics

Here are some common errors you may see with tape drives under Linux:

  • Tape has been marked as write-protected or read-only:
tar: /dev/st0: Cannot open: Read-only file system
tar: Error is not recoverable: exiting now


How do I gather CrashPlan logs?

View a step-by-step screencast of this process:

Before contacting CrashPlan for support, please gather the CrashPlan PRO client backup logs:

  • (Optional) Launch the CrashPlanDesktop client
  • (Optional) Double-click the CrashPlan logo in the upper right corner
  • (Optional) At the prompt that appears along the bottom of the screen, type “dump all” and hit Enter
  • Open a terminal session to the server and run the following commands to create an archive of the CrashPlan client logs. In this example, we’ll name the archive “crashplan_logs_20110124.tar.gz” and send it to the root user’s Desktop folder:
  • cd /usr/local/crashplan
    tar czvf /root/Desktop/crashplan_logs_20110124.tar.gz ./log
  • To attach the logs to directly from the server, launch the web browser and browse to the CrashPlan Support website
  • To transfer the logs to your workstation for use as an email attachment or otherwise, log into the server via FTP and transfer the archive you just created


How does ABS Failover work?

Epicor’s ABS Failover offering builds on the capabilities of our ABS Online Backup service to offer cost-effective Eclipse hosting in the event of a disaster.

There are a few requirements that must be met for the ABS Failover service to function:

  • Eclipse must be running on the Linux or Windows platforms
  • Broadband Internet connection for secure, offsite ABS Online Backup
  • Cisco-compatible WAN equipment for establishing connectivity to ABS Failover server(s)

In the event of a disaster, here is a general overview of the ABS Failover process:

  • Disaster causes customer’s primary Eclipse server(s) to go offline
  • Customer contacts Epicor Eclipse Systems Support team
  • Eclipse restores customer’s most recent ABS Online Backup to a set of failover servers
  • Customer connects to ABS Failover servers and continues business

What happens when my CrashPlan destination runs out of space?

If your backup destination runs out of space then backups to that destination will simply stop. CrashPlan will not automatically delete backed up data in order to make room at the destination.

In order to resolve the situation you’ll need to perform one of the following actions:

  • Option 1: Add more disk space to the destination
  • Option 2: Select fewer files to back up or change the retention settings
  • Option 3: Run Compact on the destination to prune any data that shouldn’t be backed up anymore

Option 1: Add Storage

If you are backing up to a local folder, consider increasing the amount of available space in the destination filesystem.

If you are backing up to an external drive, consider replacing the drive with a larger device. You could also consider rotating drives.

If you are backing up to an external network device, consider allocating additional storage to the NFS or iSCSI share.

If you are backing up to another server on your network, consider increasing the amount of available space in the destination filesystem or migrating the filesystem to a new location (Settings > Backup > Inbound Backup > Default Backup Archive Location) .

Option 2: Adjust Retention Settings

See also:

Option 3: Compact or Maintain Archive

See also: CrashPlan PRO Wiki: FAQ: What happens if my backup destination runs out of space?

Archive maintenance involves cleaning up the backup archive to remove backed up data according to the retention settings you’ve specified. Archive maintenance removes:

  • File versions that are too old
  • Deleted files that no longer need to be kept
  • Files that are no longer selected for backup
  • Self-heal archive blocks that have become corrupted (re-requests those blocks from the client).

A user can perform a manual archive maintenance by clicking the Compact button in PRO Client for a specific destination.

  • Within your client, de-select the file/folder you want to remove
  • Click Destinations and then select the appropriate destination type (Computers or Folders.)
  • Click the specific destination
  • Click the Compact button

NOTE: Removing files from your backup selection permanently removes the files from the backup archive. After compacting, de-selected and old data will be removed in the remote destination. You will not be able to restore any de-selected or old data once the maintenance/compact process is complete.