Jan 06 2015

You can now signup for VMware’s BIG event on Feb. 2nd


Still no word about what it’s all about though but I’m sure you can figure it out from this other post I did on it. The banner for the event says Live and Online but the link only takes you to the Online registration page. No word on the Live part and who can attend it but the event does correspond with PEX and is timed (1:00pm PST) a few hours before the Welcome Reception (5:00pm PST) so maybe they will broadcast it from Moscone West. Also not sure what the 28 Days of February event is all about either, coincidentally VMware just did a blog post today on “28 Days Later, Physical to Cloud … Done” Technically though if they start on 2/2 and with February having only 28 days it will only be a 27 days event.

As far as being the biggest launch in VMware’s history, I’d argue that the vSphere 5 launch was bigger as it had much more new and enhanced features in it. You can sign-up for the online event by clicking the above image.

Dec 31 2014

Something big is about to happen…


according to VMware, they posted this banner on their website a week or so ago hinting at a big announcement coming soon. Hmmm, I wonder what that could be? If one had to make a guess I would suspect a new vSphere version which is overdue. The date corresponds with VMware Partner Exchange (PEX) which runs from 2/2 to 2/5 this year, there are no keynotes on Monday (2/2), just the Welcome Reception which opens at 5:00pm. Being that PEX is only a partner audience I suspect VMware will hold a separate online event earlier that day so customers can hear all about whatever big thing they are announcing. They did this with the release of vSphere 5 (banner below) which was a small event broadcast live at the Terra Galley in SF at which I was one of a handful of bloggers that VMware invited to.


I still have the solid metal keepsake that they gave out to us at the vSphere 6 event.


One thing to note is that all of VMware’s recent new vSphere version launches have occurred at VMworld, and PEX has always been pretty un-exciting so hopefully this will spice it up. It also breaks VMware’s traditional one year release cycle of new vSphere major releases as I outlined in this post on VMware’s ever shortening release cycle for hypervisor versions. I suspect that the new VVOLs storage architecture took more effort to perfect than anticipated which may have caused the delay. Whatever they are announcing though I’ll guess you’ll have to wait a few more days until they officially let the cat out of the bag. I’ll be at PEX so I’ll be reporting on whatever they announce and show off at the event.

Dec 31 2014

The Top 100 VMware/virtualization people you MUST follow on Twitter

My last post triggered my memory that a few years ago (5 actually, my doesn’t time fly) I put together a list of the top 100 people to follow that were influential with VMware and virtualization technologies. It’s been quite a while since I updated that list (5 years!), so I thought I would bring it up to date by removing some people an adding new ones based on who I think are good people to follow these days.

Putting together these types of lists is always difficult, I try and research a bit to see who is fairly active on Twitter and tweets about VMware & virtualization stuff a good amount of time. It is entirely possible I missed some people though (I’m sure I did) that should be on the list, it wasn’t easy to limit it to 100 as there are tons of great people that tweet about VMware & virtualization but I did the best I could. So I apologize in advance if I missed someone that I probably should of included.

So without further ado, click the image below to see my Twitter list of the Top 100 VMware/virtualization people you MUST follow on Twitter.


Dec 30 2014

Top Twitter Influencers To Follow for Virtualization


I was contacted by the folks at Techopedia a few weeks ago and notified that they had added me to their Twitter list for Top Influencers for Virtualization. Not sure what the qualifications were or why they picked me but I’m thrilled to have been recognized by them. They also asked me if I had any recommendations for other people to add to the list so I gave them some names of the top bloggers in the community. While there are certainly a lot of worthy people on the list I’m not sure I agree with all of them (there certainly a lot of good people missing), for instance one person on the list hasn’t tweeted in over 2 years. So if you’re looking for virtualization people to follow on Twitter be sure and check the list out and start following the people on it.

Dec 29 2014

A new vChat so epic it was a year in the making

It’s been a while (over a year!) since David, Simon and I have gotten together and done a vChat podcast for various reasons but we finally managed to get together and record a new one. In this new episode #36 we chat about virtualization and other topics such as vSphere home labs, how to stay up to date on virtualization news, HP MicroServers, Apple Mac Minis, Dr. Who and what we plan to chat about in the future (might be another year, ha)! So click the video below and enjoy.


Dec 22 2014

Yes Veeam and Nutanix will be at PEX this year

Last year at VMware’s annual Partner Exchange (PEX) conference, VMware told both Veeam and Nutanix that they were not welcome there. Both companies had planned on being there already and did show up anyway and had a presence outside of the Moscone to engage with attendees. This year it looks like VMware has had a change of heart and both companies will be there. I noticed this when I was submitting a sponsor session submission and both companies were listed in the sponsor selection, they are also listed in the PEX Content Catalog (yeah Rick Vanover will be there).

PEX2015-small-circleWhy did VMware do this last year? It could be that they felt threatened by them and VMware wanted partners to focus on VMware’s offerings instead. To single them out doesn’t make a lot of sense though as almost every other vendor competes with VMware these days as well. About the only vendors left that do not compete with VMware in some way are SuperMicro and Seagate who sell hardware solutions only that are server-based and cannot be virtualized.

Why the change of heart this year? Could be that they don’t want to call attention to them and cause a Streisand Effect and thereby giving them even more exposure. Also PEX has mainly be a mostly VMware show in the past, however this year VMware is limiting partner activities at PEX by cutting down on the Solutions Exchange hours to only Monday from 5:00-7:00 and Tuesday/Wednesday from 11:00-3:30. There are also only 14 sponsor sessions versus 153 VMware only sessions.

Regardless of why, it should be a good show as we finally have a PEX that will be aligned with a major vSphere product launch. I’ll be there again this year and if you’re going as well I hope to see you there.

Nov 19 2014

Content Catalog now live for VMware Partner Exchange (PEX)



Once again VMware Partner Exchange (PEX) will be held in San Francisco and registration is open for the event which is being held on Feb. 2-5 at Moscone West. As the name applies this is not a customer event and attendees at PEX are made up of a mix of VMware partners and resellers. PEX is essentially a scaled down VMworld with breakout sessions, keynotes, labs, solutions area, etc. with the focus more on training resellers on how to sell VMware and partner products to customers. Attendance is usually around 5,000 people.

The call for papers for PEX is internal to VMware only and almost all the sessions are from VMware speakers with the exception of a handful of partner sessions that they receive with sponsorship (generally 1 per partner for highest level sponsorships). In addition VMware holds special Boot Camps that are usually an all-day event on a specific topic, this is a great form of live training. Select partners also receive a Boot Camp as part of their sponsorship of the event. The Boot Camps are being held Jan. 31-Feb. 2.

Last year there was a bit of drama around PEX as VMware told both Veeam and Nutanix that they were not welcome at PEX. Veeam came anyway and ended up setting up shop nearby and tried to route customers to their camp and events. It will be interesting to see what happens this year as VMware continues to compete more and more with pretty much all of their partners.

The cost of PEX registration is cheaper than VMworld at $1,495. there is an early-bird registration discount (good to 12/9) that lets you save $300, if you are an alumni they also take off another $100. This year the event is a week earlier and as a result it conflicts with the SuperBowl Big Game which will be sure to cause problems with peoples travel plans. As the Big Game is in my city (Phoenix) this year I haven’t decided if I want to try and fly out very late Sunday/very early Monday after the Big Game or early Sunday before the Big Game to make sure I can watch it.

The content catalog also just went live for PEX, right now only the VMware sessions are listed (130 of them) and very few Boot Camps. Expect to see it become more populated as it gets closer to the show. The Storage track only has 11 sessions with 2 on VVols and 4 on VSAN. The official Welcome Reception kicks off Monday (Feb. 2) from 5:00-7:00pm, you can see the full agenda here.

I’ll be attending PEX again this year so if you’re going I hope to see you there.


Nov 06 2014

Nominations for Season 7 of the vExpert program now open


The VMware vExpert program was born back in 2009 thanks to the efforts of John Troyer to help recognize members of the VMware community that continually give back by sharing their knowledge and experience with others. The original group was about 300 members which included myself and was mostly compromised of bloggers and VMUG leaders. The group has expanded over the years as both the number of bloggers has grown and the criteria and requirements have changed. I believe in the last year they are up to around 700 vExperts.

I think it’s important for people to understand the definition of a vExpert, I did a post on it for Tech Target back in 2009 on what it means to be a vExpert. First off the vExpert title is not an official certification and it is only good for one year, so if you don’t stay active you could lose it as you have to nominate your self each year. The name vExpert is a bit mis-leading as it doesn’t really certify that you are an expert on VMware technologies like a VCP or VCDX certification does. Think of the vExpert title as a recognition award from VMware that validates your contributions to the VMware community. What you get from it is recognition and some other great perks like VMware licenses, beta program access, exclusive early access webinars, special events and more. Some vendors will also reward vExperts with special giveaways like this great shirt from Tintri which includes a star for the number of years that you were recognized as a vExpert..


So what does it take to become a vExpert? First off, understand it’s not a popularity contest. You can read the blog post here on the paths to vExpert and some of the characteristics that they look for. If I had to summarize it in a few words it might look like this: passion, leaders, bloggers, enthusiasts, sharing, champion, speaker, evangelist, commitment. So want to become a vExpert? All it takes is getting involved with the community and staying committed to it, there are a lot of different ways to do this. You can start a blog, become a VMUG leader, do a podcast, speak at events, be active in the VMTN community, be social and more. I did a presentation at VMworld back in 2011 on how to succeed at blogging and becoming a vExpert that you might find helpful. Remember it takes time and dedication so stick with it and once your contributions build up don’t be afraid to apply. If you’ve already made contributions in 2014 be sure and apply and detail them for consideration to become a vExpert in 2015.

Oct 26 2014

Import files to subscribe to all the Top vBlogs via RSS

I’ve been long meaning to create RSS import files that can be used to automatically add all the Top vBlogs to your RSS reader of choice but have never gotten around to completing them. Thanks to a reminder from a reader (Brian Olsen) I have gone and created them by exporting my top vBlog WordPress table from the vLaunchpad and clearing out all the non RSS feed related HTML code. I then went and created 4 separate OPML files that can be used to import into a RSS reader. I created 4 files in case someone wanted to import only the Top 10, the Top 25, the Top 50 or the whole Top 100 vBlogs. The files are available for download on my page bar on the vLaunchpad. The process to import them is fairly simple as outlined below:

1) First download the file you want by going to the vLaunchpad, selecting it and right-click on it and select “Save link as”, it will default to a XML file name (i.e. Top50vBlogs.xml), save it to your computer.


2) Now that you have the import file its time to go into your RSS reader and import it. How you do this will vary depending on the RSS reader you are using but it should be pretty straightforward. In this example I’ll be using a popular free RSS reader, FeedDemon. First I created a folder to put the blogs in and called it Top 50 vBlogs. Then I select File from the top menu, then Import/Export and then the Import Feeds option.


3) The Import Feeds window will open, select “Import An OPML File” click the Folder icon to browse for the file, change the File types to “XML Files” and select the file you downloaded.


4) On the next screen it will list all the blogs that are contained in the import file, you can select them all or just specific ones that you want to import, once you select them click Next.



5) On the next screen choose a folder to place them in, I selected the Top 50 vBlogs folder that I had already created, once you do that click Next.


6) Click Finish and the blogs will be added to your RSS reader and it will connect to all of them and pull the latest content from them. Note the original OPML file had the RSS feed URL as the blog title which made it difficult to identify blog names so I went and manually edited the file so they display as they do on the vLaunchpad with the blog ranking, blog name and blog author. Also note the number of posts that are pulled from a blog are dictated by each blog’s WordPress settings under “Settings–>Reading–>Syndication feeds show the most recent _ items”



Oct 19 2014

Don’t miss out, subscribe to vSphere-land via email



I just added a new option to be notified via email of any new posts here at vSphere-land. So sign up now so you never miss a post again, especially with the upcoming Top vBlog voting coming up soon. Every year I have people complain that they missed out on posts related to Top vBlog so here’s your chance to stay informed.


Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Oct 19 2014

The vLaunchpad is finally updated!

I’ve spent a lot of time recently updating and refreshing all my sites and I recently migrated my vLaunchpad site to a new hosting provider, new WordPress version and to a new theme. I also took some time and went through the big backlog I had of adding new blogs to it. I’ve added at least 50 new blogs as I get ready for the upcoming top vBlog voting which will be kicking off in December. There are some cool changes in store for top vBlog this year so make sure your blog is listed on the vLaunchpad so it is included in the voting and you don’t miss out. I just updated the blog submission form so make sure you use that as it includes all the key info that I need to add your blog to it.

Oct 18 2014

Why the VMware vSphere TPS vulnerability is a big deal


VMware recently acknowledged a vulnerability with their Transparent Page Sharing (TPS) feature that could potentially allow VM’s to access memory pages of other VMs running on a host. TPS is a host process that leverages the Virtual Machine Monitor (VMM) component of the VMkernel to scan physical host memory to identify redundant VM memory pages. The benefits of TPS are that it allows a host to reduce physical memory usage so you can squeeze more VMs onto a host as memory is often one of the most constrained resources on a host. TPS is basically the equivalent of storage de-duplication for RAM and works at the 4KB block level. You can read a full description on how it works in this classic VI3 memory white paper that refers to it as “Memory Sharing” or this more recent vSphere 5 white paper on memory management. Here’s a brief description of it and a slide on how it works:


When multiple virtual machines are running, some of them may have identical sets of memory content. This presents opportunities for sharing memory across virtual machines (as well as sharing within a single virtual machine). For example, several virtual machines may be running the same guest operating system, have the same applications, or contain the same user data. With page sharing, the hypervisor can reclaim the redundant copies and keep only one copy, which is shared by multiple virtual machines in the host physical memory. As a result, the total virtual machine host memory consumption is reduced and a higher level of memory overcommitment is possible.


It’s important to note that the TPS feature is nothing new to vSphere having been first introduced with the VI3 release back in 2006, but apparently someone has now finally gotten around to try and successfully exploit it. Why is this a big deal? Because a virtualized architecture demands VM isolation, this is the most important security requirement for virtualization. Each VM guest running on a host must not be allowed in any way to access another VM guest. They must be kept in separate locked rooms with only the hypervisor possessing the keys to access all of them.

To illustrate this let’s use a real world scenario, imagine if you checked into a hotel, you expect privacy and isolation and to not have any other guests be able to come into your room. However your room has an adjoining shared door with another room but neither guest could get through it, only the hotel management can control the door. But somehow a guest has figured out a way to to open that door and get into your room and invade your privacy, that’s a pretty big deal wouldn’t you say.

VMware appears to be down-playing it as it obviously exposes a chink in their virtual armor, they have issued a KB article describing the vulnerability and giving guidance on how customers can disable TPS on their hosts. VMware doesn’t name the specific source that found the vulnerability in the KB article, they simply refer to it as “an academic paper”. The academic paper is entitled “Wait a minute! A fast, Cross-VM attack on AES” and was written by a group of individuals from Worcester Polytechnic Institute in 2014. It was funded by a National Science Foundation grant and it’s a pretty technical, head-spinning read with a lot of mathematical formulas. It’s worth taking a look at though as parts of it are more easily consumable and describe the attack scenarios and results. The overview of the paper is described as:


In this work, we show a novel cache-based side-channel attack on AES that—by employing the Flush+Reload technique—enables, for the first time, a practical full key recovery attack across virtual machine boundaries in a realistic cloud-like server setting. The attack takes advantage of deduplication mechanism called the Transparent Page Sharing which is employed by VMware virtualization engine and is the focus of this work. The attack works well across cores, i.e. it works well in a high-end server with multiple cores scenario that is commonly found in cloud systems. The attack is, compared to [13], minimally invasive, significantly reducing requirements on the adversary: memory accesses are minimal and the accesses do not need to interrupt the victim process’ execution. This also means that the attack is hardly detectable by the victim. Last but not least, the attack is lightning fast: we show that, when running in a realistic scenario where an encryption server is attacked, the whole key is recovered in less than 10 seconds in non-virtualized setting (i.e. using a spy process) even across cores, and in less than a minute in virtualized setting across VM boundaries.

When I was going through the paper at the end of the paper in the references section one thing I noticed was that the authors of the paper had previously written a paper earlier in 2014 entitled “Fine grain Cross-VM Attacks on Xen and VMware are possible!“. So it appears based on that they worked to apply the theoretical research from that paper into a real-life attack which succeeded and prompted the 2nd paper to be written.

It’s important to note that this is not an easily exploitable vulnerability and the risk is super low so most environments should not really be impacted by it. VMware is being overly cautious though and will disable the feature by default in all upcoming releases of vSphere which includes:

  • ESXi 5.5 Update release – Q1 2015
  • ESXi 5.1 Update release – Q4 2014
  • ESXi 5.0 Update release – Q1 2015
  • The next major version of ESXi

In addition they will be issuing patches before that to address it sooner rather than later as follows:

  • ESXi 5.5 Patch 3
  • ESXi 5.1 patch planned for Q4, 2014
  • ESXi 5.0 patch planned for Q4, 2014

All versions of vSphere back to VI3 are vulnerable to the exploit but VMware is only patching the 5.x versions of vSphere as the 4.x versions are no longer officially supported as of May 2014. Note these patches only disable TPS which is currently enable by default, they do nothing to fix the vulnerability, it will most likely take VMware some time to figure out how to make TPS work in a way that cannot be exploited. So if you disable TPS on your own you don’t really need the patch. VMware states in the KB article that “Administrators may revert to the previous behavior if they so wish” so it sounds like they are not too worried about it.

The benefits that TPS provides will vary in each environment depending on VM workloads so if you are really paranoid about security you will probably want to disable it. You can view the effectiveness of TPS in vCenter by looking at the “shared” and “sharedcommon” memory counters to see how much you benefit from it. You can disable TPS in your current environment by changing advanced settings on each host as described in the KB article, updating the setting is pretty simple but having it take effect is tedious work:

  1. Log in to ESX\ESXi or vCenter Server using the vSphere Client.
  2. If connected to vCenter Server, select the relevant ESX\ESXi host.
  3. In the Configuration tab, click Advanced Settings under the software section.
  4. In the Advanced Settings window, click Mem.
  5. Look for Mem.ShareScanGHz and set the value to 0.
  6. Click OK.
  7. Perform one of the following to make the TPS changes effective immediately:
    1. Migrate all the virtual machines to other host in cluster and back to original host.
    2. Shutdown and power-on the virtual machines.

While the impact and exposure may be minimal with this, the fact that someone has finally cracked those solid walls that have stood between VMs is a big deal. I’ve written about it previously in my post on Escaping the Cave, VMware officially describes this as “inter-process side channel leakage” and mentions this in the KB article:


Side channel attacks that exploit information leakage from resources shared between processes running on a common processor is an area of research that has been explored for several years. Although largely theoretical, techniques are continuously improving as researchers build on each other’s work. Although this is not a problem unique to VMware technology, VMware does work with the research community to ensure that the issues are fully understood and to implement mitigation into our products when appropriate

Note they mention these types of vulnerabilities have been “explored” for years, meaning lots of people have been looking for a way to penetrate those walls as this is the holy grail type of hack of a virtual environment. Imagine if someone compromised a less critical VM through one of the many thousands of OS and application vulnerabilities that exist. At least the damage and exposure is contained within that one VM, but if some one could somehow use that compromised VM as a launchpad for attacking other VMs on a host that’s a real big deal. The fact that most of these types of vulnerabilities have been theoretical up until now really exposes VMware and their security foundation.

Overall vSphere is a very secure platform and has stood the test of time without any major issues which is a testament to how seriously they take security in vSphere. VMware will no doubt learn from this one and work to improve the security in vSphere to make it even better. However the circumstances of this one resulted from them trying to be more efficient with hypervisor resources by mixing VM data together. They will definitely need to be careful going forward as they continually look for new ways to optimize vSphere so they do it in a secure manner and do not risk exposure between VMs.

If you want to find out more about memory management in vSphere check out some of these links:

Oct 06 2014

So you have a virtualization blog, what are you doing to back it up?


Have you ever had that awful sick to your stomach, oh shit feeling when you just realized you lost a lot of important data whether it be photos, documents or other important stuff that can’t easily be replaced? It sucks doesn’t it, usually it takes just one instance like that to inspire us to start taking backups seriously. Unfortunately though it won’t bring back what you lost. Backups are one of those things that many people don’t think about especially when they store data on a location that is hosted on the internet.

There are a great many people that are blogging about virtualization these days and most of them are using WordPress as their platform of choice to do it. WordPress is an ideal platform for blogging but all that hard work you put into blogging could be wiped out if you don’t properly backup your WordPress site.

But doesn’t my hosting provider backup my site?

You should never trust that your hosting provider is backing up your website, many of them do not backup your content and if they do they probably do not guarantee them. Some hosting providers will offer a backup option as a paid add-on service. In addition they usually are not backing up your WordPress MySQL database which contains much of your valuable content. Take a look at this notice from my hosting provider, I think you’ll find the policy is similar with whatever provider you use, if you don’t know check with them.


How often should you backup your site?

Depending on how often you blog you should backup your WordPress instance at least once a month. If you are blogging several times a week you should probably do it daily or weekly. You should also do a backup before you upgrade WordPress to a newer version or update your plug-ins. Just like you do in the data center you should also plan on preserving older backups for as long as possible as often you may have something corrupted or malicious content that has been that way for a while that you need to go back a while to find a clean copy.

What should you backup?

With WordPress there are two main sets of data that you need to back up to ensure all your content is backed up and you can easily recover if needed, your WordPress files and your WordPress database. When you install WordPress on your website there are hundreds of files that get copied to specific directories that contain the complete WordPress web application. A new install of WordPress is only about 16MB in size with around 1,100 files but as you add content that will grow. Your WordPress database is typically hosted on a MySQL database that is installed and managed by your hosting provider. The WordPress database has many tables that store configuration and content for your WordPress website.

How do I back it up?

So now we know what needs to be backed up, how do we actually do it? There are several ways that you can backup WordPress:

  1. Manually by copying all your files to a PC using FTP and then doing a SQL export of your WordPress MySQL database and copying that to your local PC as well.
  2. Automatically by using some type of PHP script that can run scheduled on your hosting provider server using a scheduling tool like cron.
  3. Automatically using a WordPress plug-in designed to backup WordPress.
  4. Some hosting providers will do it if you pay for a add-on backup service.

Doing a manual backup

This method is OK for ad-hoc backups but it can be tedious to do on a frequent basis and it can easily slip your mind. I used this method for years, I did it nowhere near as often as I should of and I got lucky a few times were I almost lost a lot of data. To backup WordPress manually you will need to copy the all appropriate files and directories from the hosting provider web server to your local PC or even better to a cloud storage platform like Dropbox. Below are the files and directories that are come with a new install of WordPress.


The easiest way to move the files is to use an FTP application to copy them from your old server to your local PC and then to your new server. It’s also a good idea to periodically do this to backup WordPress. If you need a FTP client, check out FileZilla which is a free open source application. You may need to setup a FTP username/password on your hosting site before you can connect to it. Create a new site in FileZilla and give it a name (i.e. mywebsite-old), use the IP address or DNS name of your website and then enter in your login credentials. Once you connect to your web server you’ll see the directory listing of the contents, what you see will usually vary by hosting providers, some providers partition you off so you don’t see much of the web server files.

You may not need all the files you see to backup WordPress but its best to copy everything to a sub-directory on your PC so you do have a full backup just in case. In the figure above you can see the 3 WordPress directories that you need to copy for sure along with all the files that start with “wp” in the root directory. I’ve manually copied things to my site in the past (i.e. images) which I copy also. Other files that are part of the hosting platform you typically don’t need to bring over but it doesn’t hurt to copy them any way. Once you’ve copied everything to your PC it’s time to move on to the next step, backing up your MySQL database.

Your WordPress database is typically hosted on a MySQL database that is installed and managed by your hosting provider. The WordPress database has many tables that store configuration and content for your WordPress website. You can find a complete description of the database tables here. Log into your hosting provider control panel for your website and you should see a link for database management via phpMyAdmin which is a free software tool that is written in PHP that is used to administer MySQL over the Web. Once you launch phpMyAdmin you should be prompted for a username and password to connect to your database. You probably won’t know it or remember it but you can easily look it up by opening the wpconfig.php file that you copied to your PC as part of the backup in a text editor like Notepad and looking for the MySQL section which will contain your MySQL username/password.

Note some hosting providers may require you to whitelist your IP address to do remote MySQL administration, if they do there should be a section in your hosting control panel to put in your IP address. Once you are logged into phpMyAdmin you want to Export your database, click the Export link. You may be prompted for a quick export where you don’t need to enter a lot of options which will work just fine, if you do get a selection screen you typically can just use the defaults and then just hit Go and it will ask you for a location for the file on your PC and then begin the Export. It shouldn’t take more than a few minutes. Here’s how the Export screen looks with my hosting provider:


Once you have completed this it will create a .SQL file on your local PC that you should save with the other WordPress files that you copied. You now have everything you need to restore WordPress if needed by copying all the files you backed up back to the server and Importing the .SQL file back into WordPress, see my other post on moving to a new hosting provider for more info on how to do that.

Also note some hosting providers like GoDaddy provide a link in their control panel to kick off a database backup so you don’t have to go into PHPMyAdmin. They dump the resulting .SQL file in a db backup directory on your website, just make sure you copy the file from there to your local PC.

Doing an automatic backup with a PHP script and cron

I’m not going to go into much detail on this method, it can be a bit technical to setup. There are some WordPress plug-ins available that will make this easier to setup. Your hosting provider control panel should have a section to setup and manage cron jobs like below:


You then need to configure the scheduling and action for the cron job for the cron job to perform like below:


Again look for some WordPress plug-ins that support cron or a PHP script that is written to backup WordPress MySQL databases. If you are feeling adventurous you could also write your own PHP script. Here’s one I found by searching the internet. Some scripts may only backup the database so make sure you know what the script is doing and where it is storing your backups.

Doing an automatic backup with WordPress plug-in

This is probably the easiest and most convenient way to backup your WordPress site. There are many plug-ins available that will automate the backup of both your WordPress files and MySQL database so you don’t have to do anything but install the plug-in and configure it. You can search through the WordPress plug-in directory and you’ll see many of them. The one I ended up using which had 4.8 out of 5 stars and is free but has some paid add-on’s is UpDraftPlus Backup & Restoration. You can go to their add-on page which contains a big list of add-on’s and pricing for each that expand the flexibility, functionality and backup targets supported. Another popular WordPress backup plug-in is BackWPup.

You can backup your site just fine with the free version but it only puts the backup files on your hosting web server. If you want to use other backup destinations like Dropbox, Amazon E3, Rackspace, Google Drive and more it will cost you about $10 for each. If you do backup to your website only just remember to copy those files off periodically to somewhere safe.

Install UpDraftPlus like you would any other WordPress plug-in, once activated go into Settings, UpDraftPlus Backups in WordPress to setup your backup jobs and you will be at the main screen:


Here you can see your backup status and quick actions for backing up and restoring. It’s best to click on the Settings tab first to configure backup schedules and retention. Since most hosting providers now provide unlimited space don’t be afraid to retain a lot of backups.



You can also specify what files to backup, database encryption if you are really paranoid, reporting, remote storage options and other advanced settings. Note by default with the free version it will not backup your core WordPress files (i.e. wp-admin) but unless you customize yours you won’t have to worry about those as you can easily download those again if needed. All the files specific to your WordPress site are in the Themes and Plugins directories.

Once the backup runs you can look at the log files to see everything that occurred during the backup, it’s not something you’ll need to do regularly but I looked as I was curious. If you are using the free version which puts the backups into your WordPress directory you’ll see a new sub-directory under wp-content called updraft that contains your backup files all zipped up, make sure you backup these backup files somewhere else!


What about Backup as a Service?

If you prefer not to deal with your backups at all you can outsource them to a company that provides backup services for WordPress. Note both of these companies below backup both your WordPress files and database.


One such company that does this is blogVault. Their Basic plan starts at $9/month for backing up a single site and retain 30 days of backups. If you have more than one site you they have a Plus plan for $19/month that will backup 3 sites. It works by installing their WordPress plug-in on your site and then their server automatically contacts the plugin everyday to backup new changes to your site.


Another company that provides WordPress backup services is Backup Buddy. Their Blogger plan rate is $80/year for backing up 2 sites with 1GB of backup space available. Presumably with that much space available you could store more than 60 days of backups with them. They also have a Freelancer plan available for $100/year for up to 10 sites with 1GB of backup space. Again it works by installing their WordPress plug-in on your site and then configuring it, they have a video that demonstrates this process.


And that’s all there is to it, pick the service/method/plug-in that works best for you. For me I’ve setup UpDraftPlus and will also periodically do manual backups as well. Regardless of how you do it the important thing is that you are backing up your WordPress site which contains all your hard work that you do not want to ever take the chance of losing.

Oct 06 2014

10 Ways to Ruin a Presentation


I’m always looking to improve my public persona and a few months ago I wrote a post on how to gain confidence to be an effective public speaker. Recently I came across a great paper from Harvard Business Review entitled “How to Give a Killer Presentation” that is a great read. Within that there was a sidebar with great tips focused on surefire ways to ruin a presentation that I thought I’d pass along.

  1. Take a really long time to explain what your talk is about.

  2. Speak slowly and dramatically. Why talk when you can orate?

  3. Make sure you subtly let everyone know how important you are.

  4. Refer to your book repeatedly. Even better, quote yourself from it.

  5. Cram your slides with numerous text bullet points and multiple fonts.

  6. Use lots of unexplained technical jargon to make yourself sound smart.

  7. Speak at great length about the history of your organization and its glorious achievements.

  8. Don’t bother rehearsing to check how long your talk is running.

  9. Sound as if you’re reciting your talk from memory.

  10. Never, ever make eye contact with anyone in the audience.


Remember these are all ways to ruin your presentation, not improve it. So if you are guilty of any of these maybe it’s time to stop if you want to become a better speaker.

Oct 05 2014

Get your free virtualization tools right here!


Nothing beats free and many companies offer scaled down versions of their full products or purpose built mini tools as free tools. SolarWinds is one company which specializes in all sorts of tools that has many different free tools available for just about everything in the data center.

VMware has been developing free tools that they call Flings for several years now. Flings are lightweight, specific use tools developed by VMware Labs that often make up for some functionality that might be missing in their products. These tools often make their way into VMware products later on.

Whatever the motivation that a vendor has for creating a free tool the end result is tools that don’t cost you anything that can make your virtual life much easier.

I just updated my free virtualization tools section with many new tools from companies like SolarWinds, VMTurbo, Unitrends and VMware Labs. So head on over there and check them out and if there is a tool missing that you want people to know about just let me know.

Older posts «

» Newer posts