Jump to content

haggis999

Members
  • Posts

    203
  • Joined

  • Last visited

Posts posted by haggis999

  1. My new Windows workstation has 32GB of RAM, so I would not be too worried about losing a bit of it to leave Retrospect running but minimised. However, my current auto launching process usually works fine and usually still lets me open the normal interface, so I'll leave things as they are for the time being. 

    Having decided to go for the V17 upgrade (and a free upgrade to V18 when it arrives), I will probably not consider further upgrades until they make a serious change to the GUI.

  2. I have just finished a lengthy support call from a very knowledgeable Retrospect support technician in Romania, who spoke excellent English. He contacted me by phone and gained remote access to my PC via Team Viewer. The bottom line is that he fixed my problem.

    It appears to have been an issue regarding the credentials for accessing my NAS when using the Launcher Service . My Retrospect security setting is to run Retrospect 'as the logged-in user', which has the side effect that it uses the 'local system account' when launched automatically. That system account was failing to access the NAS (though the error messages gave no indication that this was the cause). He worked too quickly for me to see everything he did to fix the problem, though he did disable an obscure Windows security setting (User Account Control: Run all adminstrators in Admin Approval Mode). 

    After fixing the script on my PC, the Management Console now displays the script correctly, though I won't ever use the console again to modify the source or destination settings. The Retrospect technician did admit that the console was still a work in progress that lack some functionality and suffered from some bugs. The primary benefit of the Management Console is that it will let me check my backup status via the Internet when away from home.

    I doubt if the trial upgrade to V17 was a key factor in this fix, but I am grateful for the rapid provision of competent technical support and will pay for the upgrade at the end of the trial.

  3. Hi David,
    As recommended, I have now raised a formal support request with Retrospect.

    Any distinction you may have previously made between the Retrospect Management Console and the Retrospect Console Preview went right over my head! I just signed up for the only obvious option containing the word 'console'.

    However, I wasn't really expecting the Management Console to be capable of "temporarily reproducing the conditions in which Duplicate has worked" for me on my previous PC. I was simply hoping that it would let me reconfirm the script parameters and offer another method of scheduling its execution (ideally bypassing the Retrospect Launcher service that is failing to run the script in my normal fashion). What I got instead was an impossibly buggy interface (I also mentioned that in my support request). 

     

  4. I was not too surprised to find that V17 made no difference whatsoever to my failing duplicate script  ☹️

    I've just signed up for the Retrospect Management Console, but am rather confused when I view my problem script via the console. The source setting is fine, but I can't drill down to the required folder on my NAS. It only allows me to select one of the top-level shared folders on the NAS.

    To be specific, the script on my workstation is set up to access the Photos/My Pictures - DUPLICATED from PC folder on the NAS, but the Console only lets me select the Photos folder.

     

    EDIT:  I was looking under 'All Network Shares' to specify the duplication destination, but I've just found my correct destination folder under 'All Local' in the Console interface. However, as soon as that problem was solved, another one appeared. The Console insists on ticking the source folder in the destination pane (in addition to my selected folder). Even if I untick that unwanted selection it just reappears when I save the script. The reverse applies In the source pane, so that both source AND destination are selected in both panes!

    When I came out of editing this script to view the list of all my scripts, this duplication script was summarised as having my NAS folder as the source and no destination at all!  Is there a way out of this nightmare?

     

  5. My setup is not quite as you have described. The NAS is the destination for my Retrospect backups. The source for all backups is my primary Windows 10 workstation. It is that workstation that was recently replaced and thus required a reinstallation of Retrospect. The only things I needed to change in my Retrospect scripts were data paths, as the new machine has a different disk configuration from the old workstation.

    The old Windows 10 workstation had no problem working with the NAS.

    I'm not quite sure what you mean by "cutting out the Activity Monitor" when running my duplicate script in a more manual fashion. After setting up a one-time execution via 'Manage Scripts', I then watch it all happen via the Activity Monitor.

    I will check out the new Retrospect Console as soon as I have installed V17. That is not a feature that had previously caught my eye.

     

  6. Unless they introduce new features of genuine interest to me, both V18 and V19 are now less appealing prospects. If a trial of V17 doesn't fix my current bug, even with the help of tech support, I will probably just revert to V12 and wait for a genuine overhaul of the user interface.

    I hope to give V17 a go tomorrow.

  7. Hi David,
    When running my problematic duplicate operation manually I wasn't using the immediate mode. I used Manage Scripts and scheduled a one-off execution. However, a quick test of immediate mode proved that this also worked fine.

    I've just had a reply from Simon Carr, the EMEA Regional Director of Retrospect Inc. He is expecting V18 to be released in the next couple of weeks and has confirmed that if I buy V17 now then I would get a free upgrade to V18. However, the following quote from his email shows that your expectation that this will include a radically revised UI is not correct.

    Quote

    The UI won't be changing too much with v18. There is a new remote UI in the works, which is being developed to enable some other features and architecture, so there will be a UI/UX revamp in the future. Currently I would pencil this in for early 2022 and v19, but that's certainly not set in stone at this time.

    Will installing V17 uninstall V12?  You warned me to copy the password if I wish to revert to V12, but I'm not aware of any password required to install this software (though my Backup Sets do have passwords). Did you really mean to say I should copy the license code?

  8. I run 2 backup scripts and 1 duplicate script on a daily basis (ignoring that extra sacrificial script). The recent failures of the duplicate script on my new PC were all via automatically scheduled executions. Manual executions always run OK.

    My username does indeed betray my Scottish origins, and where I spent the first 40 years of my life, though I now live in the south of England. However, most commercial organisations make no distinction between Scotland, Wales, England, or Northern Ireland. We are all part of the United Kingdom (at the moment). The Scottish National Party aspires to separate Scotland from the UK, but with any luck that will never happen. We are stronger together in my opinion and have been so since 1707.

    Thanks for the free V17 trial suggestion and the warning about that checkbox. I'd missed the free trial option on the main menu and it's not mentioned on the Downloads page.

  9. I have now run a test with a 'No Files' copy of my script set to run 5 mins before the proper duplication script. Sadly, it didn't help, as the No Files script also failed with Windows error 487. Incidentally, I had no problem today in opening the Retrospect interface.

    I have emailed the UK sales office to see if they are prepared to offer a free upgrade to V18 if I buy V17 now.

       

    --Script Summary--
    * Script: MyPicsDuplicateToNAS(no files)
    * Date: 5/16/2021 11:28 AM
    * Errors: 1
    * Warnings: 0
    * Performance: 0.0 MB/minute
    * Duration: 00:00:01
    * Server: Scan 3XS
    
    --Log--
      + Duplicate using MyPicsDuplicateToNAS(no files) at 5/16/2021 11:28 AM
    		[*] MapError: unknown Windows error 487
    		[*] TNetResource::Connect: UNetAddConnection2 failed, osErr 487, error -1001
    		[*] MapError: unknown Windows error 487
    		[*] TNetResource::Connect: UNetAddConnection2 failed, osErr 487, error -1001
    		Can't access volume My Pictures - DUPLICATED from PC... on Photos on Bonzonas, error -1001 (unknown Windows OS error)
    	5/16/2021 11:28:14 AM: Execution incomplete ..
  10. Hi David,
    Many thanks for those suggestions and apologies for my rather slow response. Other matters have taken precedence over the past few days.

    My problematic duplication script failed again this morning (as usual). The error message tends to vary a bit and today's version is shown below. I was intending to try out your idea of using a 'sacrificial' script, but my initial attempts to open Retrospect never got beyond the Dashboard and a never ending wait for it to close the instance of Retrospect running in the background. I had to kill all references to Retrospect in the Windows Task Manager before I was finally able to open the app.

    This had the unexpected effect of launching that duplication script as soon as Retrospect opened. The script completed without any errors on this occasion. Does that offer any further clues to the reasons for my problem?

     

    EDIT:  I have set my Execution Startup Preferences to Enable Retrospect launcher service, Automatically launch Retrospect, and to Stay in Retrospect after script execution is complete. My Security Preferences are set to Run Retrospect as the logged-in user. Those settings are the same as on my old computer and never previously prevented me from manually opening Retrospect.

     

    +	Duplicate using MyPicsDuplicateToNAS at 5/15/2021 9:00 AM
    		[*] MapError: unknown Windows error 487
    		[*] TNetResource::Connect: UNetAddConnection2 failed, osErr 487, error -1001
    		[*] MapError: unknown Windows error 487
    		[*] TNetResource::Connect: UNetAddConnection2 failed, osErr 487, error -1001
    		Can't access volume My Pictures - DUPLICATED from PC... on Photos on Bonzonas, error -1001 (unknown Windows OS error)
    	5/15/2021 9:00:21 AM: Execution incomplete

     

  11. I have just moved Retrospect Professional 12.6.1.101 to a new Windows 10 PC. With the help of the User Guide, I have successfully got my backup scripts working, but one of my daily duplication scripts always generates the following error message. I have no problem accessing the target folder (My Pictures - DUPLICATED from PC) on my NAS via Windows File Explorer and if I run the job again all is well.

    Can anyone explain this rather odd behaviour? My searches for Windows error 487 have not proved very useful so far.  

     

    --Log--
    
      + Duplicate using MyPicsDuplicateToNAS at 5/8/2021 11:00 AM
    
                            [*] MapError: unknown Windows error 487
    
                            [*] TNetResource::Connect: UNetAddConnection2 failed, osErr 487, error -1001
    
                            [*] MapError: unknown Windows error 487
    
                            [*] TNetResource::Connect: UNetAddConnection2 failed, osErr 487, error -1001
    
                            Can't access volume My Pictures - DUPLICATED from PC... on Photos on Bonzonas, error -1001 (unknown Windows OS error)
    
                5/8/2021 11:00:23 AM: Execution incomplete ..

     

  12. On 7/11/2019 at 5:30 AM, Lennart_T said:

    Not necessarily. It is just the last link in a long chain of things that can go wrong. See it as the messenger, if you wish.

    Too bad the catalog file isn't a simple text file. That way you could have opened it in Notepad (for instance) and see if you could make changes and save. 

    By the way, do you have more than one version of Retrospect installed? Both could be running and one could be locking the catalog file from the other. 

    Maybe you have anti-virus software installed that interferes with Retrospect.

    Apologies for the long delay in updating this thread. Among other things, I have been very busy supervising a house extension.

    I must confess that I never noticed Lennart's reference above to antivirus software, but about two weeks later I found a suggestion in some other forum that made me suspect that Microsoft Windows Defender (which now seems to be called Windows Security) might be the cause of my problems. Within its Ransomware Protection settings there is an option called 'Controlled folder access'. I turned off that option on 29 July and my daily Retrospect backups have been running fine ever since!

    One strange byproduct of using the 'Controlled folder access' option is that I found my attempts to save a modified Word or Access file under a new name was rejected on the grounds that the file did not exist. Of course the file didn't exist. That error message made no sense at all. I can only assume that Microsoft introduced a bug into into its security software via a recent update.

  13. 7 hours ago, Nigel Smith said:

    Have you got the new drive fitted yet?

    If so (i.e. hardware fault is now out of the equation), I'm thinking you've hit an internal limit on catalog size/contents or member size.

    How big is the "locked" catalog file (in Windows Explorer). In Retrospect's properties for that Backup Set, what's the "Used" space and file count?

    Then copy that locked file of to your C drive, back to G, and "relink" it as you did before to unlock it. Check the above again -- what are the numbers this time?

    If the unlocking trick works, try adding another member and continuing the backups. If everything continues working it was a "member size" limit (Ooo-errr!), probably from a weird coming together of RS, Windows 10, and Synology's volume presentation. If, however, the catalog "locks" again very quickly you may have hit a file-count limit -- you might be able to groom the old catalog and then carry on, but maybe it's time to start a new set.

    Otherwise, it's log time! Towards the bottom of the page from David's link above you'll find instructions on how to access "Secret Preferences" and change the log levels. You can generate a lot of noise with these, so I'd start by leaving everything as is except for winding up "Backup Sets and Catalog Files" to the max. Try another backup and let us know what the Operations Log reports.

    Yes, the new drive has been running for several days. The size of 'Backup Set NAS1.rbc' is 527,579 KB. The properties box for that backup set tells me that it is using 1,440.8 GB for 619,113 files. Copying the RBC file to my C drive and then copying it back again to my G drive made no difference to those properties. It also failed to fix the locked catalogue issue.

    There was a grooming event shortly after this backup started working again a few days ago, which erased around 118 GB from the backup, so file count issues seem very unlikely.

    I opened up the Secret Preferences and wound up the debug logging setting for Backup Sets and Catalog Files to 99. However, this setting was rejected and it was automatically set to 7 instead. I then attempted once again to run the backup job. It failed almost immediately, just like before. The only differences in the log file were the top 2 lines shown below.

        ArcPro::DbExportToXML: no volRef returned for 1-Backup Set X
        ArcPro::DbExportToXML: no volRef returned for 1-Dell 7500 Backup Y

    +    Normal backup using MyDocsBackupToNAS at 09/07/2019 22:30
            Can't add to Backup Set Backup Set NAS1, the Catalog File is locked    09/07/2019 22:30:16: Execution incomplete

     

  14. 20 hours ago, DavidHertzberg said:

    haggis999,

    These are simply a couple of WildA**edGuesses from a Retrospect Mac administrator:  First, the cumulative Retrospect Windows Release Notes say for version 15.5.0 (which is later than you're running, but it may only cost you US$75 to upgrade the Desktop Edition)

    Second, look in the "Security Settings" section of this KB article, which was updated 15 May 2018 for Windows 10.

    Hi David,
    The last time I paid for an upgrade purely in the hope that it would fix a long-standing bug, it proved to be a waste of money. I'd be happy to pay for v15.5 if I felt more confident that it was going to fix my current problem, but a bug fix for cloud backup does not immediately appear relevant to my situation. That KB article is all about issues with troubleshooting email notifications and that's something that has never ever been a problem for me.

  15. Sadly, the problem did not stay fixed for very long. Once again, I am getting the following emailed warning from Retrospect. This backup job worked fine the previous day and I had made no changes of any kind.

    • From Retrospect: Script "MyDocsBackupToNAS" failed during automatic execution, error -1017 (insufficient permissions). Please launch Retrospect and check the log for details.

    The log doesn't repeat that reference to error -1017. It simply reads as follows.

    • Can't add to Backup Set Backup Set NAS1, the Catalog File is locked    07/07/2019 13:00:02: Execution incomplete.

  16. 12 hours ago, Nigel Smith said:

    Meh -- computers!

    I'm afraid my stock answer in these situations is "Don't know why, don't care why -- it worked, and that's enough for me!".

    Any chance you can increase the capacity on your Synology next? Looks like you're below 10% free space so, depending on how it's formatted, you might be taking a hit to write speeds. Of course, if performance is still OK for your workflow, carry on as you are 😉

    I share your pragmatic attitude to such situations. While it would be nice to know why that fixed the problem, my only real concern is that it stays fixed!

    The space on my primary NAS is indeed getting a bit tight and I plan to add a fourth disk to my Synology Hybrid RAID array in the near future. If there has been a drop in performance it hasn't been obvious.

  17. 9 hours ago, Nigel Smith said:

    Totally normal. chkdsk reports on "current usable disk", and doesn't include those previously found bad sectors -- they've already been re-allocated (note that it doesn't say that there are no bad sectors but that you have "0 kb in bad sectors" -- not quite the same thing). S.M.A.R.T. works at the hardware level and so also reports those sectors which have previously found to be bad and thus re-allocated.

    Hopefully, the new disk will sort things out. Otherwise the steps you took above indicate that you have read access to the catalog file (could do a restore) but not write access (the repair options you chose require the original catalog to be deleted). You could always try copying the catalog over to your C drive and using it from there. Or you could do a complete rebuild to a new file in a different location.

    Hi Nigel,
    Thanks for the useful explanation of how chkdsk differs from S.M.A.R.T.

    I copied all the files from the G disk that displayed S.M.A.R.T. errors in CrystalDiskInfo to my new disk and modified the drive letters so that this new disk is now the G drive. Sadly, this made no difference to my problematic Backup Set NAS1. Retrospect still told me that the catalogue was locked.

    However, your suggestion to copy the catalogue file to my C drive (and redefining the Backup Set accordingly) eliminated that problem and the associated backup job completed without error. I then recopied the modified catalogue file back to the G drive and ran my backup again from there (after ensuring that at least one file had changed). This also worked without error, so it looks like my problem may have been resolved.

    I'm very grateful for your assistance on this, though I'm not quite sure how copying the catalogue was enough to unlock it.

  18. I have now downloaded a free tool called CrystalDiskInfo, which provides S.M.A.R.T. analysis of internal drives. This gives a health rating of 'BAD' for my G drive, mainly due to a Reallocated Sector Count of 3 (it also places a warning flag on the figures for Current Pending Sector Count and Uncorrectable Sector Count). It therefore seems odd that chkdsk claims there are zero bad sectors.

    Since I am also getting low on space, that has prompted me to order a new and larger disk.

     

  19. I think running chkdsk via a command prompt is just the same as running Properties > Tools >Error checking for the relevant drive (which is what I did originally).

    The results were the same:

    Windows has scanned the file system and found no problems.
    No further action is required.

     976759807 KB total disk space.
     945051668 KB in 323994 files.
        173624 KB in 30000 indexes.
             0 KB in bad sectors.
        639471 KB in use by the system.
         65536 KB occupied by the log file.
      30895044 KB available on disk.

          4096 bytes in each allocation unit.
     244189951 total allocation units on disk.
       7723761 allocation units available on disk.

  20. 10 minutes ago, Lennart_T said:

    Did that coincide with a Windows Update? ...and with the Retrospect problems starting?

    Did you do a surface scan also? If not, please do.

    Both problems occurred at about the same time and I had already speculated that a Windows update might have been the cause, but my PC is still running version 1809 of Windows 10 Pro, which I think has been the case for some time. 

    I'm not quite sure what disk checking utility you mean by 'surface scan'. Are you referring to chkdsk /scan?

  21. 2 hours ago, Lennart_T said:

    I still think something has gone wrong with the permissions.

    Does Retrospect run as the logged in user, or as another user (set up in Retrospect's Preferences)?

    If you run (for instance) Notepad or MS Word as the same user as Retrospect is running, can you create and edit a document in the same folder as where the catalog file is?

    Earlier in this thread, I stated that "My Retrospect security preferences are set to run as the logged-in user. My normal user login has full control over the relevant catalogue file."

    I have just saved a Wordpad document in the Retrospect catalogue folder, closed and reopened Wordpad and was able to successfully save changes to that document, so normal access to that folder on my G drive does not seem to be a problem. However, a couple of very old apps (AutoCAD 2000i and Quicken XG 2004) recently started to have problems writing to my G drive. I've run the normal Windows disk checks, but no faults were found. 

  22. My attempt to repair the catalogue failed with a -1017 error, so I did my best to follow the above-mentioned troubleshooting process.

    • Both my PC and the relevant Synology NAS have been rebooted
    • Retrospect has been started manually after stopping a couple of RS processes in Task Manager
    • As an initial test, I ran a restore of a single file from the affected Backup Set (called 'Backup Set NAS1'). This restore was successful. Backup Set NAS1 is only used to back up files stored on my PC.
    • The Synology DSM interface tells me that the NAS has 143.5GB of free space. This NAS is used for one other Backup Set (for Outlook emails) and a daily digital image duplication task.
    • The PC hard disk that holds all my RS catalogue files has 30GB of free space
    • RS itself is stored on my C drive, which has 62.1GB of free space
    • The Members tab of the Properties box for Backup Set NAS1 shows that it is currently using 1,562.0GB with 8.7GB free space. I opened the Properties box for that member and increased the max size of the member to 1,580GB and clicked OK. This then showed that there was now 26.7GB free space.
    • After closing and reopening the Properties box for Backup Set NAS1, the sizes had reverted to the previous settings and once again there was only 8.7GB free space
    •  As mentioned in a previous post, the Add button on the Members tab for Backup Set NAS1 is greyed out
    • I initiated the MyDocsBackupToNAS job that has been failing (after limiting the scope of the backup, in light of the limited free space), but it failed almost immediately with the Operations Log listing the error "Can't add to Backup Set Backup Set NAS1, the Catalog File is locked. Execution incomplete." 
    • I then tried once again to run a Repair Catalog process, using the Recreate from disks option. The selected disk source folder was 1-Backup Set NAS1 and I took the option to recreate the catalogue file under the original name. This instantly failed with the error "Couldn't create Backup Set Backup Set NAS1, error -1017 (insufficient permissions)."
×
×
  • Create New...