November 12, 2012

QPKG updated to support CrashPlan 3.4.1 on QNAP NAS

CrashPlan backups stopped working on QNAP NAS

It seems that the excellent backup software CrashPlan was recently updated to version 3.4.1.

For users running CrashPlan on a QNAP NAS, by using the QPKG package available from the QNAP forums, this means that CrashPlan has simply stopped working (and is no longer backing up files).

This has to do with the CrashPlan auto-update feature, which unfortunately can't be disabled. The CrashPlan installer and the QPKG have completely different directory structures, and it appears to be something that can't be made to work on a QNAP NAS.

Unable to connect to the backup engine on QNAP NAS after CrashPlan released an upgrade.


Upgrade to the latest CrashPlan QPKG for your QNAP NAS

Good news is that dynek, who maintains the CrashPlan QPKG, released an updated version on November 11. It is now available in the QNAP forums and can be used for fresh installations or upgrades.

NOTE: Make sure to read the section "Update instructions" if you have already installed a previous version and are upgrading! You should not uninstall the old version!


November 6, 2012

SQL query shows the benefits of Block Change Tracking

SQL query that shows the benefits of BCT

To see how much you benefit from having Block Change Tracking enabled, use this query to calculate the percentage of blocks read and the number of blocks backed up during incremental backups.

For results to show up, you need to have Block Change Tracking enabled and have performed an incremental level 0 backup followed by one or more incremental level 1 backups.

The query returns one row for each datafile backed up using RMAN.

select file#, avg(datafile_blocks) blocks,
avg(blocks_read) blocks_read,
avg(blocks_read/datafile_blocks)*100 pct_read,
avg(blocks) blocks_backed_up
from v$backup_datafile
where used_change_tracking='YES'
and incremental_level=1
group by file#
order by file#
;

November 3, 2012

Stop "S Voice" from starting after double-pressing the home button on Samsung Galaxy S3



In Samsung Galaxy S3, Vlingo Voice Command (from SGS2) has been replaced by an application called "S Voice". Like its predecessor it is, by default, launched whenever you double-press the Home button.

Luckily, it's a lot easier to disable the shortcut than it was on the SGS2. You don't even have to remove the app from your phone.

Here's how to stop S Voice from starting whenever you double-press the Home button.

  1. Launch the S Voice application.
  2. Go to settings.
  3. Disable/uncheck the "Launch S Voice" option in the settings menu.




Related:



Source: Androidcentral