#DROPDMG REVIEW FULL#

I rebooted and then tried to use Disk Utility to restore the compressed image to a firewire drive. Using the Zlib compression only 1.5 hours rather than 3 hours with Bzip2. I could see from the SuperDuper log that my shell script unmounted the sparse image and that DropDMG did it’s thing. What settings do I need to use for DropDMG to get this same, one-step compressed dmg functionality? With Disk Utility it will create the compressed dmg reasonably quickly in one step. Not only does this take a lot of disk space, it also takes a long time to complete. I started the DropDMG processes again from the Terminal and now I see what’s happening: DropDMG first creates an uncompressed dmg file and then as a separate step it creates a compressed version. There was 70gb+ on the target disk and the compressed dmg should only be about 30gb.

#DROPDMG REVIEW FULL#

I went ahead and had it do the full backup last night but in the morning I found that DropDMG encountered this error:Įrror 1 - hdiutil: convert failed - No space left on device for “Backup”

SuperDuper did the backup and was able to run the shell script and DropDMG did it’s thing. I had run some small tests and everything was working fine. The config “systembackup” creates a “.dmg bzip-compressed” image and I’ve got the ecryption passphrase set in there. I’m now using SuperDuper to create the initial backup and then I have it run a shell script when it completes. I’m trying to automate the process so I can just let it run overnight.

I’ve got my boot drive backed up and the data is encrypted so that it’s secure off site. I’ve been using this procedure for about a year and it’s worked out well.

The dmg goes on one of several firewire drives that I rotate off site.

Create a compressed, encrypted disk image of the backup drive.

I’m attempting to automate my backups and it looked like DropDMG would fit in perfectly but I’m running into a problem.

Dropdmg review