View Single Post
  #14  
Old 03-19-2008, 10:31 AM
dnanian's Avatar
dnanian dnanian is offline
Administrator
 
Join Date: Apr 2001
Location: Weston, MA
Posts: 14,923
Send a message via AIM to dnanian
If you're in a situation where the process gets interrupted, I strongly recommend that you not back up to an image, or -- if you do -- stop the backup and eject the image before you sleep the Mac.

Yes, "in the real world", things happen. But those things also have consequences. A system crash can corrupt a drive. Memory problems can cause failures. Disconnecting a network during a file copy can very likely corrupt that file. If you're writing to an image, you can corrupt the image... the system does the best it can to keep that image flushed, but it can definitely happen, to anything.

I don't have enough information to provide any detailed response, but in general:

- We mount images by asking the system to mount the network volume (if not there) and then mount the image itself. The network volume is mounted by resolving an alias to the image file itself (which mounts the drive). It's hard to know why that might fail without any error. You can try to mount the image by hand and then schedule with the volume (rather than the file) selected. That mounts a different way, and might help.

- v2.5 has fixed a problem with Growl reporting (in rare situations) that should work. Have you recreated your schedule since installing 2.5?
__________________
--Dave Nanian
Reply With Quote