| Author |
Message |
Wayne
Guest
|
 Posted:
Mon Feb 07, 2005 8:38 pm Post subject:
FRS and large file counts |
|
|
We currently have FRS set up, we are using it to keep tow FTP sites in sync.
We use one FTP server primarily, and the other as a back up, IIS is disabled
on the one currently not in use. Our FTP site is access by our customers,
they upload mainly creating a new file for each piece of data that they want
to send us. The files are rarely ever over 1k in size. However, we have
thousands upon thousands of files. the last time we archived the files for a
four month period it took 9 CD's to hold them all, and business is only
increasing, I shudder to think how many CD's the next archive is going to
take.
Currently we are having an issue with Directories getting renamed to the
_NTFRS_XXXXXXX names, indicating a problem (posted a separate thread about
this). We are also having another issue, which I wish I had more details
about at this time but currently don't.
I'm not looking for answers to the above issues, I'm just wondering if
anyone has an opinion on using FRS for the above purpose described. Is what
we are doing outside the capacity for FRS to handle? could the sheer number
of files cause issues with the FRS setup and keeping them in sync?
--
Thanks
Wayne Sepega
Jacksonville, Fl
"When a man sits with a pretty girl for an hour, it seems like a minute. But
let him sit on a hot stove for a minute and it's longer than any hour.
That's relativity." - Albert Einstein |
|
| Back to top |
|
 |
Jimmy Andersson [MVP]
Guest
|
| Posted:
Mon Feb 07, 2005 10:12 pm Post subject:
Re: FRS and large file counts |
|
|
Have you considered alternatives like Double-Take from
http://www.nsisoftware.com/pro/doubletake/ or clustering?
I've used Double-Take numerous times and I'm really happy with the results.
Regards,
/Jimmy
--
Jimmy Andersson, Q Advice AB
Microsoft MVP - Directory Services
---------- www.qadvice.com ----------
"Wayne" <MeNotYou@community.nospam> wrote in message
news:uIBNtKSDFHA.3108@TK2MSFTNGP10.phx.gbl...
| Quote: | We currently have FRS set up, we are using it to keep tow FTP sites in
sync.
We use one FTP server primarily, and the other as a back up, IIS is
disabled
on the one currently not in use. Our FTP site is access by our customers,
they upload mainly creating a new file for each piece of data that they
want
to send us. The files are rarely ever over 1k in size. However, we have
thousands upon thousands of files. the last time we archived the files for
a
four month period it took 9 CD's to hold them all, and business is only
increasing, I shudder to think how many CD's the next archive is going to
take.
Currently we are having an issue with Directories getting renamed to the
_NTFRS_XXXXXXX names, indicating a problem (posted a separate thread about
this). We are also having another issue, which I wish I had more details
about at this time but currently don't.
I'm not looking for answers to the above issues, I'm just wondering if
anyone has an opinion on using FRS for the above purpose described. Is
what
we are doing outside the capacity for FRS to handle? could the sheer
number
of files cause issues with the FRS setup and keeping them in sync?
--
Thanks
Wayne Sepega
Jacksonville, Fl
"When a man sits with a pretty girl for an hour, it seems like a minute.
But
let him sit on a hot stove for a minute and it's longer than any hour.
That's relativity." - Albert Einstein
|
|
|
| Back to top |
|
|
Richard Chinn [MSFT]
Guest
|
| Posted:
Tue Feb 08, 2005 6:47 am Post subject:
Re: FRS and large file counts |
|
|
FRS does not do well when the total number of files *and* folders gets
high. In our case, "high" is around 500,000 files and folders in a
replica set. It won't necessarily help to spread the files out among
replica sets because there is a single FRS service running on a
machine to handle all the replica sets.
Often FRS will function well and be able to grow far beyond 500,000
files and folders, but you will likely run into problems with disaster
recovery. It's possible for FRS to grow to a point where it cannot
recover should anything go wrong.
It is always important to have good monitoring in place when using
FRS. Ultrasound can help with this.
The following articles may be of interest.
Configuration and operational recommendations for the File Replication
sservice in Windows Server 2003 and Windows 2000 Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;840675
FRS Technical Reference
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techref/en-us/W2K3TR_frs_intro.asp
FRS Monitoring Help File (has an introductory section that discusses
scenarios for FRS)
http://download.microsoft.com/download/3/2/e/32e40b0d-fbba-44ea-8d06-326732b04f0c/Ultrasound.chm
Generic FRS Information (links to the above and more)
http://www.microsoft.com/frs
--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.
On Mon, 7 Feb 2005 09:38:21 -0500, "Wayne" <MeNotYou@community.nospam>
wrote:
| Quote: | We currently have FRS set up, we are using it to keep tow FTP sites in sync.
We use one FTP server primarily, and the other as a back up, IIS is disabled
on the one currently not in use. Our FTP site is access by our customers,
they upload mainly creating a new file for each piece of data that they want
to send us. The files are rarely ever over 1k in size. However, we have
thousands upon thousands of files. the last time we archived the files for a
four month period it took 9 CD's to hold them all, and business is only
increasing, I shudder to think how many CD's the next archive is going to
take.
Currently we are having an issue with Directories getting renamed to the
_NTFRS_XXXXXXX names, indicating a problem (posted a separate thread about
this). We are also having another issue, which I wish I had more details
about at this time but currently don't.
I'm not looking for answers to the above issues, I'm just wondering if
anyone has an opinion on using FRS for the above purpose described. Is what
we are doing outside the capacity for FRS to handle? could the sheer number
of files cause issues with the FRS setup and keeping them in sync? |
|
|
| Back to top |
|
|
Wayne
Guest
|
| Posted:
Thu Feb 10, 2005 6:22 pm Post subject:
Re: FRS and large file counts |
|
|
Well I was asked Tuesday to get a file count off of our FRS server, at that
time we had 2.5 million files in the FTPRoot directory. Very busy FTP
Server. Out of curiosity you wrote below:
"In our case, "high" is around 500,000 files and folders in a replica set."
who is OUR?
Wayne
"Richard Chinn [MSFT]" <rchinn@online.microsoft.com> wrote in message
news:f5hg01dd98brqij012fqesc5ef2afg4qan@4ax.com...
| Quote: | FRS does not do well when the total number of files *and* folders gets
high. In our case, "high" is around 500,000 files and folders in a
replica set. It won't necessarily help to spread the files out among
replica sets because there is a single FRS service running on a
machine to handle all the replica sets.
Often FRS will function well and be able to grow far beyond 500,000
files and folders, but you will likely run into problems with disaster
recovery. It's possible for FRS to grow to a point where it cannot
recover should anything go wrong.
It is always important to have good monitoring in place when using
FRS. Ultrasound can help with this.
The following articles may be of interest.
Configuration and operational recommendations for the File Replication
sservice in Windows Server 2003 and Windows 2000 Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;840675
FRS Technical Reference
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techref/en-us/W2K3TR_frs_intro.asp
FRS Monitoring Help File (has an introductory section that discusses
scenarios for FRS)
http://download.microsoft.com/download/3/2/e/32e40b0d-fbba-44ea-8d06-326732b04f0c/Ultrasound.chm
Generic FRS Information (links to the above and more)
http://www.microsoft.com/frs
--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.
On Mon, 7 Feb 2005 09:38:21 -0500, "Wayne" <MeNotYou@community.nospam
wrote:
We currently have FRS set up, we are using it to keep tow FTP sites in
sync.
We use one FTP server primarily, and the other as a back up, IIS is
disabled
on the one currently not in use. Our FTP site is access by our customers,
they upload mainly creating a new file for each piece of data that they
want
to send us. The files are rarely ever over 1k in size. However, we have
thousands upon thousands of files. the last time we archived the files
for a
four month period it took 9 CD's to hold them all, and business is only
increasing, I shudder to think how many CD's the next archive is going to
take.
Currently we are having an issue with Directories getting renamed to the
_NTFRS_XXXXXXX names, indicating a problem (posted a separate thread
about
this). We are also having another issue, which I wish I had more details
about at this time but currently don't.
I'm not looking for answers to the above issues, I'm just wondering if
anyone has an opinion on using FRS for the above purpose described. Is
what
we are doing outside the capacity for FRS to handle? could the sheer
number
of files cause issues with the FRS setup and keeping them in sync?
|
|
|
| Back to top |
|
|
Richard Chinn [MSFT]
Guest
|
| Posted:
Fri Feb 11, 2005 6:47 am Post subject:
Re: FRS and large file counts |
|
|
In this case, "our" means Microsoft recommended limits for FRS.
2.5 million files is likely too much for FRS, especially with your
high change traffic scenario.
As an alternative to FRS, you might want to try experimenting with
Robocopy. I haven't had much experience with it, but I know that the
tool is popular. It's available in the Windows Resource Kit.
http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en
--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.
On Thu, 10 Feb 2005 07:22:38 -0500, "Wayne"
<MeNotYou@community.nospam> wrote:
| Quote: | Well I was asked Tuesday to get a file count off of our FRS server, at that
time we had 2.5 million files in the FTPRoot directory. Very busy FTP
Server. Out of curiosity you wrote below:
"In our case, "high" is around 500,000 files and folders in a replica set."
who is OUR?
Wayne
"Richard Chinn [MSFT]" <rchinn@online.microsoft.com> wrote in message
news:f5hg01dd98brqij012fqesc5ef2afg4qan@4ax.com...
FRS does not do well when the total number of files *and* folders gets
high. In our case, "high" is around 500,000 files and folders in a
replica set. It won't necessarily help to spread the files out among
replica sets because there is a single FRS service running on a
machine to handle all the replica sets.
Often FRS will function well and be able to grow far beyond 500,000
files and folders, but you will likely run into problems with disaster
recovery. It's possible for FRS to grow to a point where it cannot
recover should anything go wrong.
It is always important to have good monitoring in place when using
FRS. Ultrasound can help with this.
The following articles may be of interest.
Configuration and operational recommendations for the File Replication
sservice in Windows Server 2003 and Windows 2000 Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;840675
FRS Technical Reference
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techref/en-us/W2K3TR_frs_intro.asp
FRS Monitoring Help File (has an introductory section that discusses
scenarios for FRS)
http://download.microsoft.com/download/3/2/e/32e40b0d-fbba-44ea-8d06-326732b04f0c/Ultrasound.chm
Generic FRS Information (links to the above and more)
http://www.microsoft.com/frs
--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.
On Mon, 7 Feb 2005 09:38:21 -0500, "Wayne" <MeNotYou@community.nospam
wrote:
We currently have FRS set up, we are using it to keep tow FTP sites in
sync.
We use one FTP server primarily, and the other as a back up, IIS is
disabled
on the one currently not in use. Our FTP site is access by our customers,
they upload mainly creating a new file for each piece of data that they
want
to send us. The files are rarely ever over 1k in size. However, we have
thousands upon thousands of files. the last time we archived the files
for a
four month period it took 9 CD's to hold them all, and business is only
increasing, I shudder to think how many CD's the next archive is going to
take.
Currently we are having an issue with Directories getting renamed to the
_NTFRS_XXXXXXX names, indicating a problem (posted a separate thread
about
this). We are also having another issue, which I wish I had more details
about at this time but currently don't.
I'm not looking for answers to the above issues, I'm just wondering if
anyone has an opinion on using FRS for the above purpose described. Is
what
we are doing outside the capacity for FRS to handle? could the sheer
number
of files cause issues with the FRS setup and keeping them in sync?
|
|
|
| Back to top |
|
|
Wayne
Guest
|
| Posted:
Fri Feb 11, 2005 10:07 pm Post subject:
Re: FRS and large file counts |
|
|
I've looked through the docs for FRS but didn't see a recommended number of
files, I could just not be looking in the right place. Do you happen to have
a link directly to where Microsoft suggests this? I'd like to pass it on to
management.
"Richard Chinn [MSFT]" <rchinn@online.microsoft.com> wrote in message
news:tn5o01dsi7q2765qkppq0ffh893ckc2mv5@4ax.com...
| Quote: | In this case, "our" means Microsoft recommended limits for FRS.
2.5 million files is likely too much for FRS, especially with your
high change traffic scenario.
As an alternative to FRS, you might want to try experimenting with
Robocopy. I haven't had much experience with it, but I know that the
tool is popular. It's available in the Windows Resource Kit.
http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en
--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.
On Thu, 10 Feb 2005 07:22:38 -0500, "Wayne"
MeNotYou@community.nospam> wrote:
Well I was asked Tuesday to get a file count off of our FRS server, at
that
time we had 2.5 million files in the FTPRoot directory. Very busy FTP
Server. Out of curiosity you wrote below:
"In our case, "high" is around 500,000 files and folders in a replica
set."
who is OUR?
Wayne
"Richard Chinn [MSFT]" <rchinn@online.microsoft.com> wrote in message
news:f5hg01dd98brqij012fqesc5ef2afg4qan@4ax.com...
FRS does not do well when the total number of files *and* folders gets
high. In our case, "high" is around 500,000 files and folders in a
replica set. It won't necessarily help to spread the files out among
replica sets because there is a single FRS service running on a
machine to handle all the replica sets.
Often FRS will function well and be able to grow far beyond 500,000
files and folders, but you will likely run into problems with disaster
recovery. It's possible for FRS to grow to a point where it cannot
recover should anything go wrong.
It is always important to have good monitoring in place when using
FRS. Ultrasound can help with this.
The following articles may be of interest.
Configuration and operational recommendations for the File Replication
sservice in Windows Server 2003 and Windows 2000 Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;840675
FRS Technical Reference
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techr
ef/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techr |
ef/en-us/W2K3TR_frs_intro.asp
| Quote: |
FRS Monitoring Help File (has an introductory section that discusses
scenarios for FRS)
http://download.microsoft.com/download/3/2/e/32e40b0d-fbba-44ea-8d06-326732
b04f0c/Ultrasound.chm
Generic FRS Information (links to the above and more)
http://www.microsoft.com/frs
--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.
On Mon, 7 Feb 2005 09:38:21 -0500, "Wayne" <MeNotYou@community.nospam
wrote:
We currently have FRS set up, we are using it to keep tow FTP sites in
sync.
We use one FTP server primarily, and the other as a back up, IIS is
disabled
on the one currently not in use. Our FTP site is access by our
customers,
they upload mainly creating a new file for each piece of data that
they
want
to send us. The files are rarely ever over 1k in size. However, we
have
thousands upon thousands of files. the last time we archived the files
for a
four month period it took 9 CD's to hold them all, and business is
only
increasing, I shudder to think how many CD's the next archive is going
to
take.
Currently we are having an issue with Directories getting renamed to
the
_NTFRS_XXXXXXX names, indicating a problem (posted a separate thread
about
this). We are also having another issue, which I wish I had more
details
about at this time but currently don't.
I'm not looking for answers to the above issues, I'm just wondering if
anyone has an opinion on using FRS for the above purpose described. Is
what
we are doing outside the capacity for FRS to handle? could the sheer
number
of files cause issues with the FRS setup and keeping them in sync?
|
|
|
| Back to top |
|
|
Richard Chinn [MSFT]
Guest
|
| Posted:
Thu Feb 17, 2005 2:06 am Post subject:
Re: FRS and large file counts |
|
|
This KB has the relevant FRS scalability numbers and limits
information.
http://support.microsoft.com/default.aspx?scid=kb;en-us;840675
--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.
On Fri, 11 Feb 2005 11:07:57 -0500, "Wayne"
<MeNotYou@community.nospam> wrote:
| Quote: | I've looked through the docs for FRS but didn't see a recommended number of
files, I could just not be looking in the right place. Do you happen to have
a link directly to where Microsoft suggests this? I'd like to pass it on to
management.
"Richard Chinn [MSFT]" <rchinn@online.microsoft.com> wrote in message
news:tn5o01dsi7q2765qkppq0ffh893ckc2mv5@4ax.com...
In this case, "our" means Microsoft recommended limits for FRS.
2.5 million files is likely too much for FRS, especially with your
high change traffic scenario.
As an alternative to FRS, you might want to try experimenting with
Robocopy. I haven't had much experience with it, but I know that the
tool is popular. It's available in the Windows Resource Kit.
http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en
--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.
On Thu, 10 Feb 2005 07:22:38 -0500, "Wayne"
MeNotYou@community.nospam> wrote:
Well I was asked Tuesday to get a file count off of our FRS server, at
that
time we had 2.5 million files in the FTPRoot directory. Very busy FTP
Server. Out of curiosity you wrote below:
"In our case, "high" is around 500,000 files and folders in a replica
set."
who is OUR?
Wayne
"Richard Chinn [MSFT]" <rchinn@online.microsoft.com> wrote in message
news:f5hg01dd98brqij012fqesc5ef2afg4qan@4ax.com...
FRS does not do well when the total number of files *and* folders gets
high. In our case, "high" is around 500,000 files and folders in a
replica set. It won't necessarily help to spread the files out among
replica sets because there is a single FRS service running on a
machine to handle all the replica sets.
Often FRS will function well and be able to grow far beyond 500,000
files and folders, but you will likely run into problems with disaster
recovery. It's possible for FRS to grow to a point where it cannot
recover should anything go wrong.
It is always important to have good monitoring in place when using
FRS. Ultrasound can help with this.
The following articles may be of interest.
Configuration and operational recommendations for the File Replication
sservice in Windows Server 2003 and Windows 2000 Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;840675
FRS Technical Reference
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techr
ef/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techr
ef/en-us/W2K3TR_frs_intro.asp
FRS Monitoring Help File (has an introductory section that discusses
scenarios for FRS)
http://download.microsoft.com/download/3/2/e/32e40b0d-fbba-44ea-8d06-326732
b04f0c/Ultrasound.chm
Generic FRS Information (links to the above and more)
http://www.microsoft.com/frs
--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.
On Mon, 7 Feb 2005 09:38:21 -0500, "Wayne" <MeNotYou@community.nospam
wrote:
We currently have FRS set up, we are using it to keep tow FTP sites in
sync.
We use one FTP server primarily, and the other as a back up, IIS is
disabled
on the one currently not in use. Our FTP site is access by our
customers,
they upload mainly creating a new file for each piece of data that
they
want
to send us. The files are rarely ever over 1k in size. However, we
have
thousands upon thousands of files. the last time we archived the files
for a
four month period it took 9 CD's to hold them all, and business is
only
increasing, I shudder to think how many CD's the next archive is going
to
take.
Currently we are having an issue with Directories getting renamed to
the
_NTFRS_XXXXXXX names, indicating a problem (posted a separate thread
about
this). We are also having another issue, which I wish I had more
details
about at this time but currently don't.
I'm not looking for answers to the above issues, I'm just wondering if
anyone has an opinion on using FRS for the above purpose described. Is
what
we are doing outside the capacity for FRS to handle? could the sheer
number
of files cause issues with the FRS setup and keeping them in sync?
|
|
|
| Back to top |
|
|
Wayne
Guest
|
| Posted:
Thu Feb 17, 2005 6:47 pm Post subject:
Re: FRS and large file counts |
|
|
Thank you very much for your help on this. Due to the information you have
provided we are working on a project now to archive the data on the machine
as quickly as we can, which should help our situation.
--
Thanks
Wayne Sepega
Jacksonville, Fl
"When a man sits with a pretty girl for an hour, it seems like a minute. But
let him sit on a hot stove for a minute and it's longer than any hour.
That's relativity." - Albert Einstein
"Richard Chinn [MSFT]" <rchinn@online.microsoft.com> wrote in message
news:ss97115ngsqli2plqduvo8f1e4htb09m9o@4ax.com...
| Quote: | This KB has the relevant FRS scalability numbers and limits
information.
http://support.microsoft.com/default.aspx?scid=kb;en-us;840675
--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.
On Fri, 11 Feb 2005 11:07:57 -0500, "Wayne"
MeNotYou@community.nospam> wrote:
I've looked through the docs for FRS but didn't see a recommended number
of
files, I could just not be looking in the right place. Do you happen to
have
a link directly to where Microsoft suggests this? I'd like to pass it on
to
management.
"Richard Chinn [MSFT]" <rchinn@online.microsoft.com> wrote in message
news:tn5o01dsi7q2765qkppq0ffh893ckc2mv5@4ax.com...
In this case, "our" means Microsoft recommended limits for FRS.
2.5 million files is likely too much for FRS, especially with your
high change traffic scenario.
As an alternative to FRS, you might want to try experimenting with
Robocopy. I haven't had much experience with it, but I know that the
tool is popular. It's available in the Windows Resource Kit.
http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7
-96ee-b18c4790cffd&DisplayLang=en
--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.
On Thu, 10 Feb 2005 07:22:38 -0500, "Wayne"
MeNotYou@community.nospam> wrote:
Well I was asked Tuesday to get a file count off of our FRS server, at
that
time we had 2.5 million files in the FTPRoot directory. Very busy FTP
Server. Out of curiosity you wrote below:
"In our case, "high" is around 500,000 files and folders in a replica
set."
who is OUR?
Wayne
"Richard Chinn [MSFT]" <rchinn@online.microsoft.com> wrote in message
news:f5hg01dd98brqij012fqesc5ef2afg4qan@4ax.com...
FRS does not do well when the total number of files *and* folders
gets
high. In our case, "high" is around 500,000 files and folders in a
replica set. It won't necessarily help to spread the files out
among
replica sets because there is a single FRS service running on a
machine to handle all the replica sets.
Often FRS will function well and be able to grow far beyond 500,000
files and folders, but you will likely run into problems with
disaster
recovery. It's possible for FRS to grow to a point where it cannot
recover should anything go wrong.
It is always important to have good monitoring in place when using
FRS. Ultrasound can help with this.
The following articles may be of interest.
Configuration and operational recommendations for the File
Replication
sservice in Windows Server 2003 and Windows 2000 Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;840675
FRS Technical Reference
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/tech
r
ef/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/tech
r
ef/en-us/W2K3TR_frs_intro.asp
FRS Monitoring Help File (has an introductory section that discusses
scenarios for FRS)
http://download.microsoft.com/download/3/2/e/32e40b0d-fbba-44ea-8d06-32673
2
b04f0c/Ultrasound.chm
Generic FRS Information (links to the above and more)
http://www.microsoft.com/frs
--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.
On Mon, 7 Feb 2005 09:38:21 -0500, "Wayne"
MeNotYou@community.nospam
wrote:
We currently have FRS set up, we are using it to keep tow FTP sites
in
sync.
We use one FTP server primarily, and the other as a back up, IIS is
disabled
on the one currently not in use. Our FTP site is access by our
customers,
they upload mainly creating a new file for each piece of data that
they
want
to send us. The files are rarely ever over 1k in size. However, we
have
thousands upon thousands of files. the last time we archived the
files
for a
four month period it took 9 CD's to hold them all, and business is
only
increasing, I shudder to think how many CD's the next archive is
going
to
take.
Currently we are having an issue with Directories getting renamed
to
the
_NTFRS_XXXXXXX names, indicating a problem (posted a separate
thread
about
this). We are also having another issue, which I wish I had more
details
about at this time but currently don't.
I'm not looking for answers to the above issues, I'm just wondering
if
anyone has an opinion on using FRS for the above purpose described.
Is
what
we are doing outside the capacity for FRS to handle? could the
sheer
number
of files cause issues with the FRS setup and keeping them in sync?
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in