Author: paul.deluca

How do I determine how much space is being used by the PostgreSQL database?

First, determine where your postgresql database is installed. Here are the default locations for common platforms:

  • AIX: /u2/pgsql
  • RHEL (postgresql 8.1): /var/lib/pgsql/
  • RHEL (postgresql 8.4): /opt/PostgresPlus/

Once you have determined where the postgresql database lives, use the UNIX du command to report how much space is currently being used by the database files. Here’s an example from a RHEL server with postgresql 8.1 showing a database using 125 MB of data:

[root@firestorm ~]# du -sm /var/lib/pgsql/
125     /var/lib/pgsql/

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.

Solar Java Compatibility

Q. Which version of Java should I install for compatibility with ePad and Element?

[table “4” not found /]

Q. Should I install Java updates when prompted?

Yes, you should install Java updates when prompted, because Oracle often releases important security updates to the JRE. In almost every case, installing Java updates will not cause problems with Solar.

In the rare case that a Java update causes problems with the Solar client, we recommend that you first try to reinstall Solar. If performing a clean installation of Solar doesn’t resolve the issue, we recommend that you uninstall all other versions of the Java runtime environment (JRE), re-install only the JRE version that was certified with your specific release of Eclipse from the table above, and open an SR for our development team to review the issue.

Q. How do I determine which version of Java is certified for my release of Eclipse?

Please refer to the table above.

Q. Why is the version of Java on my web start page out of date?

As versions of Java with major security patches or significant features are released, the Eclipse development team integrates and tests each new version with the current version of Eclipse.

Due to the overhead involved with testing hundreds of possible combinations of Java runtime environments and Eclipse releases, the Eclipse development team only certifies the most recent Java runtime environment and Eclipse release.

Q. Is Solar compatible with Java 7?

Yes, Java 7 is bundled with Eclipse release 8.7.4.09 and later, and it may be manually installed for use with earlier versions of Eclipse.