lroathe Posted August 22, 2002 Report Share Posted August 22, 2002 So I purchased Retrospect 4.3 a while back and have never been able to get it to work with FTP (which is the entire reason I purchased it), no tech support is available and a "we're looking into it" is all I've heard for over a year. So a couple days ago I decided that I'd try backing up to another HD I just got so at least I'd have an automated way of backups (vs. drag and drop I do now...pretty nice after paying $150 for a backup program...NOT!) I chose the "backup to file" option because I could find no other method for doing a backup to a non-device/ftp destination. What I found is that Retrospect CRASHES the system during the backup procedure. Nice. So; does 4.3 even work at all? If so with what? I loved Retrospect 2.0 that I used for backups years ago at a company I worked for, but my experience with this version has been nothing but a disaster and a complete waste of time and money. I'm still doing backups by dragging folders when I remember to. Appologies for the rant, but previous experience says that it's a waste of time trying to get any help from this company so why bother? Here's an example StdLog in case anyone cares: MacsBug 6.6.3, Copyright Apple Computer, Inc. 2000 NMI (user entered MacsBug on purpose) 22-Aug-2002 10:05:54 AM (since boot = 19 hours, 33 minutes) Current application is “Retrospect Express” Machine = #406 (NewWorldMac), System $0922, sysu = $01008000 ROM version $077D, $45F6, $0001 (ROMBase $FFC00000) VM is off NIL^ = $FFC10000 Stack space used = -19552620 Address 004D2270 is in the System heap at 00002800 at YourHeapIsProbablyCorrupt+079FC It is in the CFM fragment “MemoryMgr” at 004C9610 It is 00008C60 bytes from the start of the fragment and 00008BE0 bytes into a non-writeable code section at 004C9690 It is 00008C60 bytes into this heap block: Start Length Tag Mstr Ptr Lock Prg Type ID File Name • 004C9610 0000DDDC+08 N Fragment “MemoryMgr” PowerPC 7400 (G4) Registers CR0 CR1 CR2 CR3 CR4 CR5 CR6 CR7 PC = 004D2270 CR 1000 1000 0000 0000 0000 0000 0010 0100 LR = 004CD6A8 <>=O XEVO CTR = 004C9EB4 MSR = 00000000 SOC Compare Count Int = 0 XER 000 01 00 MQ = 00000000 R0 = 004CD6A8 R8 = 00000000 R16 = 00000000 R24 = 00000000 SP = 3D742D80 R9 = 00000000 R17 = 00000000 R25 = 00000000 TOC = 00348514 R10 = 00000020 R18 = 00000000 R26 = 00000000 R3 = 00000000 R11 = 0041D9A0 R19 = 00000000 R27 = 00000001 R4 = 00000000 R12 = 00348620 R20 = 00000000 R28 = 01FF3EE0 R5 = 00002800 R13 = 00000000 R21 = 00000000 R29 = 00002800 R6 = 00000000 R14 = 00000000 R22 = 00000004 R30 = 00017D90 R7 = 00000000 R15 = 00000000 R23 = 00000001 R31 = 01FF3EE0 Disassembling PowerPC code from 004D2248 YourHeapIsProbablyCorrupt +079D4 004D2248 li r5,0x0005 | 38A00005 +079D8 004D224C sth r5,0x0038(SP) | B0A10038 +079DC 004D2250 b YourHeapIsProbablyCorrupt+07A14 ; 0x004D2288 | 48000038 +079E0 004D2254 bne cr6,YourHeapIsProbablyCorrupt+079FC ; 0x004D2270 | 409A001C +079E4 004D2258 cmplw r8,r30 | 7C08F040 +079E8 004D225C blt YourHeapIsProbablyCorrupt+079FC ; 0x004D2270 | 41800014 +079EC 004D2260 li r3,0x0002 | 38600002 +079F0 004D2264 stw r31,0x003C(SP) | 93E1003C +079F4 004D2268 sth r3,0x0038(SP) | B0610038 +079F8 004D226C b YourHeapIsProbablyCorrupt+07A14 ; 0x004D2288 | 4800001C +079FC 004D2270 *add r31,r31,r9 | 7FFF4A14 +07A00 004D2274 li r6,0x0000 | 38C00000 +07A04 004D2278 b YourHeapIsProbablyCorrupt+07934 ; 0x004D21A8 | 4BFFFF30 +07A08 004D227C li r4,0x0006 | 38800006 +07A0C 004D2280 sth r4,0x0038(SP) | B0810038 +07A10 004D2284 li r28,0x0000 | 3B800000 +07A14 004D2288 mr r31,r28 | 7F9FE378 +07A18 004D228C cmpwi r31,0x0000 | 2C1F0000 +07A1C 004D2290 bne YourHeapIsProbablyCorrupt+07A4C ; 0x004D22C0 | 40820030 +07A20 004D2294 cmpwi r26,0x0000 | 2C1A0000 Heap zones #1 Mod 38929K 00002800 to 02606C4F ! SysZone^ #2 Mod 6K 0008AAA0 to 0008C48F ROM read-only zone #3 Mod 216K 00750DA0 to 00786D9F #4 Mod 94K 00826E20 to 0083E9FF #5 Mod 128K 01B85C50 to 01BA5C4F #6 Mod 986931K 02606C50 to 3E9D3B1F Process Manager zone #7 Mod 559K 3AB4D530 to 3ABD938F “SimpleText” #8 Mod 8754K 3CE7AD80 to 3D7075AF “Retrospect Express” ApplZone^ TheZone^ TargetZone #9 Mod 384K 3E20EE80 to 3E26F12F “File Sharing Extension” #10 Mod 959K 3E64E4D0 to 3E73E0EF “Finder” #11 Mod 382K 3E840FF0 to 3E8A095F “Folder Actions” #12 Mod 128K 3E8B74F0 to 3E8D765F “DVD AutoLauncher” WARNING: One or more heaps may be corrupt. Use HC ALL (Heap Check) for a thorough check. Checking all heaps The System heap at 00002800 is bad Master pointer does not point at block Block header 00AFEF30 00AF EEC0 AB80 0004 0000 0250 01FF 1B24 •ØÓ¿´Ä•••••P•ˇ•$ The ROM read-only heap at 0008AAA0 is ok The heap at 00750DA0 is ok The heap at 00826E20 is ok The Process Manager heap at 02606C50 is ok The “SimpleText” heap at 3AB4D530 is ok The “Retrospect Express” heap at 3CE7AD80 is ok The “File Sharing Extension” heap at 3E20EE80 is ok The “Finder” heap at 3E64E4D0 is ok The “Folder Actions” heap at 3E840FF0 is ok The “DVD AutoLauncher” heap at 3E8B74F0 is ok System heap high free space + TempMem low free space = #945645200 (#901M) The target heap is the System heap at 00002800 Totaling the System heap at 00002800 >>> With all macros expanded, your command line was: log "StdLog";set suspendprompt on;dv v;stat;wh;td;ip;hz;hc all;hx 02A6^ ;ht;hx 02A6^^+10 ;ht;hx 02AA^ ;ht;file 0;vol;drive;drvr -v;rd -s;sc6;sc7 sp 1k;dm sp 80;dm 0 20;log The System heap at 00002800 is bad This block's back pointer doesn't point to the previous block. Block header Link to comment Share on other sites More sharing options...
AmyJ Posted August 22, 2002 Report Share Posted August 22, 2002 Retrospect is fully qualified to backup to hard drives. I suspect that with a little troubleshooting, you'll be able to find the cause of the problem. First, what kind of hard drive are you using? SCSI, Firewire, USB? You didn't mention, so I'll list appropriate troubleshooting for all (USB and Firewire troubleshooting are essentially the same): With a lock up on the backup computer you want to try moving the mouse to see if the ADB or USB bus has locked up as well. If you are using a USB device, and the mouse is frozen, this is often the indication of a USB hang. Try the USB device connected directly to the computer rather than via a Hub. Try unplugging the mouse and plugging it back in again. Try unplugging the USB drive and plugging it back in again. Update to the latest USB drivers and device firmware. If the mouse moves but the Mac is hung up it's most likely that your SCSI bus is hung and you have a SCSI problem. If the mouse doesn't move with a SCSI device that means that the Mac's processor is hung and you should look at System Software and extensions. More often than not you will find that the mouse moves and you can force quit the program (at which point the Mac may or may not completely crash). A SCSI or USB hang or error can be caused by one or more of the following: 1) Another device on your SCSI bus is interfering with the drive's communication. Make sure your SCSI ID numbers are set correctly. Turn off your computer and the devices. Disconnect all SCSI devices except for the drive. Try the backup device connected directly to the computer 2) Bad format. Reformat the drive. Be sure to use the software that came with the drive, if applicable. The drive should be formatted as Macintosh Extended. 3) You have a bad cable. Replace the SCSI or USB cable that connects the tape drive to the computer after removing other devices and cables from the SCSI or USB chain. 4) You are missing a terminator (SCSI) or have a bad terminator. The last device and ONLY the last device in your SCSI chain needs to be terminated. Try replacing the terminator if you already have one on the chain. 5) The computer may be having a problem. Install Retrospect on another computer and try the tape drive there as the lone device on the USB or SCSI chain. 6) Try a test backup to the local drive, rather then the external drive. Retrospect accesses all drives through the OS - regardless of whether they are SCSI, USB, Firewire or ATAPI. A failure writing only to the external drive could point towards hardware problems. 7) The drive may be defective. If you have implemented all of the preceding steps and get failures changing cables terminators and computers then the drive (being the only factor that has not changed) is the culprit--send it back to your vendor for repairs. The steps above are essentially the outline of our device troubleshooting here at Dantz. Hands on testing of device issues is really still the best method and even getting device logging information is usually only to confirm empirical testing. Note that concluding something is a bad device is the LAST thing we assume after all other components and variables have been ruled out. "SCSI voodoo" as they call the nebulous symptoms that can plague a SCSI bus can often lead one to false assumptions of the cause of problems. It's important that once a variable is tested that it be tested more than once for consistency's sake to rule out dumb luck. For example SCSI voodoo accounts for why a tape drive may work fine for many months without proper termination but then suddenly fail in some way later. Although customers will often cite that nothing has changed with their SCSI bus configuration in months and that it was all working before this is really indicative of the inconsistency of SCSI voodoo. The quickest and most conclusive test for most devices is to test it on more than one computer as the only device on the bus and with a different SCSI cable. If the problems can be reproduced on multiple computers it's more than likely a hardware problem with the device itself. Of course there a myriad of other specific issues having to do with a device's own hardware settings like with internal jumper cables dip switches or internal termination that has to be sorted out with the device's manual and/or vendor or manufacturer of the drive, but the kernel of SCSI troubleshooting above is a good general guideline. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.