Re: moving Time Machine disc to Airport Extreme?

On Feb 18, 2013, at 3:05 PM, David Herren <[email protected]> wrote:

>=20
> On Feb 18, 2013, at 4:42 PM, objectwerks inc =
<chad+macosx-AU1NHruoRJaEK/[email protected]> wrote:
>=20
> Hey Chad, thanks for the quick come back!
>=20
>> I suspect it will work but you will have to "start over" with the =
backups because the way that TM uses a remote disk is different than a =
local disk.  You should also have to go into TM on the laptop and tell =
it to use the remote disk.
>=20
> That's unfortunate given the slow performance of air backups, but if I =
can achieve a situation where my daughter's school papers get backed up =
with minimal, and ideally, zero, intervention on her part, it will be =
worth it.

It's possible to seed the target hard drive by manually creating a =
sparse bundle disk image, mounting it, setting that as the backup disk. =
After the first large backup is finished, you can then put the drive on =
the network. The disk image needs a specific file name, must be in root =
directory of the drive. There are recipes to do this floating about.

> I didn't realize that file server backups were an option yet. It =
didn't work when I first attempted it back in 2008 or so.

It's been possible for quite a while. I've used it reliably until 10.8.2 =
and now it seems to be broken. Two computers, both clean installed =
10.8.2, one has an external disk using Core Storage, encrypted, HFSJ. If =
the drive is made available via File Sharing, backup stalls for ~15 =
minutes with no activity, with an estimated initial backup time of 6 =
days for merely 55GB of data.

Conversely, I can network copy files consistently at 30MB/s over AFP and =
100MB/s over NFS. If the drive is directly connected to the source, Time =
Machine backups proceed fine. I haven't done enough regression to figure =
out what might be the cause, but because of the clean installs, works =
when direct connected, file sharing performance is normal, that there's =
a bug.


Chris Murphy=