Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


hevanw last won the day on January 22 2019

hevanw had the most liked content!

Recent Profile Visitors

540 profile views

hevanw's Achievements


Newbie (1/14)



  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. The point is. I run the backup. Then after it completes, I immediately run it again, even though nothing was done on that external drive in the meantime. Yet, the backup again manages to find the same set of files to be backed up, and when backing up, the backup set increases with about 250GB. Since I do block incremental, and I'm 100% certain the contents of the files have not changed, 250GB is a weird size for a 1.5TB set of video files (I now noticed, it's only video). Clearly it's doing some block level deduplication, but if it's a matter of some attributes having changed, I should not have 250GB from 1700 files. Version btw is I'll remove the links and see what it does then.
  13. Thanks, but it is a negative to all questions. * All files (and the links which inherit the target file timestamp) have Last Modified dates well in the past. * The folders themselves also have old Last Modified dates. * The links have not been touched (recreated) in 2 months.
  14. I have the following situation. I have an external drive on my Server that has a ton of media files on them. For organization sake, there are a few subdirs on the drive that have hard links to the actual media files. The total number of files linked to is exactly 1698, worth around 1.5TB. I have a dedicated backup set for this external drive, with it's own Selector and own backup script. The selector does exclude the subdirs that contain the links, since the files are already backed up from their normal location. The script has 'block level incremental backup' enabled. Compression is off since these are media files that don't compress well. Now the weird thing: every time I run my Retrospect backup via the script, it finds those exact 1698 files to backup. Backup takes many hours with a total 1.5TB to be backed up and verified. After the backup has completed, I find that the new backup consumed around 250GB on my NAS. The external disk has not been touched so none of those 1698 files have changed one bit, and neither were the links modified. Does anyone have an idea why Retrospect is behaving like this ? First, it should not even backup those files, since they are never touched. But even if it does a backup, the resulting snapshot should be minimal given that nothing has modified. EDIT: I realize I'm actually not quite sure what sort of links these are given these are all Windows systems with NTFS filesystems. I have a Perl script that creates the links with link($to,$from) running in Cygwin.
  15. With the recent Windows October Update disaster, where users have been reporting that their files or even programs disappeared on their machines, I was wondering if I could use Retrospect to just do a compare of a backup and a local folder, and get a report of the differences so that I can see what files are in the backup but not in the local folder. Of course, I could do a restore to a different location and then compare both folders but that seems a bit cumbersome with an unnecessary restore.
  • Create New...