Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. (At long last, I have filed a support case with extensive info on how/why I recommend this change...) Here's what I wrote: Hi! In 2014 KB article https://www.retrospect.com/en/support/kb/file_vs_block_deduplication your team discusses why you've chosen File-based dedupe, based on name/size/attributes. I strongly recommend revisiting this decision, due to changes in technology, typical usage, and data volume. AND, there's at least one good implementation in a competitor that demonstrates the advantages of a move to block-based dedupe. Tech change: hash calcs are *extremely* fast in modern CPU's. Both traditional and new ones (cf CityHash). Multiple GB/sec! Storage technology now easily exceeds 100MB/sec, often to 500MB/sec. Data volume: with multi-TB drives, large SSD's, 4k video and large photo sensors, it's quite common to toss around many many GB of *noncompressible* files. Many TB in fact. Compression has little value as we move toward photo/video media. Typical usage: File-metadata dedupe is woefully inadequate today. The 2014 article doesn't cover many common scenarios: the exact same 20MB photo is often renamed as it gets copied to dropbox, shared with others, etc. Multi-MB audio files can have header info significantly changed, while the modify timestamp is retained. (eg every play causes the play count to update in the file! Yes, the access timestamp is updated. Photo and video collections are typically duplicated, renamed, and minor metadata header info is updated, while the bulk of the data blocks are not touched at all. A simple partition copy can cause Retrospect to make a new backup of every file in the partition. Many modern apps use the same DLL. Unfortunately, filenames and timestamps *often* vary (for identical content.) (A great, paid, tool I use for content-dupe-finding is SpaceMan99. Run it against a 😄 drive on a well-used computer!) C:\Windows\Installer contains duplicates of installed executables, with different names. Many hundred MB. Right now, all of the above scenarios cause anything from waste to havoc in Retrospect. One commercial example that handles all of this quite well: CrashPlan. (They left the home and SMB market last year, so not really competing anymore...) The client maintains a local database of file metadata and block hashes. Across the board, a "file" is a [metadata packet] plus N [content blocks]. Metadata can be quickly scanned for grooming, storage, recovery purposes Content block references can be efficiently rebuilt as needed via a scan Deterioration of both source and backed-up blocks is easily detected via a scan, and re-backup solves it - Up to N copies of any given content block can be retained for redundancy.
  3. Today
  4. henry-in-florida, Thank you for pointing this out, but you ought to know by now that nobody from Retrospect Inc. reads this sub-forum anymore. Here's why and how to file a Support Request for a bug fix.
  5. organisum, I guess it's time to tell you to "RTFM". Pages 158-160 of the Retrospect 15 Mac User's Guide provide complete "Email Preferences" instructions, including an "Outgoing mail server" paragraph that tells you how to specify the TCP/IP port—using an SMTP server as an example. I found this by the extremely secret technique of doing a browser search of the UG for "email"; it showed up as the second such occurrence in the Table of Contents. The same paragraph is in the UG for Retrospect Mac 12, in case you're not running the latest version—which BTW you didn't specify. Doing the same browser search in the Knowledge Base turns up this article, which says "you will need to include a platform-specific port after the SMTP server name" in the first paragraph and has a "Port Configuration" section. That article appears to have been updated for the "... Supports SSL" checkbox—which BTW is not mentioned to this day in the UG but which defaults to checked—in connection with the release of Retrospect Mac 12. However the "Troubleshooting" section has been updated in connection with the release of Retrospect 15, which explains why the current version of the article is dated 15 May 2018. This OP in another thread may explain why the KB article was updated.
  6. That link prompted me to check my C:\ProgramData\RetroISA\RetroISAScans folder. It was empty, which suggested that Instant Scan has never previously worked for me, even though the RetroInstantScanService was running. However, stopping and restarting that service did the trick. Running one of my scripted backup tasks caused the first scan to take place of the My Documents folder and running it again used this scan info to shorten the backup process. Many thanks for pointing me in the right direction 🙂
  7. Yesterday
  8. Hello, My email provider requires port 2525 be used for SMTP SSL. Unfortunately Retrospect provides no email control other than a username and password. SoftRAID; another Mac product from the 1990s that is making a comeback, provides all of the modern day email support one needs. Why not Retrospect?
  9. Perhaps this Technote may help
  10. JamesOakley

    Backups "freeze" part way with no error

    Yes, and in fact it can't be an invisible dialog in my case, because the front-end doesn't stop responding, just the engine. So I cannot "stop" the running job - it just sits there trying to connect to the client. I also cannot close the Retrospect main window, and I cannot relaunch it from the dashboard - if I try, nothing happens. But I can browse around the application, read logs, look at selectors, clients, volumes, etc. - none of which would be possible if the program were paused waiting for me to click "OK" somewhere.
  11. Instant Scan is enabled in the Preferences for my installation of Retrospect 12.6.1.101, but I have only just noticed that the logs for my scheduled backup jobs have contained the warning "Unable to use Instant Scan for My Documents on MyData1 (G:)" for well over a year (I really must need new glasses). G: is a local NTFS drive on the same Windows 10 PC as Retrospect. How do I fix this?
  12. Scillonian

    Backups "freeze" part way with no error

    Yes, 'Z' order will be irrelevant when running in the background via Launcher Service.
  13. Nigel Smith

    printing the content of a media set

    There's a way... but you won't want to use it. Start a Restore job and select the "Search for files..." option, "Continue" Leave the search as the default "Any" and a blank filename field, select the set your want to print, "Continue" Select a restore destination (don't worry about disk space, you won't be restoring), "Continue" After Retrospect has finished searching the sessions, click the little "Preview" button alongside the set details Go through the preview list and click on every disclosure triangle which might have contents you want to print out Select "Print..." from the File menu <recommended>Cancel the job once you grok the number of pages... Even for a subset of files (I've done it for someone who thought "the name might include 'December' or something") it's a horrible job. What are you trying to achieve, and why? There may be another way. For example, if you want a hard copy of the files backed up from a client you can: Go to "Past Backups" Find the client's most recent backup and click the "Browse" button associated with that Make sure the "Only show files..." box is not checked Click "Save..." ...and you'll get a CSV file that you can further process and/or print. You could do that for each client in the backup set, which may be both quicker than the above and closer to what you actually require. Nige
  14. JamesOakley

    Backups "freeze" part way with no error

    The dialog issue may be behind this. It's hard to find out, by definition. If that were the case, fixing the z-order wouldn't solve the problem, since Retrospect usually runs without the UI open. If Retrospect is running in the background, the only way to get the UI up to interact with it is to restart it, which cancels any running jobs.
  15. 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.)
  16. In Mojave, using the new client, the icon no longer appears by default. Clicking the checkbox on or off accomplishes nothing on the menu bar.
  17. 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.
  18. 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!)
  19. JamesOakley

    Backups "freeze" part way with no error

    I've noted this with 15.5.x (Professional) on Windows 10. The trigger here seems to be if a client is not available for whatever reason. Retrospect hangs looking for that unreachable client. The trouble is, it doesn't timeout like it used to on earlier versions, and move onto the next task. It hangs totally. If you try to close Retrospect, or relaunch from the Dashboard, it never does. The only way to get things back is to kill retrospect.exe in the task manager. I always notice emails telling me that a backup run had a problem. It takes me longer to notice I haven't had any emails from Retrospect for a while, so I need to find out what's wrong.
  20. I would do this: Rename the drive to its old name, so you won't confuse yourself. Recreate the catalog file from the backup on that drive. Since it has the same name as your original backup, you have to fotget the old catalog file. Now you should be able to restore your files. In the future, let Retrospect "Transfer backups" from your backup to your backup's backup. That way you could restore from either backup set.
  21. Lennart_T

    Can't access volume Error -1102

    Sorry. In the old days, you could not search for a folder. At least that's how I remember it. I had not realized you can nowadays. The yellow exclamation sign is a sign of trouble. In this case it's probably the lack of metadata such as permission or ACLs missing from the backup, not the files itself.
  22. Lennart: thanks for that suggestion. There was one disk sent where this was appropriate and it did clear out enough space to continue until I can get the off-site set back on-line and/or purchase additional storage. I admit being a bit cryptic, as what David noted about the default being 12 is what I meant by '...past year'.
  23. Last week
  24. I think the solution to this problem is to change the Drive ID or serial number, but I don't know how to do that. I seem to recall doing this change years ago. Here is my situation: I just had a complete failure of my Retrospect drive, which is Drive G: in my Windows 10 system. Right now I'm running Retrospect 12.6, but I'm planning to upgrade to the latest 15.x as soon as I can find some "quality time" for that project. I keep a "backup of the backup drive," which I keep offline. It is simply a copy of all the Retrospect folders and files. Unfortunately, the last time I did a backup of the backup drive was mid-August, but that's better than losing all of my 2018 backups. I do a fresh set of backup data sets every years. Even though I renamed that backup of the backup to "Backup 2018," which was the name of my original backup drive, and set it up as the same Drive G:, Retrospect says that it can't find any backup sets of that volume. So how do I fix this situation?
  25. oslomike

    Can't access volume Error -1102

    So, I went to restore files and folders I was able to select the disk but it had a "yellow exclamation sign" on the disk. I was able to see my test folder was there. So I guess it's getting backed up but the application is showing misleading information and probably isn't doing something correctly. At least I feel a bit better now. I only wish I could get to be totally back to normal. Thanks Lennart!! BTW, Does it not work to search for a folder name?
  26. Lennart_T

    printing the content of a media set

    Not that I'm aware off. A Media set typically contains hundreds of thousands of files. You would have to print thousands of pages.
  27. Lennart_T

    Can't access volume Error -1102

    How did you do the "search restore"? I see now what the problem is: You can't search for a folder. You have to search for a file within that folder. Is the backup listed in the Media set's list of "snapshots"?
  28. Is it possible to print a hardcopy of the Media Sets Catalogues ?
  29. oslomike

    Can't access volume Error -1102

    OK. I tried to do a search restore for a specific folder that created as a test, and after the backup was finished, the folder wasn't found in the search of the catalog. So, it might be backed up, but I don't see how I can ever retrieve it. Is it possible to tell Retrospect to forget a local disk and then re-add the disk somehow? I just can't seem to figure out what caused this disk to suddenly get these errors. EVERYTHING in the console looks normal, except that the disk in question looks like it's never been backed up. BTW, I'll have to see if there is something that needs repairing on the disk. Disk Warrior didn't find anything. I've run out of ideas. Anyone else?
  1. Load more activity
×