I wouldn't expect it to be excessive, and you can always set your site replication schedules to coincide with low usage times.
Pull up perfmon on one of your DCs, and watch the "NTDS\DRA Inbound Bytes..." counters for a day or so. The "DRA Inbound Bytes Not Compressed (Within Site)" counters will give you a worst case scenario, as intra-site replication traffic won't be compressed but inter-site replication traffic will. Hunter -----Original Message----- From: Network Administrator [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 03, 2004 8:17 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] DC Replication Bandwidth Issue I have an upcoming project that I'd like to seek some input on. I'm looking at building a third domain controller for a tiny domain of about 250 users. Currently, we have two domain controllers at a central location where approximately 85% of our users reside. The rest of our users are at branch locations connected by 128k links that aren't horribly taxed. I'd like to place the third domain controller at one of the branch locations as a "disaster recovery" box that will be capable of processing domain authentications and other DC-related functions in case our central locations is hit by some catastrophe. Since this is a single site, single domain, single forest topology, I don't necessarily need this box to do anything other than replicate domain information and critical services (DNS, WINS, etc.) on a semi-regular basis. How much bandwidth do you guys think this box will take? Again, it is a tiny domain with approximately 250 users and 225 workstations. It won't hold any FSMO roles, I'll just seize them from the console at the branch location if Joe's volcano makes it all the way over to Kalamazoo. -James R. Rogers List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
