View Full Version : Restore speed from sparse image ..

11-28-2009, 01:37 PM

Is it normal that a not so big (▒22GB) sparse image located on a USB2 external drive takes 4 hours to restore back to an Imac G5 ?



11-28-2009, 05:10 PM
It kind of depends on the speed of the device you're restoring from, memory, etc...

11-28-2009, 05:25 PM
Like I said the sparse image was on an attached USB 2drive and the copy was made to my iMac G5 (1.6GHZ - 2GB of memory) while the computer was running the install CD.

What other informations do you need to give an idea about the restore time required ? Is 4 hours normal or should I expect it to be faster ?

11-28-2009, 05:31 PM
Well -- it's hard to know what's normal in these situations. Is it progressing?

11-28-2009, 05:51 PM
For sure ... I have been on this since morning. It took a bit of time to pay around with install DVDs and SD procedures to mount the sparse image. The restore took at least 4 hours. Just wondered if the time could be improve some way. Would it take less time if the restore was made from a direct FW400 or 800 drive sparse image ?

BTW why is sparse images the only way to backup to a mounted shared volumes over my LAN ?

11-28-2009, 05:57 PM
Yes, restoring from FW400/800 is going to be faster, especially if you start up from them and restore.

You have to use an image over a network because you can't otherwise preserve all ownership, permissions, metadata, etc without a far-side agent. (Note that Time Machine uses an image for the same reason.)

11-28-2009, 08:59 PM
I understand the importance of preserving ownership, etc... , but that concern does not exist if I duplicate a hard drive on a partition of a direct connected drive.

What is the difference of creating a partition on a direct drive and on a local shared volume ?

11-28-2009, 09:57 PM
I don't understand what you mean. A directly connected drive is entirely different than a network drive.

11-29-2009, 09:04 AM
That is all the point of my question ... I want to understand WHY a źnetwork╗ shared volumes is different from a volume located on a źdirect╗ connected drive.

11-29-2009, 09:20 AM
Because a network drive abstracts the file system through network interfaces (the other side of the connection could be FAT32, NTFS, HFS, ext3... anything) whereas a direct connection interacts with the file system directly.

11-29-2009, 09:26 AM
I see .. Thank you !