Jump to content

Nigel Smith

  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by Nigel Smith

  1. Seems likely you hit the nail on the head. Just for fun, what happens to times if you run a second backup of the Synology on the same day? I don't know if an RS scan would be considered "file access", but it's possible that you are triggering a metadata update across all the files (see here) which is slowing things down.
  2. Nigel Smith

    Slow closing of clients after backup

    Probably something on the server is slowing things down -- other processes using the disk, disk errors slowing down write times, potentially problems with the Retrospect catalogs... Check the whatever is Windows's equivalent of System Log for errors, try running a process monitor to see if you can spot other active (especially disk I/O) processes, run a backup manually to the same set with a single client at a different time to see if it is something scheduled, try a new backup set to eliminate catalog problems.
  3. The "Sleep" slider has been eliminated because they've tied computer-sleep and display-sleep together -- the default is that, when your display sleeps your computer does too. But below that is a "Prevent computer from sleeping..." checkbox and, with that ticked, the display will turn off but the computer remain awake. That's how I leave my work iMac so I can access it from home of an evening. That's how it *should* happen, anyway. Maybe you've got some borked settings from the "upgrade"? Check the "Power" section of a System Information report, "System Power Settings"->"AC Power", and the "System Sleep Timer" should be set to "0" (ie never) or the same as "Display Sleep". Try leaving the MBP's Console running overnight, then searching for "sleep" in the morning -- if it is sleeping you should see some "prepareForSleep" messages from the apsd process. It's a shame if the client no longer keeps the Mac awake during backup but, in your case at least, it should be an easy workround. And if your Mac isn't honouring your Energy Saver settings, try an SMC reset.
  4. Nigel Smith

    Can retrospect recover after error.

    Saw that after -- I'll answer there. Agreed, but that can be very time consuming -- and very expensive in some situations (eg cloud sets). Since you're doing backups anyway it's worth taking the extra time to back up Retrospect's catalogs and settings too, ready for the inevitable failure of the server. 3-2-1 ain't just for your clients! 😉
  5. "Synology" and "QNAP" covers an *awful* lot of units of varying spec. Can you be more precise (model, disks, cache, filesystem, networking, etc)?
  6. That sounds as if you are using your Synology as your backup target, connecting your Retrospect server to it via Minio (running on the Synology). In which case you might be making things more complicated than you need to! Mount the Synology on the Retrospect server machine as an AFP or SMB share. Set that share as your backup destination. No need for Minio at all. Either way, you'll have a potential bottleneck in that the server's network connection handles roughly twice the load of the other parts of the system -- both incoming from the client and outgoing to the Synology -- just as you surmised. That may not be a problem -- client read/server write speeds may mean your network never saturates -- but, if it is and it means you exceed your backup window, it's easily solved with a second network interface on the Mini (eg Thunderbolt Ethernet adapter) and using one for the clients and the other for the server connection, or even an upgrade to 10Gb. If you explain what you have (client numbers, amount of data) and what you're trying to achieve, we might be able to suggest ways of doing it.
  7. Nigel Smith

    Can retrospect recover after error.

    What change is that, then? Sorry for the hijack, Trevor. Whilst the correct answer is probably "It depends...", interrupting the backup is something you want to avoid if possible[1]. A reboot may be OK, assuming Windows lets Retrospect close down gracefully first, but a power cut or similar could leave the catalog in a strange state. So make sure you are backing up your catalog as well, so you can restore it to a previous "good" version in case of trouble (a good practice, regardless of situation). But, hopefully, you'll rarely have a problem. Once you get that initial, time consuming, full back up done you can carry on with incrementals, which should complete much faster. [1] I don't like to contradict David, but I think you have a different situation to his. In his case it is the client that is interrupting the process while the server continues "unharmed", in yours you'd effectively be killing the server halfway through the process...
  8. Awesome -- hopefully a tale that'll get less frustrating and more amusing to you with repeated telling... Can you "keypress" your way past the dialog? I don't know how consistent Windows dialogs are compared to Macs, but you might be able to e.g. tab-return to "press" the next button. Does an external monitor work in recovery mode -- maybe try the one from your desktop? Wouldn't that all be done by the Retrospect restore? Honest question -- we only back up User folders here, partly to save on time/storage but mainly because we treat a "full restore" as an opportunity to clear out years of accumulated cruft in system/application folders by re-installing from scratch. I know this is all by-the-by now the actual problem has become apparent, but it's good to know the limits of a backup system *before* you run into them!
  9. So, since you can boot from a Windows image... Boot from a Windows installer. Reformat you drive to how you had it before. Reinstall Windows, update drivers, etc, etc. Create Retrospect Recovery disk. Boot from newly created RS Recovery, restore with Retrospect. Windows image is a basic system -- I'd thought that the RS Recovery you tried to create is a "bootable clone" of *your* system, complete with your hardware's drivers etc (hence the need for a "dissimilar hardware" add-on), though I'll defer to mbennett's experience. Either way, you should create a Recovery Disk *before* you need it, and check that it works! That used to be a standard part of the "new computer experience", both PC and Mac, though in these days of internet booting and fast downloads of images/drivers/etc it seems to have fallen by the wayside (and I include myself amongst those who seldom bother anymore...).
  10. The "supported" way is to use MDM profiles -- but that involves enrolling the devices into MDM, etc. Der Flounder's page here is a good starting point for info, and visit Jamf for more MDM goodness. (Note: I've not used MDM myself, bar a bit of a play.) AFAIK, the TCC (Transparency, Consent and Control) database is read-only protected by SIP -- indeed the only command available in tccutil is "reset". Carl Ashley's TCC Roundup is a good primer, see also other pages on Der Flounder's site and these results from the Eclectic Light Co. So I think that, absent MDM, hitting every station is your only option. You might be able to push an Applescript that uses GUI interaction to automate things a bit while you're connected via ARD, but I can see that being highly error prone... But even something as simple as: tell application "System Preferences" activate reveal anchor "Privacy_AllFiles" of pane id "com.apple.preference.security" authorize pane id "com.apple.preference.security" end ...could save you a lot of mousing. You might even be able to wrap it in "osascript -e ..." and use ARD's Send Unix Command, though you'll have to be controlling the machine with ARD at the time.
  11. The recovery disk should have been created *before* your laptop went south, not after (in the same way that a new OEM PC will often throw up a "Now create a recovery disk" after first configuration). It's probable that your recovery disk, built using your borked system, will only boot as far as your borked system would... While the manual does "strongly recommend" you create the disk "as soon as possible", they could be more explicit about doing it before it might be needed. I think you'll need to find another method -- perhaps pull the disk, mount it and reformat on another PC, full restore to it there and then put it back in the laptop? But I'm a Mac guy, so will defer to those more knowledgable...
  12. Sample contents? I've got similar -- probably an older client giving a slightly different naming scheme -- looking like tight clusters around a single event per file, and every line refers to problems with "...ExcludeList...". Same backup set all through, no rebuilds. Nothing recent so I can't check logs properly -- but I have a "Private Backup Server" address in the client Preferences "Advanced" tab, and the logs feel like they correspond to server restarts or network downtimes. Maybe an error from a "phone home" function? I'd guess that going to the client Preferences "Advanced" tab and setting logging to "Off" would quiet things down, if they're annoying you.
  13. Exactly my point. We do all this, it's much easier than re-adding a client to lots of scripts -- but it would be *even easier* if you could say "This new client? It's actually that old client re-done", kind of like "Locate" does with client IP address, whereupon the client would "inherit" the old Favo(u)rite definitions (assuming absolute path remains the same), tags, etc without any work from us. And, especially, a seamless series of snapshots across old and new clients. But snapshots may be one of the practical/security reasons why this seemingly good idea really, *really*, isn't...
  14. Oh, but he does! Being able to tell RS that "this new client is that old client, only reinstalled" would be useful. Not having to re-define Favourite Folders, re-do Tags, etc, would be great. But I get the feeling that there are practical, and probably security, reasons why this can't/shouldn't be done else we would have had the feature ages ago. But, in the meantime, Tags are a time-saving feature that anyone who isn't using should take a good look at.
  15. Tags. If you set your scripts to use tags to determine what to back up, you only have to set a new/replaced client's tags once and it will be picked up by all appropriate scripts. And as David said, you shouldn't get a full backup unless that's part of the script's definition -- "Match only files in same location/path" may be the culprit here.
  16. Nigel Smith

    Dissimilar Hardware Restore

    Thanks for that, David -- though to me it is still as clear as mud 😉 Luckily doesn't apply to us, with the way we use RS. DHR is definitely an "extra" -- RS's core task is to "restore what was previously on the client" while DHR adds "and then do whatever's required to make the new client bootable with its different hardware", so an automation of something you could do yourself. Talking to my PC-supporting colleague, he wouldn't bother with it unless we had frequent restores onto differing machines -- his example was a group of road warriors who have accumulated machines of different ages/models/makes over time and where a complete refresh onto standard Ghosted machines isn't worthwhile. I guess I've become the "boiling frog" -- I've spent so long looking at software that charges more because you're "Enterprise", looks cheap until you add per-TB usage costs, or seems good until you realise that *every* piece of functionality requires an extra-cost sub-licence, that now I just shrug and accept it. Thanks for giving me a shake-up! Now, if you could just turn the hot-plate off and lift me out of the saucepan...
  17. Nigel Smith

    Dissimilar Hardware Restore

    I'll leave my original reply in italics, below. But I'm losing my mind trying to work out what does what -- Retrospect's own pages seem to contradict each other: Single Server 5 includes "...Dissimilar Hardware Restore, making it possible to recover an entire boot volume—including the OS, applications, registry, and data—to a different physical computer..." while the DHR D2D add-on "...covers your Retrospect host server only." Implication: clients are covered by the base software, host server isn't. Single Server Unlimited includes "...Dissimilar Hardware Restore, making it possible to recover an entire boot volume—including the OS, applications, registry, and data—to a different physical computer" while the DHR Unlimited add-on "...extends to all Windows systems protected by your Retrospect host server, including end-user desktops and laptops." Implication: the host is covered by the base software, the clients aren't. Of course, they may have given very similar names to things which enable completely opposite use-cases... <Sigh> Probable garbage below... As I understand it (and I fully accept I could be wrong -- I *hate* trying to decipher licenses for any Windows software, since they all seem to be create to confuse!) those prices reflect different "abilities": DHR Desktop helps you to restore your *desktops* to different hardware -- applies to the Desktop for Windows product. DHR Disk-to-Disk helps you to restore your Retrospect host server to different hardware -- Single Server 5 already includes DHR Desktop functionality above Windows Server and Desktop, unlike the Mac and Linux OSs, really are different beasts -- and it's pretty standard across the industry to charge more for a WinServer-aimed product than WinDesktop. Whether that reflects a greater difficulty/cost in creating and maintaining the server product or is based on a willingness of businesses to pay more, I couldn't tell you. But if you think RS's pricing for this is bad, check out the competition. Better yet, have a look at Microsoft's Server OS licensing -- nightmare!
  18. Nigel Smith

    Dissimilar Hardware Restore

    IIRC, Desktop can have it without ASM, Server requires ASM. Slightly unfair. As a Mac user you've probably forgotten (or maybe never knew) the pain involved moving a Windows install between different hardware. It would only take one or two uses for a business to cover the cost of the add-on and, realistically, business is the target market. And not just for "restores", also for migration from old to new machines. I wouldn't bother with it as a home user, but if time was money...
  19. Nigel Smith

    Incorrect tapes names and possible overwriting tapes

    Not quite. It is showing three of the library slots are designated as cleaning tape slots -- it doesn't matter what tapes are in there, as you've seen, it just blocks out those slots during a device scan and tries to use their contents when a clean is triggered. Check that you haven't inadvertently marked off two more cleaning slots than you want... I don't think RS has "knowingly" wiped the second tape, since it is still listed as holding data on the set's Properties. "Unknowingly"? That would depend on whether it's dumb enough to only (mis-)read the barcode and not sanity-check the tape header before proceeding... Something's out of whack though. I think my first move would be to Disable Barcode Scans in Retrospect's tape library properties window then do a Scan Selected or even move the tapes in and out of the drive manually and see if that gives better results. Try opening/closing the library door *before* doing Scan Selected -- if it works like the Mac version it'll put all tape names into italics until they've been scanned, so you can easily see what has and hasn't been done.
  20. Given the above, it looks like a good test would be to compare the transfer of the veeAM files from the Windows client to a) an hard drive directly attached to the Retro server, and b) to tape. While everything looks good I'm starting to wonder if you've got a dodgy SAS cable or something. Would also be worth turning off the speed-enhancing features on the ATTO card, if you haven't already -- you hardly need them for this. As to cleaning -- you've done that far more often than I have! LTO is largely self-cleaning so, unless the library is in a dusty environment, you could get away with turning auto-cleaning off entirely and just doing it manually once a year or when you start seeing tape errors. But I'd still look at going D2D2T. Retrospect -- indeed, most backup solutions I've tried -- hate doing lots of small files to tape, especially when those files are on a mounted share. There's a lot of overhead for each file so you aren't using the tape drive optimally. You may even find D2D2T faster, if you can run multiple backup sets and your Mac Pro has the throughput to back up clients to Set A whilst also copying from Set B to tape...
  21. Which is another reason for asking about the drive make/model. LTO drives are clever and slow down the tape speed to try and match the data rate but even then there's a minimum speed and, at rates below that, underrun occurs. Although, at only 100GB on an LTO7, that sounds more like an interrupted transfer -- RS is interpreting it as a tape error, considers the tape done with (though the data is safe up to that point), and asks for another tape so it can carry on. I get similar with my not-really-supported Thunderbolt to Fibre Channel adapter...
  22. Nigel Smith

    unistall engine

    Open Retrospect Console, select "Preferences..." from the "Retrospect" menu, click the "Console" icon at the far-right, click "Export server installer and uninstaller...", save them where you want. Haven't actually *tried* the uninstaller myself, but see how you get on. Even if you've already manually uninstalled I suggest you give it a go in case it clears up cruft from your launchd files, logs, etc.
  23. Sounds like you've got problems with the library/drive. What make/model is it? I try to use Retrospect Client on the source servers rather than SMB-mounting them onto the Retrospect server since I find it generally works better -- an interrupted/resumed SMB session is usually handled fine during, say, a Finder copy but can be death to a backup. Otherwise, try the usual troubleshooting: how fast is a Retrospect Server to tape backup (i.e. eliminating SMB from the problem); how fast is a backup of SMB-mounted share to a disk directly attached to the Retro Server (i.e. eliminating the tape drive), and so on. For best speed you may want to look at a disk-to-disk-to-tape setup... As to overwriting tapes -- we don't do that here but, IIRC, that's what the "Recycle Media Set" media action (in the "Schedule" pane of the script definition) is for. Or have you tried that and found it doesn't work?
  24. It would be a new volume. You can try it for yourself with a USB stick -- add it, tag it and add as a "Selected Volume" in RS, rename it, refresh, and the tag and selected status is gone. As Lennart says, by default the files won't be backed up a second time. Unless you've selected "Match only files in same location/path" in the script options (which is off by default, I believe).
  25. Nigel Smith

    How to restore files on top of what's there?

    Thinking about this, your recovery might be easier than I thought... Make a new backup, to include everything created/modified since the last of the old backups Restore Volume using the old backups Replace Corresponding using the new backup Assuming the matrix is correct, that should mean that "corrupted" files are returned to their uncorrupted form then new/changed files are overlayed, replacing previous versions where appropriate (assuming you weren't doing something silly like editing file data without updating the metadata to suit). All you should lose is data created/modified *after* the last old backup but *before* the borkage *if* it was affected by said event -- that would require data recovery of some sort.