Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About haggis999

  • Rank
    Occasional Forum Poster
  1. I'm aware that Retrospect has had a chequered history. However, it still provides a very powerful backup tool, despite the sluggishness in fixing bugs highlighted many years ago. More to the point, I'm not aware of any other software that does a similar job at a similar price. I'm used to the idea of using quotes in other forums to limit a search to the whole phrase, thus eliminating all the partial matches, but in this case I didn't get ANY match for that error message (apart from this thread) until I encapsulated it in quotes. That seems a little odd to my eyes. Why does it need the quotes to find a mention of that exact error message in the 2007 thread you mentioned earlier? It's some time since I looked at my issues with autolaunching Retrospect, so I can't remember if an -530 error was involved, but I'll keep your comments in mind when I find the time to look at this again.
  2. Your first link is interesting. It quotes Retrospect tech support saying that problems with relocating the backup set are on their bugfix list. That was over 11 years ago!! Earlier this afternoon, I searched the forum for "Cannot use the specified backup data folder", but failed to find any thread except this one I raised today. However, my search was done without encapsulating the phrase in quotes. Adding the quotes at the beginning and end makes a surprising difference to the search results. With regard to your second link, I never did get to the bottom of why Retrospect no longer autolaunched in a reliable manner, despite finding a way to nudge Windows 10 into rediscovering my NAS drives. Certain events, such as my recent NAS rebuilds, made Win 10 forget how to automatically discover my NAS units on the network, but mapping the drive to a drive letter was the key to jogging its memory (the drive mapping could then be deleted). Since then, I have just been starting Retrospect manually every morning. Many thanks for your help on this. I will try again to fix my current problem...
  3. I am currently looking at the Member Properties dialogue box for the relevant member of my backup set and simply trying to change its storage location, but I just get the message "Cannot use the specified backup data folder". I can browse to this folder from within the dialogue box, so what might be going wrong here? After my NAS (called BonzoNAS) died recently, it was rebuilt and had the data restored from a backup NAS. Previously, the member called 1-Backup Set NAS1 was stored in the following path and the Member Properties dialogue box successfully used a location of \\BONZONAS\Backup\. Backup/Retrospect/Backup Set NAS1/ I tried to store this member folder in a new path on the NAS as follows, but a location of \\BONZONAS\Retrospect\ doesn't work. I have tried moving 1-Backup Set NAS1 to a variety of different subfolders but I still can't find a path that is acceptable to Retrospect. It is insisting that I use a volume name of Backup on my NAS and is also appears to be insisting that I use a subfolder called Retrospect. Retrospect/Backup Set NAS1/ In other words, the only location that works is when I recreate the original path on the NAS! Is there a hidden secret to relocating member locations?
  4. I've just realised that you may have misunderstood what I was trying to do. It's not a matter of wanting to "move member folders of disk sets to new locations". It is the Backup Set itself that now has a new name and path on my NAS. This Backup Set has no subfolders and contains about 4,000 rdb files. EDIT: Please forget this post! I misunderstood the terminology. It is indeed a member folder I am trying to modify.
  5. Hi David, My previous attempts to obtain guidance from the Retrospect 12 for Windows User Guide had been unsuccessful, so thanks for that useful information (and apologies for not making it clear I was using version 12). I will now dig a little deeper and see if I can do the edit you have suggested.
  6. I have just made a major reorganisation of the folder structure on the NAS unit I use to store my Retrospect backup files. The destinations in all my backup scripts therefore need adjusting. How exactly do I do this to ensure a smooth transition to the new folders without losing any of the previous backup information?
  7. Catalog Files on a NAS

    Thanks for persevering with this, David. I will do as you suggest and check out that KB article more carefully over the coming weekend.
  8. Error -1017 (insufficient permissions)

    Thanks for that link. I've now posted a question on that other thread.
  9. Catalog Files on a NAS

    I've just checked the member properties as Scillonian advised and found that the location is already in UNC format (\\PRIMARYNAS\Backup\). However, the job in question actually saves the backup in \\PRIMARYNAS\Backup\My Pictures. You suggest that this might be a problem, but the job has been running successfully for many years. It's only become an issue since Windows 10 decided to forget my NAS boxes. I already have my primary NAS listed under Quick access. That's useful in Windows Explorer, but doesn't help Retrospect find the NAS when running an automated job using the Retrospect Launcher.
  10. Catalog Files on a NAS

    I'm hitting similar problems with Windows 10 occasionally losing the ability to discover the NAS boxes on my home network, a situation that is currently preventing one of my automated backup jobs from running (though it works fine if I open Retrospect manually before the job is due to start). Rather oddly, several other automated backup jobs that use the same NAS (though not the same destination folder) continue to run fine. I've just upgraded to V12.5, but it made no difference. However, I have not yet found a way in Retrospect to specify the backup destination using the UNC path. I would appreciate some guidance on this point.
  11. Error -1017 (insufficient permissions)

    That KB article doesn't appear to contain anything relevant. It merely addresses some of the basic issues regarding how to configure Retrospect for auto launching, something I sorted out a long time ago. However, it now appears that an issue with the Windows 10 network discovery process is the most likely source of my problem. If I open up Windows Explorer and click on the Network icon, it is not currently displaying my NAS drives (something it normally does), though they are listed under 'Other devices'. I have seen this before and have never found the cause, but it just tends to go away after a few days and everything returns to normal. It's very irritating. Grrrrrrr.
  12. Error -1017 (insufficient permissions)

    Having found nothing relevant so far in previous posts about error -1107, I decided to pay for the upgrade to V12.5. Sadly, it made no difference. I still get the same error.
  13. Error -1017 (insufficient permissions)

    Hi David, The KB article just appears to address initial setup issues for automated backups. I did that successfully a long time ago. Thanks for the search advice. I had already run a search for Error -1017 in the Professional forum, but this produced a long list of hits relating to different error messages, despite the results being sorted by relevancy. A search for "-1017" was much more useful, though I fail to see why my original search did not include these results. I will now check out those previous posts to see if I can find anything of use in my current situation.
  14. I'm running Retrospect Professional 10.5 under Windows 10 and my backups are stored on a Synology NAS. I have several automated daily backup jobs that have been running successfully for several years, but one of them has recently started to fail with the following error message. Can't access volume XXXX on YYYY, error -1017 (insufficient permissions) My Startup Preferences are configured to use the Retrospect Launcher service, so Retrospect is normally opened and closed automatically. If I open Retrospect manually and leave it open then the job works fine, but when Retrospect is left to launch automatically then it always fails. I have not altered anything in my Retrospect configuration for a very long time and can't think of any reason why its behaviour should have changed during the past few days. Any suggestions would be gratefully received.
  15. Scheduled jobs failed but no alerts were generated!

    Hi JoTRaGo, You have correctly identified the source of my problem! Your post immediately reminded me that I had recently disabled a bunch of services via msconfig.exe as part of an attempt to diagnose some other problem. This happened at around the time my backups began to fail. A quick check showed that the Retrospect launcher is still disabled. Many thanks for your help. Senior moments like this happen when you get older David