![]() |
HowTo.TimeMachineBackups HistoryHide minor edits - Show changes to markup March 06, 2013, at 06:54 AM
by --
Changed lines 193-194 from:
UPDATE: SlugOS users should copy the start files from /opt/etc/init.d/ to /etc/rcS.d/ for the files to be run on boot. to:
UPDATE: SlugOS users should create a symbolic link (ln -s) from the start files from /opt/etc/init.d/ to /etc/rc3.d/ for the files to be executed on boot. March 05, 2013, at 07:13 AM
by -- added SlugOS note
Added lines 193-194:
UPDATE: SlugOS users should copy the start files from /opt/etc/init.d/ to /etc/rcS.d/ for the files to be run on boot. January 03, 2011, at 12:28 PM
by -- Plug Time Machine
Changed lines 193-194 from:
This supplement should work for most plug computers. Please see warnings in Optware installation since it pertains to this. It is based on the work of Seongbae and the above articles. What you end up with is a network time machine which appears to be quite authentic (like a Time Capsule) since it uses Avahi so the drive will show up in the sidebar. This will not work with a root password to log into the Time Machine. to:
This supplement should work for most plug computers (Pogoplug V1, V2, Pro, Biz, Dockstars, etc.). Please see warnings in Optware installation since it pertains to this. It is based on the work of Seongbae and the above articles. What you end up with is a network time machine which appears to be quite authentic (like a Time Capsule) since it uses Avahi so the drive will show up in the sidebar. This will not work with a root password to log into the Time Machine. January 03, 2011, at 12:25 PM
by -- Plug Time Machine
Changed lines 193-194 from:
This supplement should work for most plug computers. Please see warnings in Optware installation since it pertains to this. It is based on the work of Seongbae and the above articles. What you end up with is a network time machine which appears to be quite authentic since it uses Avahi so the drive will show up in the sidebar. This will not work with a root password to log into the Time Machine. to:
This supplement should work for most plug computers. Please see warnings in Optware installation since it pertains to this. It is based on the work of Seongbae and the above articles. What you end up with is a network time machine which appears to be quite authentic (like a Time Capsule) since it uses Avahi so the drive will show up in the sidebar. This will not work with a root password to log into the Time Machine. January 03, 2011, at 12:17 PM
by -- Plug Time Machine
Changed lines 219-220 from:
Just like the preceding section. Edit the "/opt/etc/netatalk/AppleVolumes.default" file and add the following line at the bottom (The options:tm is so that your Mac will treat the Plug like a Time Machine). to:
Just like the preceding section. Edit the "/opt/etc/netatalk/AppleVolumes.default" file and add the following line at the bottom (The options:tm is so that your Mac will treat the Plug like a Time Machine). Changed lines 227-228 from:
Verify that it exists and contains: to:
Verify that the "/opt/etc/dbus-1/system.d/avahi-dbus.conf" file exists and contains: January 03, 2011, at 12:09 PM
by -- Plug Time Machine
Changed lines 219-220 from:
Just like the preceding section. Edit the "/opt/etc/netatalk/AppleVolumes.default" file and add the following line at the bottom (The options:tm is so that your Mac will treat the Plug like a Time Machine). to:
Just like the preceding section. Edit the "/opt/etc/netatalk/AppleVolumes.default" file and add the following line at the bottom (The options:tm is so that your Mac will treat the Plug like a Time Machine). Changed lines 223-224 from:
Unlike the preceding section, do not edit the afpd.conf. In fact make sure that there are no functional lines and everything is commented. The authentication will default correctly. to:
Unlike the preceding section, do not edit the afpd.conf. In fact make sure that there are no functional lines and everything is commented. The authentication will default correctly. Changed lines 226-227 from:
Verify that it exists and contains: to:
Verify that it exists and contains: Changed lines 258-259 from:
We will now change to "/opt/etc/avahi/services/" directory and create an afpd.service file which should contain: to:
We will now change to "/opt/etc/avahi/services/" directory and create an afpd.service file which should contain: January 03, 2011, at 12:06 PM
by -- Plug Time Machine
Changed lines 195-196 from:
You should use new hard drive formatted in ext2/ext3 depending if you want a journaled file system (recommeded). It will be mounted on "/tmp/timemachine". I have tested this with a username with spaces. If you install a package and there are errors/warnings, take care of this or the install will not work. I had to rename a file in a directory under "/opt/etc/" to do this. to:
You should use a new hard drive formatted in ext2/ext3 depending if you want a journaled file system (recommeded). It will be mounted on "/tmp/timemachine". I have tested this with a username with spaces. If you install a package and there are errors/warnings, take care of this or the install will not work. I had to rename a file in a directory under "/opt/etc/" to do this. Changed lines 215-216 from:
If you want to use your OSX username which probably contains spaces. You can do this by using quotes (adduser "Some User Name" and afppasswd "Some User Name"). to:
If you want to use your OSX username which probably contains spaces. You can do this by using quotes (adduser "Some User Name" and afppasswd "Some User Name"). Changed lines 218-220 from:
Just like the preceding section. Edit the "/opt/etc/netatalk/AppleVolumes.default" file and add the following line at the bottom. The options:tm is so that your Mac will treat the Plug like a Time Machine.\\ to:
Just like the preceding section. Edit the "/opt/etc/netatalk/AppleVolumes.default" file and add the following line at the bottom (The options:tm is so that your Mac will treat the Plug like a Time Machine). Added line 222:
January 03, 2011, at 11:58 AM
by -- Plug Time Machine
Changed lines 202-203 from:
We need to set up some users and groups. If I use a group or user number that is used, choose another one. You can verify with "cat /etc/passwd" or "cat /etc/group". to:
We need to set up some users and groups. If I use a group or user number that is used, choose another one. You can verify with "cat /etc/passwd" or "cat /etc/group". Changed lines 209-210 from:
We will use afppasswd to create an afp password for someusername for authentication. The utility afppasswd checks /etc/passwd to make sure that the username you use exists. If there is no afppasswd file in /opt/etc/netatalk, afppasswd will error out. to:
We will use afppasswd to create an afp password for someusername for authentication. The utility afppasswd checks /etc/passwd to make sure that the username you use exists. If there is no afppasswd file in /opt/etc/netatalk, afppasswd will error out. Changed lines 215-216 from:
If you want to use your OSX username which probably contains spaces. You can do this by using quotes (adduser "Some User Name" and afppasswd "Some User Name"). to:
If you want to use your OSX username which probably contains spaces. You can do this by using quotes (adduser "Some User Name" and afppasswd "Some User Name"). January 03, 2011, at 11:56 AM
by -- Plug Time Machine
Changed lines 195-201 from:
You should use new hard drive formatted in ext2/ext3 depending if you want a journaled file system (recommeded). It will be mounted on /tmp/timemachine. I have tested this with a username with spaces. If you install a package and there are errors/warnings, take care of this or the install will not work. I had to rename a file in a directory under /opt/etc/ to do this. "ipkg install netatalk" to:
You should use new hard drive formatted in ext2/ext3 depending if you want a journaled file system (recommeded). It will be mounted on "/tmp/timemachine". I have tested this with a username with spaces. If you install a package and there are errors/warnings, take care of this or the install will not work. I had to rename a file in a directory under "/opt/etc/" to do this. "ipkg install netatalk" Changed lines 204-208 from:
"addgroup -g 84 avahi" to:
"addgroup -g 84 avahi" Changed lines 211-214 from:
"cd /opt/etc/netatalk" to:
"cd /opt/etc/netatalk" January 03, 2011, at 11:50 AM
by -- Plug Time Machine
Changed lines 193-194 from:
This supplement should work for most plug computers. Please see warnings in Main.PlugCompters? since it pertains to this. It is based on the work of Seongbae and the above articles. What you end up with is a network time machine which appears to be quite authentic since it uses Avahi so the drive will show up in the sidebar. This will not work with a root password to log into the Time Machine. to:
This supplement should work for most plug computers. Please see warnings in Optware installation since it pertains to this. It is based on the work of Seongbae and the above articles. What you end up with is a network time machine which appears to be quite authentic since it uses Avahi so the drive will show up in the sidebar. This will not work with a root password to log into the Time Machine. January 03, 2011, at 11:47 AM
by -- Plug Time Machine
Changed lines 193-194 from:
This supplement should work for most plug computers. Please see warnings in Plug Computers Optware Installation? since it pertains to this. It is based on the work of Seongbae and the above articles. What you end up with is a network time machine which appears to be quite authentic since it uses Avahi so the drive will show up in the sidebar. This will not work with a root password to log into the Time Machine. to:
This supplement should work for most plug computers. Please see warnings in Main.PlugCompters? since it pertains to this. It is based on the work of Seongbae and the above articles. What you end up with is a network time machine which appears to be quite authentic since it uses Avahi so the drive will show up in the sidebar. This will not work with a root password to log into the Time Machine. January 03, 2011, at 11:43 AM
by -- Plug Time Machine
Changed lines 193-194 from:
This supplement should work for most plug computers. Please see warnings in since it pertains to this. It is based on the work of Seongbae and the above articles. What you end up with is a network time machine which appears to be quite authentic since it uses Avahi so the drive will show up in the sidebar. This will not work with a root password to log into the Time Machine. to:
This supplement should work for most plug computers. Please see warnings in Plug Computers Optware Installation? since it pertains to this. It is based on the work of Seongbae and the above articles. What you end up with is a network time machine which appears to be quite authentic since it uses Avahi so the drive will show up in the sidebar. This will not work with a root password to log into the Time Machine. January 03, 2011, at 11:38 AM
by -- Plug Time Machine
Added line 208:
Added line 210:
Added line 214:
Changed line 218 from:
Just like the preceding section. Edit the /opt/etc/netatalk/AppleVolumes?.default file and add the following line at the bottom. The options:tm is so that your Mac will treat the Plug like a Time Machine.\\
to:
Just like the preceding section. Edit the "/opt/etc/netatalk/AppleVolumes.default" file and add the following line at the bottom. The options:tm is so that your Mac will treat the Plug like a Time Machine.\\ Added line 221:
Changed lines 271-272 from:
We need to edit "/opt/etc/avahi/avahi-daemon.conf" and add an entry for "host-name=PlugTime?", where PlugTime? is whatever you choose to name your Time Machine host plug (try to make it different from your current hostname - "uname -n"). Uncomment "enable-dbus=yes". to:
We need to edit "/opt/etc/avahi/avahi-daemon.conf" and add an entry for "host-name=PlugTime", where PlugTime is whatever you choose to name your Time Machine host plug (try to make it different from your current hostname - "uname -n"). Uncomment "enable-dbus=yes". Changed lines 275-276 from:
Create the "/tmp/timemachine" directory with "mkdir /tmp/timemachine" and mount your ext2/ext3 drive that you want to use for the Time Machine back-up. Then, Create an empty file named ".com.apple.timemachine.supported" in the top directory of the drive with "touch .com.apple.timemachine.supported" in the top directory. to:
Create the "/tmp/timemachine" directory with "mkdir /tmp/timemachine" and mount your ext2/ext3 drive that you want to use for the Time Machine back-up. Then, Create an empty file named ".com.apple.timemachine.supported" in the top directory of the drive with "touch .com.apple.timemachine.supported" in the top directory. January 03, 2011, at 11:31 AM
by -- Plug Time Machine
Changed lines 191-364 from:
to:
Supplement for Plug ComputersThis supplement should work for most plug computers. Please see warnings in since it pertains to this. It is based on the work of Seongbae and the above articles. What you end up with is a network time machine which appears to be quite authentic since it uses Avahi so the drive will show up in the sidebar. This will not work with a root password to log into the Time Machine. "ipkg install netatalk" We need to set up some users and groups. If I use a group or user number that is used, choose another one. You can verify with "cat /etc/passwd" or "cat /etc/group". "addgroup -g 84 avahi" Time to edit some config files. <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"> <busconfig> <!-- Only root or user avahi can own the Avahi service --> <policy user="avahi"> <allow own="org.freedesktop.Avahi"/> </policy> <policy user="root"> <allow own="org.freedesktop.Avahi"/> </policy> <!-- Allow anyone to invoke methods on Avahi server, except SetHostName --> <policy context="default"> <allow send_destination="org.freedesktop.Avahi"/> <allow receive_sender="org.freedesktop.Avahi"/> <deny send_interface="org.freedesktop.Avahi.Server" send_member="SetHostName"/> </policy> <!-- Allow everything, including access to SetHostName to users of the group "netdev" <policy group="netdev"> <allow send_destination="org.freedesktop.Avahi"/> <allow receive_sender="org.freedesktop.Avahi"/> </policy> --> </busconfig> We will now change to "/opt/etc/avahi/services/" directory and create an afpd.service file which should contain: <?xml version="1.0" standalone='no'?><!--*-nxml-*--> <!DOCTYPE service-group SYSTEM "avahi-service.dtd"> <service-group> <name replace-wildcards="yes">%h</name> <service> <type>_afpovertcp._tcp</type> <port>548</port> </service> <service> <type>_device-info._tcp</type> <port>0</port> <txt-record>model=Xserve</txt-record> </service> </service-group> We need to edit "/opt/etc/avahi/avahi-daemon.conf" and add an entry for "host-name=PlugTime?", where PlugTime? is whatever you choose to name your Time Machine host plug (try to make it different from your current hostname - "uname -n"). Uncomment "enable-dbus=yes". Change to the "/opt/etc/init.d" subdirectory and create two start files. There should be a start file for dbus, but none for avahi and afpd. The one for dbus "S20dbus" needs modification to work properly. So edit "S20dbus" and make the modification below: shut_it_down()
{
echo -n "Stopping $DESC: "
if [ -e $PIDFILE ]; then
PIDNUM=`cat $PIDFILE`
rm -f $PIDFILE
kill $PIDNUM
else
killall ${DAEMON}
fi
echo "$NAME."
rm -f $PIDFILE
}Create this start file "S52avahi" for avahi: #!/bin/sh #start avahi-daemon /opt/sbin/avahi-daemon -D return 1 Create this start file "S81afpd" for afpd: #!/bin/sh # Start afpd /opt/sbin/afpd return 1 Create a script "mount_tm" (based on Openpogo mount_opt) in "/opt/sbin" to mount the proper drive in "/tmp/timemachine", give it full access, and run the scripts. If you want to use a journaled file system drive, substitute ext3 for the ext2. Of course making sure that your drive is ext2 or ext3 correspondingly: #!/bin/bash
#
mkdir /tmp/timemachine
mount -t ext2 -o rw,nosuid,nodev,exec,noatime,sync /dev/sda1 /tmp/timemachine
if [ ! -f /tmp/timemachine/.com.apple.timemachine.supported ]
then
{
umount /tmp/timemachine
mount -t ext2 -o rw,nosuid,nodev,exec,noatime,sync /dev/sdb1 /tmp/timemachine
if [ ! -f /tmp/timemachine/.com.apple.timemachine.supported ]
then
{
umount /tmp/timemachine
mount -t ext2 -o rw,nosuid,nodev,exec,noatime,sync /dev/sdc1 /tmp/timemachine
if [ ! -f /tmp/timemachine/.com.apple.timemachine.supported ]
then
{
umount /tmp/timemachine
mount -t ext2 -o rw,nosuid,nodev,exec,noatime,sync /dev/sdd1 /tmp/timemachine
if [ ! -f /tmp/timemachine/.com.apple.timemachine.supported ]
then
{
umount /tmp/timemachine
}
else
{
umount /tmp/.cemnt/mnt_sdd1
}
fi
}
else
{
umount /tmp/.cemnt/mnt_sdc1
}
fi
}
else
{
umount /tmp/.cemnt/mnt_sdb1
}
fi
}
else
{
umount /tmp/.cemnt/mnt_sda1
}
fi
/bin/chmod 777 /tmp/timemachine
rm -f /opt/var/run/dbus/pid
/opt/etc/init.d/S20dbus start
/opt/etc/init.d/S52avahi
/opt/etc/init.d/S81afpdOn all the scripts, make sure to set the permissions so that they are executable with "chmod 755 scriptname" where scriptname is the name of the script. You can then include "mount_tm" in the "/etc/init.d/rcS" start up script so that it will be executed on start up. When you shut down your plug computer or reboot, it would probably be a good idea to kill the processes and umount the drive. November 28, 2009, at 07:43 AM
by -- Snow Leopard Tips3
Changed lines 5-6 from:
UPDATE Again: There are some issues with the sparsebundle on Snow Leopard (10.5.x). My Time Machine continued working after an upgrade from Leopard to Snow Leopard, but when trying to set this up from scratch on Snow Leopard, it did not work. See http://www.macosxhints.com/article.php?story=20090905212640957 for information on how to get this working on Snow Leopard. to:
UPDATE Again: There are some issues with the sparsebundle on Snow Leopard (10.6.x). My Time Machine continued working after an upgrade from Leopard to Snow Leopard, but when trying to set this up from scratch on Snow Leopard, it did not work. See http://www.macosxhints.com/article.php?story=20090905212640957 for information on how to get this working on Snow Leopard. November 28, 2009, at 07:28 AM
by -- Snow Leopard Tips2
Changed lines 5-6 from:
UPDATE2?: There are some issues with the sparsebundle on Snow Leopard (10.5.x). My Time Machine continued working after an upgrade from Leopard to Snow Leopard, but when trying to set this up from scratch on Snow Leopard, it did not work. See http://www.macosxhints.com/article.php?story=20090905212640957 for information on how to get this working on Snow Leopard. to:
UPDATE Again: There are some issues with the sparsebundle on Snow Leopard (10.5.x). My Time Machine continued working after an upgrade from Leopard to Snow Leopard, but when trying to set this up from scratch on Snow Leopard, it did not work. See http://www.macosxhints.com/article.php?story=20090905212640957 for information on how to get this working on Snow Leopard. November 28, 2009, at 07:27 AM
by -- Snow Leopard Tips
Added lines 5-6:
UPDATE2?: There are some issues with the sparsebundle on Snow Leopard (10.5.x). My Time Machine continued working after an upgrade from Leopard to Snow Leopard, but when trying to set this up from scratch on Snow Leopard, it did not work. See http://www.macosxhints.com/article.php?story=20090905212640957 for information on how to get this working on Snow Leopard. November 03, 2009, at 11:38 PM
by -- edit
Changed lines 194-197 from:
After you have replaced the faulty hardware and have booted from the install disk, you will be at a menu that lets you do a few basic things (disk util, terminal, etc...). Before selecting to restore from a time machine, you have to manually mount the time machine volume since its not a locally attached volume. Make sure you are connected to the network. If you are using wired network, the install disk has likely already obtained a DHCP IP and you are good. If you choose to go the (slower) wireless route, connect using the wireless icon at the top right of the screen, then proceed below. The following commands assume you used the AFP method above. I haven't tried, but switching the mount command to mount an smb volume should be all that's needed if you used smb instead. to:
After you have replaced the faulty hardware and have booted your mac from the install disk, you will be at a menu that lets you do a few basic things (disk util, terminal, etc...). Before selecting to restore from a time machine, you have to manually mount the time machine volume since its not a locally attached volume. Make sure you are connected to the network. If you are using wired network, the install disk has likely already obtained a DHCP IP and you are good. If you choose to go the (slower) wireless route, connect using the wireless icon at the top right of the screen, then proceed below. The following commands assume you used the AFP method above. I haven't tried, but switching the mount command to mount an smb volume should be all that's needed if you used smb instead. Start a terminal section by selecting Terminal from the tools menu. November 03, 2009, at 11:36 PM
by -- Included networking info to restore section
Changed lines 194-195 from:
After you have replaced the faulty hardware and have booted from the install disk, you will be at a menu that lets you do a few basic things (disk util, terminal, etc...). Before selecting to restore from a time machine, you have to manually mount the time machine volume since its not a locally attached volume. to:
After you have replaced the faulty hardware and have booted from the install disk, you will be at a menu that lets you do a few basic things (disk util, terminal, etc...). Before selecting to restore from a time machine, you have to manually mount the time machine volume since its not a locally attached volume. Make sure you are connected to the network. If you are using wired network, the install disk has likely already obtained a DHCP IP and you are good. If you choose to go the (slower) wireless route, connect using the wireless icon at the top right of the screen, then proceed below. November 03, 2009, at 11:34 PM
by -- Added restore instructions
Added lines 190-211:
How To Restore To New DiskThis howto is great, but it was lacking a section on how to do a restore to a brand new drive. This section isn't needed if you are just restoring an old copy of a file to an already running system, but if your HDD crashed (like mine did!), you have to do a few special steps to be able to restore from your time machine. After you have replaced the faulty hardware and have booted from the install disk, you will be at a menu that lets you do a few basic things (disk util, terminal, etc...). Before selecting to restore from a time machine, you have to manually mount the time machine volume since its not a locally attached volume. The following commands assume you used the AFP method above. I haven't tried, but switching the mount command to mount an smb volume should be all that's needed if you used smb instead.
And thats it! Exit out of terminal, and select restore from time machine and it should detect your time machine backup disk created above. You will be asked to pick a destination volume, so make sure you have already partitioned your new disk. Happy restoring! July 08, 2008, at 01:29 PM
by -- Added \"return 1\" to end of rc.local script example
Added line 177:
return 1 July 01, 2008, at 05:13 AM
by --
Added lines 68-69:
You need to be running OpenSlug, or Unslung, or anything that's not the stock firmware. July 01, 2008, at 05:10 AM
by -- Finally got it right, I hope...
Changed line 84 from:
to:
Changed lines 95-98 from:
to:
Changed lines 119-122 from:
to:
July 01, 2008, at 05:06 AM
by --
Changed lines 79-82 from:
case sensitive = True
default case = upper
preserve case = no
short preserve case = no
to:
Changed lines 88-93 from:
$ ls -la
total 4
drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 .
drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 ..
-rwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 .MacBook?_001a45bc231a.sparsebundle
drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 MacBook?_001a45bc231a.sparsebundle
to:
Changed lines 100-107 from:
$ ls -la
total 6
drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 .
drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 ..
-rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:00 .MacBook?_001a45bc231a.sparsebundle
-rwxr-xr-x 1 smbuser smbuser 16 May 23 12:25 .macbook_001a45bc231a.sparsebundle
-rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:00 MacBook?_001a45bc231a.sparsebundle
drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 macbook_001a45bc231a.sparsebundle
to:
Changed lines 109-117 from:
$ cd macbook_001a45bc231a.sparsebundle
$ ls -la
total 6
drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 .
drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 ..
-rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 Info.bckup
-rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 Info.plist
drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 bands
-rwxr-xr-x 1 smbuser smbuser 1276 May 23 12:25 token
to:
Changed lines 124-133 from:
$ ls -la
total 6
drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 .
drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 ..
-rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 info.bckup
-rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:05 Info.bckup
-rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 info.plist
-rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:05 Info.plist
drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 bands
-rwxr-xr-x 1 smbuser smbuser 1276 May 23 12:25 token
to:
July 01, 2008, at 05:02 AM
by -- Cleanup. Wish the \"preview\" button worked.
Changed lines 79-82 from:
to:
case sensitive = True
default case = upper
preserve case = no
short preserve case = no
Changed lines 88-93 from:
$ ls -la total 4 drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 . drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 .. -rwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 .MacBook?_001a45bc231a.sparsebundle drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 MacBook?_001a45bc231a.sparsebundle to:
$ ls -la
total 4
drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 .
drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 ..
-rwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 .MacBook?_001a45bc231a.sparsebundle
drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 MacBook?_001a45bc231a.sparsebundle
Changed lines 100-107 from:
$ ls -la total 6 drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 . drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 .. -rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:00 .MacBook?_001a45bc231a.sparsebundle -rwxr-xr-x 1 smbuser smbuser 16 May 23 12:25 .macbook_001a45bc231a.sparsebundle -rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:00 MacBook?_001a45bc231a.sparsebundle drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 macbook_001a45bc231a.sparsebundle to:
$ ls -la
total 6
drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 .
drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 ..
-rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:00 .MacBook?_001a45bc231a.sparsebundle
-rwxr-xr-x 1 smbuser smbuser 16 May 23 12:25 .macbook_001a45bc231a.sparsebundle
-rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:00 MacBook?_001a45bc231a.sparsebundle
drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 macbook_001a45bc231a.sparsebundle
Changed lines 109-117 from:
$ cd macbook_001a45bc231a.sparsebundle $ ls -la total 6 drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 . drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 .. -rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 Info.bckup -rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 Info.plist drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 bands -rwxr-xr-x 1 smbuser smbuser 1276 May 23 12:25 token to:
$ cd macbook_001a45bc231a.sparsebundle
$ ls -la
total 6
drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 .
drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 ..
-rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 Info.bckup
-rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 Info.plist
drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 bands
-rwxr-xr-x 1 smbuser smbuser 1276 May 23 12:25 token
Changed lines 124-133 from:
$ ls -la total 6 drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 . drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 .. -rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 info.bckup -rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:05 Info.bckup -rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 info.plist -rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:05 Info.plist drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 bands -rwxr-xr-x 1 smbuser smbuser 1276 May 23 12:25 token to:
$ ls -la
total 6
drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 .
drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 ..
-rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 info.bckup
-rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:05 Info.bckup
-rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 info.plist
-rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:05 Info.plist
drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 bands
-rwxr-xr-x 1 smbuser smbuser 1276 May 23 12:25 token
July 01, 2008, at 04:58 AM
by -- Added \\\"Advanced Setup with Samba (SMB)\\\".
Changed line 29 from:
"macbook_001a45bc231a" to:
Changed line 39 from:
hdiutil create -size 140g -fs HFS+J -volname "Backup Drive" macbook_001a45bc231a.sparsebundle to:
Changed lines 60-142 from:
to:
Advanced Setup with Samba (SMB)This hint is for more advanced users of Samba. If you're not comfortable with the theory and instructions below, take a look at the next section, "Alternate Setup with AFP (Apple Filing Protocol)". As noted in GettingStartedWithSamba in the "Transfer Speeds with Many Files in the Same Directory" section, Samba is very slow when you have many files in the same directory. This is what Time Machine does, so Time Machine backups are very slow. There is a way to speed things up: turn off case sensitivity in Samba, and rename all your files to be upper- or lower-case. For instructions and more info, see http://www.samba.org/samba/docs/man/Samba-Guide/HA.html#id403899 To do this for your Time Machine share, try the following:
OK, so now we have your first backup! It's slow, but we know that it works. Here's how to speed things up:
$ ls -la total 4 drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 . drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 .. -rwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 .MacBook?_001a45bc231a.sparsebundle drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 MacBook?_001a45bc231a.sparsebundle
$ ls -la total 6 drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 . drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 .. -rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:00 .MacBook?_001a45bc231a.sparsebundle -rwxr-xr-x 1 smbuser smbuser 16 May 23 12:25 .macbook_001a45bc231a.sparsebundle -rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:00 MacBook?_001a45bc231a.sparsebundle drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 macbook_001a45bc231a.sparsebundle
$ cd macbook_001a45bc231a.sparsebundle $ ls -la total 6 drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 . drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 .. -rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 Info.bckup -rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 Info.plist drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 bands -rwxr-xr-x 1 smbuser smbuser 1276 May 23 12:25 token
$ ls -la total 6 drwxr-xr-x 1 smbuser smbuser 0 Nov 15 2007 . drwxr-xr-x 1 smbuser smbuser 0 Jan 1 1970 .. -rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 info.bckup -rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:05 Info.bckup -rwxr-xr-x 1 smbuser smbuser 510 May 23 12:25 info.plist -rwxr-xr-x 1 smbuser smbuser 0 Jun 30 11:05 Info.plist drwxr-xr-x 1 smbuser smbuser 0 May 23 12:25 bands -rwxr-xr-x 1 smbuser smbuser 1276 May 23 12:25 token
So, how does it work? Here's how:
June 29, 2008, at 10:59 PM
by -- It\'s Filing protocol not File protocol
Changed lines 3-4 from:
UPDATE: Read the additional section on AFP (Apple File Protocol). Running Time Machine backups over AFP seems to work a lot better than over Samba (SMB). to:
UPDATE: Read the additional section on AFP (Apple Filing Protocol). Running Time Machine backups over AFP seems to work a lot better than over Samba (SMB). Changed lines 61-62 from:
Alternate Setup with AFP (Apple File Protocol)to:
Alternate Setup with AFP (Apple Filing Protocol)June 29, 2008, at 02:32 PM
by -- Formatting update...
Changed lines 71-72 from:
to:
Changed lines 85-88 from:
[@
to:
* Create or edit /unslung/rc.local in your favorite editor
* At a minimum have the following lines in your file:
[@
Changed lines 95-97 from:
[@
to:
* Make the file executable by running
[@
June 29, 2008, at 02:27 PM
by -- Added instructions for setting up Time Machine with AFP
Added lines 3-4:
UPDATE: Read the additional section on AFP (Apple File Protocol). Running Time Machine backups over AFP seems to work a lot better than over Samba (SMB). Added lines 7-8:
Basic Setup with Samba (SMB)Changed lines 61-63 from:
Works great for me! to:
Alternate Setup with AFP (Apple File Protocol)I've found that Time Machine backups work much better over AFP. They run much faster and appear to be a little more reliable and tolerant to interruptions (like putting the computer to sleep). So if you have an unslung box, I'd recommend going this route. For my setup, I don't configure any user security. Some forums mention difficulties with getting user security to work with the NSLU2 and since my setup doesn't require it, I didn't try it. These instructions are for Unslung 6.10, but I'd imagine they apply to most distributions other than the stock linksys firmware.
ipkg install netatalk
/share/flash/data/public "Time Machine"
"Time Capsule" -uamlist uams_guest.so
#!/bin/sh # Start afpd /opt/sbin/afpd
chmod 755 /unslung/rc.local Reboot, and AFP should be running. Place your sparsebundle file in the shared directory, and follow the remaining directions in the "Basic Setup with Samba" section. May 25, 2008, at 04:36 PM
by --
Changed lines 28-29 from:
The next step is to create a disk image to use for the backups, which will created on your mac and then moved later to your NSLU2 disk: to:
The next step is to create a disk image to use for the backups, which will be created on your mac and then moved later to your NSLU2 disk: May 25, 2008, at 02:41 AM
by -- some language consistency edits
Changed line 18 from:
to:
May 25, 2008, at 02:40 AM
by -- Formatting updates
Changed lines 7-16 from:
- Open System Preferences - Click on "Sharing" - Note the "Computer Name" - Open a terminal window in OSX - Run the command "ifconfig en0 | grep ether" - This will produce a line similar to the following: ether 00:1a:45:bc:23:1a - Combine the hostname and the mac address (without the ":"s) to create the backup identifier name as such: to:
Changed lines 21-22 from:
For example, to:
@] For example,
[@
Changed lines 26-27 from:
to:
@] Changed lines 30-33 from:
- Open a terminal window - Change into your desktop directory: "cd ~/Desktop" (or whatever directory you want to create the backup file) - Run the following command, and change the "size" parameter to be the maximum size of the backup, and change the name of the sparsebundle file to match the identifier we came up with earlier: to:
[@
Changed lines 36-37 from:
to:
@] Changed lines 40-43 from:
- Copy the sparsebundle we just created from your desktop to a share on your NSLU2. I created a share that only contained the sparsebundle, so I don't know if you can put the file in a share with other files. - If you have OS X 10.5.2 or later then you DON'T need to do this step (skip to the next step). Enter the following command into the terminal window: to:
[@
Changed lines 46-55 from:
- Open the network share that you copied the sparsebundle file to - Double click on the sparsebundle file to mount it - Open System Preferences - Click Time Machine - Turn Time Machine on if it isn't already - Click on "Change Disk" - Select the mounted backup disk to:
@]
Deleted lines 59-63:
May 25, 2008, at 02:00 AM
by -- How to set up the NSLU2 to do Time Machine Backups with an OS X Leopard computer
Added lines 1-56:
For those of you running Leopard, you can use your NSLU2 as a backup drive for Time Machine, effectively making a "Time Capsule". Unfortunately there is a little bit of work required to get it going, but once it is set up it runs pretty well. I am running Unslung 6.10. I'd imagine that this would work on just about any of the possible OS choices out there, even the stock Linksys firmware, but I haven't tested it, so YMMV. The first step is to gather information about your system that we will need later: - Open System Preferences - Click on "Sharing" - Note the "Computer Name" - Open a terminal window in OSX - Run the command "ifconfig en0 | grep ether" - This will produce a line similar to the following: ether 00:1a:45:bc:23:1a - Combine the hostname and the mac address (without the ":"s) to create the backup identifier name as such: "hostname_macaddr" For example, "macbook_001a45bc231a" The next step is to create a disk image to use for the backups, which will created on your mac and then moved later to your NSLU2 disk: - Open a terminal window - Change into your desktop directory: "cd ~/Desktop" (or whatever directory you want to create the backup file) - Run the following command, and change the "size" parameter to be the maximum size of the backup, and change the name of the sparsebundle file to match the identifier we came up with earlier: hdiutil create -size 140g -fs HFS+J -volname "Backup Drive" macbook_001a45bc231a.sparsebundle The final step is to copy the sparsebundle to your NAS and configure Time Machine: - Copy the sparsebundle we just created from your desktop to a share on your NSLU2. I created a share that only contained the sparsebundle, so I don't know if you can put the file in a share with other files. - If you have OS X 10.5.2 or later then you DON'T need to do this step (skip to the next step). Enter the following command into the terminal window: defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes? 1 - Open the network share that you copied the sparsebundle file to - Double click on the sparsebundle file to mount it - Open System Preferences - Click Time Machine - Turn Time Machine on if it isn't already - Click on "Change Disk" - Select the mounted backup disk Works great for me!
view ·
edit ·
print ·
history ·
Last edited by Scheb.
Based on work by Scheb, OddballHero, Mike Machado, mkurtz, and Smee Jenkins. Originally by mkurtz. Page last modified on March 06, 2013, at 06:54 AM
|