Jump to content

Nigel Smith

Members
  • Content count

    85
  • Joined

  • Last visited

  • Days Won

    5

Nigel Smith last won the day on June 7

Nigel Smith had the most liked content!

Community Reputation

6 Neutral

About Nigel Smith

  • Rank
    frequent Poster

Recent Profile Visitors

336 profile views
  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).
×