 |
 |
 |
 |
 |
 |
 |
 |
|
|||||||||||
|
|
|
|
|
|
|
|
|
#2
09-09-2009, 02:30 PM
|
||||
|
||||
|
Because we cannot authorize against a network drive sufficiently to ensure proper metadata preservation, etc. In addition, a network volume is a 'virtualized' file system, where it might 'act' like HFS+, but it's actually NTFS, EXT3, FAT32, etc.
Supporting all those specialized and not-at-all-the-same disk formats (and all the potential problems in the network transport layers) wasn't something I wanted to do. That's also why Time Machine uses an image when backing up to a network volume, by the way: the image acts like a local drive, and a real file system, which puts everything on the same level...
__________________
--Dave Nanian 
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Back up a network volume to a local volume | Albee | General | 3 | 07-31-2009 10:36 AM |
| Backing up connected network drives | bmathers | General | 5 | 05-08-2008 05:24 PM |
| A SuperDuper Back Up Strategy | Bagelturf | General | 3 | 09-09-2007 01:23 PM |
| Back up to secondary HDD over network? | Paul_G | General | 18 | 07-17-2007 07:08 AM |
| Can I schedule back up of 2 different drives? | randyburleson | General | 3 | 11-14-2006 05:13 PM |
Threaded Mode