Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. I'll end my comments on the merger with a bit of pure speculation on what the synergy might be for Drobo. I found this 7-year-old blog post, briefly updated over two years ago. Its "Why I'm done with drobo" section basically says that if your Drobo box dies, you have no choice other than to replace it with another Drobo box because its BeyondRaid formatting is proprietary. In the meantime the data on the HDDs that were contained in that Drobo box are inaccessible; one commenter on that blog said 4 years ago that she couldn't get files off her crashed Drobo, a model that is out of production with no parts available, so her only option was purchasing a new Drobo model. The Wikipedia article on Drobo has the same criticism. There is one backup application whose maker partners with Drobo, but it only backs up to the cloud—which may be rather expensive for an administrator with many large files on their Drobo. So why not give Retrospect Inc., now a subsidiary of Drobo's parent company, the proprietary format for BeyondRaid—enabling backup of a Drobo to tapes or a big-but-non-RAID HDD? I'm not saying the Retrospect engineers could add this capability in a week, but they've already done the equivalent for Avid Media Composer. "And now that you've paid US$49 [ or maybe nothing—my marketing genius tendencies are telling me to double-cross the maker of the cloud-only backup application ] for your license to Retrospect Solo with Drobo Capability, how about upgrading to Retrospect Desktop Edition with Drobo Capability for another US$35?"
  3. Earlier
  4. Since installing 16.1.2, I haven't been able to do backups to disk media sets on a NAS. Now, when the backup wants to start writing to the media set, it goes to Needs media, and when I use Choose Media..., I can navigate down into the top levels of the NAS filesystem, but when I get to the directory that contains the top-level directory of the disk that contains the media set members, I can open and display some directories, but not the Retrospect directory that contains the backup members. I get similar results when I try to use Verify on the backup set, or to create a new backup set on the NAS. I can access the directories where the Retrospect stored the media sets in Finder (as myself) and by using U*ix commandline access to list the directories both as myself and when su'd to root (which RetrospectEngine runs as). This all worked for several years before I upgraded to 16.1. Anyone have any ideas? Retrospect for Mac 16.1.2 (102) MacOS 10.11.6 (Please don't suggest that I upgrade - my Mac is a MacBook Pro 13-inch, Mid 2009, and this is the most recent MacOS version that runs on it) NAS: SMB shares served from a Fritz!Box 7390 router (yes, it's slow, but it worked until the Retrospect upgrade)
  5. What Lennart said... Plus, if you are running Windows with concurrent users, you can get similar symptoms with only one copy of RS installed. Next time it happens -- and I'm sure it will -- try the "resmon" thing above and see if that points to the culprit.
  6. Not necessarily. It is just the last link in a long chain of things that can go wrong. See it as the messenger, if you wish. Too bad the catalog file isn't a simple text file. That way you could have opened it in Notepad (for instance) and see if you could make changes and save. By the way, do you have more than one version of Retrospect installed? Both could be running and one could be locking the catalog file from the other. Maybe you have anti-virus software installed that interferes with Retrospect.
  7. Retrospect has a mind of its own. I have changed nothing since yesterday's 'Catalog File is locked' error, but today's backup worked just fine.
  8. henry-in-florida, Read all of my OP in that same thread. I believe it answers all your bulleted-point questions except the third one. Nigel Smith's final post in that thread recaps my experience doing a suggested upgrade from Sierra to High Sierra, but we're not sure how the Apple Support person found an installer that enabled me to do that—and we're pretty sure we couldn't find one ourselves.
  9. Thanks for your insight, David. My goals: Restore my backed up user data, settings and data from a working version of Mojave (10.14.5). Erase and Install a new version OS (e.g., Mojave 10.14.6) to an external (at first, as a test and ultimately) the internal drive on my MBP recovering all data from previous working version. Pare down installed apps on the original to 64 bit on/after the upgrade. This could be done after the install. Scope, which I hope to apply to any new future version (Catalina): Erase and Install new OS. Migrate apps using Migration Assistant from the fastest possible connection method. Migrate or preferably (if it's proven to work) use Retrospect (Restore: Replace corresponding...) to move the Users folders data onto the target drive. Questions: Have you tried your method? Coming from High Sierra -> High Sierra, same OS, what problems did you have to face? Has anyone tried it for an upgrade to different OS's? Example: High Sierra to Mojave. Have you used the Retro function, Restore: Replace corresponding...for this purpose? Were you ultimately satisfied by the cost vs. gain, e.g., time required and the results achieved?
  10. henry-in-florida, The bottom of this April post contains my method for fully restoring a machine after a bare-metal Erase and Install of the High Sierra OS on a MacBook Pro with an SSD. As discussed in the OP of that thread, it has been combat-tested ; I'm pretty sure it will also work for Mojave and Retrospect Mac 16. In the last post of that thread, the worthy Nigel Smith gives the method his blessing.
  11. ObDisclaimer -- I know little more about Windows than what Mr Google tells me. With that out of the way... It would be worth checking if any process has that catalog file open (which would make it read-only to RS, hence the "locked" error). Click "Search Windows" in the Taskbar, type in "resmon", then hit <Return> to launch Resource Monitor. In the "Associated Handles" section type ".rbc" in the search box and hit <Return>. Mouse over each path in the "Handle Name" column and see if any refer to your catalog file. (When I do this I get two lines back, one for "explorer.exe" referring to a registry key, the other for "Retrospect.exe" pointing to the currently running backup's catalog). You could try increasing the other logging settings (yes, "7" is the max) -- I have *no* idea what you'd be looking for but, if it was me, I'd create a new set, flush the log, do a manual backup of a single folder to that set, save that log and flush, then do a manual backup of that same folder to the borked set, save that log, then compare the two logs to see what was different. If nothing shows there then I'd be thinking along the lines of: David's suggestion of trying the trial version of v16 and seeing if that solved it Restore previous version of catalog then repairing it to bring it up to date Retiring the old set (keep it in case you need to restore from it at some time) and starting a new one If desperate to keep a single running set, archiving the old catalog (just in case...) and starting a "new" set by recataloging your current backup data
  12. DavidHertzberg

    Request to increase size of disk backup set is being ignored

    You can get a free 45-day trial of Retrospect Windows 16.1.2.102 here. If you talk to Sales at (888) 376-1078 or (925) 476-1030, they can probably check with Tech Support to see if that release fixes your problem—and if so tell you how much it will cost you to permanently upgrade. If it does, you can presumably find some disk drive on which to install it.
  13. Yes, the new drive has been running for several days. The size of 'Backup Set NAS1.rbc' is 527,579 KB. The properties box for that backup set tells me that it is using 1,440.8 GB for 619,113 files. Copying the RBC file to my C drive and then copying it back again to my G drive made no difference to those properties. It also failed to fix the locked catalogue issue. There was a grooming event shortly after this backup started working again a few days ago, which erased around 118 GB from the backup, so file count issues seem very unlikely. I opened up the Secret Preferences and wound up the debug logging setting for Backup Sets and Catalog Files to 99. However, this setting was rejected and it was automatically set to 7 instead. I then attempted once again to run the backup job. It failed almost immediately, just like before. The only differences in the log file were the top 2 lines shown below. ArcPro::DbExportToXML: no volRef returned for 1-Backup Set X ArcPro::DbExportToXML: no volRef returned for 1-Dell 7500 Backup Y + Normal backup using MyDocsBackupToNAS at 09/07/2019 22:30 Can't add to Backup Set Backup Set NAS1, the Catalog File is locked 09/07/2019 22:30:16: Execution incomplete
  14. Hi David, The last time I paid for an upgrade purely in the hope that it would fix a long-standing bug, it proved to be a waste of money. I'd be happy to pay for v15.5 if I felt more confident that it was going to fix my current problem, but a bug fix for cloud backup does not immediately appear relevant to my situation. That KB article is all about issues with troubleshooting email notifications and that's something that has never ever been a problem for me.
  15. Have you got the new drive fitted yet? If so (i.e. hardware fault is now out of the equation), I'm thinking you've hit an internal limit on catalog size/contents or member size. How big is the "locked" catalog file (in Windows Explorer). In Retrospect's properties for that Backup Set, what's the "Used" space and file count? Then copy that locked file of to your C drive, back to G, and "relink" it as you did before to unlock it. Check the above again -- what are the numbers this time? If the unlocking trick works, try adding another member and continuing the backups. If everything continues working it was a "member size" limit (Ooo-errr!), probably from a weird coming together of RS, Windows 10, and Synology's volume presentation. If, however, the catalog "locks" again very quickly you may have hit a file-count limit -- you might be able to groom the old catalog and then carry on, but maybe it's time to start a new set. Otherwise, it's log time! Towards the bottom of the page from David's link above you'll find instructions on how to access "Secret Preferences" and change the log levels. You can generate a lot of noise with these, so I'd start by leaving everything as is except for winding up "Backup Sets and Catalog Files" to the max. Try another backup and let us know what the Operations Log reports.
  16. I've been interested in new ways you may have found to use Retro 16 to fully restore a machine after an OS (bare metal) Erase and Install of the Mojave OS. Anybody have a proven step-by-step after such an OS upgrade using Retrospect 16 instead of Time Machine, for example to migrate data, users, settings? Alternatively, in a bare metal install recreating the user manually how about to migrate the users information (data files/folders) if all the user setting are in place. Maybe discuss here the pros and cons of each?
  17. DavidHertzberg

    Request to increase size of disk backup set is being ignored

    haggis999, These are simply a couple of WildA**edGuesses from a Retrospect Mac administrator: First, the cumulative Retrospect Windows Release Notes say for version 15.5.0 (which is later than you're running, but it may only cost you US$75 to upgrade the Desktop Edition) Second, look in the "Security Settings" section of this KB article, which was updated 15 May 2018 for Windows 10.
  18. Sadly, the problem did not stay fixed for very long. Once again, I am getting the following emailed warning from Retrospect. This backup job worked fine the previous day and I had made no changes of any kind. From Retrospect: Script "MyDocsBackupToNAS" failed during automatic execution, error -1017 (insufficient permissions). Please launch Retrospect and check the log for details. The log doesn't repeat that reference to error -1017. It simply reads as follows. Can't add to Backup Set Backup Set NAS1, the Catalog File is locked 07/07/2019 13:00:02: Execution incomplete.
  19. Getting back to the latest problems with the Wikipedia articles, DovidBenAvraham has done further work—which Pi314m has left alone so far. It looks as if the fact that other WP editors, who may be administrators, took DBA's side in the latest Request for Comments has at least temporarily persuaded Pi314m to go mess with some other articles instead. Actually it now appears that Pi314m's heart was in the right place when he merged the "Continuous Data Protection" article into the "Backup" article. The difficulty is that there are two types of backup applications that are called "CDP". One is "true CDP", which was invented in 1989 but is only implemented in a handful of applications. "True CDP" applications must get their "fingers" into an OS filesystem at the level where actual disk writes take place; they do so either by requiring that the OS be run inside a virtual machine so that they can get their "fingers" into the VM, or by requiring that special disk driver software with built-in "fingers" be installed. "True CDP" backup can restore interactive applications to precisely the point where the system failed, but they're too expensive in money and complications for ordinary home/SME installations. R. V. (whose spelled-out name I am forbidden to mention on these Forums) may be a "true CDP" backup application, but I can't tell. Much more common and less expensive are "near-CDP" backup applications, which were introduced after the front 7 screen pages of the "Backup" article were written. AFAIK the first of these was Apple's Time Machine, which automatically does an incremental backup once an hour without a script. They are made possible by intent-logging features that are now in all commercial OSs' filesystems, and are made non-burdensome by "snapshotting" facilities that are also in such filesystems (at long last for Apple's APFS, which was introduced at least partly because Apple couldn't bolt "snapshotting" onto its older HFS+). "Near-CDP" backup applications can with proper add-ons restore interactive applications to the last point at which an incremental backup was done, possibly as little as 10 minutes ago, which is close enough for Microsoft Exchange and some database applications. Retrospect non-V. can backup hourly, if you schedule a script accordingly, but it doesn't (so far) do so from "snapshots" (not to be confused with Retrospect Snapshots, which are a different feature named a decade before the industry-wide OS feature appeared—at which point EMC dropped the use of the term Snapshot with Retrospect Mac 8 but not with Retrospect Windows). So DBA had to write three different versions of the above exposition. The first version revises the re-established "Continuous Data Protection" article, with added quotes from the references because Pi314m evidently can't read technical English at a senior-high-school level (possibly as a result of his apparent sub-culture, in which boys past the age of 13 are educated—without any math or science classes—almost entirely in a non-modern European language). The second version is the "Near-CDP" sub-subsection of the "Backup" article, which omits everything but a mention of "real CDP" because ordinary readers will never encounter it. The third version is the "Backing up interactive applications via true Continuous Data Protection" paragraphs of the "Enterprise client-server backup" article, which can omit any mention of "near CDP" because it refers readers to the "Continuous Data Protection" article.
  20. Nigel Smith

    Catalog Rebuild issues V16 OSX

    Nice catch! Had forgotten that -- our main v6 backups are Internet Backup Sets, which can't be rebuilt in any recent version. At least you won't have to do the multi-terabyte restores I'm (slowly!) going through 😉 I know v10.5 will run on OS X 10.6.8 through 10.9, not sure if it'll cope with Yosemite or higher though. Anyone?
  21. Hi Nigel Yes they would probably be that old, I have been using retrospect for many many years, since version 1 I think, so I reckon you have hit the nail on the head There is knowledge base article here, so 10.5 is what I need https://www.retrospect.com/au/support/kb/rebuilding_mac_v6_catalog I can probably install in on a external drive and boot my mac from that to get the job done Thanks a heap Steve
  22. Nigel Smith

    can't connect to server

    Then I'm very surprised that you have something listening on port 22024 on the Console-running Mac. You might want to find out what that is, if only for your own peace of mind. Check System Preferences first -- the clean Mac I did the test install on (above) *did* have Retrospect Engine running at the the end of the install process, even though I never asked for it or entered any license info etc, and was listening on 22024 until I turned it off (and unchecked "Launch on System Startup" to be sure it stayed off). Otherwise, in Terminal on the Console-running Mac, enter "sudo lsof -iTCP -sTCP:LISTEN -n -P | grep 22024". The first word of the returned line is the reported name of the process, the first number is its Process ID (PID) -- you can use either in Activity Monitor to work out what is going on. Again, if it is RS Engine I don't believe it would cause your problem -- but why spend the resources if you don't need it?
  23. Very true -- I think this will catch out most people the first time they try it so thanks for the reminder. The latest manual does include that information, albeit in the "Disaster Recovery" section. IMHO there should be a big banner announcing that fact in the "Restore" section as well, or at least the "If you have experienced disastrous data loss..." paragraph amended to "If you want to restore your System drive or have experienced disastrous data loss...".
  24. pbartoli

    can't connect to server

    Just to be clear, I have only one Retrospect Server running, on the Server Mac.
  25. Nigel Smith

    Catalog Rebuild issues V16 OSX

    Old? How old? What version of Retrospect were these tape sets created with? It sounds suspiciously like you've got RS v6 sets, which can't be rebuilt in v10 or higher. If I'm right (and you want to keep the data), your best option is to find an old Mac on which you can reinstall v6, restore everything to a disk drive, back it up again with the new RS. You'll probably lose snapshots but, if you get the options right, you can retrieve all the data including "versions" of the same file.
  26. Nigel Smith

    can't connect to server

    That implies that you've also got Retrospect Engine running on the Console Mac. Is that deliberate? If not, try shutting that Engine down and see if the situation improves (I don't believe it should cause a conflict, but the fewer "unnecessary" processes running the better).
  27. Hi David, I have tried creating a new media set and deleting the file, then running a repair. I was thinking along the same lines, making a backup on a blank tape and seeing if it works. It may well be it's all just a bit to old My upgrade was recent so I might have to call support as you say. Thanks Steve
  1. Load more activity
×