Google Drive is finally here

Google has finally released the Google Drive service. If you’re familiar with Dropbox, Microsoft’s SkyDrive, Apple’s iCloud, etc, it’s the same thing. I’ve been using Dropbox for years and enjoy it a lot. The free service gives you 2GB and you can upgrade it with a paid subscription. There are already many advantages for me to switching to Google Drive:

  1. I already use many Google services and they are all integrated.
  2. I already have a Google account so I don’t have to sign up for another new account.
  3. Many of my friend’s already have a Google account so it makes sharing easier.
  4. You get 5GB for free. I know Microsoft and Apple start you off with 5GB+ but Gmail has always been friendly with all operating systems – which is another advantage.
  5. Cost. For $2.49/month you get 25GB of storage. You can quadruple that and only pay twice that per month at $5. I may save more money versus using Amazon’s S3 service.

As I mentioned above, I’m currently using Amazon’s S3 service to back up my photos in the cloud. I’m currently paying around $3-4 per month. It’s a nice service and it’s a pay for what you use service. Not only am I paying for the storage that I use, I also pay for the bandwidth and server requests as well. That, I didn’t like. So far, it looks like storage is all I pay for with Google Drive. I may make the switch after I do some testing.

RAID boo boo

I got my RAID1+0 set up Sunday night and I bought some molex to SATA power cable adapters (I ran out because of the positioning of the devices). After Windows 7’s backup/restore failed to restore my OS onto my new drives from a backup and image file on my NAS, I decided to plug in my old/space 1TB hard drive internally – hoping to fix that issue. The 4 drives on my RAID were plugged in with 3 red and 1 blue. Nitpicking around, I wanted to have them all red so I swapped the drive3 of the array (blue) cable with red. Then I plugged in the new drive. After booting up, I noticed my RAID manager saying that my array needed to be rebuilt. I’m guessing even swapping out cables is not allowed or it will break the chain – noob IT guy :\

So for the last few hours, my 3rd drive is being rebuilt. I’m just glad I didn’t have to reinstall Windows and all those drivers. Nevertheless, if you can set up any RAID configuration on your computer, I highly recommend it. Not only will it increase performance, but it can increase hardware reliability – based on the RAID configurations of course. If you got any questions, email Jeff from JB Tech Enterprisessupport@jbtechent.com. He’ll be able to help you out. He’s a genius when it comes to these things and he helped me build my new PC, or leave a comment below.

rebuild_raid

MySQL backup and restore databases with views

We recently installed OS X Leopard Server at work. I had to take MySQL databases from our old Tiger Server and restore them onto the new XServes. Both servers are running MySQL Server version 5.0.45 but our Tiger server is running MySQL Client version 5.0.22 while our Leopard servers are running MySQL Client version 5.1.18. According to MySQL’s documentation (http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html):

Prior to release 5.0.48, this option did not create valid SQL if the database dump contained views. The recreation of views requires the creation and removal of temporary tables and this option suppressed the removal of those temporary tables. As a workaround, use --compress with the --add-drop-table option and then manually adjust the dump file.

I tried the –compress option but it didn’t work. I still had to manually adjust the SQL file. The I tried the GUI tool from MySQL, http://dev.mysql.com/downloads/gui-tools/5.0.html (MySQL Administrator).

mysql_admin.jpg

Once you create the backup, you can restore it using the same application on the newer server. It will even include the views. Once you start using the newer client, you shouldn’t have a problem restoring databases with views from backups made with the mysqldump command.