I think you're trying to compare apples and oranges. Yes, both solutions can help reduce the time it takes to perform a restore (give a specific scenario), but that's basically it. Lag sites are single snapshots based on the number of lag sites you deploy. The products you mention below are true backup solutions that you could, if you wanted to, perform hourly, daily, weekly, etc backups, all of which can be restored as needed. They also typically allow attribute level restores. So if lag sites are N dollars and the software is Y dollars it doesn't really say much. You need to evaluate your own restore requirements and budget to determine what's best. It's my opinion most customers don't need lag sites and that it's a distraction from the normal backup processes they're probably failing to properly implement. But that's just me.
_____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Almeida Pinto, Jorge de Sent: Friday, March 03, 2006 1:20 PM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] AD Lag Sites When talking about "a software solution to restore deleted objects" I know about: Netpro's RestoreADmin Quest's Recovery Manage for AD I don't know the price of both products (I guess per managed object or something like that) but I would be interested in knowing where the break even point is compared to a hardware solution. And for a hardware solution you can use: * just hardware, where you need at least 1 DC per domain in the lag site (for each day of the week that would be 7 DCs per domain) (not forgetting licensing for the server OS) * hardware combined with software (e.g. ESX/GSX or virtual server) (not forgetting licensing for the server OS and the the virtual solution) I'm very interested in hearing what folks have chosen and how much it costs and of course why that particular solution. Of course don't forget to mention the type of environment and size but let's start by pinging Rick... ping rick.kingslan.microsoft ;-) jorge _____ From: [EMAIL PROTECTED] on behalf of Tony Murray Sent: Fri 2006-03-03 19:59 To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] AD Lag Sites I think Rick Kingslan did something like this with virtual machines. I'll ping him to see if he has any comment. Tony _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Almeida Pinto, Jorge de Sent: Saturday, 4 March 2006 5:17 a.m. To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] AD Lag Sites 7 lag sites? holy sh*t! would it be much cheaper to use a solution that can undelete the deleted objects and restore (push back) the attributes? jorge _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ulf B. Simon-Weidner Sent: Friday, March 03, 2006 16:59 To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] AD Lag Sites As Jorge mentioned you do not have to follow your physical subnets for Lag-Sites. Usually you would use that as a guideline, but for lag-sites you can do a sub-subnetting. AD replication does not care about the physical structure or TCP/IP-Settings (Subnetmask, Def-Gateway) - it just cares what you have configured in the sites, subnets and what IP the DC is using. So you can in a 10.1.x.x network you could configure all servers with 10.1.x.x IP-Adresses with a Subnet-Mask of 255.255.0.0, however you keep all servers in one lagsite in the same "virtual subnet" 10.1.9.x and all production Servers in 10.1.1.x - 10.1.8.x. Remember that all have the default gateway and subnet mask for 10.1.x.x. But now you create the virtual subnets in AD, and join 10.1.1.x - 10.1.8.x to the production site, and 10.1.9.x to the lag-site. AD-Replication will do what you wanted it to do, even without the need for routing. However - and this was the main reason why I wanted to follow up on this - remember that one lag-site might not be enough. Imagine you configure your lag-site to replicate every thursday 6pm. So if someone makes an error deleting a whole OU on e.g. Tuesday, you are recognizing it on Wednesday and are able to rollback this OU (authoritative restore on the lag site, then force replication). However if someone deletes a OU on thursday, and you recognize it on friday (or even thursday 7pm) you have to restore a server from tape first, because your only lag-site has already replicated that deletion. What I prefer is creating two lag-sites, one which replicates in the middle of the week and one which replicates on the weekend. No matter when the error will be performed (even right before replication of one of the lag-sites), we always have a at least half week old copy of the AD in the one of the Lag-Site. And I've even heard from someone using seven lag-sites for every day in the week. Perhaps he's jumping into this thread later ;-) Gruesse - Sincerely, Ulf B. Simon-Weidner MVP-Book "Windows XP - Die Expertentipps": <http://tinyurl.com/44zcz> http://tinyurl.com/44zcz Weblog: <http://msmvps.org/UlfBSimonWeidner> http://msmvps.org/UlfBSimonWeidner Website: <http://www.windowsserverfaq.org/> http://www.windowsserverfaq.org Profile: <http://mvp.support.microsoft.com/profile=35E388DE-4885-4308-B489-F2F1214C81 1D> http://mvp.support.microsoft.com/profile=35E388DE-4885-4308-B489-F2F1214C811 D _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frank Abagnale Sent: Friday, March 03, 2006 4:29 PM To: Active Subject: [ActiveDir] AD Lag Sites Single Forest, Single Domain, W2K3 FFL I am thinking about setting up a lag site for DR purposes. Just for clarification purposes, would I need a separate IP subnet i.e IP subnet that isn't assigned to any other site in AD to create this? All my existing IP Subnets are assigned to existing Sites which are used for normal replication, so I am assuming my question will result in a yes. Does anyone have any recommended guides to follow thanks frank _____ Relax. Yahoo! Mail virus <http://us.rd.yahoo.com/mail_us/taglines/virusall/*http://communications.yah oo.com/features.php?page=221> scanning helps detect nasty viruses!
<<attachment: winmail.dat>>
