Comparing Resco Backup v2 and BBVFS Pro v4
Published on: 13th April 2007.
Link to Resco Backup v1, BackupBuddyVFS Pro v3 and v4 review.
Since reviewing Resco's Backup and Blue Nomad's BackupBuddyVFS Pro [BBVFS], Resco have released version 2 of Backup. This review is aimed at comparing how Resco Backup has changed since version 1.The result of the previous review was that I changed my automated backup application to Resco Backup, while keeping BBVFS v3 as a manual option. I also set up a dedicated backup SD card for keeping backups at home: this too has both Resco Backup and BBVFS v3 installed.
One thing that BBVFS was less good at was saving multiple snapshots of the backup: creating permanent checkpoints being a manual action. A BBVFS checkpoint is a saved backup set that doesn't get updated again: it allows users to have saved, known configurations of their Palm. Resco Backup allows users to create multiple backup projects, each triggered according to its own schedule, and each being able to maintain multiple snapshots.As I said before: with a background in IT security, I know that backing up and archiving data is an important task and, indeed, BBVFS v3 has saved me many times. As I like to test new software, the option to rollback and wipeout an erratic application is important. It has also helped in managing the occasional switch to new, or old, devices.
Never was this truer than a few days ago when I tried to clean up after installing a few apps and testing them. My T3 ended up in a permanent soft reset cycle.
My backup strategy is:- Resco Backup:
-
- Project 1: 1 incremental backup that is triggered during the day when I exit PIM applicaitons
- Project 2: 6 incremental backups triggered each morning, Monday to Saturday
- Project 3: 4 full backups triggered every Sunday morning.
- BBVFS v3: manual backup
Through trial and error I had to rollback to the previous morning's 'Project 2' backup: my fourth newest set between BBVFS and Resco Backup.
I am glad I changed my backup strategy from having just one backup set being incrementally updated each morning.
The Comparison
The comparison was performed with these applications:
- Resco Backup v2.01 beta, provided by Resco.
- Resco Backup v1.40.7, provided by Resco.
- BackupBuddyVFS v4.1, in evaluation mode (which is fully functional).
The test device was a Palm Tungsten T3 with a SanDisk Ultra II Plus 1GB and a standard ByteStor 512KB SD card [my dedicated backup card].
While the T3 is not the newest Palm, both applications include options that are specific to newer PIM and NVRAM based Palms.
I've colour coded the review:
- Green:
-
- Provides feature.
- Provides feature and is the best implementation.
- Good comment.
- Yellow:
-
- Provides feature partially.
- Provides feature but is not the best implementation.
- Comment that is neither good nor bad: ambiguous.
- Red:
-
- Does not provide feature.
- Critical comment
| Selecting files to backup | |||
|---|---|---|---|
| Feature | Resco Backup v2 | Resco Backup v1 | BBVFS Pro v4 |
| Multiple backup file sets? |
Yes
The file selection is set for each 'Project' |
Yes
The file selection is set for each 'Project' |
Yes
File sets are can be assigned to one of the 5 available backup triggers |
| Automatically selects all files | Yes | Yes | Yes |
| User definable file set | Yes | Yes | Yes |
| Automatically add new files to the user selection |
No
New files are only added if the user selection is All files. |
No
New files are only added if the user selection is All files. |
Yes |
| User definable set of file using a filter |
Yes
New quick file selection action: select PIM database files. |
Yes | No |
| Automatically add new files to filter results |
Yes
Filter set can be static or dynamically set during the backup session. |
Yes
Filter set can be static or dynamically set during the backup session. |
No |
| Global excluded files | Yes | Yes | Yes |
| Global locked files | Yes
It offers to suggest suitable files, plus for non-NVFS devices (e.g. T3) it warns that this option is not necessary. |
Yes | Yes |
|
Supports multiple HotSync ID users
[Useful for shared backup cards or sharing a card between multiple devices] |
Yes
There is only one main backup folder on the SD card and this holds all the 'Project' folders. Each backup folder within a project's folder is name: {Hotsync ID} {Timestamp} This allows for multiple users to share the same project settings. Each users is allocated the number of backup sets defined in the project settings. |
Yes
There is only one main backup folder on the SD card and this holds all the 'Project' folders. Each backup folder within a project's folder is name: {Hotsync ID} {Timestamp} This allows for multiple users to share the same project settings. Each users is allocated the number of backup sets defined in the project settings. |
Yes
Each hotsync user gets their own folder with in the main BBVFS backup folder on the card. The user's folder holds sub-folders for all their checkpoints, archives and backed up files |
| Backup device/RAM options | |||
|---|---|---|---|
| Feature | Resco Backup v2 | Resco Backup v1 | BBVFS Pro v4 |
| Backup RAM | Yes | Yes | Yes |
| Backup Flash drive folders | Yes | Yes | No |
| Backup SD/MMC card folders | Yes | Yes | No |
| Compressing backups | |||
|---|---|---|---|
| Feature | Resco Backup v2 | Resco Backup v1 | BBVFS Pro v4 |
| Supported? | Yes | Yes | Yes |
| Compression levels? |
Yes
1. Normal
|
Yes
1. Normal
|
Yes
1. Quickly
|
| ZIP | Yes | Yes | Yes |
| Other | No | No | Yes |
| Encrypting backups | |||
|---|---|---|---|
| Feature | Resco Backup v2 | Resco Backup v1 | BBVFS Pro v4 |
| Supported? | Yes | Yes | Yes |
|
ZIP
[Note: do not use the same password for ZIP encryption as for other stronger encrypting applications, as their effective encryption strength will be exactly that of the ZIP encryption] |
Yes
Is this sufficient to protect personal data? Use of password/data protection applications should be considered, such as one using AES, IDEA etc. |
Yes
Is this sufficient to protect personal data? Use of password/data protection applications should be considered, such as one using AES, IDEA etc. |
Yes
Claimed to be weaker than their Non-Zip based compression backup scheme |
|
Other
[Still wise not to use the same password as used for other application: a 56bit key is not as secure as 128 / 1024 / 2048bit] |
No | No |
Yes
XTEA ECB with 56bit:claimed to be better than ZIP, but effective strength is unknown. |
| Archiving files no longer in RAM | |||
|---|---|---|---|
| Feature | Resco Backup v2 | Resco Backup v1 | BBVFS Pro v4 |
| Able to opt to save files in backup set that are no longer in RAM | Yes | Yes | Yes |
| Scheduling backups | |||
|---|---|---|---|
| Feature | Resco Backup v2 | Resco Backup v1 | BBVFS Pro v4 |
|
Supported?
[With multiple schedules / triggers it is still wise to plan to have only one triggering action for a given scenario] |
Yes
The following are set for each 'Project', so multiple backup schemes can be active and gives a flexible approach to backup strategy: for example, this allow for an incremental, uncompressed snapshot triggered by exiting important apps, incremental, compressed daily backups for the previous week, and a full, compressed backup every week. Giving 9 'Backup Sets' with known data configurations. |
Yes
The following are set for each 'Project', so multiple backup schemes can be active and gives a flexible approach to backup strategy: for example, this allow for an incremental, uncompressed snapshot triggered by exiting important apps, incremental, compressed daily backups for the previous week, and a full, compressed backup every week. Giving 9 'Backup Sets' with known data configurations. |
Yes
There is only one backup scheme active at any one time, that can be activated by many triggers. Backups are normally incremental, with full backups being performed only after a 'Checkpoint' event. 'Checkpoint' events can be automatically triggered, but they may happen at unwanted times. |
| Number of schedules supported |
Unlimited?
A schedule is a 'Project' and each defines the files on which it works and the triggers that kick-off the backup: as such, 'Triggers' are local to each 'Project'. Files are backed up to the / PALM / Backups / {Project Name} / {Backup Set folder} |
Unlimited?
A schedule is a 'Project' and each defines the files on which it works and the triggers that kick-off the backup: as such, 'Triggers' are local to each 'Project'. Files are backed up to the / PALM / Backups / {Project Name} / {Backup Set folder} |
1
Each trigger is global but can be assigned to backup a different user defined 'Set' of files to the common / Palm / Backup / {Hotsync ID} / Backup folder |
| Trigger on set time of selected days of the week | Yes | Yes | No |
| Trigger on set time on all days |
Yes
Just select all days in the above feature |
Yes
Just select all days in the above feature |
Yes |
| Trigger when power button pressed to switch off unit | Yes | No |
Yes
Activated when the global trigger is enabled or if a power-off is performed when a 'Continuous Backup' application is active |
|
Trigger when selected applications exit
[It is best to limit this to a select few application as it can quickly become very annoying] |
Yes | Yes |
Yes
Globally set with 'Continuous Backup'. This sets the files which activate this trigger |
| Trigger after HotSync | Yes | Yes | Yes |
| Trigger before HotSync | Yes | Yes | No |
| Trigger if no HotSync in a set elapsed time | No | No |
Yes
The wait time is set between 1 minte and 99 days 23 hours and 59 minutes. The trigger repeatedly actives between HotSyncs. |
| Trigger repeatedly for selected days of the week |
Yes
A repeating period can be set between 1 and 12 hours. The scheduled period can also be limited to a user defined time range within the day: e.g. only trigger for selected days between 08:00 and 22:30. |
Yes
A repeating period can be set between 1 and 12 hours |
No |
| Trigger on set threshold of low battery power | No | No | Yes |
| Incremental backup supported | Yes | Yes | Yes |
| Automated incremental backup |
Yes
A 'Project' is set to be 'Update' backup |
Yes
A 'Project' is set to be 'Update' backup |
Yes
Backups are incremental except when a defined 'Checkpoint' threshold is actived |
| Automated full backup |
Yes
A 'Project' is set to be 'Full' backup |
Yes
A 'Project' is set to be 'Full' backup |
Yes
A full backup is performed after a 'Checkpoint' is saved |
| Multiple backup snapshots? |
Yes
Each 'Project' can be set to save an unlimited or a defined number of 'Backup Sets'. The backup sets are cycled, if a defined limit of sets is specified, so that, when the maximum number of sets have been created, the oldest set is used for the next backup session. These are either incrementally maintained 'Update' sets that build on the older backup session files or a completely new 'Full' backup is performed after deleting the old backup's saved files. With incremental backups, the impact is to minimise the disruption to the user while maintaining multiple, historical versions of the the selected files from the RAM: a 'Full' backup can be very time consuming. |
Yes
Each 'Project' can be set to save an unlimited or a defined number of 'Backup Sets'. The backup sets are cycled, if a defined limit of sets is specified, so that, when the maximum number of sets have been created, the oldest set is used for the next backup session. These are either incrementally maintained 'Update' sets that build on the older backup session files or a completely new 'Full' backup is performed after deleting the old backup's saved files. With incremental backups, the impact is to minimise the disruption to the user while maintaining multiple, historical versions of the the selected files from the RAM: a 'Full' backup can be very time consuming. |
Yes
'Checkpoint's of the current backed up files can be manually created or automatically triggered to happen every N days and/or N backups. The number of 'Checkpoint's can be limited by the user if required. The space used by 'Checkpoint' folders can be limited to a set value of MB. During a 'Checkpoint' event it seems that the backup folder is renamed with a timestamp and then a new empty backup folder is created. This forces that full backup is performed after the 'Checkpoint' and depending on the trigger (such as N backups) this could be at an inconvenient time. |
| Listing type | File 'explorer' listing with sorting based on file parameter, such as: name, date, creator, size etc | File 'explorer' listing with sorting based on file parameter, such as: name, date, creator, size etc | Tree listing with files listed by creator: either shows the associated application name or creator ID if not known. |
| Select incremental backup
[The backup updates a previous backup session] |
Yes | Yes | No |
| Select full backup
[A complete new backup] |
Yes | Yes | No |
| Select groups of files by application using single click |
Limited
Only PIM database files are specifically accommodated with a action to select them from the list of files. |
No |
Yes
Tree-viewing allows the selection of the application which selects all of that creator ID's files. |
| Browsing files and lists | |||
|---|---|---|---|
| Feature | Resco Backup v2 | Resco Backup v1 | BBVFS Pro v4 |
| Listing type | File 'explorer' listing with sorting based on file parameter, such as: name, date, creator, size etc | File 'explorer' listing with sorting based on file parameter, such as: name, date, creator, size etc | Tree listing with files listed by creator: either shows the associated application name or creator ID if not known. |
| Manual backups | |||
|---|---|---|---|
| Feature | Resco Backup v2 | Resco Backup v1 | BBVFS Pro v4 |
| Supported? | Yes | Yes | Yes |
| Select incremental | Yes | Yes | No |
| Select full | Yes | Yes | No |
| Select groups of files by application using single click | No | No |
Yes
Tree-viewing allows the selection of the application which selects all of that creator ID's files. |
| Restoring files | |||
|---|---|---|---|
| Feature | Resco Backup v2 | Resco Backup v1 | BBVFS Pro v4 |
| Full restore | Yes | Yes | Yes |
| Selected file restore | Yes | Yes | Yes |
| Select groups of files by application using single click | Yes
Tree-view groups files into applications using creator ID, known alternate/hidden creator IDs, and association to ROM applications. |
No |
Yes
Tree-viewing allows the selection of the application which selects all of that creator ID's files. |
| Requires encryption password to be entered before the restore? | Yes | Yes |
No
Tries to use the saved password. |
|
Using the stored password is convenient but it does
bypass the protection provided by the encryption in
the situation where an unlocked Palm and card are
mislaid.
The better solution would be to allow the user to decide if the stored password is to be tried during restore: this would have to be an option on the dialog screen used to type in the password, and not a generally accessible option. |
|||
| Initial restore file selection | Depend ons on the option selected:
1. Full Restore: Restore Now 2. Partial Restore: Select Files ... 3. Partial Restore: Select Applications... Option 1 does not need a file selection: it proceeds to perform the restoration. Options 2 and 3 default for a full restore. |
All
Defaults for a full restore. |
Previous selection
|
| Other notes | The Restore workflow now has Numbered windows with descriptive titles and built-in help. The ability to click a Full Restore button removes any doubt about the default selection of files. | The 'Restore' dialog window and 'Next >' button at first looks like it is only a full restore. The window and button could be renamed to imply that it is pre-restore activity, which will lead to a file selection screen. | The previously selected files are still selected. For a partial restore, this could be an issue if they are not visible in the list window. It is advisable to always do a 'Select None' first and then select the files to restore. |
| Restore from multiple backup snapshots during a single restore event | Yes | Yes | No |
| Other features | |||
|---|---|---|---|
| Feature | Resco Backup v2 | Resco Backup v1 | BBVFS Pro v4 |
| Verify backup integrity | Yes | Yes | No |
| Compare backup snapshots differences | Yes | Yes | No |
| Easy for novice users? | Yes
Basic and Advanced user modes. New users are first presented with Basic mode, which provides a clearer interface than v1: using normal menus to access project set up screens. There are two buttons a big 'Backup' button and smaller 'Restore'. This gets the first backup done quickly. The initial launch also creates additional default projects for backing up image and contacts data. The Backup button performs an Update [incremental] backup. But a hidden menu under the Resco Backup icon to the left of the button provides access to create a new backup set and view. Basic mode also hides the more advanced, device specific features and instead sets default values based on the Palm being used. If Advanced mode has been used to configure these features, then these values will take precedence. The v1 interface is retained in Advanced mode. |
No
There is no 'basic' mode that allows new users to bypass the more advanced options and concepts of backing up. There are New Backup and Restore…buttons, but also an Update button. Plus others for Verify, Setup, Sets, and Schedule. A basic mode should allow a new user to instantly understand what to do, and so make a first backup 'now'. Then there is time to learn about other features. The most important thing is to do backups [and be able to restore from them, too]; an easy entry to do a first backup is essential so as not to frighten away users. |
Yes
Basic and Advanced user modes. The Basic mode is equivalent to the 'lite' version of BBVFS. This gets any user backing up straight away with the big Backup button - almost impossible to go wrong. There is a button for accessing Preferences [schedules, and compression and encryption] and another for a full restore. Advanced mode provides access to archiving, checkpoints, backup sets, partial backup/restore. |
| Support for newer Palms |
Yes
Caters for newer Palms with options to set excluded files, and address various PIM and NVRAM specific issues related to backing up: DbCache, newer PIM DBs, locking risky apps. These options are useful but time is needed to understand which are most appropriate for the user's Palm. |
Yes
Caters for newer Palms with options to set excluded files, and address various PIM and NVRAM specific issues related to backing up: DbCache, newer PIM DBs, locking risky apps. These options are useful but time is needed to understand which are most appropriate for the user's Palm. |
Yes
Caters for newer Palms with excluded files and locking risky apps. This is overtly more appropriate to newer devices than V3, whether this is truly the case or not, it would be better to use V4 for peace of mind. |
| Price |
$14.95
Upgrade from V1: Free |
$14.95 |
$24.95
Upgrade from V3: $11.95 |
| Comparative Performance | |||
|---|---|---|---|
| Feature | Resco Backup v2 | Resco Backup v1 | BBVFS Pro v4 |
| Settings | ZIP | ZIP | ZIP |
| Application size | 206KB | 191KB | 627KB |
| Tests with ByeStor 512KB SD card | |||
| Full backup (KB) - Best | Untested* | 'Maximum' compression with encryption and computing CRC | 'Thorough' compression with encryption |
| -- | 09:27 minutes | 16:26 minutes | |
| -- | 12,700KB | 12,831KB | |
| Full backup (KB) - Fastest | Untested* | 'Fastest' compression with encryption | 'Quickly' compression with encryption |
| -- | 05:38 minutes | 15:48 minutes | |
| -- | 13,798KB | 13,371KB | |
| Tests with SanDisk Ultra II Plus 1GB SD card | |||
| Full backup (KB) - Best | Untested* | 'Maximum' compression with encryption and computing CRC | 'Thorough' compression with encryption |
| -- | 05:50 minutes | 06:46 minutes | |
| -- | 12,700KB | 12,831KB | |
| Full backup (KB) - Fastest | Untested* | 'Fastest' compression with encryption | 'Quickly' compression with encryption |
| -- | 02:08 minutes | 06:06 minutes | |
| -- | 13,798KB | 13,371KB | |
|
* While no new tests where conducted on Resco
Backup v2, my Palm has a similar composition now as
when those tests where performed and with v2 the
observed times and backup sizes are unchanged from
v1: a full backup with fastest compression still
takes between 2:00 and 2:10 minutes.
The original tests where performed as full backups of the same RAM (30,520KB containing 721 files) and, before performing a new test, the backup files of previous tests were deleted to bring the card state back to the pre-test structure. All encryption was performed using the same password. The Resco Backup timings are based on the time reported by the application [I checked and verified that they reported the times as stamped in the backup folder and its files]. For BBVFS I used the first backed up file's creation data and the last backed up file's modification time and calculated the elapse time: this omits the time for checking for orphan files, which is an unnecessary activity in full backups. Note: Tests are specific to the composition of files resitent in RAM, the Palm device, and the SD card used. Tests on other environments will yield different results. VFSMark Results for ByteStor 512KB SD Card used in the tests:
VFSMark: 562 VFSMark Results for SanDisk Ultra II Plus 1GB SD Card used in the tests:
VFSMark: 567 Tests where also performed without any compression at all, and for both applications these tests were significantly slower than the results with compression. As such I will be backing up with compression switched on. |
|||
Comments
I performed backups and restores, full and partial, and both performed well. The success of recreating a working Palm was demonstrated by both.
I have omitted commenting on advanced backup operations that are not visible to the user, such as device specific issues addressed in the application code.
The summary of the unique benefits of each application is given below.
Resco Backup v2 plus points
- Speed of backup.
- Much better implementation of multiple backup snapshots/sets: BBVFS v4 needs to perform a full backup after a checkpoint is why I never used them [manual action in v3] as the time was too onerous.
- Selectable incremental and full backups instead of forced full only after checkpoint.
- Different compression settings for quick snapshot projects and higher compression and comparison checking for less frequent backup projects.
- With the scheduled options to hide the count-down and abort button the dialog is nice and small and seems to be an integral part of the system.
- Backup projects can be associated with named SD cards, so stopping unwanted backing up to swapped out cards.
- Relatively small application size.
- Ease of use for novice users: a clearer interface in Basic mode hides 'advanced' settings for newer Palms [which are addressed by device specific default or already set Advanced mode settings]. Still provides access to incremental backup and restore within Basic mode.
- Tree-view mode for restore of selected applications - the application's group of files is determined by creator ID, known alternate/hidden creator IDs, and applicable associations with ROM applications.
- New scheduling to restrict the 'every <time period>' periodic daily backups to between set times of the day.
BackupBuddyVFS Pro v4 plus points
- Ease of use for novice users: BBVFS has a lot less 'advanced' settings for newer Palms on display, in fact only locking 3rd party apps is shown: BBVFS must address other new Palm issues under-the-hood?
- Supports stronger encryption backups, and weaker PC compatible ZIP encryption: RescoBackup is only ZIP. Relative strength is unknown: how difficult is [X]TEA 56bit to brute force?
- Tree-view is useful for easily selecting multiple files associated with an application - this isn't fool-proof as some software authors use other creator IDs to obscure files from users.
- Scheduling triggers for low battery and time since last hotsync are only available in BBVFS.
- Maximum space for backup sets useful for shared-usage/smaller cards.
- Restores without password prompt - but the ability to do this should be an option set when storing the password.
- The main screens are visually better: especially now with the coloured tree view.
- Scheduled backups have countdown and re-schedule dialog, and not for continuous backups. More user-friendly than having the dialog for all or no backup events.
- Option to add new files to user defined file sets.
Conclusion
While both applications aim to address the needs of advanced users there are significant differences that leave me believing that BackupBuddyVFS Pro is more appropriate to novice users and users that don't require Resco's more advanced support for multiple backup sets. BBVFS v4 has support for user defined file sets but these are always applied to the current, single backup folder, whereas Resco Backup allows multiple backup folders to be active so giving concurrent backups for, e.g., this morning, yesterday, last sunday and so recovery - and all these can be maintained as incremental backups.
In version 1 Resco Backup did not have a Basic mode for novice/new users, and because of this omission I thougtht it was better suited for the more experienced user. With version 2 Resco Backup has addressed this and now caters for both. The Basic mode hides enough of the advanced features, while still allowing an interested new user to create full/partial scheduled backups and perform full/partial restores. In fact the Basic mode is probably enough for many experienced users to use as their normal interface: once they have set the exclude and lock risky apps lists.
Unlike BBVFS v4, where the Basic mode stopped partial backup and restore and forces the user to enter the Advanced screens, the Resco Backup v2 Basic mode provides the two button 'Backup' and 'Restore' view while still allowing access to these addition functions.
Just to be clear, in both applications, the Basic and Advanced modes are simply different screens/views presented to the user to manage the same set of backup files. For example, Resco Backup Basic mode can be used to manage backup projects created when the user was in Advanced mode, and vice versa.
Resco Backup has now added support for performing a partial restore based on a selection of applications. Like BBVFS, a tree-view listing is presented to the user showing expandable branches labelled with application names. As well as using a file's creator ID to identify to which application it belongs, Resco Backup also uses known alternate and hidden creator IDs and known associations to ROM applications.
As before:
However, the performance difference, is very marked and may lead users to not perform frequent BBVFS checkpoints. From my experience, we were always told to do daily backups for each day of the week, rotated each 7 days, then keep each weekly backup for a month and then archive and retain the monthly backup. This might be over-kill for a Palm but support for a modified scheme would be useful. If the time impact of creating multiple backups is too onerous then users may put off performing them: so it is strongly recommended that a fast SD card is used with any backup application.
Both vendors provided a comprehensive user guide, on their websites, and users should read these while evaluating the applications. Much of what might seem complex is explained in the guides and, having done so myself, leads to a more thorough understanding of how the applications work and can best be used. Additionally, both applications included useful built-in help too: BBVFS omitted details for some of the newer features.
With either application I would strongly advise that users use a stronger encryption solution for securing their most important data, as the relative strength of ZIP and TEA will probably be not sufficient. Currently I use SplashID with Mac desktop and it has proven to be a stable solution, provided it is properly backed up along with all my other data! Just remember that, just like any other piece of technology, SD cards can fail, so it is best to backup to more than one card and/or backup the SD card to another location (Mac, PC, CD etc).
To summarise:
The new features of Resco Backup v2 improve on its already wide list of capabilities. The two stand-out additions for me are the Basic mode and the ability to select applications for partial restore. These two features reduce the number of important unique features that BBVFS v4 had over Resco Backup v1and so make it a worthwhile upgrade.Notes
Resco kindly provided a licenced copy of Backup. However, the review was performed for my own benefit and as such it was performed objectively as I don't want to lose my data.
Both Resco and Blue Nomad have expressed interested in this review and seem keen to see to how they can improve their products, which can't be a bad thing for us users!