Jump to content

Nigel Smith

  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by Nigel Smith

  1. Could you go back to whatever version you were using before you "upgraded" to 16.1?
  2. Surface test only checks "usable" disk space -- it doesn't include bad sectors that have already been mapped out. So it's probable that the "missing" files were on a bad sector that has already been "fixed" by Windows. Possibly, given the numbers involved, a problem in whatever is NTFS's equivalent of the file allocation table. You can check by viewing the SMART data for the drive, which will tell you how many sectors have already been re-allocated.
  3. You might still be carrying some cruft over from the "old" directory structure. Instead of what you did, copy (not move) the members from old to new directory, creating any required sub-directories by hand as you go. Set all permissions to the same as the newly-created top level Retrospect directory. Get Retrospect to "Rebuild" the media set, adding members as required, but make sure to save the new catalog in a different location so you don't overwrite the old one. That's quite a lot of work. But it could get you out of a hole if you need to keep the old sets available for restores -- you never said in the OP if Retrospect still had the read-access that restores require. If it does then I wouldn't bother, just move onto the new sets.
  4. Doesn't need much. NASs usually use Windows ACLs for permission control, which don't directly translate to POSIX/OS X permissions. So it's always a "best approximation", can be tighter or looser than expected/intended, and can be interpreted in different ways by different programs (if they aren't using OS X's APIs). I'm not expecting my workround to work, but it's worth trying before you contact Support -- more data points will help them help you.
  5. Nigel Smith

    AWS virtual tape library

    But S3 would also offer you Standard, Glacier and even Deep Archive. So you could use Retrospect's Cloud Backup or Disk Set(s). I've never used Cloud (some who has might want to chip in) so I'd probably default to Disk Sets with reasonably small member sizes, generated on-prem then uploaded to S3 Standard once each is "full", then migrating from Standard to Glacier after a year or so. There are many ways to skin this cat -- how exactly you do it will be prompted by your data, how you manage your backups, how the regulations say you *must* manage them, how much money you're allocated for the job, etc... The use-case for VTL I thought of first was "lots of physical tapes which I can put into cloud storage by duplicating through the Gateway" i.e. you need to generate an exact virtual replica of your current physical holdings. If that isn't a regulatory requirement and you can manage the migration using Transfer operations from tape set to Cloud/disk set, VTL support may not be needed at all.
  6. Nigel Smith

    AWS virtual tape library

    Why use a VTL instead of doing a "normal" disk backup set to an S3 bucket or similar cloud service? (I can think of some reasons, but would be interested to hear yours.) Regardless, Retrospect isn't listed in Amazon's supported applications table and neither media changer is listed by Retrospect (unless the STK-L700 is close enough to e.g. the SL500 that it'll work), so I think you're still left waiting. Or very much on your own if you try to make something work. As David suggested, try contacting Sales. You may get lucky, and at least you'll flag it as something for them to consider in the future.
  7. What happens if you let Retrospect make a new set in a new, separate, directory on the NAS -- i.e., instead of your current NAS/folder1/folder2/Retrospect structure you do NAS/folder1/folder3? Can it create and, afterwards, verify the test set OK? If so, check for any permissions differences between the two using the NAS's management interface. Sometimes a NAS, which is usually running a SAMBA variant, can present itself in different ways to different OS X programs. And if the first step works but you can't see any differences, try copying one of your "old" catalogs into the "new" Retrospect directory. Can you access that now? In which case you might be able to get round the problem by moving all your catalogs to the new folder.
  8. 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.
  9. 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
  10. 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.
  11. 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?
  12. 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?
  13. 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...".
  14. 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.
  15. 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).
  16. Nigel Smith

    can't connect to server

    Hopefully that's a typo. You should be scanning *from* the Console Mac, checking it can see the open Port 22024 on the server Mac. I've tried with a "clean" 10.14.4 Mac -- installed RS, checked it works, updated to 10.14.5 and it still works -- so I don't think it's the recent OS update that's the problem. Try another machine -- if that works then uninstall/reinstall Console on the problem Mac. I'd also clear the relevant KeyChain password entries (Keychain Access and search for "Retrospect") before the reinstall, though I'm not sure that's necessary (have I borked my settings? I'm finding that *anything*, even *nothing*, in the password field allows me to connect!). The only other way I've been able to replicate your never-ending "Connecting..." is by trying to add an IP that doesn't have RS Engine running. RS Console doesn't handle that gracefully -- you very quickly see a "...failed with error 61:Connection refused..." in system.log (launch Console.app, select "system.log", type "retrospect" in the search bar), but the wheels just keep on spinning... So you could try removing all servers from RS Console and quitting it, launching Console.app and setting it up as above, then launching RS Console and adding the server again -- see if the log gives any clues.
  17. Meh -- computers! I'm afraid my stock answer in these situations is "Don't know why, don't care why -- it worked, and that's enough for me!". Any chance you can increase the capacity on your Synology next? Looks like you're below 10% free space so, depending on how it's formatted, you might be taking a hit to write speeds. Of course, if performance is still OK for your workflow, carry on as you are 😉
  18. Nigel Smith

    can't connect to server

    To add to David's sage advice: Is Retrospect Engine running on the server? Check with Activity Monitor viewing "All processes" to be sure or, in the Terminal, "ps -axww | grep RetrospectEngine". Is Engine's port open? In the Terminal, "sudo lsof -iTCP -sTCP:LISTEN -n -P | grep 22024" and you should see a line starting with "Retrospect", showing it listening on port 22024. Can your Console Mac reach the server? Use Network Utility to "Ping" or, in Terminal, "ping -c 10" (regardless of what IP Scanner tells you, it's worth a double-check). If you can ping the server, is the port visible to your Console Mac? On the Console machine use Network Utility to scan, setting both "ports between" fields to "22024" for speed. Or, since we're relaxing with Terminal 😉 , "/System/Library/CoreServices/Applications/Network\ Utility.app/Contents/Resources/stroke 22024 22024". If the first two tests fail, troubleshoot Retro Engine starting up on the server -- it'll help to know your OS version for that. If the first two pass but the last tests fail, check for firewalls or similar network security. If they all pass, it might be something like a change of Retrospect Engine password or a problem with the Console install (re-install or try a different machine). 'Fraid that's all off the top of my head. Let us know how you get on.
  19. Totally normal. chkdsk reports on "current usable disk", and doesn't include those previously found bad sectors -- they've already been re-allocated (note that it doesn't say that there are no bad sectors but that you have "0 kb in bad sectors" -- not quite the same thing). S.M.A.R.T. works at the hardware level and so also reports those sectors which have previously found to be bad and thus re-allocated. Hopefully, the new disk will sort things out. Otherwise the steps you took above indicate that you have read access to the catalog file (could do a restore) but not write access (the repair options you chose require the original catalog to be deleted). You could always try copying the catalog over to your C drive and using it from there. Or you could do a complete rebuild to a new file in a different location.
  20. Nah -- long on detail, short on practical examples. For most of the questions about RS (indeed, software in general) the answer are already there or can be inferred from available information, but the questioner can't frame the query to meet a technical writer's expectations. Instead of "our software does this using this menu item" (kind of obvious *if* you know the software author's name for the function you require) you could do a more Q&A "operations" based approach -- "You want to back up? -> using a cloud service to store your data; -> using a NAS; -> using an external drive" or similar. A "busy admin" doesn't want to know the technicalities behind block-level backups, he wants to know how to use path filters in the real world. But I'm guessing I won't be able to persuade you to write this -- which is a shame. Also: Similar criticisms can be levelled at Synology, QNAP, our Isilon cluster... We had some Drobos, and their USP at the time was BeyondRAID's incremental expandability. Unit full of disks but need more space? Pop a disk, install a bigger one, let it rebuild while still having access to your data. Much cheaper, easier, and *much* less downtime than backing up your entire RAID, replacing *all* the disks with higher capacity versions, restoring your data. Struggling grant holders could spend just enough money for this year's data capacity and upgrade when the next year's funding came through. But HDs and enclosures were a lot more expensive then, relative capacity increases larger, software-based volume expansion more common, and client (rather than Drobo) performance tended to be the speed bottleneck. Other companies introduced their own ways of adding disks without the hassle of reformatting. Things have changed and, for similar usage, we now tend towards over-provisioned desktop RAID arrays (single machine use) or NASs (multi-user), making sure they are not only full of big disks but can also be expanded across multiple units if required. Drobo's models, especially "business", are looking a little long-in-the-tooth now -- I was hoping for more after their merger with Nexsan. And we've always been interested in Nexsan, if only so we could say "I've got to go check the Beast in the Server Room" 🙂 but, unfortunately, the units are too deep for our sealed racks. The optimist in me would love to see Drobo's innovation on Nexsan hardware running optimised Retrospect -- an excellent turn-key on-prem backup solution for SMB (even if I wouldn't buy it for here). The pessimist says "Oh God, it's EMC all over again...". The pragmatist thinks that, as long as Retrospect gets some love, I don't care who owns it. Time will tell, I guess.
  21. I probably should, at this point, mention that the minimum Retrospect version required for updated Windows 10 is v15.6 I'm always laughed at for making things work well past their sell-by date, so I'm not one to talk 😉 , but be aware that will be the first solution suggested by more official sources... That said, "Catalog file is locked" can happen for a bunch of reasons. Start with standard troubleshooting (shut everything down, restart in sequence, verify volumes on both PC and NAS, make sure RS is "up to date" -- you say you have 12, I'd assume 12.1 is a free update, maybe 12.5 as well but I don't follow Windows versions). Make sure you don't have more than one version of RS on your HD (not even in the Trash). Once everything is checked, use Task Manager to make sure RS *isn't* running, then launch the app manually. Doing all operations from within the app (no double-clicking catalogs or run files), try running the backup again, checking in Task Manager to make sure a second instance isn't being launched. If there's still a problem what are the *exact* errors recorded in the Operations Log? And if there are still problems it would help to know what the NAS is (make, SW version, format and capacity of target volume, etc), what you are backing up (just the "host" PC, or are there other clients?), any other sets using the NAS as a target (including their capacity settings and actual size) -- more info is better. Catalogs do get corrupted, so you could go back to a previously backed up version and "rebuild" any recent changes into it and carry on from there -- if you haven't a back up then you could do a complete rebuild from your NAS data, though that could take some time... Plenty of things to try, so let's not give up yet!
  22. Why not publish your own? "Hertzberg's Guide to Retrospect for Busy Backup Admins". I'd buy that for a dollar! I'm actually semi-serious here. You know your stuff and write well. It might be worth a pitch to the Take Control guys (who you may know of from the TidBITS mailing list/magazine). Retrospect got a mention in "Take Control of Backing Up Your Mac", but there's nothing else in any depth.
  23. Is the "Skip this member" box checked (IIRC, RS will automatically check this when you hit the space limit)? Make sure you uncheck it when setting the new size limits. How big is the current set member? There are limits, both in Retrospect and in the NAS's file system, and it may be that you are falling foul of one of those. Regardless of the above -- why not just add another member in the same place, since it seems you have plenty of free space on the NAS? While most people think of "add member" as being a way to add another real-life disk or volume to a backup set, you can also use it to add another "virtual disk" to the same directory of a NAS-based set. (Useful if you want to off-site -- rather than repeatedly copying a single, ever-growing, multi-terabyte, file you can have multiple smaller files in the set and you only have to copy the most recently changed. Think of each file almost as "virtual tapes".)
  24. Nigel Smith

    multicast on wrong interface

    Retrospect Client binds to the first available interface -- Client queries the OS for active interfaces, OS responds with an array of those available, Client binds to first item in the array. That suggests three possible approaches: If one interface *always* comes up before the other, re-do your network settings so that one is on the Retrospect subnet. This will stuff up any other software that also only binds to "first available" but you want on the *other* interface If interface order can vary you'll have to get creative with your machine's startup scripts -- basically you're looking to get the interface you *don't* want Retrospect to use to come up after Retrospect has been initialised. Again, this could stuff up other software You might be able to do it later by taking down the interface you don't want to use, stopping and starting RetroClient (so "retrocpl --stop" then "rcl start" -- turning the client off and on will not do the job), then restarting the "unwanted" interface. Unfortunately the Linux client has nothing equivalent to the "ip" and "ipsave" commands available on Mac and Windows. There may be other ways round this, depending on your network setup, but I'm afraid I'm no Linux guru...
  25. While it's a good idea to enable Full Disk Access in Mojave to allow Retrospect to back up all the files on a machine, it'll rarely have an impact on external volumes. Privacy mainly acts on parts of the user folders -- ~/Library/Mail, ~/Library/Cookies, etc -- and any Time Machine Backup folders. It generally won't be in play when backing up a mounted NAS volume unless that volume has been set as a TM backup target, *possibly* if you're redirecting User directories to the (non-startup) volume, or something similarly funky. In fact, "Error -1101" is almost certainly not a Full Disk Access issue, since that generates an error when scanning -- an error that includes the path to the folder, text to the effect that 'Retrospect has detected it is not listed under "Full Disk Access..."', and a link to the KB article explaining how to fix the problem. In both cases above it is most likely a name, permissions or volume integrity problem. But the various flavours of NAS and client implementations of SAMBA/AFP can make this difficult to troubleshoot...