Thanks for your help Jill.
Both servers run W2k3 SP1, so target priority sounds ideal.
Database is implemented in Access, of which I am fairly ignorant - sorry -
but I will explain as best I can.
At logon, workstations map I: to a conventional share on SERVER1, and copy
rules.mdb (form & table defs, procedures) to local drive. When they wish to
examine any records, these are filtered from data.mdb which resides on
If they edit, a lock is set in the .ldb file on SERVER1 until the relevant
record is returned to SERVER1.
For such a small network as ours, we don't need SERVER2 for load sharing.
What I am trying to achieve is a self-activating hot-pluggable almost
up-to-date backup in case SERVER1 goes down while I am relaxing by the
Mediterranean! So I will be happy if replication only happens lunch-time and
DFS technology appeals because if procedure writers and data authors have
rigorously used I:\ and not \\SERVER1\SHARE\, all I have to do is set up DFS,
then modify the mapping of I:\ in the logon script. If replication can work
for me, it will save me implementing scheduled copying from SERVER1 to
Post by Jill Zoeller [MSFT]
When you say you want to make the database more robust, what kind of
database are you talking about? Databases are tricky to replicate because
FRS and DFSR Replication (new in R2) only replicate files after they are
closed, and database files are typically held open.
Assuming you can work around this, what we usually recommend is 2-way
replication between the two members. As far as the namespace goes, you have
If you aren't using W2K3 SP1 or R2, you can enable/disable referrals for
link targets. For example, keep Server2's referral disabled unless Server1
goes down. THen you can enable Server2's referral.
If you're using W2K3 SP1 or R2 on your root servers, you can use a new
features called target priority, which allows you to (among other choices)
specify a target as "always first" or "always last." You could set Server2's
referral as "always last" and clients will only be referred there if Server1
You don't mention whether you are using R2 or not. If you are, we highly
recommend DFS Replication over FRS.
You can find more details at www.microsoft.com/dfs.
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
Post by Newell White
Having at last added a 2nd DC to our domain to get a fault tolerant network
(25 LAN workstations, 10 VPN clients), I now want to make our database more
At present it is a single share of folders on the drive of SERVER1.
If I make it a domain root DFS, and set up replication with a copy of the
folders on SERVER2, can I force DFS to point all referrals to SERVER1 if that
is up, otherwise to SERVER2?
This way I achieve 1-way replication until I restart SERVER1, which can be
done after business hours.