NTFRS will not start replication since 8hours :-(((

[Alex]

hi

here is what i've done

1. share dir INETPUB on SERVER1 (all data inside - 15GB - 600.000 files)
2. share dir INETPUB on SERVER2 (new directory - newly installed server)
3. created the domain DFS tree and added both servers as replicate
4. activated replication on SERVER1 and make it (Master)
5. activated replication on SERVER2, OK
6. created a DWORD Value "Ntfs Journal Size in MB" of about "1024"
7. changed the "Staging Space Limit in KB" to "2048000"
8. restarted NTFRS Service on both machine
9. deleted the replication and recreated it, while the growing ntfrs.jdb
stops growing for about hours and it looks like nothing is in process...

10. now i'm waiting since 8 hours... and now the ntfrs.jdb is about
210MB and growing but NO file is synced!!!


what is wrong or how long does it take? and why is it stopping if i
restart the ntfrs service?


Greetings
Alex

[Richard Chinn [MSFT]]

Check the event log and see if there are any suspicious events. If the FRS
is showing activity, it sounds like it's working. It may be going through
the local file system and adding files to its database. This could take a
while on a 15 GB replica set.

One question: what do you mean when you say "deleted the replication and
recreated it?" Are you saying you went into the DFS GUI, deleted your
replica sets, then recreated them?

Also, install Ultrasound. To get Ultrasound, go to
http://www.microsoft.com/frs. Follow the link for "FRS Troubleshooting and
Monitoring." You should see the link for Ultrasound there. Note you will
need to follow the in the Ultrasound help file (FRS Monitoring Help File) to
install Ultrasound - it requires MSDE (free) or a SQL database.

We have an upcoming chat on Ultrasound if you're interested. Here are the
details.

February 4, 2004
11:00 A.M. - 12:00 P.M. Pacific time
2:00 - 3:00 P.M. Eastern time
19:00 - 20:00 GMT/BST



TechNet:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itcommunity/chats/default.asp

MS Communities: http://www.microsoft.com/communities/chats/default.mspx


--Richard

Please post FRS related questions to microsoft.public.windows.server.dfs_frs
and prefix the subject line with "FRS:" to make it easier to spot. Note
that FRS is used to replicate SYSVOL on domain controllers and DFS root and
link targets.

For additional FRS resources, please visit http://www.microsoft.com/frs.

This posting is provided "AS IS" with no warranties, and confers no rights.

Post by Alex
hi
here is what i've done
1. share dir INETPUB on SERVER1 (all data inside - 15GB - 600.000 files)
2. share dir INETPUB on SERVER2 (new directory - newly installed server)
3. created the domain DFS tree and added both servers as replicate
4. activated replication on SERVER1 and make it (Master)
5. activated replication on SERVER2, OK
6. created a DWORD Value "Ntfs Journal Size in MB" of about "1024"
7. changed the "Staging Space Limit in KB" to "2048000"
8. restarted NTFRS Service on both machine
9. deleted the replication and recreated it, while the growing ntfrs.jdb
stops growing for about hours and it looks like nothing is in process...
10. now i'm waiting since 8 hours... and now the ntfrs.jdb is about
210MB and growing but NO file is synced!!!
what is wrong or how long does it take? and why is it stopping if i
restart the ntfrs service?
Greetings
Alex

[Alex]

hi

Post by Richard Chinn [MSFT]
Check the event log and see if there are any suspicious events. If the FRS

no errors. no warnings.

Post by Richard Chinn [MSFT]
is showing activity, it sounds like it's working. It may be going through
the local file system and adding files to its database. This could take a
while on a 15 GB replica set.

1 Week??? it ran since 2 days... how ig will the ntfrs.jdb db per
100.000 files? 128MB like MFT? what does MS think about a 5 day waiting
job for replication starts... if this is normal there MUST be a faster
way! a simple copy of this data takes about 6-8hours with 100Mbit and
10K SCSI disks in RAID5. FRS takes about 8 hours for building a
ntfrs.jdb of 100MB without any file replicated... and i don't know where
this will ends up.

Post by Richard Chinn [MSFT]
One question: what do you mean when you say "deleted the replication and
recreated it?" Are you saying you went into the DFS GUI, deleted your
replica sets, then recreated them?

yes. recreated about the gui. today i stopped the ntfrs and cleanup the
jet dir and restartet all. i think this many restarts will blow up the
db and my diskspace isn't possible enough...

Post by Richard Chinn [MSFT]
Also, install Ultrasound. To get Ultrasound, go to
http://www.microsoft.com/frs. Follow the link for "FRS Troubleshooting and
Monitoring." You should see the link for Ultrasound there. Note you will
need to follow the in the Ultrasound help file (FRS Monitoring Help File) to
install Ultrasound - it requires MSDE (free) or a SQL database.

i read about - but i don't like to install MSDE on my webservers!
additional this tools looks like total overkill. i don't like to install
a database server for event-logging my FRS. finaly i don't have disk
space for such things. Is it possible to use existing SQL2K EE Server?


Alex

[Richard Chinn [MSFT]]

For a new replica set, FRS will not replicate any files to partners until it
completes its primary load. This means the server must iterate through the
entire replica set on the local machine and build the FRS database. If you
have a lot of folders and files, this can take a very, very long time.

If you stop FRS in the middle of this process, it needs to start back up and
continue its work. It will effectively start from the beginning and check
that its database that's been generated so far (from the previous run) is in
okay before it'll continue building.

Regarding Ultrasound, you only need to deploy a single WMI provider to the
monitored FRS machine. The SQL database and other Ultrasound components can
reside on some other computer, even a desktop machine if you like. You can
use an existing SQL instance for the Ultrasound DB. Simply point to it in
the Ultrasound setup.

But until your replica is up and running, it won't be of much help to you.

--Richard

Please post FRS related questions to microsoft.public.windows.server.dfs_frs
and prefix the subject line with "FRS:" to make it easier to spot. Note
that FRS is used to replicate SYSVOL on domain controllers and DFS root and
link targets.

For additional FRS resources, please visit http://www.microsoft.com/frs.

This posting is provided "AS IS" with no warranties, and confers no rights.

Post by Alex
hi
here is what i've done
1. share dir INETPUB on SERVER1 (all data inside - 15GB - 600.000 files)
2. share dir INETPUB on SERVER2 (new directory - newly installed server)
3. created the domain DFS tree and added both servers as replicate
4. activated replication on SERVER1 and make it (Master)
5. activated replication on SERVER2, OK
6. created a DWORD Value "Ntfs Journal Size in MB" of about "1024"
7. changed the "Staging Space Limit in KB" to "2048000"
8. restarted NTFRS Service on both machine
9. deleted the replication and recreated it, while the growing ntfrs.jdb
stops growing for about hours and it looks like nothing is in process...
10. now i'm waiting since 8 hours... and now the ntfrs.jdb is about
210MB and growing but NO file is synced!!!
what is wrong or how long does it take? and why is it stopping if i
restart the ntfrs service?
Greetings
Alex