I only have one drive at present. Of course, I'd rather have more. If I had more drives, I'd clone and Time Machine to each one since the sweet spot size for HDDs can hold both. TM backups are all in one directory that I can easily exclude from a restore if needed. I could separate them using partitioning, but that would introduce the complication of having to allocate the correct amount of space to each, and my backup policies might change which takes more space.It's a bad idea to use same drive for both backups:
1. If it has hardware failure you lose all backups.
2. It creates more complex scenario for restoring files or whole system.
3. If the volume becomes corrupt good luck trying to get your data out of it...
Its much safer to have several drives for backups, if one dies no harm done.
[doublepost=1454037867][/doublepost]
I've seen weird problems backing up to a Mac running OS X Server and hosting volumes over AFP. For one, it fails with an unknown error if I try to back up over my VPN (which is hosted on that Mac server). I don't even know how the VPN could affect it; that's abstracted to the application layer anyway.Time Machine only uses a sparse bundle if you are doing a networked backup, like to a Time Capsule or NAS device. I don't think there is anything inherently wrong with sparse bundles, but I have read quite a few reports form users having trouble with networked Time Machine backups on third parry (non-Apple) NAS devices. I've used Time Machine with an Apple Time Capsule for years and never had any troubles with it.
I suspect the problem with third party devices is their implementation of AFP (Apple Filing Protocol) that is required for Time Machine over the network.
Last edited: