> -----Original Message-----
> From: writelog-bounces@contesting.com
> [mailto:writelog-bounces@contesting.com]On Behalf Of Bob McCormick W1QA
> Sent: Wednesday, January 22, 2003 10:23 AM
> To: WriteLog@contesting.com
> Subject: RE: [WriteLog] Converting a disk to NTFS
>
>
> Regarding Steve KB3MM's comments:
>
> Indeed the actual I/O of the application program
> (like WriteLog) is NOT protected by the NTFS journal ...
> only the disk's file system is (as you pointed out).
However, if you run GOBACK, then the application changes are protected , at
least most of them and much more so than the NTFS which does nothing with
them. If you have the full version you can go back in time to recover the
old writes and it also save the files that were overwritten during the
revert operation so you can recover the new things too.
It is NOT perfect but it is very good.
>
> Still ... I think you'll find that if you crash or
> power fail an NTFS based system (versus a FAT based one),
> you're a lot less likely to find your data files are
> corrupted by inaccurate update of the file's sectors
> (clusters).
>
> If a disk sector becomes bad (ugh!) ... and your data
> is on it - doesn't really matter what file system you
> are running. (A RAID based logging computer?! <grin>)
>
> Still ... the NTFS file system maintains more redundant
> information in its structures. Disk errors in critical
> places in the FAT system are usually fatal where NTFS can
> often recover.
>
> Maybe someday ... an SQL server based version of WriteLog?
> For those important multi-op's and DXpeditions!
>
> Bob W1QA
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
>
|