Business Relationships vs. Hostage Situations


I’ve been working with computers for a very long time, dating back to the time when you needed to use punched cards to program them. After graduating with several engineering degrees from Penn State, I went on to design computer peripherals for a major computer firm for many years. Because of my computer experience, my friends, most of whom are not computer experts, often use me as their first line of defense when they have a computer problem. And these days, “business is a boomin’.”

Part of the reason people have trouble with their PCs is because of the aggressive nature of companies trying to shove services down the throat of anyone who gets on the Internet. Not content to festoon what might otherwise be useful information with blinking banner ads, the new target of choice is the browser’s toolbar.

Last night I was helping my auto mechanic friend with his computer because it had lost his user profile, and Windows would let him log in but wouldn’t remember any of his desktop icons or save any of his browser’s bookmarks. He needs his computer to do his job as a mechanic since GM has moved all of its documentation on-line and without a computer, you just can’t function as an auto mechanic anymore. I know that sounds unbelievable but it’s true.

While I was adding a new user and copying his data over from his prior user’s settings, which seems to be the only way to fix a broken user profile on Windows, I noticed that his browser real estate had shrunk considerably since I first helped him to set up the computer. Why? It was because numerous toolbars had somehow managed to install themselves without my friend’s help. I suppose he may have helped a little but I can assure you it wasn’t intentional. I know this because his smile brightened more each time I managed to make one of them disappear. So in addition to fixing the main problem, namely the lost Windows profile, I also spent a lot of time cleaning up the computer.

Not only did I remove the offending toolbars, but I also removed all the miscellaneous links HP had included in his browser before he even set up the computer. He was too afraid to delete these items for fear he might break something. I call this stuff ‘crapware’, because it usually induces a customer to try crippled versions of programs or services which seek to get him to sign up for a perpetual subscription to an unnecessary service. And I should mention that the computer crawled along at a snail’s pace because of its heavy-handed virus protection software which his employer requires him to use, at his expense, of course.

I might have forgotten about this travesty and you’d not be reading it here, but then I got spammed by Sun today. I’ve been constructing an article in my head about Sun Microsystems which I will publish soon about how this once proud and capable company is now engaging in a desperate attempt to monetize the un-monetizable, namely Java, by using Java’s persistent need for updates as a trojan horse. I made sure to visit Sun’s CEO blog, written by the pony-tailed Jonathan Schwartz himself, just to make sure that was their plan. Sure enough, it was.

In my haste to quiet that little Java coffee cup by saying ‘yes’ to the update, it installed Carbonite’s crapware on my PC. Now, I’m no fan of on-line backup services and had previously written a critical review of what I think of them. Part of my view is colored by an image that I will now convey to you. Hang on, because I think you’ll like it. In any event, I can guarantee you won’t forget it.

A few years ago I witnessed a sales pitch for a service to provide on-line backup. I won’t mention the perpetrator, and you’ll never guess who it was because this idea was pitched by at least a million companies over the past few years and it’s one of those bad ideas that simply will not die. But during the presentation, the presenter took several opportunities to indoctrinate us, much like he was reciting a mantra, with this phrase:

“When you hold the customer’s data, you hold the customer.”

Along with this mantra, delivered with pregnant pauses both before and after, he used a hand gesture. Imagine holding an invisible tennis ball out in front of you at approximately waist level, palm pointed upward. The image is that of grasping and squeezing a person’s unmentionables. Wow! I think I knew where he was going with this. It wasn’t a business relationship he was proposing, it was a hostage situation.

Thanks, but no thanks. I’d prefer not to get involved in that kind of thing.

Yet it is precisely this kind of desperate business model that gets investors all worked up these days. No longer can you propose to provide a useful and valuable service for which people are willing to pay. Instead you must trick them into accepting something (often something offered for ‘free’) and then force them to become some sort of stooge, paying you perpetually for your right to continually abuse them.

I can only hope that this nonsense fades into oblivion, because I don’t want to live in a world where every business relationship requires duplicity and, eventually, larceny.

The next time someone is proposing to give you something that sounds like it’s for free, grab your wallet and anything else you’d like to hang on to and run in the opposite direction, because if you don’t, your valuables will soon be in the possession of someone who may not treat them with the same respect that you have for them.

Backing up a WordPress Blog on GoDaddy


Blogging is a great way to prepare content for the Internet without spending a lot of time worrying about the details of website administration and content formatting. But it’s easier to put content in a blog than it is to get it out of the blog for backup purposes. WordPress has a way to export the postings and comments into an XML file for local storage, but since you have to remember to do it periodically, you’re likely to lose a few postings if something goes awry on the server and you haven’t done a backup for a while. And the XML export doesn’t save the images you may have uploaded to your web host because those are not stored in the same database as the posts and comments.

I started looking around for a WordPress backup solution and was unable to find anything that looked like a good fit. WordPress posts and comments are not located on your GoDaddy web host. They are on a separate host/database that GoDaddy sets up when you install WordPress as an application. I download my website’s changed files to my local PC using a scheduled WS-FTP session. I generally use FileZilla for FTP and would like to use it instead of WS-FTP, but it doesn’t have a way to automate periodic downloads so I’m forced to use WS-FTP for my backups. WS-FTP isn’t free, but until FileZilla supports recurring automated scheduling of uploads/downloads, it’s the only way I know to do this. The FTP backup takes care of downloading my blog images and other website files but not the actual blog postings or comments.

GoDaddy has a web interface to set up cron jobs and I was pretty sure I could back up my blog’s database to the same WordPress directory that stores my blog’s theme and php files using a script to dump the database. A database dump could put a copy of the postings and comments in SQL format in a location where my WS-FTP job could find it and download it on a regular basis.

I figured others would like to know how to do this, so I’ve written up a short ‘how to’ here.

I will assume you have are using GoDaddy’s Linux hosting and have an SSH login and know your way around a Linux system. If not, you’ll need some help from a Linux expert who can understand the instructions below.

First of all, you can use a single command to perform the WordPress database backup manually, to make sure it’s working. Here is an example of mine which I store in a file called “wpbackup” located in the wordpress directory (please note, this command should all be on a single line):

mysqldump --add-drop-table -h mysqlhostname -u mysqlusername -pmysqlpassword mysqldatabasename | gzip -c > $HOME/html/wordpress/yourblogbackup.sql.gz

If you can’t remember the mysql hostname, username, password, and databasename because GoDaddy generates them for you automatically when you install WordPress as an application, you can find them all in the /wordpress/wp-config.php file. Please note that there is no space between the -p and the password. All other spaces are required. The mysqldump command takes all the data from your wordpress blog database and puts it in a SQL format that allows you to re-import it should the need arise. The “| gzip -c” compresses the database since SQL is made of plain text and it compresses pretty well, probably 4:1 or better. If you don’t want to use it, you can leave it out.

You will need to confirm that this is working properly. Just make sure it’s executable and type in “./wpbackup” to run it. Then you can do a “gzip -d” on the yourblogbackup.sql.gz file to turn it back into sql statements so you can browse the contents of the output file. Once you’re sure it’s working, then you are ready to set up the cron job. It is possible set up a cron job manually by editing the crontab file in your home directory, but GoDaddy has a web interface that allows you to set up and manage cron jobs without having to know how to edit the crontab file directly. You can see the result in the crontab file by looking at it in your home directory after you set it up if you’re curious.

Just go to the Hosting Control Center -> Content -> Cron Manager

Set up the job to make the wpbackup script execute on a regular basis. It should be done frequently enough to insure that your FTP download is getting a recent backup of the database.

With the cron job executing on a regular basis, and a scheduled FTP download of your website, the most recent content from your blog will get backed up so that should misfortune strike, you’ll be able to restore it to its original condition. The two commands to do that are:

gzip -d yourblogbackup.sql.gz
mysql -h mysqlhostserver -u mysqlusername -pmysqlpassword mysqldatabasename < yourblogbackup.sql

(please note, the mysql command should be all on one line)

If you found a better or easier way to backup your WordPress blog, please leave a comment with a link to your solution.
WP Starter Guide