Hi Folks
Subject originally:
Re: biz-network BACKUP choices and strategies
(changed to show the main products under discussion)
To backup the important PC files to a server (this can be .pdf or labels or various documents and database files) from a number of PCs, the first choice is whether the backup should be centralized or done PC-by-PC, initiated locally. Both have advantages, I am not sure if there is a free strong network backup program, and the following are the main choices so far for PC backup.
==================================================================
Cobian Backup Version 9 Amanita
http://www.educ.umu....ian/cobianbackup.htmForum
http://www.cobiansoft.com/forum/SyncBack Freeware V3.2.19.0 -
http://www.2brightsp...re/freeware-hub.htmlFBackup
http://www.fbackup.com/ Forum
http://www.fbackup.com/forum/Comodo Backup -
http://forums.comodo...776.0.html;msg280048Cobian and Comodo are designed as full products, SyncBack and FBackup (from Backup4all folks) are the Lite versions. Personally I avoid Comodo for other reasons, however the backup product deserves comparison here.
==================================================================
The Microsoft tool for .pst files may come to play
http://office.micros.../HA010875321033.aspxOr, you may decide to go to a commercial program on the .pst.
===================================================================
Certain issues come to play, such as how to schedule a backup when the puter is on and the files are available. (Especially with PST.)
So the first question is this, between the four products above, how do we make the decision, what are the strengths and weaknesses of each. We can combine our use with various reviews and comments on the .net. Personally I am on the cusp of choosing one, yet which one ? ? ?
Let's look at a number of issues on backup and see if any of the four stand out. And how to handle those 10 Gigabyte PSTs.
Also let's decide on a strategy, how do you decide what to backup, do you use inclusions of file types, or exclusion ? Folks can be running their own specialty programs for sales management or label making or scanning or this or that so how do you decide what to backup and what to ignore ? (Images are not my consideration, here, we want to hold on to data and config type files for hand restore.)
Here are some issues to consider.
RELIABILITY
SUPPORT including FORUMS
EASE-OF-USE
FLEXIBILITY IN CREATING BACKUP SETS
TARGET DATA TYPES (same as source, .zip, proprietary)
SCHEDULING
FULL RESAVE vs. INCREMENTAL & DIFFERENTIAL
I noticed on the Cobian boards an issue was raised that when the source "deletes" a file Cobian does not want to delete it at the target, and issues like that are :
ARCHITECTURAL DESIGN
Probably there are a dozen more. Bring your screenshots and experiences, let the battle begin, which one will be the Iron Backup ?
Are any of these 4 far more capable or incompetent than the others ?
Shalom,
Steven