Often, I field questions about how to protect a computer, especially when it's brand new. I've often given customized advice to people, depending on their current environment. But, I get the questions enough that I considered composing a document that outlines this information.
Fortunately, I have (and, so have you) paid for someone else to compose this document for us:
http://www.us-cert.gov/security-publications/ten-ways-improve-security-new-computer
This federal government site has a wealth of information, including this well-written document, on how to secure your computer from the bad guys. There's lots of ways to protect your new computer from getting compromised, but this document provides a great baseline for everyone to follow.
Besides the steps outlined in this document, I would also add that setting up a new machine is a perfect time to also setup a solid backup solution and consider encrypting the hard drive in your computer, especially if it's a notebook that gets lots of miles.
Welcome. Here you will find information on technical subject matter that I love or despise, as well as practical information you may find handy in your own troubleshooting experiences. Questions and comments are always welcome.
Showing posts with label backup. Show all posts
Showing posts with label backup. Show all posts
Friday, April 19, 2013
Tuesday, November 06, 2012
TIPS & TRICKS: Manually Change Time Machine Backup Schedule
Apple's Time Machine was, by far, the best tool Apple introduced with OS X Leopard (10.5). Backups are always the last thing most users think about. But, it's the first thing people wish they would have had when there's some failure that prevents them from accessing their data. Time Machine's simplicity should have every single person who doesn't already have a backup solution adopt it with fervor.
As great as the tool is for most backup needs, I have discovered a drawback. Time Machine runs a backup once an hour. The constant barrage of data hitting the backup destination can put a toll on the media. In many cases, the media is an external hard drive with physical hard drive. The drives themselves are not nearly as sturdy as they used to be. I've come across users who have had to replace their backup drives inside of 6 months. If you need the once an hour backup interval, then you'll need to put up with this routine maintenance. Think of it as changing the oil filter every time you change your oil in the car.
Fortunately, there is a fix for those people who don't need the backups nearly that frequently. As the saying goes, there's an app for this. However, I am an fan of understanding how the underlying code works. The manual method is this command (all one line):
The 14400 is the number of seconds in 4 hours. The number you choose should be a factor of 3600 seconds (1 hour). For example if you want to do it once every 7 days, you would use 604800. You can also check the change with this command:
Hope this helps you out with extending the life of that backup hard drive.
As great as the tool is for most backup needs, I have discovered a drawback. Time Machine runs a backup once an hour. The constant barrage of data hitting the backup destination can put a toll on the media. In many cases, the media is an external hard drive with physical hard drive. The drives themselves are not nearly as sturdy as they used to be. I've come across users who have had to replace their backup drives inside of 6 months. If you need the once an hour backup interval, then you'll need to put up with this routine maintenance. Think of it as changing the oil filter every time you change your oil in the car.
Fortunately, there is a fix for those people who don't need the backups nearly that frequently. As the saying goes, there's an app for this. However, I am an fan of understanding how the underlying code works. The manual method is this command (all one line):
sudo defaults write /System/Library/LaunchDaemons/com.apple.backupd-auto StartInterval -int 14400The 14400 is the number of seconds in 4 hours. The number you choose should be a factor of 3600 seconds (1 hour). For example if you want to do it once every 7 days, you would use 604800. You can also check the change with this command:
sudo defaults read /System/Library/LaunchDaemons/com.apple.backupd-auto StartIntervalHope this helps you out with extending the life of that backup hard drive.
Labels:
backup,
command line,
OS X,
Time Machine,
tips and tricks,
unix
Tuesday, August 23, 2011
TIPS & TRICKS: Free Backup Tool - EaseUS Todo Backup
Heard about this free local backup tool that seems to have a set of good tools built-in, including an all-important scheduling mechanism. In addition, there's also incremental & differential backup, disk cloning, selective file and folder backup, restoring to dissimilar hardware, and auto deletion of old images.
http://www.todo-backup.com/
I haven't actually tried this tool yet, but I will as I need a better tool than the built-in Windows one for one of my boxes.
http://www.todo-backup.com/
I haven't actually tried this tool yet, but I will as I need a better tool than the built-in Windows one for one of my boxes.
Friday, October 08, 2010
RANTS: Apple Migration Assistant
Just had (luckily) only my second user data loss in my IT career. The first experience helps guide how I operate with other people's data today. I can't have too many backups or can't be too careful.
Fortunately, this second experience was not a complete repeat of my first experience, though I definitely could have used extra backups here. I had a user who had a disk corruption on his MacBook Pro. Nothing I could to to recover, except reload the entire machine. I loaded a clean copy of OS X on an external hard drive. From there, I booted off the external hard drive off the disabled MacBook Pro. Then I ran Migration Assistant from the external hard drive and pointed it to the internal hard drive on the MacBook Pro. At this point, I assumed that the external hard drive had all the files from the internal hard drive. I wiped the internal hard drive. I reloaded the internal hard drive with a fresh copy of OS X. I connected up the external hard drive again and ran Migration Assistant from the internal hard drive to copy over all the files.
At this point, I figured I was just about done. I tested logging into a user account and reconfigured a few things on the new reload. User even logged in and found his files on the desktop he needed. A day or two later, he discovered that his mail was no where to found. Long story short, Migration Assistant did not copy over the contents of Mail at all. I checked the external hard drive and found nothing. All his mail inside of Mail was lost. I felt terrible, even if this user was quite understanding.
Now that I think of it, the hard drive corruption could have caused Migration Assistant to fail to copy over the contents of Mail. I, then, have to wonder how many other files were lost.
Yet another hard lesson learned. Don't rely on one process. Even the method/solution should be backed up, not just the data.
(Not so) Happy Computing.
Update: 10/28/2010, revisiting this machine, I figured it that it wasn't my fault that the data did not come over. Migration Assistant failed due to the drive corruption. Granted, I should have checked it before wiping the drive and reinstalling. The way I found out was that the user did a search on the freshly rebuilt OS with migrated data and found some of the messages he needed. Turned out the messages were moved over to a folder at the root of the drive probably because the messages were sitting in an area that was affected by the corruption. The folder was actually created by DiskWarrior when it attempted to recover the original build. Whew!
Fortunately, this second experience was not a complete repeat of my first experience, though I definitely could have used extra backups here. I had a user who had a disk corruption on his MacBook Pro. Nothing I could to to recover, except reload the entire machine. I loaded a clean copy of OS X on an external hard drive. From there, I booted off the external hard drive off the disabled MacBook Pro. Then I ran Migration Assistant from the external hard drive and pointed it to the internal hard drive on the MacBook Pro. At this point, I assumed that the external hard drive had all the files from the internal hard drive. I wiped the internal hard drive. I reloaded the internal hard drive with a fresh copy of OS X. I connected up the external hard drive again and ran Migration Assistant from the internal hard drive to copy over all the files.
At this point, I figured I was just about done. I tested logging into a user account and reconfigured a few things on the new reload. User even logged in and found his files on the desktop he needed. A day or two later, he discovered that his mail was no where to found. Long story short, Migration Assistant did not copy over the contents of Mail at all. I checked the external hard drive and found nothing. All his mail inside of Mail was lost. I felt terrible, even if this user was quite understanding.
Now that I think of it, the hard drive corruption could have caused Migration Assistant to fail to copy over the contents of Mail. I, then, have to wonder how many other files were lost.
Yet another hard lesson learned. Don't rely on one process. Even the method/solution should be backed up, not just the data.
(Not so) Happy Computing.
Update: 10/28/2010, revisiting this machine, I figured it that it wasn't my fault that the data did not come over. Migration Assistant failed due to the drive corruption. Granted, I should have checked it before wiping the drive and reinstalling. The way I found out was that the user did a search on the freshly rebuilt OS with migrated data and found some of the messages he needed. Turned out the messages were moved over to a folder at the root of the drive probably because the messages were sitting in an area that was affected by the corruption. The folder was actually created by DiskWarrior when it attempted to recover the original build. Whew!
Subscribe to:
Posts (Atom)