Mount Sparseimage - what is happening?

[magoo66]

Hi. I backup to an NAS, so that creates a sparseimage. I have SD! set to run every night at 9:30 using smart update. I've noticed that it takes a *really* long time to mount the sparseimage (we're talking 3+ minutes over gigabit lan, and 15+ minutes over wireless). Why is that? What is it doing? According to iStat Pro, it looks like my computer is downloading a butt-load of data. What data does it need? I figure it's not just my computer, because I've tested this using a directly-attached firewire drive and there is essentially no time (though, that's not sparseimage).

It's all working just fine, I'm just curious. Thanks.

[dnanian]

As of 10.4.9 or so, OS X started to scan every image that's mounted to make sure it's valid for security purposes. It takes a long time to do.

[magoo66]

Is there any way to bypass that? Since I know what this image is, can I set some security parameter to allow easy access?

[dnanian]

Not that I know of.

[cutterfilm]

Within a week, either our Sparse Image backups end up corrupted or Super Duper stops backing up for some other reason. I was so happy to kiss Retrospect goodbye when we first switched, but now it's becoming just as much hassle and work as Retrospect. SuperDuper always seems to time out or give up before our Macs are able to load the proper Sparse Images. Why can't SuperDuper back up to regular disks over a network?

Anybody figure out ways to deal with this stuff that doesn't take daily maintenance? It is just a $25 dollar program. Anyone using something better?

[dnanian]

Corrupted? If the images are becoming corrupted, it sounds like you're having some serious networking problems or other issues. SD! can only work as well as the environment it's running under.

We don't have any "timeouts", though, so I'm not quite sure what you're referring to here...