Jump to content

hevanw

Members
  • Content count

    39
  • Joined

  • Last visited

  • Days Won

    3

hevanw last won the day on January 22

hevanw had the most liked content!

Community Reputation

4 Neutral

About hevanw

  • Rank
    Advanced Member

Recent Profile Visitors

336 profile views
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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 12.6.1.101. I'll remove the links and see what it does then.
  7. 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.
  8. 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.
  9. 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.
  10. hevanw

    Error -1101 after Windows October Update

    Yes, I know about that, but don't think it's the case in my problem. In fact, should first have searched on the site here. This problem has occurred for others in the past. E.g. here : So I did the ias.xml thing and rebooted the server, and this also for me seems to have fixed the problem.
  11. Another big Windows Update, another problem. I run Retrospect 12.6 on my Windows 10 Pro home server. It makes backups of 4 client PCs, and also a backup of its own filesystem. After applying the Windows October Patch to the Server, the Server's own backup now reports the following errors. Interestingly, the client backups still run just fine. Writer "NPS VSS Writer" backup failed, error -1101 (file/directory not found). Component "NPS Database" backup failed, error -1101 (file/directory not found). The Server backup is run as a Scheduled backup, while the client backups are proactive. Apart from the 2 errors however, the operations log seems to indicate that all files got backed up. Any an idea how to fix this, or can these errors be safely ignored (though I don't like seeing daily Errors in my History).
  12. hevanw

    Error -1103 after Windows 10 April Update

    While trying to recall if I had installed anything on her laptop, I realized that indeed I had installed Roblox right before leaving on vacation so our son could play it on my wife's laptop. And so I realized that after all, this is again the same OneDrive related problem. I had created his own account on the laptop, which then also automatically enabled OneDrive on his account. Unlinking OneDrive for his account solved the problem. Linking it back later however had the problem re-occur again, which it did not in the past. But so for now, I have just disabled it, since he does not need OneDrive on my wife's laptop.
  13. hevanw

    Error -1103 after Windows 10 April Update

    This error -1103 is driving me crazy. Everything worked fine for months. Then went on vacation with the family. 10 days later we return and my wife's laptop is aborting every C-drive backup with the notorious error. Again no clue why this is suddenly happening. She was already on Windows' April Update for several months so has nothing to do with that.
  14. hevanw

    Error -1103 after Windows 10 April Update

    Excited to report that I got my Retrospect backups fixed now as well !! So, disabling the "Save space and download files as you use them" setting did not work for me. So in addition to that, I tried disabling OneDrive altogether (Unlink PC/account and then remove the entire OneDrive folder) and then linking my account again which then again downloaded all files. The next Retrospect scheduled (proactive actually) run then succeeded with 0 errors or warnings ! This worked now on 2 machines already, so will try kids laptop next, but pretty confident this will work as well. Thanks to the folks active in this thread !
  15. hevanw

    Error -1103 after Windows 10 April Update

    Thanks! I can confirm that OneDrive is a real folder, not a reparse point (tried both your methods). However, your second method does not yield 'File Not Found' but a bunch of other folders under my homedir: Application Data, Cookies, Local Settings, etc.... which all show up as <JUNCTION>. Also, I'm the only user on this specific machine so I'm certain there are no other OneDrive folders. I'll give Lucky_Phil's approach a try though.
×