Symantec recently “lost” a bunch of cell phones to see what would happen when they were found. What they found will make you want to password protect your phone right away. Check out the news story here: http://digitallife.today.msnbc.msn.com/_news/2012/03/08/10595092-exclusive-the-lost-cell-phone-project-and-the-dark-things-it-says-about-us
For years now Corner Edge Solutions has been using VMware exclusively for all of our new server installs, and even for hardware upgrades by virtualizing the original server install and configuration to a new physical server with VMware. This goes for even a small, one server setup as well. We have felt this is a great way to increase reliability as well as improve disaster recovery times.
While having two complete setups of VMware is probably cost prohibitive, with the small footprint of VMware ESXi, you can use a simple workstation or even a laptop as a cold spare DR backup. As you’ll see below, I have easily installed VMware on my laptop, and with a large enough hard drive, and enough memory, I could run a small to medium office server environment setup on my one laptop, or even a mid-range business desktop. The cost of these is usually around $1500-2500, and when you consider the cost of a second server may come in at $5000 or more, this is a great low-budget way to have your office back up and working quickly in the event of a major disaster.
To do this simply, just power off the VM’s on a schedule that fits your DR needs and copy the files from the main DataStore and upload them the the DataStore on your backup setup. You will want to make sure your backup processor is a 64-bit proc with VT enabled if you are running 64-bit VM’s, you have enough storage space for the foreseeable future, and definitely install as much memory as your budget and workstation will allow, and that should be it.
You clearly shouldn’t expect the same performance of this setup as you would get from a true server, but it would get people back online and running again while you work on the main server.
Here is a quick picture I took of my laptop running VMware ESXi just for fun. I had installed ESXi on a USB stick, and booted to that when I powered on my laptop. This install was originally done on a PowerEdge 2950, and without any modifications to the install, it came up just fine on an Dell Latitude E6500. Simply carry a USB flash drive and a large external storage drive and you can have a backup ESXi server wherever you go.
We at Corner Edge Solutions LOVE VMware. It’s not too hard to tell that based on our blog, but this past week we found a new reason to fall in love all over again. One of our ESXi 4 servers in a cluster had a double drive failure on our RAID 5 array, which would have completely crashed a server had it been a typical setup, but since it is running VMware ESXi with all the VM DataStores on a iSCSI storage device, we had ZERO impact on our environment. ESXi is the lightweight version of the original ESX server which runs entirely in memory, not requiring disk access once it has been loaded at startup.
Since this machine was part of a cluster, we simply migrated the VMs on the failed server to the other working ESXi server through vSphere vCenter Server. The working VMware server was able to overcommit the available physical memory by almost 50% with room to spare. We then took down the server with the bad drives to rebuild. We also took this opportunity to install the OS onto a USB flash drive, which installed internally to the server, and remove the remaining two working hard drives to run a completely diskless server configuration. With a small amount of configuring to VMware, the newly rebuilt server was ready to join the cluster again and the VMs were then evenly distributed throughout the cluster, all the while never having to power anything off. That means never having to send out maintenance notices to customers that their hosted servers will be offline, and keeping out uptime in tact. The whole process took only about 5 hours as well. When was the last time a total failure on a system RAID drive, and nothing went down, and everything was upgraded and repaired in 5 hours?
There are a lot of forums where people are having trouble writing to the WD ShareSpace and getting an Access is Denied error. I have seen this plenty of times, and no matter if you set the shares to Public access, or set users with permissions, it is the same thing. While i think the root problem lies with Western Digital’s architecture, there is a way around it that works well.
First, create the share you want to use, or use an existing share you have already setup and are having trouble with. After that, set the user permissions in the web interface to be Public, or whatever you would like. So far, this is probably what you have done with no luck writing to the Network Attached Storage (NAS) device.
This is the part that will help you. Browse to the device in Windows Explorer (\[NAS Name or IP Address]), and right-click on the share you are trying to use. Go to the security tab and click advanced. Go to the Owners tab and make yourself the owner; you will probably see the current owner is “root(Unix Userroot)”. You will want to put a check mark in the “Replace owner on subcontainers and objects” also, so this change trickles down if you have any other folders there. Click OK until you are back at the Windows Explorer view.
You should now be able to write and delete to the share. To be sure you are the owner, you can always right click in the column header and add Owner to the current view to confirm you are now the owner.
I hope this helps get your Western Digital ShareSpace NAS online and usable for you.
Hi CPU usage in the VMware guest may not be caused from an overloaded CPU. It may be from a DataStore that is too slow. Check the performance tab in your VMware client and see if that too is showing high CPU utilization. If it isn’t, consider the speed of your DataStore.
We recently moved a VM from a RAID 5 with 3 slower SATA drives to a RAID 10 with 6 SAS 15k drives and with no other changes to the VM configuration and the machine performance has increased dramatically.
The problem appears to be caused by a backup writing files to the disk, which backs up the processor causing it to run at near 100% utilization waiting to be able to move on to its next task. This will probably be most noticeable with database servers like Exchange and SQL.
Take this into consideration also when you are spec’ing out a new VMware server, as upgrading the DataStore disks to faster ones is not a simple job. Include growth into your design; it’s always better to have an under-utilized server that is fast than one that is over-utilized and slow.
Lifehacker had a great article today showing the good old windows tricks to make your PC faster. Which ones really work? This is definitely worth your time if you are into tweaking or tuning your computers performance.
You might be surprised which ones help performance vs. hurt performance.
OK, who hasn’t tried to get to a website on your internal network using the public name or sometimes IP address when troubleshooting. sure enough, “Page not Found” shows it’s head. But i know it’s there and running, i can get to it using the internal IP or with a modified hosts file. well, a lot of firewalls by default don’t redirect outgoing traffic back into the network. Well, if you are using a pfSense (a FreeBSD based OS focused on firewall and routing tasks), this is a very simple fix.
Assuming you already have the port forwarding set and the site is accessible from the internet, there is only one check mark you need to remove to get this working from the inside. Start by hovering over the “System” in the menu bar, then click “Advanced”.
From there, scroll almost all the way down to the “Network Address Translation” section, and uncheck the “Disable NAT Reflection” option.
Now you will be able to type the public name or IP address into your browser and be able to see the page being hosted on your internal LAN. No more keeping hosts files to keep things easy, which sounds even easier to me.
Exchange server 2007 provides higher security and less SPAM potential by elimination authenticated mail over SMTP port 25. This leaves us without the ability to relay mail from other SMTP servers without the following tips.
Here are some setup tips on setting up SMTP relay over port 587 securely.
After setting up your network with a back-end Exchange 2007 Hub Transport/Client Access/Mailbox server and an isolated Exchange 2007 Edge Transport server in a DMZ or separate internal network, try setting up an IMAP connection to the Exchange Client Access server. Since all incoming mail traffic is supposed to flow through the Edge Transport server, you set up that as the endpoint for your outgoing SMTP server in your mail client like Microsoft Outlook or Mozilla Thunderbird, but no matter what you do, it just won’t work without authentication. The Edge Transport server is not (or at least it’s not supposed to be) a member of the domain, and therefore cannot authenticate the user.
One way to fix this is to set your firewall(s) to pass SMTP Submission traffic to the back-end Client Access server (CAS). Mail will be sent first to the back end Exchange Client Access server for authentication, and then be forwarded on to the front end server for external delivery.
Also, don’t forget to to check off the TLS or SSL security option and change the outgoing SMTP port number to 587 for SMTP Submission, rather than port 25 for standard SMTP traffic. And now, you should be sending mail securely.
Well, you took the leap and are now virtualized. You’re now doing more than ever, and data size is growing rapidly. Time to add a new virtual hard drive to your machine, but wait… I said 500 GB, why is it only 256 GB. Well, you hit a limitation of the data store in VMware under your current default configuration. Check to see what your data store block size is. here’s where to find it:
When data stores are created, their default block size is 1 MB, which gives you a maximum virtual hard drive size maximum of 256 GB. So how do you get larger VHD’s?
Hopefully you are reading this and have a brand new ESX/ESXi setup, in which case you can just delete the data store and recreate it, choosing a different block size. If you already have machines running on the data store, you have a project ahead of you, because deleting the data store will format all data on that drive, and you will have to start from scratch, or be creative before you make the change (there are some ideas of how to work around this below).
If you have the disk space to cover 2TB, then I would go with the maximum of 8MB block size to give you a maximum virtual HDD size of 2TB. There is no noticeable I/O performance difference by using maximum size, so use the largest size to mazimize your storage. Here is a quick reference of what block size you can choose and what the maximum VHD that will give you:
Block Size Max VHD size
Already have servers running? How do you fix it?
If you already have the data store in use, and can afford some downtime for a maintenance window, here is a workaround you could do, asuming you have more than one ESX(i) server at your disposal. You can power the VM down and use the free VMware vCenter Converter (http://www.vmware.com/products/converter/) to move the virtual machine from one ESX(i) server to another. Figure on about 1 minute per gig of hard drive size when moving it, with a GB network. Once the VM is moved to its new location, power it an and make sure all is working well before you delete from disk the VM on the original ESX(i) server. Once all the VMs are moved off the ESX server, you can go ahead and remove the data store and create a new one using the new block size.
If you hapen to have your VMs in a cluster with vMotion, this task is even easier, as you can change the location of the datastore through the migrate option. If you dont have any other ESX servers, you could probably do it to VMware Servers, but at that point, you would probably be better just adding multiple drives to the VMs, it would be a lot less work.
Here is a nice reference guide from VMware with this and other importand configuration information: http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_config_max.pdf