Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by Scillonian

  1. Disaster Recovery Disk Method

    Are you running a version of Bootcamp on the Mac Mini that is compatible with Windows Vista? From what I have read Apple started to drop support for Windows Vista with version 3.2 and dropped it completely by version 4.
  2. In this respect there is no difference between 12.5 and 12.6.
  3. On the Windows platform Retrospect is a monolithic application. The reason for the behaviour you have observed is because of security features that were introduced with Windows 7. In short the restrictions are that any application that is automatically launched in not able to interact directly with a user, even if it was launched as that user. For Retrospect to Work on Windows the same way it does on Mac will [apparently] require a substantial rewrite. There have been hints in the past from Retrospect staff that they thinking about doing this, maybe, one day but that is about it for now.
  4. Disaster Recovery Disk Method

    You only need to create the Disaster Recovery Disk on the Backup Server. If you have a valid Disaster Recovery license on the Backup Server the functionality will be added to the Disaster Recovery Disk. When you boot the Client from the Disaster Recovery Disk the Dissimilar Hardware Restore will be available.
  5. Retrospect 12.x Cannot Backup System State

    Hi Tony This line is telling the user that Retrospect is trying to backup the System State but the underlying Windows function that is called is returning an error condition to Retrospect that Retrospect dose not understand. This would indicate to me that there is some problem with the 'EFI System Partition' which isalso referred to as the ESP. The ESP is a small hidden partition ~128 MB in size which contains the files necessary to boot an operating system on a device with UEFI firmware. A good place to check first for what the problem may be with the ESP is the 'Event Viewer' in Windows. Look for any error or warning events at the same time as Retrospect reported the error. Initially look for errors/warnings where the 'Source' is VSS (Volume Shadow Copy Service) as this is the Windows feature that provides the System State data. EDIT: What version of Windows are you running?
  6. ?corrupt data file - how to fix in 12.6

    The only solution I have found is to delete the corrupted .rdb file — in your case AA000077.rdb. Once the file has been deleted rebuild the Catalog file during which Retrospect will give a warning about the missing .rdb file. Grooming should now run to completion on the Backup Set as long as there are no other corrupt .rdb files. If there are then repeat the procedure. What I will add is that by manually deleting a .rdb file the integrity of the Backup Set is now compromised. When I have encountered this in the past I have as soon possible afterwards retired the Backup Set and transferred its contents, less what is in the missing file(s), to a new Backup Set. I have not found a way to directly repair a corrupt .rdb file but it is sometimes possible to recover the active contents of the file, if you really need to, by doing a Transfer Snapshot for the appropriate date to another Backup Set.
  7. only scan specific folders

    My interpretation of the description of FileChangeNotify in the link you provided is that is related to the synchronisation of file data between the native file system and emulated file system(s). On a NAS it is quite possible that an individual file can be changed from the host Linux OS, a Windows machine through SMB/CIFS, an OS X machine through AFP, and a Linux machine through NFS. Any change from one access method has to be propagated to the other access methods. However there still remains the problem of installing the Retrospect Client on a Linux based NAS. Most Linux based NAS devices use a custom Embedded Linux where it can range from difficult to impossible to install any third party system level applications such as the Retrospect Client. Instant Scan would ne nice to see on Linux but I suspect development of it would be a low priority because of the low, relative to Windows and OS X, user base and the added complication of testing on the many more file systems native to Linux compared to Windows and OS X.
  8. only scan specific folders

    For a Linux or BSD based NAS the NTFS file system that a Windows PCs would see when accessing a share through SMB/CIFS is an emulation provided by Samba. This emulation translates the NTFS file attributes and metadata to their nearest equivalents on the underlying Linux or BSD file system (e.g. ext4, XFS, UFS, ZFS, etc).
  9. 1 Raid 10 vs multiple raid 1 members

    With an array using 6TB drives I would recommend RAID6. I would not recommend RAID5. With RAID5 and >2TB drives the statistical chances of a total loss of the array because of an Unrecoverable Error (URE) during recovery from a single disk failure become increasingly high. Many factors influence how long it takes a RAID array to rebuild but with 6 x 6TB drives a RAID6 or RAID5 array rebuild could easily be measured in days. (For example my 4 x 4TB RAID5 array in my NAS takes at least 8 hours to rebuild under ideal conditions.)
  10. I have just done a few quick tests in a Windows 10 1709 virtual machine. When Files on Demand (FOD) is enabled the normal OneDrive folder and its contents are converted to reparse points. Trying to find where these reparse points point to returns 'UNKNOWN MICROSOFT REPARSE POINT' as the target. (This is possibly why Retrospect can't backup the OneDrive folder when FOD is enabled.) What I did to return the OneDrive folder to a normal folder was: Right click on the OneDrive icon in the system tray and select Settings On the Account tab select Choose Folders Uncheck Sync all files and folders in OneDrive the check the folders and files you want to sync Select OK to close the dialog Disable the Files on Demand feature EDIT: The key point is to ensure that you have selective folder and file syncing enabled before you disable FOD. I did have to do some manual cleanup of some sync error in the OneDrive folder after disabling FOD but that have been due to what I had done during my tests.
  11. I can confirm that Retrospect 12.6 can backup a OneDrive folder structure where FOD is not active. My current understanding of how FOD works is that when enabled changes are made to NTFS that are only understood by Windows 10 1709 and later. Systems that multi-boot with Windows 7, Windows 8.x and Windows 10 1703 and earlier will have problems with OneDrive files. Those with good memories will remember the problems that the similar Placeholders feature in OneDrive's predecessor SkyDrive caused Retrospect and other backup applications.
  12. error -1101

    In your case a restart fixed it but if it doesn't when I have had the NPS VSS Writer and NPS Database errors in the past on Windows 10 Clients I have fixed it by adding an empty (zero byte) file named "ias.xml" in the "C:\Windows\System32\ias\" folder on the affected Client.
  13. In the past when I have had the NPS VSS Writer and NPS Database errors on Windows 10 Clients I have fixed it by adding an empty (zero byte) file named "ias.xml" in the "C:\Windows\System32\ias\" folder on the affected Client.
  14. Windows 10 "Fall update" Directory properties missing?

    I did a quick check on two machines running Windows 10 Pro 1709 and they both have an unknown user listed in the security permissions but on checking a machine running Windows 10 Pro 1703 this unknown user also exists there. However what I did notice was that the folder the permissions for the known users are inherited from has changed between 1703 and 1709. The unknown user does not inherit its permissions. If I get time over the weekend I will try and do a more detailed comparison. Are you using a Local Account or a Microsoft Account for your login? I don't think it should make any difference but...
  15. Windows 10 "Fall update" Directory properties missing?

    I'm only running Windows 10 1709 in VMs at present. (I'm testing how many unwanted/unneeded/unusable "features" I can remove and still keep a working system.) Is the log extract from a backup or a duplicate? The extract looks like it is from a duplicate. Which version of Retrospect are you running? Is this error from a backup/duplicate of the Backup Server or a Client?
  16. Slow backing up 7tb

    Is this a backup of the files on the array to a backup set on the 8TB USB3 disk or is it a duplication of the files from the array to the disk? How many files are you trying to backup off the RAID array and what is their average size? Generally a small number of large files will backup faster than a large number of small files. What RAID level (RAID1, RAID5, RAID6, etc) is the array using? Is the array internal or external to the HP z800 running Retrospect? Is the performance you quote for the RAID array what you have measured or what the manufacturer is quoting? The specification for USB 3 states maximum throughput of 5 gigabits/second or 625 megabytes/second. This no where near what you are quoting for the USB 3 connected 8TB Seagate drive.
  17. Dedicated Backup Server: Retrospect Desktop on Windows 10 Pro

  18. Catalog Files on a NAS

    You can set the path to the members of the Backupset as follows: Open the Backupset 'Properties' dialog Select the 'Members' tab Select the member you want to update then press the 'Properties' button In the 'Location for backup data folder:' field enter the UNC path in the format \\NAS-NAME\share-name\ Press 'OK' to save the new path The above directions assume that the 'Retrospect' folder which contains the Backupsets is not in a sub-folder of the NAS share. A reliable workaround I use for Windows Explorer not being able to find my NAS automatically is to add and pin a link to the 'Quick access' list in the left panel of Windows Explorer.
  19. Catalog Files on a NAS

    I have found the most reliable way to access my Retrospect (and other applications') files on a NAS with Windows 10 is to use the UNC path (i.e. \\NAS-name\share-name\). Even if Windows 10 cannot 'see' the NAS as being present when trying to browse the network you can still enter the UNC path to the files you want in the Windows Explorer location bar to access them. If you can view the Catalog file for the Backup Set in Windows Explorer then a double-click on the Catalog file should open it in Retrospect. It could also be possible that your NAS only supports the SMB1 protocol. Microsoft is in the process of disabling support for SMB1 in Windows 10. (Various factors govern whether SMB1 is enabled or disabled.) If your NAS supports SMB2 or later this should not be a problem.
  20. Backup keeps including all files

    I think the Block Level Incremental Backup only works for backups of volumes on physical disks connected to the Backup Server itself or client computers when they are accesses through the Retrospect Client. As far as I know only file level backup is available for volumes on network shares. Another area worth checking in the Backup Script is the settings for the backup of file and folder security information. In the settings dialog for the Backup Script they are at Options > Windows > Security. If anything changes in the security information for a file or folder and Retrospect is set to backup security information the file will be backed-up again even though the file itself has not changed. I have a QNAP NAS which I use as the destination for my Retrospect Backup Sets and general file storage. I use the 'Backup Station' utility on the NAS to backup the shares to ext4 formatted external disks four times a month. The reason I use ext4 formatted disks is to ensure the files, folders, and their metadata are copied 'as is' from the NAS.
  21. Backup keeps including all files

    What is the make and model of your NAS? If it is a Linux based NAS then the problem could be because the Windows file system that the Retrospect Server sees is an emulation running on top of the underlying Linux file system. Depending on the capabilities of you NAS a better solution may be a backup to the external drive directly from the NAS instead of using Retrospect over network shares. NAS manufacturers such as QNAP and Synology provide Apps to backup NAS shares to external drives.
  22. Did any updates to CentOS 6.9 happen around 1 September? It's possible that an update on that Client introduced by design or accident a memory limitation that Retrospect is now hitting.
  23. Data deduplication query

    Block Level Incremental Backup only applies to files over 100MB in size. Additionally if the time since the last backup of the file is more than thirty days the whole file will be copied. These rules can be changed and there is a Retrospect Knowledge Base article that covers this. Unless you tell Retrospect to ignore changes to security settings on a file any change will cause the file to be copied even if the content has not changed. (This is an option on Retrospect for Windows and I assume Rectrospect for MacOS has the same.)
  24. I've had this problem too with Windows 10 clean installs. It usually comes down to some driver files and/or registry entries that get installed under Windows 7 and are carried over in the Windows 10 upgrade but are not installed when adding the device to a Windows 10 clean install. Turning off automatic detection and installation of devices in Windows 10 (after installation of the OS but before connection of the LTO drive) and then manually installing the Windows 7 drivers can sometimes work. If the SAS interface and LTO drive are using Microsoft supplied generic drivers try installing drivers from the manufacturer. The generic drivers may lack functionality that is required for Retrospect to detect them. Are you using Windows 10 version 1511 or 1607?
  25. ... and note that RDX devices have been moved to Disk from Removable Disk.