Using Dsync for Partition mirroring!

Ok, there is something wrong with Dsync when using the JFS file system, so I am no longer recommending Dsync.  See below:


Dsync is quick and easy to set up:

The main purpose of this program is to store the whole copy of important data
 on the spare HDD or spare partition for fast restoring in the case of the main
 media damaging. You can store the whole copy of your system bootable partition
 and in the emergency cases just select the spare disk as the bootable.

This is a text mode program, results are showed on the stdout or log file.
 It has a daemon working mode in which the data synching will be done once
 a day at the specified time.

YES, I know that the second drive is just as venerable as the first one is, but
 as the topic is backup solutions for OS/2 this is only one of them. And trust me
 when your one and only harddrive fails, you'll be begging for a backup one.

Ok, there is something wrong with Dsync when using the JFS file system, so I am no longer recommending Dsync.  See below:

Greggory Shaw

I'm trying Dsync, and it mostly works the first time I run it. But the second time, I notice that it's not skipping existing, identical files. I might as well use xcopy...

Try adding the -u option for update only.

Did you use the config_file?

 UseArchive = On|Off
 Default is Off.
 Enables the using of Archive attribute for files.
 The using of this mode raises considerably the probability of file changing
 recognizing. For example, it is impossible to recognize the changing of file
 with the hiew editor.

I'm trying Dsync, and it mostly works the first time I run it. But the second time, I notice that it's not skipping existing, identical files. I might as well use xcopy...

I have the same experience.  I want to only update files that are changed / newer.  I turned on the full debug logging 'FullLog = on" and "UseArchive = On" in the dsync.cfg file.  Additionally, I am using the -u parameter on the command line as suggested.  I seem to get the same result, no matter if I use -u or not, or UseArchive = On or Off.   The app appears to copy over the same files even if they have not changed. 

I am interpreting this from the log files where, for example, I continue to see something like the following:

25/05/2010 21:32:25 [Info]  Starting dSync for OS/2, Version 0.1.6z  (c) 2001-2003 by MaDdEd-Ii.
25/05/2010 21:32:25 [Info]  ...
25/05/2010 21:32:25 [Info]  Phase #1 : Scan SrcPath=J:\xxx.
25/05/2010 21:32:25 [Info]  Phase #1 finished, found 2 dirs, 13 files, 0 errors.
25/05/2010 21:32:25 [Info]  Phase #2 : Scan DstPath=I:\xxx and kill old files.
25/05/2010 21:32:25 [Info]  Phase #2 finished, found 2 dirs, 13 files, 0 errors, killed 0 objects.
25/05/2010 21:33:01 [Info]  Phase #3 finished, found 0 errors, 2 dirs changed, 13 files changed.

I use the -v parameter as well and watch on the screen what it is doing.  It doesn't seem to matter what options I use for the options I mentioned.  I still see the same things on the screen and in the log file.

Does anyone have any ideas in what the issue may be?  I'd like to sync from one drive to the other on a daily basis only updating the changed files using dsync.  Not being able to update only updated / changed files will most probably prevent me from using dsync.  If I can't resolve, is there another alternative program to use on eCS (v2) to do the same functionality?

Any help is most appreciated

Ok, there is something wrong with Dsync when using the JFS file system.

1) I used Dsync between two partitions formatted with HPFS and it works for me (updated files).

2) When I used Dsync between a HPFS and JFS partition, Dsync does not work.

3) HERE IS THE BIG THING, after I reformatted a JFS partition, with JFS again.   The partition would show all available free space, but all the directory and files still show up in the WPS. 

4) This has happen to me before when I did a new install on JFS partition.  The history from Firefox show up from my old system, even after a new format of JFS and new install of eCom.

5) Will no longer recommend Dsync.

6) Actually the problems looks like it has to do with JFS.

Greggory

Just a quick follow-up to my prior post to add a few details.  Both the source and destination drives were formatted with JFS file system as well on eCS v2 Silver Release