VPN tunnel between AD and offsite backup?
in [Windows Servers]
|
From: Ace Fekay [MVP-DS, MCT] on 21 Feb 2010 18:41 "Nippoo" <Nippoo(a)discussions.microsoft.com> wrote in message news:F3DCBF1B-0194-4060-BEFB-637206C41DE6(a)microsoft.com... > What other options do I have apart from installing Exchange on a DC? > Unless I > buy two new servers... > > Exchange 2010, by the way. I don't have any option for SCR I don't think? > > N > Sorry, I misread you are using Ex2010. Either way, Exchange should not be on a DC. Here are some options with Ex2010: You Had Me At EHLO... : Should You Virtualize Your Exchange 2007 ...Figure 2 - Possible Warm Site Disaster Recovery Configuration using Hyper-V ..... Exchange Server 2010... http://msexchangeteam.com/archive/2009/01/19/450463.aspx Ace
From: Phillip Windell on 22 Feb 2010 15:37 "Nippoo" <Nippoo(a)discussions.microsoft.com> wrote in message news:F3DCBF1B-0194-4060-BEFB-637206C41DE6(a)microsoft.com... > What other options do I have apart from installing Exchange on a DC? > Unless I > buy two new servers... You're running 2008R2!! That means you have Hyper-V! It is already there,...and it is free. You just have to buy one more Server License to cover the OS in the VM for Exchange. but then 2008R2 might already cover having *one* copy in a VM,...but you'll have to verify that. Run Exchange in a VM under Hyper-V,...so it will still be on the same "physical" box,...but will not be on the same "logical" machine as the DC. Since the DC is on the Parent Machine, and since a DC should always be already running *before* Exchange is started up or shutdown,...it should be fine. In the end your weak link would be if the hardware is not powerfull enough to run two OSs efficiently. -- Phillip Windell The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. -----------------------------------------------------
From: Russ Kaufmann on 22 Feb 2010 15:43 Three or so users? Why not go to BPOS? "Nippoo" <Nippoo(a)discussions.microsoft.com> wrote in message news:DB85A032-3E94-47D5-A18A-29AA3754039B(a)microsoft.com... > We have a small (residential) business which runs an AD with three or so > users, and a single Server 2008 R2 Exchange 2010 / AD server (say, > 192.168.0.2/255.255.255.0, public IP 123.123.123.123/255.255.255.248) > running > onsite. We're often away from the office (sometimes we're all abroad at > the > same time with nobody at the address) so, in the interests of redundancy > and > always being able to access email, we have bought a second server hosted > in a > datacenter nearby (say, 124.124.124.124/255.255.255.0) which will also be > an > AD and Exchange server, (both CAS and maibox servers with the mailbox > database in a Database Availability Group - hope this will work!). > > What I'd like to do is figure out a way of joining the domain and keeping > all traffic flowing between the two networks encrypted by VPN tunnel or > similar. (I wouldn't mind it going over the public network, but it's > probably > too insecure). How would I go around creating a VPN tunnel between the two > in > WS2008R2? What routing parameters would I use? Given that there's no > similar > private subnet on the colocated server (it only has a single IP allocated > to > it, though I don't mind routing the entire 124.124.124.* subnet through > the > VPN; it's so unlikely I'll ever need to contact any other server on the > same > subnet) - do I need to create a 'ghost private subnet' of 192.168.1.* or > something? > > I'm a little lost, and would love advice on what to do. > > N
From: Ace Fekay [MVP-DS, MCT] on 22 Feb 2010 19:17 "Phillip Windell" <philwindell(a)hotmail.com> wrote in message news:%23v9RY9$sKHA.5976(a)TK2MSFTNGP05.phx.gbl... > "Nippoo" <Nippoo(a)discussions.microsoft.com> wrote in message > news:F3DCBF1B-0194-4060-BEFB-637206C41DE6(a)microsoft.com... >> What other options do I have apart from installing Exchange on a DC? >> Unless I >> buy two new servers... > > You're running 2008R2!! That means you have Hyper-V! It is already > there,...and it is free. > > You just have to buy one more Server License to cover the OS in the VM for > Exchange. but then 2008R2 might already cover having *one* copy in a > VM,...but you'll have to verify that. > > Run Exchange in a VM under Hyper-V,...so it will still be on the same > "physical" box,...but will not be on the same "logical" machine as the DC. > Since the DC is on the Parent Machine, and since a DC should always be > already running *before* Exchange is started up or shutdown,...it should > be fine. > > In the end your weak link would be if the hardware is not powerfull enough > to run two OSs efficiently. > > > -- > Phillip Windell > > The views expressed, are my own and not those of my employer, or > Microsoft, > or anyone else associated with me, including my cats. > ----------------------------------------------------- > > Hi Phillip, FYI, IMHO, I usually shy away from running Exchange or SQL in a VM due to heavy processing and I/Os. DCs, etc, are fine. Ace
From: Phillip Windell on 23 Feb 2010 09:36 "Ace Fekay [MVP-DS, MCT]" <aceman(a)mvps.RemoveThisPart.org> wrote in message news:eNYwk2BtKHA.4636(a)TK2MSFTNGP06.phx.gbl... > Hi Phillip, > > FYI, IMHO, I usually shy away from running Exchange or SQL in a VM due to > heavy processing and I/Os. DCs, etc, are fine. > > Ace That's true. MS used to be really "down" on doing that, but it was mainly when everyone was using Virtual Server on 2003. They used to say the same about ISA Server as a VM, but now they don't have a problem with it. Hyper-V on 2008 should be providing better performance than Virtual Server anyway. With VMware virutalization I've actually had a VM outperform the previous physical machine they were on just because the hardware on the parent machine was so much more powerful than the original machine that was being used,..of course it was not an I/O intensive machine. But I still think it is better than running those things directly on the DC itself. Looking back at the original post he said there were only "three or so" users,...so the Exchange and the SQL are not going to be hit hard. -- Phillip Windell The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. -----------------------------------------------------
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 Prev: windows server 2003 SP2 failed with error 0x800703e7. Next: FSMT Error |