Jump to content

mohrus

Members
  • Posts

    6
  • Joined

  • Last visited

mohrus's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Simple, yet convincing remark I will move forward in purchasing a new piece of equipment. Will keep you posted.
  2. I actually had these issues with each one of my three disks... right now I suspect my sharkoon quickport and/or the usb-connection to be the cause. It is one of these HD-docking stations. I might get one with FW800 like the newertech voyager q.
  3. Update: Recreated the config file from scratch. Verification off. Same Backup Sets. Backup starts looping again with several (other) files. It's repeating over and over again. Any input greatly appreciated! Log says this: [color:green]> !Trouble writing: "1-MD-Backup Set 3" (3285934080), error -102 ( trouble communicating) !Trouble writing media: "1-MD-Backup Set 3"error -102 ( trouble communicating) MapError: unknown Mac error 22 TFile::Create: UCreateFile failed, /Volumes/MD-Backup3/Retrospect/MD-Backup Set 3/1-MD-Backup Set 3/AAd.rdb, oserr 22, error -1002 Additional error information for Disk Media Set member "1-MD-Backup Set 3", Can't write to file /Volumes/MD-Backup3/Retrospect/MD-Backup Set 3/1-MD-Backup Set 3/AAd.rdb, error -1002 ( unknown Mac OS error) [/color] Update2: Force-unmounted + repaired + mounted disk with disk utility. Backup running fine now. I had this same cycle a few times now. I bet it's coming back tomorrow. Any ideas? Could it be the Backup-Hardware? I chose this relatively cheapish Sharkoon Quickport for super easy disk swapping. Could it even be the USB-Cable?
  4. Update: Disk has to be repaired with disk utility prior to using it again. Disk utility shows no repairs done but it makes the difference. Retrospect will not be backing up otherwise. (see other thread) Note: This is not a solution, because it keeps happening again after these repairs. Any input greatly appreciated!
  5. Hi again, I have a problem with removable backup disks (USD harddrives) not being able to unmount/eject after Retrospect backed up on them. Only force eject works. There are no opened files on the disks and the problem persists even if the retro engine ist stopped. This may be related to my other issue with an endless loop backing up the Config80-files. Topic to be found here: http://forums.dantz.com/showtopic.php?tid/35201/ My setup: Xeon XServe with Snow Leopard, Retro 8.2, external disk (USB). A proactive script is backing up the whole startup/data Volume of the server to the ext.disk. There are 3 ext.disks with individual scripts for max. flexibility. Thank you for your suggestions. I will keep you posted.
  6. I need some help here. Have been trying to get this backup-setup running for weeks now. There seems to be one consistant error that is reoccuring: My setup: Xeon XServe with Snow Leopard, Retrospect 8.2, external disk (USB). A proactive script is backing up the whole startup/data volume of the server to the ext.disk. There are 3 ext.disks with individual scripts for maximum flexibility. The script enters an endless loop when copying the file Config80.bak. The status constantly changes between: - Copying >drivename<... - Please Wait every now an then: - Updating Catalog File This happened with different drives and different scripts (also regular backup scripts). What I tried: - rebooting, starting/stopping retro engine - rebuilding scripts - deleting Config80.bak -> same loop with Config80.dat - permissions are correct: -rwxr-xr-x root admin Any ideas greatly appreciated! Thanks in advance. Will keep you posted on solution, if there's any.
×
×
  • Create New...