The source server is the Reference time server for our whole tree, and
after checking, it is in sync with the target.  We'd be having a lot
more problems anyway with nds sync if they were that far out of whack.
There are files on the target with a 7/25 date, that still haven't been
overwritten by files on the source with a 8/11 date.


>>> Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG 8/14/2006 3:18 PM >>>
-----"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote: -----

>I've got a poor man's replication job setup to, twice a day, backup a
>folder on one server and restore it to a different server (both
>netware).  I realize this isn't real replication (deletes from the
>source don't happen on the target), but it's good enough for now.
>
>The problem I'm having is that the restore job is failing to
>overwrite
>target files when the source is newer.  I get a ANS1946W message in
>dsmerror.log , and it says the file was skipped because it already
>exists on target. Which is true, but the newer version from the
>source
>should've overwrote it. I've listed my restore command line
>below...
>
>restore -fromnode=np-fa1 -replace=all -ifnewer -subdir=yes
>"np-fa1/Vol1:\Data\Share\Epic\*" "ne-fa1/vol1:\Data\Share\"
Are thre clocks on the two Netware systems synchronized?

Confidentiality Notice follows:

The information in this message (and the documents attached to it, if any)
is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this message by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this message in
error, please delete all electronic copies of this message (and the
documents attached to it, if any), destroy any hard copies you may have
created and notify me immediately by replying to this email. Thank you.