Jump to content

jsobel

Members
  • Content count

    33
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jsobel

  • Rank
    Newbie
  1. Does anyone have experience with cloning a complete disk using Retrospect 10. I have tried it, and always end up with 2000+ execution errors. Things like: *File "/Volumes/Macintosh HD/usr/share/man/man3/Tcl_Close.3tcl": can't link to "/Volumes/Macintosh HD/usr/share/man/man3/Tcl_Seek.3tcl", error -1101 ( file/directory not found) In this case the error message is clearly misleading since both files are found on their respective locations. Other error messages are of the type: *File "/Volumes/Macintosh HD/Applications/Utilities/Retrospect/Retrospect.app/Contents/Frameworks/Sparkle.framework/Versions/A/Resources/pt.lproj/SUUpdatePermissionPrompt.nib": different data size (src: 12723, dest: 0) *File "/Volumes/Macintosh HD/Library/Logs/DiagnosticReports/mdworker32_2013-08-27-161621_SEABB-IS-12066.cpu_resource.spin": appears incomplete It only shows 500 messages, so there may be many others. Can I trust the clone ? I log out before the clone is performed so that there will be a minimum of open files and other activity going on, by of no avail. P.S I can't find a practical way to search this forum. Just the complete website. Any hints?
  2. jsobel

    DVD visible but blanks aren't Seen

    Also see the thread at: http://forums.dantz.com/showtopic.php?tid/32543/
  3. The new User Guide p117 states that: So, I guess your hypothesis about the source of the problem could be right. As an alternative to creating a different Backup Set for each client computer, wouldn't it be possible just to turn on the option "Match only file in same location/path:"? The Users Guide says nothing about different client computers. Is it possible for two seemingly identical system files on different computers to have the same file identification number, or are these numbers assigned at random for each specific machine? Another interesting thing would be to know what happens if "Don’t add duplicate files to the Media Set" is selected, but the option "Match source files against the Media Set" is deselected. Guesses anyone ?
  4. jsobel

    Backup to DVD - "Needs Media" error

    Although, I don't have any experience of how this works with a slot DVD, I think that once the Retrospect Engine takes control of the DVD, you don't have to repeat the procedure. However, if you want to use your optical drive for anything else in between backups, you certainly do need to. For example, after a restart. I always restart with the mouse button down, in order to eject my backup DVD before startup. In this way, when I push it to close after startup, Retrospect takes control again. No, I don't think this hassle is related to the lack of user guide, but it certainly is the reason why they have backup to optical media disabled by default. Apparently they can't share the optical drive with the Finder, and are waiting for Apple to come up with a solution. I can't understand why... It was working somehow in version 6 of Retrospect.
  5. jsobel

    Backup to DVD - "Needs Media" error

    You need to start the Retrospect Engine with the tray of the DVD OPEN. Retrospect will then take charge of the DVD, after you close the tray by pushing it. Don't worry about the Retrospect Console, its just an interface to the Engine. Its the Engine that controls everything.
  6. jsobel

    Backup to DVD - "Needs Media" error

    I assume that you have activated optical support by modifying retro.ini as described in the article "Retrospect 8.x for Macintosh Optical Support (9720)" in the knowledgebase. (http://kb.dantz.com/display/2n/kb/article.asp?aid=9720&n=2&s=) However, if you can eject the tray from the Finder (e.g. using the eject button), then the Retrospect Engine does not have control of the drive. What you need to do then, is to eject the drive, stop the Retrospect Engine (from within System Preferences), restart the Retrospect Engine, and then close your tray by pushing on it. Now, the Retrospect Engine will have control of the drive and you will only be able to eject the tray from within Retrospect. Retrospect should then operate normally.
  7. On my Intel Mac Pro under MacOS 10.5.8 RetroEngine (8.1.626) uses 30.66 MB real memory (RSIZE), 15.00 MB (RPRVT) and 92.20 MB (VSIZE). Furthermore it has 15 Threads. Have you tried starting and stopping the engine to see if it still uses as much memory ?
  8. You could stop and restart the engine, and look in the Console if it says anything particular. A look for retroEngine in the ActivityMonitor will tell you if the engine has started. A reboot never hurt anyone.
  9. jsobel

    Copy Function

    In the middle of the backup. My system started to behave oddly.
  10. jsobel

    Copy Function

    Interestingly enough, if you do a disk cloning (Copy) operation and select the "Move files" option (found under the Options-tab) Retrospect will indeed erase your whole source disk, without any warning. This happens even if your source is the startup disk, and the disk on which the Retrospect Engine resides. Nothing is mentioned about this option in the (almost nonexistent) documentation, and I expected it to control whether the cloning would be disk sector-by-sector or by files, but no... It gladly started erasing my startup disk, and of course crashed half way through... Luckily, I could easily recover using Time Machine.
  11. I do daily DVD-backups (with software compression) without any problems on a MacPro, Dual-Core Xeon. It sounds to me as if your problem is machine-specific, though. Have you got enough memory?
  12. jsobel

    Copy of iPhoto Library

    I think that you might be troubled by the same bug that is mentioned in the thread "Incremental backup problem.." http://forums.dantz.com/showtopic.php?tid/30479/
  13. I executed a "Verify"-script to verify the files stored on a DVD. The activity was marked with a Warning sign (Yellow triangle with an exclamation mark) in the "Activities" window. The log reads as follows: + Executing Verify jsobel B at 8/18/2009 1:00 PM 8/18/2009 1:00:44 PM: Verifying jsobel B 8/18/2009 1:12:21 PM: Execution completed successfully Remaining: 245 files, zero KB Completed: 9798 files, 3.5 GB Performance: 304.1 MB/minute Duration: 00:11:36 (00:00:01 idle/loading/preparing) Total duration: 00:11:36 (00:00:01 idle/loading/preparing) How shall I interpret this result ? It states: "Remaining: 245 files, zero KB" The result of the last backup performed was backing up 245 files (21.0 MB). Were these checked or not? Is everything alright ? Or is this just an example of a bug in the generation of the Log?
  14. Thank you for your reply. I have been able to recover without any real problems. However, I wanted to know why it happened and perhaps warn other users. Where did you find this information? I didn't see any warning. How does it alert me? Don't you thing it is dangerous to have this option in a "Copy" script. After all there is the "Archive" script.
  15. I wanted to do a complete copy of my hard drive to another local disk before upgrading to 10.5.8. I therefore made a "Copy" script, to copy "All Files" with "Thorough verification" This worked well, but then after the normal copying and checking, in the "Status field" in the Activities window of the script I suddenly read: Status: Erasing MacPro.... And sure enough, it erased my hard drive. I think it might be due to the fact that I had checked "Move files" under the script "Options", but I'm not sure what this options does. At any rate, I didn't expect it to erase my hard drive after the backup. If this is indeed what the option does, I think it should be removed. There is the "Archive"-type script to do this type of data moving. If the "Move files"-option is not the culprit, I would be grateful to know what could have caused Retrospect to erase the source in a Copy-operation before I try again.
×