Jump to content

Scillonian

Members
  • Content count

    555
  • Joined

  • Last visited

  • Days Won

    23

Scillonian last won the day on October 29

Scillonian had the most liked content!

Community Reputation

52 Excellent

About Scillonian

  • Rank
    Error -557 ( Transaction Already Complete)

Profile Information

  • Gender
    Male
  • Location
    Isles of Scilly, UK

Recent Profile Visitors

938 profile views
  1. x509 Do you have InstantScan running on the drives in question? I have encountered situations before where, although InstantScan is active and reports no detectable errors, the volume databases stops updating and so as far as Retrospect is concerned no new files have been added files have been added, changed, or deleted on the volume. When a file is added, changed or deleted the volume database should be updated fairly soon afterwards so if the file time stamp of the volume database is not updating then InstantScan is not updating. The InstantScan volume databases are in the C:\ProgramData\RetroISA\RetroISAScans folder. To reset stop the InstantScan services, delete the volume databases, the restart the InstantScan services.
  2. If you look in the retroISA_log.utx file you will see entries similar to: [*] walkUSNjournal: err 0xc0000022 adding path for $TxfLog.blf fileFRN 0x100000000039e with parentFRN 0x100000000039b [!] walkUSNjournal: err 0xc0000022 for V:\ [*] ISAVol::Exit: error -1073741790 (unknown), deleting scan file for "V:\" [*] ! ISAVolCon::IsaVolStopOne: stopped processing "V:\" on 2018-09-14 22:26:39 and [*] walkUSNjournal: err 0xc0000043 adding path for datastores.xml.tmp fileFRN 0x250000000005db with parentFRN 0x2a0000000015ed [!] walkUSNjournal: err 0xc0000043 for C:\ [*] ISAVol::Exit: error -1073741757 (unknown), deleting scan file for "C:\" [*] ! ISAVolCon::IsaVolStopOne: stopped processing "C:\" on 2018-09-16 10:13:18 and [*] walkUSNjournal: err 0xc0000043 adding path for amd64_microsoft-windows-directui_31bf3856ad364e35_10.0.16299.492_none_c449a34c59896544 fileFRN 0xce000000000f4e with parentFRN 0xc480000000000f5 [!] walkUSNjournal: err 0xc0000043 for C:\ [*] ISAVol::Exit: error -1073741757 (unknown), deleting scan file for "C:\" [*] ! ISAVolCon::IsaVolStopOne: stopped processing "C:\" on 2018-10-16 21:46:11 The file $TxfLog.blf is one of the NTFS special files. The [Windows] error codes translate to: 0xC0000022 STATUS_ACCESS_DENIED -- A process has requested access to an object but has not been granted those access rights 0xC0000043 STATUS_SHARING_VIOLATION -- A file cannot be opened because the share access flags are incompatible.
  3. I noticed the same problem when Instant Scan first became available. There are certain special NTFS management files (Journal, MFT, etc) that cause the Instant Scan process to fail, delete the scan database, and abort any further scanning until the system is restarted. I opened a support case on this and basically the problem is these special files don't like Instant Scan 'looking' at them and generate a sharing violation which aborts the scan. With each new release of Retrospect the Instant Scan scanning process has become more reliable and/or more tolerant of these special files. What I have noticed is some systems are more prone to this than others. The catch is you need to upgrade to the current version of Retrospect to get a more reliable Instant Scan.
  4. wiki.retrospect.com sounds like a good idea. User contributed articles can be aggregated in a single place instead of scattered across the forums. Combine it with the forums and the same login could be used for both. The problem I see with Google Drive is for the users who have no prior investment in that ecosystem.
  5. Scillonian

    Retrospect 15.6 status?

    An update will show in Automatic Update and a manual check for updates from within Retrospect a few weeks after initial release. This presumably to allow the early adopters who go looking for the update to find any problems before the rollout to the masses via Automatic Update. As for safe to download and use, well I downloaded and installed it and so far the update has run without problems for me. (YMMV.)
  6. Scillonian

    Backups "freeze" part way with no error

    Yes, 'Z' order will be irrelevant when running in the background via Launcher Service.
  7. Scillonian

    Backups "freeze" part way with no error

    Never experienced this situation (yet) but there could be Retrospect it trying to show you a dialog that requires your action but has become hidden behind the main Retrospect window*. Under the normal Windows UI tools there is no way to get this hidden dialog to the foreground with the result that the only way to regain control is to kill Retrospect. This hidden dialog problem is not unique to Retrospect and many Win32 apps experience it on Windows 10 in particular. There is a way to to bring these hidden dialogs to the foreground using a third party program. (Will detail when I'm back at the Windows PC.) * When a Win32 program wants to put up a dialog for user interaction that dialog should appear above the host program in the 'Z' order. Especially Windows 10 seems to get the 'Z' order wrong and puts the dialog under the host program window with no way in the Windows UI to bring it to the foreground. (I've also had Windows put the dialog at coordinates that are outside the valid display area.)
  8. Also if the files are not in the expected folder hierarchy for backup sets then Retrospect can sometimes complain it can't find anything. I also second Lennart_T's suggestion to use Retrospect to backup the backup.
  9. Scillonian

    Preview a backup without committing.

    I'm not near a computer running Retrospect to give you detailed instructions but this has been asked before on the forum. Search the forum for something like "file selection preview" should give some leads. (If the Search box is not in the top right corner try a different browser — some browser and add-on combinations cause it to disappear!)
  10. Scillonian

    Backups "freeze" part way with no error

    The version of Retrospect you are running and the OS of the Backup Server and the Clients would be helpful in offering you suggestions. Also thoroughly check you network hardware. A momentarily failing network switch, which I have had, can wreak havoc with backups.
  11. Scillonian

    Use Retrospect to check for disappeared files ?

    From from memory... If you set up a Restore with the option to replace missing files the click then button to view the files that will be restored a list of files should be shown. Files with a black diamond exist in both the backup and the destination. Files without a black diamond exist only in the backup. (I don't have access to Retrospect today so can't say the exact steps.)
  12. Scillonian

    Subnet Broadcasting

    As you are using private IP address space anyway, would it be possible for your organisation to transition from the two Class C 192.168.45.m and 192.168.183.m networks to a single Class B 172.n.m.m. network? This would give you more than enough IP addresses for the 450 machines. (Would probably make network administration simpler too.) EDIT: Unless there is something really weird going on in your network the change from Class C to Class B can be achieved by changing the scope of the DHCP server.
  13. Scillonian

    Error -1101 after Windows October Update

    For whatever reason the Windows 10 'Feature' Updates randomly removes the ias.xml file. Keep the fix handy so you are ready for when it happens again with a future 'Feature' Update.
  14. Scillonian

    15.5.0.179 problems

    What host OS are you using for Retrospect? Is it using the UWP Task Manager?
  15. 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.
×