Jump to content

JamesOakley

Members
  • Content count

    63
  • Joined

  • Last visited

Community Reputation

3 Neutral

About JamesOakley

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. JamesOakley

    Backups "freeze" part way with no error

    I am doing this, and it is working. But, if the two scripts require a lock on the same source volume or backup destination, the system will respect that and wait for the lock to exit. But where the scripts are truly independent, one doesn't hold the other up.
  2. JamesOakley

    Backups "freeze" part way with no error

    I've been a Retrospect user for many versions now. When I upgraded from 12.x to 15.x, the Executing tab of Activity Monitor jumped from 1 to 16 units. So it seems that it's a feature as of version 15. At the time, I looked in the release notes, and the only reference I could find was this: So I think (hope) you were asking support to fix a bug that, this time, is actually a feature. I have to laugh. If you read up a few posts, that's exactly what support tried getting me to do. I wasn't convinced at the time, and like you quickly reverted. But seriously: Is this their solution to every support request and bug report? It causes a lot of disruption (you lose your backup session history, but also all the sub-volume and volume group definitions), and shouldn't be something to ask someone to do unless there's reason to believe it will help.
  3. JamesOakley

    Backups "freeze" part way with no error

    Nope. I'd clocked what it was for, which was pretty much as you put it. Except for Sally. I could see a use-case for it for us, actually, with a second office site that could then be backed up as a client to my backup storage. But I'm not sure it's an optimal solution even for that, so I've not done anything with it. I took #7748 to be about a "remote" backup client only in the sense of "not the same computer as the one running the Master copy of Retrospect". In other words, I hadn't noticed the word "remote" as significant. It's funny though, because apart from "remote" that's exactly the issue we're discussing here. I did ask in my support ticket whether my problem relates to that fix. I wonder what they'll say
  4. JamesOakley

    Backups "freeze" part way with no error

    Or even: "Remote Backup: Fixed issue where Retrospect would not time out when searching for a remote backup client (#7748)" Support had me deleting configxx.dat files, so that they were regenerated from the equivalent .xml files. That meant losing all volume information in my installation, which would have meant setting up volume groups from scratch, and then adding source volumes back into each scheduled script before it would run, hoping I remembered correctly how all that was configured. I didn't last long before I put the backup copies of configxx.dat back, and waited for a proper fix, suspecting that a corrupt config file was probably not my problem. Edit: They also got me to uninstall InstantScan from the clients. I can probably re-enable that now.
  5. JamesOakley

    Backups "freeze" part way with no error

    That's more help than I got. I'll wait for the 15.6.x release and upgrade hopefully. Thanks for the good news.
  6. JamesOakley

    Backups "freeze" part way with no error

    Duly reported
  7. JamesOakley

    Backups "freeze" part way with no error

    Before spending time on a Support Request, (from experience) does doing so actually get their attention?
  8. JamesOakley

    Backups "freeze" part way with no error

    This is a pretty serious regression since the 12.x versions. Certain errors (specifically including a client being unreachable) no longer fail elegantly with an emailed report, but cause the whole engine to hang so that nothing is backed up. Further more, the hang is serious enough that it can't be restarted from the dashboard - it requires the task manager with elevated permissions.
  9. JamesOakley

    Backups "freeze" part way with no error

    But if it's running in the background, with no UI visible, it shouldn't pop a dialog that you have to click "OK" to before anything continues. I'm now on 15.6, and it just did it again - no backups ran for 3 days until I noticed that they hadn't. Killed retrospect.exe, and started the program again, and the waiting executions all began to run. The thing is, under 15.x for Windows, even Desktop edition gets multiple execution units, so one stuck job shouldn't freeze the whole setup.
  10. JamesOakley

    Backups "freeze" part way with no error

    Go on, I'm intrigued: when you click "View the message", what is it?
  11. JamesOakley

    Backups "freeze" part way with no error

    Yes, and in fact it can't be an invisible dialog in my case, because the front-end doesn't stop responding, just the engine. So I cannot "stop" the running job - it just sits there trying to connect to the client. I also cannot close the Retrospect main window, and I cannot relaunch it from the dashboard - if I try, nothing happens. But I can browse around the application, read logs, look at selectors, clients, volumes, etc. - none of which would be possible if the program were paused waiting for me to click "OK" somewhere.
  12. JamesOakley

    Backups "freeze" part way with no error

    The dialog issue may be behind this. It's hard to find out, by definition. If that were the case, fixing the z-order wouldn't solve the problem, since Retrospect usually runs without the UI open. If Retrospect is running in the background, the only way to get the UI up to interact with it is to restart it, which cancels any running jobs.
  13. JamesOakley

    Backups "freeze" part way with no error

    I've noted this with 15.5.x (Professional) on Windows 10. The trigger here seems to be if a client is not available for whatever reason. Retrospect hangs looking for that unreachable client. The trouble is, it doesn't timeout like it used to on earlier versions, and move onto the next task. It hangs totally. If you try to close Retrospect, or relaunch from the Dashboard, it never does. The only way to get things back is to kill retrospect.exe in the task manager. I always notice emails telling me that a backup run had a problem. It takes me longer to notice I haven't had any emails from Retrospect for a while, so I need to find out what's wrong.
  14. JamesOakley

    Files missing from Snapshot after Transfer Snapshots

    Thanks! I tried that. It took a while (of course, lots to download) and the log said it was doing a "thorough" rebuild as required. After doing that, I did another "Transfer Snapshots", with the same parameters as before. The job ended quickly, with nothing to transfer. Only, now I've rebuilt the catalog thoroughly, the difference in the two sets is not 900 MB but more like 10 GB. The same directory I had identified as missing is still missing. Again, I can get that directory if I use the "Restore" function instead of "Find Files", which must again mean that the files are backed up but are just absent from the snapshot. Does anyone have any further thoughts or suggestions?
  15. I've just transferred most recent snapshots from a 100+ GB backup Disk Backup Set to a Cloud Backup Set (backblaze) I had to restart half way through - it suddenly bailed out with: [*] TBackblazeConn::b2_upload_file: Request Error: error -1010 (API request bad) () [*] DS3::ds3CloseFile: cannot write to AC000025.rdb: error -1010 (API request bad), resetting m_pos from 3,993,600 to 3,840,000 [*] xopFlush: flush failed, error -1010 (API request bad) [*] xopFlush: flush failed, error -1010 (API request bad) I restarted the Transfer, and the remaining files copied across. ? However, when I do "Find Files" on the resulting backups, the number of files is different, and the cloud set is 900 MB smaller. So it seems some files are missing. But if I re-run Transfer Snapshots, it completes instantly, saying that there is nothing to copy. Retrospect thinks nothing is missing. I tried recreating the catalog, but that didn't help. By using selectors, I've managed to track down a whole folder that's missing - except that it's not missing if I start with "Restore" instead. So I've found what's happened - the files are there, but they are not included in the snapshot. The snapshot file must have failed to transfer. So my question is: How can I ask Retrospect to copy across the Snapshots again, so that I get a complete set of Snapshots - but without having to recycle and re-upload all 100 GB. The other reason to avoid this drastic restart is that, going forwards, something similar could recur, and then recycling would lose older snapshots as well as resetting the most recent one I'm trying to get right. Retrospect 12.6. Windows 10 x64
×