And I have been using xtar on the OSX clients for years with no problems
(10.2.x - 10.4.8). You may want to try it.
cheers,
ski
Torsten Sadowski wrote:
>> What do i miss if I don't backup extended attributes?
>>
>> John
>>
> You miss the Resource Fork which will render all older MacOS (ie Cl
> What do i miss if I don't backup extended attributes?
>
> John
>
You miss the Resource Fork which will render all older MacOS (ie Classic)
programs unusable and might even destroy data files of those programs.
Incidentally I am using backuppc 2.1.2 with OSX 10.4 and native tar without
any big
Brien Dieterle wrote:
> The ".filename" stuff is called AppleDouble and I think it preserves
> metadata as well in there.
>
> Are you also getting a ton of xfer errors as below? (I did)
> /usr/bin/tar: /tmp/tar.md.Fif1QE: Cannot stat: No such file or directory
> /usr/bin/tar: /tmp/tar.md.b7XePQ: C
The ".filename" stuff is called AppleDouble and I think it preserves
metadata as well in there.
Are you also getting a ton of xfer errors as below? (I did)
/usr/bin/tar: /tmp/tar.md.Fif1QE: Cannot stat: No such file or directory
/usr/bin/tar: /tmp/tar.md.b7XePQ: Cannot stat: No such file or di
I'm running 3.0.0 and noticed that Mac OSX clients take way longer to
do an incremental backup that I would expect given how many files have
changed. I dug around in the logs and found that tar on the mac
copies extended attributes as ._filename files and totally ignores the
--newer flag w
