Really getting tired of your whining, dude. Get over all that and move on...
Don't worry, I still think you're swell. Shook ________________________________ From: Tom Strader [mailto:[EMAIL PROTECTED] Sent: Thursday, May 15, 2008 3:56 PM To: NT System Admin Issues Subject: RE: DR\BC for ESX design considerations Hell every time "I" make a comment it offends someone so I've stopped with the wise cracks, with the exception for TVK that is. ________________________________ From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Thursday, May 15, 2008 3:00 PM To: NT System Admin Issues Subject: RE: DR\BC for ESX design considerations I figured it be you, Strader or ME2 with the quick turn around. Shook ________________________________ From: Tim Vander Kooi [mailto:[EMAIL PROTECTED] Sent: Thursday, May 15, 2008 2:53 PM To: NT System Admin Issues Subject: RE: DR\BC for ESX design considerations budget = manhood From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Thursday, May 15, 2008 1:36 PM To: NT System Admin Issues Subject: DR\BC for ESX design considerations List, I'm neck deep in a developing & documenting a business continuity plan and right now I'm working on the ESX portion of my infrastructure and to put this in proper context, I don't have the budget for a secondary facility/co-lo or needed HW/SW/licenses right now but I'm planning for it sometime in the future. In the interim, I've got BackupExec, VCB and Vizioncore vRanger PRO at my disposal. I've got half a dozen servers that I decommissioned when I migrated everything to my ESX cluster. 1. Why not throw an OS and VM Server (the free product) on each of these boxes and have them on standby? 2. Keep a couple of the physical boxes online (domain controller w/all network services, single Exchange box, single SQL box) so that I could perform "dial tone restores" if ever needed. 3. I can copy the VM files to secondary storage (DAS) but the host server doesn't have enough horsepower to bring up every VM. I'm really getting into vRanger Pro, as it's a pretty happening product, despite the flame wars over on the VMWare forums of it vs VCB. I realize with either one of these scenarios I'm assuming the risk that something could happen to our building and I lose everything (I'm a single site operation at this time) but my budget is gone for the year due to cutbacks. Any insight on ESX protection for free would be much appreciated. Shook ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
