#1
|
|||
|
|||
Erase, then Copy: Disk Image Size Planning
So, I got a "No space left on device" message while trying to update a sparse image using a smart update "Erase, then copy". I can honestly say I'm happy about this. Because an "Erase, then failed copy" could create a big issue.
Now, I'm trying to plan for how much flex space to add to the sparseimage. What is SuperDuper! actually doing on this? Does it copy all the new stuff first and then erase? Or, does it erase after each file is successfully copied? I much prefer the latter as I think that means I need to make my sparse image bigger than the largest file I could expect to have. The former has me adding a lot of space to disk images based of how many big files could get updated (and with a digital photographe wife, producing MANY 60 MB files in a day, that adds up to be a lot). Thanks, Gary |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Booting from backup | guruuno | General | 27 | 10-16-2009 11:53 PM |
Multiple errors of kind: "Caught I/O exception(5): Input/output error" | amagjo | General | 7 | 04-14-2009 10:01 PM |
Disk Image size a lot bigger than the backup size | SpaceRoger | General | 3 | 03-15-2006 03:05 PM |
SuperDuper Backup of AES 128 Encrypted Disk Image | rwg4 | General | 3 | 11-30-2005 10:28 AM |
Error: No space left on device | tradervic | General | 11 | 06-29-2005 04:50 PM |