Jump to content

Hofstede

Members
  • Posts

    153
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by Hofstede

  1. All individual files on the disk are stored encrypted.

    - after Windows has booted up to its login screen thief still has to login. Without login he cannot access anything.

    - If the thief puts the disk in another computer he needs the BitLocker key to read or change files on the disk.

    - If the thief boots the computer from USB stick he needs the Bitlocker key to read or change files on the disk.

     

    Retrospect can backup the computer through Retrospect client without a human user actively being logged in. That’s because Retrospect Client is running in the background under a standard Windows account (Local System) and that account can read files.

    So of course you should have set a password on the Retrospect Client to prevent someone accessing the unencrypted files through the Retrospect API.

     

     

  2. That is not correct, if you start the computer without logging in, Retrospect can still backup just fine. 
    During Windows startup the disk is already unlocked by Windows, otherwise Windows wouldn’t be able to start. 

    You really only need the Bitlocker key if you need to recover Windows if it fails to start or if you want to access the data on the disk from other hardware (e.g. when your computer fails and you put the disk in another computer).

     

     

  3. Bitlocker encrypts the file when written to disk. It decrypts the file when read from disk. So if any program (including Retrospect) reads the file from disk it is unencrypted. So the Backup sets contain files that are unencrypted.

    To be clear: I am not talking about the backup set files themselves.

  4. I am using Retrospect 17 with 4 Windows 10 Pro machines that have Bitlocker encryption enabled and I didn't encounter any issues with backups. Bitlocker encryption works on a much lower level so I think Retrospect and Retrospect client are completely unaware that Bitlocker is enabled.

    Only thing to consider is that the files that Retrospects writes to the backup sets are unencrypted. So if you are worried about that you need to encrypt the backup set as wel.

  5. Just installed Retrospect 17. Installed without a hitch.

     

    However, first thing I notice that you now get a very annoying popup window telling you which clients ProActive backup is currently trying to connect to. 

    To make things worse is that this popup even covers the window you are currently working on, so you have to close it or move it aside to continue. Really?

     

    Please give us an option to disable this popup or only let it pop up in the background, not in the foreground.

     

  6. I can see that a Wiki article about Retrospect might be of use for others, although I personally never trust information that comes from a Wiki article and I certainly would not use that info for something as mission-critical as backups.

    What I don't understand is why all the trials and tribulations of a certain Mr. DovidBenAvraham editing that article and the problems he has with other Wiki moderators needs to be discussed here. 

     

     

  7. I am sorry, I should have worded it differently.

    I have set Retrospect to "Always run Retrospect as the specified user" and then used the same credentials for the user that I normally use to login.

    This allows the program to start the service while you are not logged into the machine and also gives it the same authorisations you have when you login. 

    If you are using a Microsoft Account to login to Windows 10:

    Username: The email adres of your Microsoft Account, something like xxx@outlook.com

    Password: The password you use for your Microsoft Account

    Computer: Name of your computer.

     

    Has been running fine for me since years.

    Remove the shortcut.

     

     

     

  8. Thanks for the heads up, Jeff.

    Just as a sidenote: There is another backup program vendor that encounters exactly the same issues as Retrospect after the Windows spring 2018 update. Their solution is to turn of the OneDrive feature that causes all this.

    So this would also indicate that it is more a Windows 10 issue than an Retrospect issue.

     

  9. Are you sure every file has been downloaded from OneDrive? So OneDrive is fully synched? Also clear the Recycle Bin.

    No other users on the computer that also use OneDrive?

     

    I can also reproduce this now on one of the machines that have worked without a problem up till now. Turning the option on causes the -1103 error to occur. Turning the option off makes the backup work again.

    Turned On:

    -    8-5-2018 22:23:24: Copying SysteemSSD (C:) on Marc1
        Scanning incomplete, error -1103 (write protected)
     

    Turned Off:

    -    8-5-2018 22:26:16: Copying SysteemSSD (C:) on Marc1
            8-5-2018 22:28:31: Found: 400.149 files, 89.455 folders, 172,2 GB
            8-5-2018 22:28:38: Finished matching
            Backing up 3 out of 8 files using block level incremental backup, storing full backups for remaining 5.
            8-5-2018 22:29:15: Copying: 6.769 files (5,5 GB) and 3.129 hard links
        8-5-2018 22:32:10: Building Snapshot...
            8-5-2018 22:32:11: Copying VSS writer files
            8-5-2018 22:32:16: Finished copying VSS writer files
            8-5-2018 22:32:20: Copying properties for 89.455 folders
            8-5-2018 22:32:55: Finished copying properties for 89.455 folders and 0 files
            8-5-2018 22:32:57: Copying UEFI System Partition
            8-5-2018 22:33:19: Copying Snapshot: 387 files (312,3 MB)
            8-5-2018 22:33:25: Snapshot stored, 312,3 MB
        8-5-2018 22:33:25: Execution completed successfully        Completed: 6769 files, 5,5 GB, with 57% compression
            2,0 GB already copied by block level incremental backup
            3,6 GB stored for this session
            Performance: 2067,9 MB/minute
            Duration: 00:07:09 (00:04:26 idle/loading/preparing)
     

     

    Another thing to try (this I did first)

    - Logout the OneDrive app.

    - Stop the OneDrive app

    - Delete the OneDrive folder.

    - Empty Recycle Bin

    - Test backup

     

  10. Ok, I did some additional  debugging and I found the issue: It's OneDrive.

    OneDrive has an option (don't know if it's new with 1803) that gives you the possibility to only actually download a file from OneDrive to your computer if you actually use it. All files in the OneDrive folder are shown as being present, but they are not actually physically present on your computer. So they are some sort of link. The explorer shows a cloud symbol with these files.

    As long as one such link is present on the drive (even if it is in the Recycle bin) it will cause the -1103 error. Scanning will be interrupted as soon as the scan engine hits the OneDrive folder.

    On both machines I turned the option off in OneDrive settings, which caused all OneDrive files to be downloaded to the computer, and both are backing up properly now, without errors.

    Also checked the machines that never showed the issue, they all have this OneDrive option set to off.

     

     

     

     

     

    • Thanks 2
  11. @eppinizer:

    The first machine I had the problem on is an Intel Compute Stick (STK2m3W64CC) running Windows Home. This machine has the default Recovery, EFI and Windows partition created by Windows during install.

    This machine performed backups normally after I wiped the drive and did a clean Windows 10 Home install. But after a day the problem returned.

    The second machine is an Asus Zenbook UX305LA running Windows Pro. This machine has an EFI, Recovery, Windows system and a data partition.

    On this machine I also tried a complete wipe and reinstall. After reinstall the machine only had the standard Recovery, EFI and Windows system partition. But even after this completely fresh install I have the -1103 error. The only software I installed on this machine after the fresh install was the Retrospect 15.0 client. So no custom drivers / software whatsoever.

    So it looks like the error pops up during the scanning of the volume. With older versions there was an option for advanced settings (ALT-P-P ?) so you could increase logging. Is that option still available?

     

  12. The machines that don't work are 3 and 1 years old. The 4 machines that work are ranging from 6 years to 3 months old with all kind of different processor types.

    For testing purposes I did a complete reinstall of one machine (after making an image backup). 

    - Reinstall Windows 10 over existing install without keeping settings: Same error.

    - Reinstall Windows 10 after completely removing all partitions on the drive: Backup works again.

    Going to try that on the other machine tonight.

     

     

  13. I am sorry, but we are talking about clients generating an error. So in my opinion nothing to do with the server and location of catalog files. (And I already have my catalog files in a different location for ages).

    With some additional testing I discovered:

    - Reverting to previous Windows 10 build: No -1103 errors. Everything works as expected.

    - Reinstalling build 1803: Error returns. 

    - Cleanup, disk check, "sfc /scannow", reinstall Windows 10 1803 over existing install did not help.

    - Backup runs if you turn "Backup open files" off. So it probably has something to do with VSS.

    On the client machines I don't see any errors whatsoever in the event logs. So it is hard to figure out what causes the scanning process to fail.

     

    Difference between the 4 that work and the 2 that don't is that I reinstalled the 4 machines that work  a few months ago, the 2 that don't work have never been reinstalled.

     

     

     

  14. I am seeing the same thing, running Retrospect 15,  with 2 out of 6 Windows 10 clients that have been upgraded to the Windows 10 April Update (v1803).

    So 2 have this error after update, the other 4 do not.

    Reverting the Windows 10 April Update on the 2 clients fixes it.

    Did not have time to investigate further yet but it would be nice to know what exactly is write protected on the client.

     

     

     

     

  15. Wow! Personally I think you are over-reacting,

     

    It seems you cannot accept that other people have different opinions than you. Everyone that does not agree with you is against you. And that gives you the right to start name-calling and offending people.

     

    Your two "explanations"  only confirm what I initially thought: Childish.

     

    I know that you will not see it that way (obviously).

     

    I will be the sensible one and stop this discussion. From now on you are on my ignore / block list for this forum. But I would seriously urge you to think about your attitude.

  16. This app hasn't been updated for more than 2 years. So I think Retrospect stopped the development.

     

    I had several issues with it. It can cause your Retrospect server to crash while you access it from the app in some circumstances.

     

    I stopped using it.

×
×
  • Create New...