Friday, September 06, 2013

Checking Time Machine Volumes


If you have followed my other article how to setup Time Machine Backup using AFP in Ubuntu, you probably experienced that sometime the backup volume is not recognised by your Mac. This article will help you checking the Time Machine volumes, and reassigned it if necessary.

I found this article that helps me checking if my Time Machine Volumes is setup properly. I still find that AFP is still the best for Time Machine.

Make sure your Ubuntu machine is up. Open Finder from your Mac and mount the Timemachine volume that you already setup. Open Terminal and type the following command:

$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            499.2 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *524.3 GB   disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:                  Apple_HFS Time Machine Backups    523.9 GB   disk1s2



See the last line which is my Time Machine Volume, note the identifier is disk1s2. Then check if Ownership is assigned.

$diskutil info disk1s2


Find the Owner line, it says Disabled, then we need to enable it:

$ sudo diskutil enableOwnership /dev/disk1s2


To check if the volume is activated for timemachine backup destinction, type this command:

$ tmutil destinationinfo


If you see no volume assigned, then type:

$sudo tmutil setdestination /Volumes/Time\ Machine\ Backups


Make sure volume name is exactly same as the volume name when you setup. In my setup, the name is Time Machine Backups. Add the "\" for each space in volume name.

That's it! Now your timemachine backup is working again.


No comments: