J;
Brian is 100% correct, if you try to use DFS/FRS for this,
your're screwed.
Think of it this way: FRS is "the Notepad of file
mirroring". If all you need is minimal functionallity,
then Notepad (or FRS) works. If you need a real tool,
break out the credit card...
*Real* file mirroring will cost anywhere from $300 to
$1500 per server (and all vendors will assume you need a
minimum of two licenses). There are two major attributes
of file mirroring that can combine thusly:
synchronous | asynchronous
blocks | blocks
-----------------+--------------------
sychronous | asynchronous
files | files
In synchronous mirroring, the application is not told the
write is successful until *after* the write has been
successfully completed on the mirror. In asynchronous
mirroring, the application is told the write is successful
immediately then the mirror utility becomes responsible
for the welfare of the mirrored write. (This can be a
major issue with mirroring over a slow link -vs- data
reliability. However if your backup machine goes down a
synchronous mirror can hang.)
In a file oriented mirror, the data is mirrored on a file-
by-file basis and is typically done when the file write is
closed. In a block oriented mirror, the data is mirrored
as each write process is closed, even though the file
remains open by the application. (Most apps can use file
mirroring, but databases (including MS Exchange) *require*
block mirroring. Block mirroring can create more traffic
of smaller packets.)
Some mirror utilities only do master/slave, and some can
do master/slave or master/master. Some require both
mirrors be on simular machines (both servers or both
clients) but some will backup server files to a client
machine. Some mirror utilities will even bring up your
backup machine as a replacement if your main machine goes
down.
Well, pick up some keywords and try Googling this, there
are lots of vendors. I have the stong feeling you need to
spend some money. Microsoft's DFS/FRS will *not* do what
you seem to want to do.
Good luck.
ScottyDM
-----Original Message-----
If two users are concurrently accessing the same replicated file on two
different DFS targets (physical machines), there is no notification process.
Both users are able to modify them at the same time; file replication will
result in only one modificaion being saved, typically the last writer.
--
Brian [MSFT]
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights. Please do not send e-mail directly to this alias. This alias is
for newsgroup purposes only.
If 2 users try to access the same file in a Dfs share will
a notification be sent to the second user that the first
user is editing the file? How do you ensure that 2 users
can not edit the same file at the same time?
Windows 2000 SP3 servers
Thanks,
J. Mauch
(e-mail address removed)
.
