Jump to content

hevanw

Members
  • Posts

    49
  • Joined

  • Last visited

  • Days Won

    3

hevanw last won the day on January 22 2019

hevanw had the most liked content!

Recent Profile Visitors

630 profile views

hevanw's Achievements

Newbie

Newbie (1/14)

  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done Rare

Recent Badges

5

Reputation

  1. Great, got it working with 4 parallel executions. Interestingly enough, the Desktop license does allow me to create Sets as Storage Groups, even though the feature matrix says it's only available in the Server licenses. EDIT: apparently I accidentally had posted this in the wrong subforum.
  2. Ah that is great news, thanks. I have separate backup sets for all my clients, so this would then mean that I can have parallel backups of each, which is exactly what I had hoped for. Yes, I had seen that all subsequent updates were primarily about supporting the latest Windows versions and seasonal releases. I never ran into issues backing up, but like you state, the main question is also about restoring. I admit that I have not tried to restore anything yet with Windows 11 so maybe I was running a risk there that I wasn't even realizing. Which reminds me to soon do a couple test restores again. Anyway, guess I will be upgrading to 18.
  3. I'm currently still on Retrospect 12 Desktop. Considered upgrading to 18, but at first sight there is nothing really compelling to upgrade for. The one thing that confuses me though, is with respect to parallel backups. The Feature Comparison matrix at https://www.retrospect.com/en/products/compare says that Desktop has 4 concurrent operations. I read this like there can be 4 concurrent executions (e.g. backups) in the engine. However, I then ran across an explanation of Storage Groups (which is only available in the more expensive Server versions) and that one says : "Protect an entire backup environment up to 16x faster with a single, centralized destination that Retrospect can use simultaneously. With Storage Groups, customers can run parallel backups to the same disk or cloud destination, reducing the backup window." which clearly seems to suggest that without Storage Group you can only backup 1 client at a time ?! Can anyone clarify ?
  4. After I installed VirtualBox on my home server, Retrospect is considering the new virtual network interface of VirtualBox as the default interface. The result was that none of my clients were detected anymore and no backups were running. I now worked around it by adding a new interface with the original subnet of my hardware interface and reconfiguring the clients on my Retrospect server. I also tried manually setting the interface metrics in Windows 10 to prioritize the hardware interface, but to no avail. Even after a reboot, Retrospect is considering the virtual interface as the default one. Is there a different way to force Retrospect back to the original default interface ?
  5. I now have a 2nd machine that got the upgrade, and which I wanted to give a try. This one has no issues at all with Retrospect 12 and has backed up nicely at full speed. So the issues with my 1st laptop are likely not to be related to Retrospect. EDIT: issue with the 1st laptop is now also resolved. It looks like you may have to log in in Windows 10 b2004 with every locally defined user first. For every local user that logs in for the first time again after the update, Windows still is doing quite a bit of activity, which may be required to have Retrospect be able to access some files.
  6. I would definitely advise against upgrading if you still want to backup with Retrospect. I have 5 machines, and my oldest, least important, machine now has 2004. I seem to have 2 big problems: * The backup will run extremely slow at times : less than 3MB/minute. Not clear whether it's related to what files are being backed up or some general networking issues. At times it will speed up to the regular >200MB/minute. * The backup will abort/fail before completion with : " Scanning incomplete, error -1001 (unknown Windows OS error) " I must admit though that I am still on version 12, because I don't want to pay for an upgrade every year.
  7. There were a lot more files that were exhibiting this issue than I thought. Some were also dll's in subfolders of Program Files, etc... As this didn't look like a healthy situation at all (still surprised my wife didn't run into any issues with the laptop) I ended up reinstalling Windows from scratch. And that obviously also solved the Retrospect problem.
  8. Looks like a OS problem indeed. I looked at some of the files that Retrospect is reporting the error on. Apparently I cannot access/copy those files with a weird error : "0x80070157 - External backing provider is not recognized." Already googled some but can't really find a good solution. It looks though that these are files that I may not need, so I have moved the relevant folders into a TEMP folder so it gets excluded from the backup and will see from there.
  9. Seems highly unlikely because the client machine otherwise acts perfectly fine, so there is definitely not an issue with corrupt filesystem or something along those lines. My further investigations now go toward The Volume Shadow Copy. Each time Retrospect runs, I see a couple of VSS Access Denied errors in the Event Viewer of the client. However, these errors seem to have been there already before I made the SSD swap.
  10. After I upgraded the SSD in my wife's laptop, I am getting thousands of errors on each backup run for that laptop. I even did a reinstall of the Retrospect client and a Recycle backup, but the problem remains. Ths SSD upgrade was done by cloning the old SSD to a new one using Clonezilla. The errors are as follows, and this for many thousands of files. Client runs Windows 10 Home. Server runs Windows 10 Pro. Retrospect is 12.6.1.101. File "C:\ProgramData\O949\langpack-sr@firefox.mozilla.org\chrome\sr\locale\sr\global\finddialog.properties": can't read, error -1001 (unknown Windows OS error) [*] T-35: --ERR-- (10856) TPipelineMgr::tryStartPipeline: m_outQ->error=-1001 m_whyEnd=-1001 [*] T-35: --ERR-- (10856) TPipelineMgr::tryStartPipeline: error=-1001 [*] T-35: MapError: unknown Windows error 343 [*] T-35: can't read data, BackupRead failed, \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy113\ProgramData\O949\langpack-sr@firefox.mozilla.org\chrome\sr\locale\sr\global\global-strres.properties, osErr 343, error -1001 [*] T-35: --ERR-- (2372) ReadStation tryReadFile: BRRead err=-1001 [*] T-35: --ERR-- (20336) Terminal: workUntilEnd:-1001 seq=0 [*] T-35: --ERR-- (20740) ChecksumStation: workUntilEnd:-1001 seq=0 [*] T-35: --ERR-- (2372) ReadStation: workUntilEnd:-1001 seq=1 [*] T-35: --ERR-- (10856) BackupReadCloseAsync: err=-1001 I already googled a bit and looked at the forum here, but could not find a solution. In the client's Windows Event Viewer I also don't seen anything that should pertain to this. Hope someone has some suggestions because I'm out of options.
  11. Ok, typical, after a reboot (Windows 10 update), I figured I give it a test. Obviously I now cannot reproduce it with the turning on the above settings. So it still must be some combination of things that lead to the issue, but with the settings above turned off, it definitely solved the problem.
  12. Sure. It's the 4 options at the top of page 380. All 4 are on by default, and I turned all of them off as I didn't really need the permissions, etc to be backed up. Since I did disable both these 4 options, as well as the Unix Client option "Use status modification date when matching", I'm not sure which of both are the true fix for my problem. I'll do another quick test tonight to see which one really fixed it.
  13. Ok, problem solved (or worked around). I followed the advice from this old thread, even though this is a NTFS drive under Windows : But I also removed all the tickboxes under the Windows Security backup options in the script. Disabling both (which I don't really need anyway) does solve the problem and a re-run doesn't backup anything anymore that was already backed up before.
  14. More testing done... When the hardlinks are not there, a 2nd (and subsequent) Retrospect backup no longer does duplicate backups, so is behaving fine. However, as soon as the hardlinks are there, it will backup again. Also if the hardlinks are removed then, it will again do 1 backup, after which it's fine again. I was thinking of a workaround of removing the links prior to doing the backup, but so this would not work, since the moment you set the hardlinks, Retrospect will force backup these files, even if the hardlink was already removed again.
  15. Ok, I'm onto something although I can't quite find yet what is happening. I inspected the previous snapshots to see what was in it, and there I can clearly see that the 1698 files that are backed up either compress to 99%, or do not compress at all. It turns out that all MP4 files do compress to 99% which obviously means that Retrospect somehow identifies them as already backed up. However, other file formats do not compress at all and basically Retrospect backs up the file entirely. This explains why I'm 'only' ending up with a 250GB increase for a 1.5TB file set. It almost looks like some process is touching these files, though I cannot imagine what it would be and why the files would be modified. Not even sure they are modified to begin with. One of the things I can test is to take an MD5 checksum of a file before running Retrospect at multiple times and see whether the MD5 stays the same or not.
×
×
  • Create New...