Jump to content

Scillonian

Members
  • Content count

    541
  • Joined

  • Last visited

  • Days Won

    21

Scillonian last won the day on June 28

Scillonian had the most liked content!

Community Reputation

50 Excellent

About Scillonian

  • Rank
    Error -557 ( Transaction Already Complete)

Profile Information

  • Gender
    Male
  • Location
    Isles of Scilly, UK

Recent Profile Visitors

876 profile views
  1. Scillonian

    Files missing from Snapshot after Transfer Snapshots

    Try doing a thorough rebuild of the catalog for the cloud backup set. To effect a thorough rebuild you will first need to delete all the *.SESSION files that are in the folder(s) that hold the *.RDB files for the backup set. Once the *.SESSION files are deleted rebuild the catalog. A thorough rebuild of the source backup set may also be advisable just in case an error their cause the initial snapshot transfer failure. Because Retrospect is now reading the file information from the .RDB files instead of the .SESSION files, and depending on the connection speed to the cloud provider, the rebuild could take some time to complete. Hopefully after the thorough rebuilds a rerun of the transfer snapshot should pickup the missing files.
  2. Scillonian

    Backup error or not?

    Am I correct in thinking that you are accessing the source RAID6 volume using the Retrospect Client and writing to the destination single disk volume over SMB? What is the CPU load on the NAS during this backup? I am wondering if the Retrospect Client is intermittently overloading the CPU.
  3. Scillonian

    Backup error or not?

    So we can get the messages in context, what are the Source and Destination of the Backup? Also, why have you got the Restrospect Client software installed on the NAS?
  4. Scillonian

    Does Restore require Write access?

    [In theory] Retrospect should be able to restore from read-only media. More of problem will be trying to mount a Linux file system under Windows. I've found it bad enough try to reliably read the older (and simpler) ext2, ext3, and ext4 file systems. BtrFS is still evolving with all that entails. Also with Microsoft pushing out a new version of Windows 10 every six months, at present, what may work now will be broken with the next version of Windows 10. Here are two more reliable solutions to consider: Mount the BtrFS drive and an NTFS on a Linux OS and copy the Retrospect files from the BtrFS drive to the NTFS drive. (If you only have one computer then boot that computer from a Linux live CD/DVD/USB to perform the copy.) If you have more than one computer and a network (preferably not wireless) then mount the BtrFS drive on a Linux OS and use SAMBA to share it over the network. A Linux live CD/DVD/USB can be used to do this if you do not have any native Linux computers. Ultimatly the only way to really know what will work is physical test the emergency restore procedure and keep testing it until it works reliably. The time spent now will be rewarded later when the restore becomes a real event not a theoretical one. "There are no successful backups, only successful restores."
  5. Sorry David, it looks like 'A Series of Unfortunate Events'. When I too read your post, perhaps 40~45 minutes after Hofstede posted his reply, only the quote and the first line/paragraph existed.
  6. Because they are they are the same entity?
  7. Scillonian

    Scanning MacBook Pro taking hours!

    Is this SSD a replaceable one with a SATA, mSATA, or M.2 connection or is it soldered to the motherboard? The fact that Apple's Disk Utility says that SMART is not supported on the SSD would lead me to believe it is one that is soldered to the system board. Do you have easy access to an Apple Store? As you have warranty cover a thorough health check at the Apple Store would eleminate hardware as a problem.
  8. Scillonian

    Scanning MacBook Pro taking hours!

    This could be a hardware problem. Personally I would check that the hard disk in the MacBook is healthy. From what you describe this would be indicative to me, if this was a Windows laptop, that the hard disk was failing. Firstly I would check the SMART data from the disk to see if there is anything untoward going on. (Not being a macOS user I don't know what utilities there are available for macOS to read the SMART data.) If you are not familiar with interpreting SMART data post the results here and I look over them. I've encountered enough failing hard disk to know that under normal day-to-day usage they appear fine but once something like Retrospect starts to use the disk intensively the problems start.
  9. Scillonian

    Why is backup speed all over the place

    My suspicion is that with your original Virtual Memory setting, and Retrospect running, Windows was periodically deciding that some memory pages needed swapping between physical RAM and the pagefile more often than was desirable resulting in the erratic performance of Retrospect.
  10. Scillonian

    Why is backup speed all over the place

    To better try to find where the bottleneck may be you need need the extra functionality that is in the Task Manager in Windows 8.x and Windows 10. The feature available in Windows 8.x and Windows 10 that is of use here is the display of the percentage use of the system's individual resources. It is quite possible for a process to have a very low disk data throughput but be using 100% of the disk resources. This information is not visible in the Windows 7 Task Manager. A search online for use windows 8 task manager in windows 7 will reveal some third party Windows 8.x style Task Manager alternatives for Window 7. Being a Windows 10 user now I have no personal current experience of these solutions for Windows 7 so provide this search information as is for a starting point.
  11. Scillonian

    New NAS, trouble recognising duplicate files

    The QNAP NAS is a new Source to Retrospect which it has never seen before so will try to do a backup of all the files it finds there regardless of whether you think Retrospect has seen them before. The reasons are covered in more detail elsewhere on the forum but in short, without doing a byte-by-byte comparison of the files which Retrospect does not do, Retrospect has no way of knowing if a file now on QNAP is the exact same file that was on the Synology. Once the first full backup of the QNAP NAS is complete normal operations should resume.
  12. Scillonian

    rdb files

    The .rbc files do not have to be in the same folder tree or even on the same volume as the .rdb file. When the backup set's .rdb files were created a .rbc must have existed. Are you saying you had existing Catalogs that did not work or the Catalogs were missing?
  13. Scillonian

    rdb files

    The .rdb backup set files contain the files, snapshots, and if a appropriate the system state for system volumes for the backup. The .rbc catalog files contain the catalog (index) for what is stored in each .rdb file. A backup set could run to several terabytes of .rdb files so it is far more efficient when searching for items to restore to use the much smaller .rbc catalog files which only contain file metadata. If not it would be necessary to sequentially read through the .rdb files to find the required item.
  14. Scillonian

    Why is it backing up the EXACT same file?

    Is "G" drive an internal or external drive? What is stored on "G" drive? Check to see whether the option to backup file and folder security information for workstations (not near Retrospect at present so can't say exact wording) is enabled in the backup script options. If this is enabled this can cause this kind of behaviour.
  15. Scillonian

    Error -1103 after Windows 10 April Update

    Do you still have Open File Backup disabled?
×