Jump to content

tman1991

Members
  • Content count

    28
  • Joined

  • Last visited

Community Reputation

1 Neutral

About tman1991

  • Rank
    Newbie

Recent Profile Visitors

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

  1. tman1991

    R16 really slow backups

    I played around with SMB settings and so far I have to have SMB1 turned on. I havent done what Nigel suggested yet, but found this thread https://community.synology.com/forum/7/post/121376 which suggested IP6 was the culprit. Sure enough I turned IP6 off on my Synology and im back to at least sorta normal speeds. So something happened with MS updates and SMB and MS updates and IP6.
  2. tman1991

    R16 really slow backups

    i think this has to do a windows 10 update that disabled SMB 1.0. I had to re-enable it to even see my NAS. I was running R15 at the time.. Im wondering if there is something also in that w10 update patch that did something else.
  3. tman1991

    R16 really slow backups

    surprised no one else has experience this.. maybe ill try a clean install retrospect instead of overwrite.. but this is pretty much at the point to delete this product and try something else.
  4. tman1991

    R16 really slow backups

    I have been on Win 10 for years so this would only have to do with some patch they pushed. The problem seemed to start I thought with R15 at least with one of the latest builds at least I thought, but brushed it aside as I saw the announcement for R16 so I thought I would just do a clean backup. So this happened in the latest patch of R15 as far as I can tell and was pushed into the R16 code. (or this is a windows 10 monthly patch... but again not sure of which). I can try the new R16 patch or at least make sure i have that. I will look into this Instant Scan option. Not sure how this would have anything to do, as the write times seems to be really slow, as in Retrospect is doing something really slow to make it take forever. - Recall the 7 minutes of backup time per 600MB vs the 10-15 seconds to just copy the file. And yes, nothing changed between my R15 and R16 installs, in fact its been the same config for many many versions.
  5. tman1991

    R16 really slow backups

    im using an \\computer\drive address like i have always done.. Did Win 10 change something to make this super slow? but copying files the same works fine, so something is set wrong or something.. probably user error on something i changed, but would be nice to see if anyone else has this problem
  6. tman1991

    R16 really slow backups

    like 10-15 seconds.
  7. tman1991

    R16 really slow backups

    Ive been using Retrospect since at least version 7 or 8 and never had issues with speed, ive upgraded every version and now either something changed with windows or with retrospect. I did a clean backup with R16. I have approx 2 TB of data across 3 computers. The main computer is running retrospect on M2 PCIe SSD drive with a tradition sata drive attached and the other 2 computers all have normal SSDs (Not PCIe SSDs). I am backing up over a gigabit network to a Synology Diskstation basically using it as a NAS. The last backup of 1.2TB of data took about 7 days. That is clearly crazy. It usually take maybe 12-14 hours. Just as a reference, each of the 600MB files would take like 7+ minutes to write. Any suggestions on what to try? Why is this taking forever to back things up? Almost wondering if I should look at other solutions.
  8. tman1991

    error -1017 in v8.1

    Sorry I wasnt clear.. Last two nights, errors. Not Last nite 2 errors. Same error set as above.
  9. tman1991

    error -1017 in v8.1

    so after 15 days in a row of no errors, last 2 nights errors.. this is really strange?
  10. tman1991

    error -1017 in v8.1

    Well after failing for 2 days, it has not failed for the last 5 or 6.. Retrospec has not been running in the foreground, its from the launched process only. I do not have a user pw.. So scratching my head on this..
  11. tman1991

    error -1017 in v8.1

    Yeah same issue. I cant log on the service without a password.. so either with is an issue. Can this be fixed in a patch? to logon as a user with no pw?
  12. tman1991

    error -1017 in v8.1

    Ok so If I am just having it do a custom backup of certain files and not my whole machine, this really is not needed or I can ignore it seems.
  13. tman1991

    error -1017 in v8.1

    OK what do these errors mean? Is it certain files that its having an issue on? Can I ignore it? otherwise I will just keep it open I guess.. Rather not have a PW for other reasons.
  14. tman1991

    error -1017 in v8.1

    Yes it is being launched by the launcher service -- and I have the box checked use the acct being logged into. However I noticed the files are owned by System -- not my user acct. I tried to change the logon details but since my user acct does not have a password I just put it in a username and nothing else and it did not seem to like that? Maybe I missed something. If there was a way to minimize to an icon on the lower right hand size vs taskbar that would be nice also?
  15. tman1991

    error -1017 in v8.1

    If I run a manual backup on my server machine it works fine and my 2 clients work fine. However if I run a scheduled backup, my 2 clients work fine, but my server does this: Writer "WMI Writer" backup failed, error -1017 ( insufficient permissions). Component "WMI" backup failed, error -1017 ( insufficient permissions). Writer "ASR Writer" backup failed, error -1017 ( insufficient permissions). Writer "MSSearch Service Writer" backup failed, error -1017 ( insufficient permissions). Writer "Registry Writer" backup failed, error -1017 ( insufficient permissions). Component "Registry" backup failed, error -1017 ( insufficient permissions). Writer "COM+ REGDB Writer" backup failed, error -1017 ( insufficient permissions). Component "COM+ REGDB" backup failed, error -1017 ( insufficient permissions). Any ideas?
×