Jump to content

kerryd

Members
  • Content count

    64
  • Joined

  • Last visited

  • Days Won

    2

kerryd last won the day on April 1 2013

kerryd had the most liked content!

Community Reputation

2 Neutral

About kerryd

  • Rank
    Occasional Forum Poster
  1. After a scan of my hard drive has happened it proceeds to executing and I constantly get back, as in the pictures attached an red X and incomplete execution. The log file reports: Scanning incomplete, error -1100 ( invalid handle) I’ve tried everything. I’ve run verify disk and repair disk, volume rebuild from Techtools Pro and found all the corrupted files and deleted them and finally I’ve run the power house of the bunch Disk Warrior. The machine is running perfectly fine and all my other backup tools seem to be working just fine. In actuality, I’ve never had a problem with Retrospect like this before except where I’ve made an error with my backup media set. I’ve tried three different targets for backup and neither of them make a difference. I’ve tried just backing up the user folder instead of the entire HD and this doesn’t make any difference at all. I’ve even talked to Retrospect support and they’re stumped. Has anyone else experienced anything like this. I’m just determined to get it going whether I need it or not but I’ve used it for ten years simply at 3 am so its never interfere with anything I do. It just runs quietly in background till now. Now, its consumed tons of time trying to get it going. Oh and I have the latest revision of Retrospect 10.1 and for that matter everything else. HELP!!!!!!!
  2. After a scan of my hard drive has happened it proceeds to executing and I constantly get back, as in the pictures attached an red X and incomplete execution. The log file reports: Scanning incomplete, error -1100 ( invalid handle) I’ve tried everything. I’ve run verify disk and repair disk, volume rebuild from Techtools Pro and found all the corrupted files and deleted them and finally I’ve run the power house of the bunch Disk Warrior. The machine is running perfectly fine and all my other backup tools seem to be working just fine. In actuality, I’ve never had a problem with Retrospect like this before except where I’ve made an error with my backup media set. I’ve tried three different targets for backup and neither of them make a difference. I’ve tried just backing up the user folder instead of the entire HD and this doesn’t make any difference at all. I’ve even talked to Retrospect support and they’re stumped. Has anyone else experienced anything like this. I’m just determined to get it going whether I need it or not but I’ve used it for ten years simply at 3 am so its never interfere with anything I do. It just runs quietly in background till now. Now, its consumed tons of time trying to get it going. Oh and I have the latest revision of Retrospect 10.1 and for that matter everything else. HELP!!!!!!! Retrospect backup failure consistently.tiff
  3. Ran TechTools Pro and deleted all corrupt files and that did no good so I ran Disk Warrior and there were still 6 bad files and that did no good. So from the post just before this I did what it suggested and that did no good. What a waste of time for a simple backup. I've used Retrospect since 2003 and have never encountered anything like this. it has to be something in the upgrade. This should not be the case in the Mac environment. Mac users just want things to work rather than pulling everything to pieces only to find each thing, which is time consuming does nothing. ------------- Posted Today, 12:46 AM Please see this article and change: SetFoundationLogging=6 (from 3) SetVolumesLogging=7 (from 3) Then perform backup and see if the log shows error -1100 with additional related info. Also, does the volume with error -1100 have a hidden Time Machine folder "Backups.backupdb"? ------------------------------ Like This Quote MultiQuote
  4. This is such a weird one. I re-installed my Retrospect and now constantly keep getting the following Normal backup using Macintosh HD Backup - 2013-03-25 1:52 AM at 2013-03-25 To Backup Set Full Macintosh HD Backup... - 2013-03-25 7:11:52 AM: Copying Macintosh HD Scanning incomplete, error -1100 ( invalid handle) I've made sure that nothing is scanning - Spotlight, Launchbar etc I even turned off RetroISA I've had errors before but never anything like this. I've rebuilt the drive using Disk Warrior even though Disk Utility checked it out as fine. I have no idea what to do about this.
  5. I wouldn't think it would matter. The client is only for other computers on the network like a laptop connected to the network via WIFI. It seems the biggest change in V10 is the client software.
  6. Under sharing I found the proper name under that other name: Kerry-Dawsons-iMac.local As soon as I input this to the Retrospect app. all the stuff turned up. Thanks a lot for your help.
  7. I downloaded that IOS app for Retrospect and it wants my server name and password. The password I know. However, i call my iMac: Kerry Dawson's iMac This is not how the IOS app expects it to be named but rather it should have . between words. Does anyone know where we can get a server name in that convention from Retrospect.
  8. I noticed that too but it seems to settle down. its at its worst after a restart, settles down and then takes off again. What I don't like is the amount of real memory it is using in Activity Monitor. I'm thinking of removing Retrospect 10 from my machine and going with a different backup strategy for my iMac and MacBook Air.
  9. I too ran into a problem with the installer but not quite like yours but for me this has never happened with any software I've got over many years. After running the instsaller there was no Retrospect to launch. I found both the old and new in the trash. I pulled the new one out of the trash and launched Retrospect. Upon restart all my scripts etc were gone. Its like I had a factory fresh version of the software. I decided that I just needed two simple scripts to run at 10 at nght aand used the easyt installer to get back up and running. However, this was all a bit scary. I phoned Retrospect and they hadn't heard of this but they had just posted it when I went and ran it. I indicaatted thsgt they probsbly would find others who will encounter some kind of problem and they should be aware aand they thanked me. I have no idea if they pulled the installer or not and re-worked it but...........
  10. I just updated my Retrospect and what a mess. It deleted Retrospect. I had to recover it from the Trash. I had to install a new engine. Plus, none of my scripts or activities show. The app folder looks the same as the one from my Time Machine backup but Retrospect is the newer version. Everything else is the same. I don’t know why none of my scripts, sources etc are showing.
  11. You’re right! No deletions especially at the root level. I’m a bit rusty with Retrospect.
  12. That sounds like a good idea. I haven’t used Retrospect in quite a while so I’m rusty with it. I bought a portable to go on my home network and I didn’t think these warnings were that important but I’ll look at the logs again. Currently, I seem to be having a lot of trouble getting Retrospect to locate the portable. It will and then when I come back to it in say a couple of hours it just can’t find it agqin. You wouldn’t know what might be causing that by any chance.
  13. I added an Air to my home WIFI network and although it is showing up in finder as a shared device I’m frequently finding that Retrospect is having problems with the connection and even a locate will not seem to find the Air unless I do a full reboot. Does anyone have any idea why this might be happening. I’ve got a once a week scheduled backup that I’m concerned it will miss if it keeps losing it on the network.
  14. I have three scripts, two that are full system backups and one that is a USR backup. With the full system backup Ive noticed I get the yellow warning sign. Checking the log file, this usually relates to some file in a root level folder. As an example, there is a file mdworker32 that is generating these warning signs. I believe it was in library>app support>retrospect etc. I tried deleting it but I'm locked out by this folder as it appears to be owned by the root. I see nothing to worry about around these warning signs but I'd love to get rid of them. Does anyone have any idea, as in the above, how i can enter this folder to remove that file which seems to have permissions restrictions thus generating the error. Thanks Kerry
×