Jump to content

Lennart_T

Members
  • Posts

    4,177
  • Joined

  • Last visited

  • Days Won

    75

Lennart_T last won the day on October 18 2021

Lennart_T had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    Helsingborg, Sweden

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Lennart_T's Achievements

Apprentice

Apprentice (3/14)

  • Reacting Well Rare
  • Very Popular Rare
  • First Post Rare
  • Collaborator Rare
  • Posting Machine Rare

Recent Badges

159

Reputation

  1. Just make sure the license code is for version 17.5 and not for (for instance) 16. The account ID should not matter. Copy and paste from the email with the license code is always better than typing.
  2. I'm pretty sure that Retrospect will not perform a full backup just because the files are on another drive. That is because it's the same computer with the same Windows version.
  3. The first script starts by grooming, indication that the destinations id (too?) full to perform the backup. This script takes about 6 minutes. The second script starts and the waits for about 12 hours. Maybe it starts grooming and can't groom out space enough to perform the actual backup? What happens at 12:10:49? The user reboots the computer? Or does indeed stop the backup? I would start looking at the (free) space on the destination.
  4. I don't understand if you will go back and forth between Mac and Windows, or if this was a one-time move.
  5. It is the metadata that makes the files look different to Retrospect. Some years ago a co-worker had a Windows computer with three hard drives: An XP boot drive, a Vista boot drive and a data drive. When booted into XP, all files of the XP disk and the data disk was backed up (as expected). When booted info Vista the entire data disk was backed up again, since the different Windows versions displayed a different set of metadata to Retrospect, making Retrospect to believe it was different files. When booted back into XP, (only) the files that had changed on the data drive since the last XP backup was backed up. Similar with the Vista backup: The files on the data drive that changed since the last Vista backup was backed up. Why do you want to backup your external drive from both Windows and Mac? I would have it always connected to a Windows computer, install the Retrospect Client on the computer and backup from your Mac running Retrospect. If that won't work for you, please elaborate on your setup, what you want to do and why you want to do just that.
  6. It would not make much sense in backing up a volume you can't restore. The OS (and/or Retrospect) can't write back any information, making the backup useless. There are no official documentation from Microsoft how NTFS really works. That's probably why Retrospect for Mac will not handle it. Do you really need it to be NTFS? I would recommend exFAT, which Windows and macOS handles just fine. Retrospect for mac and Retrospect for Windows handles it as well.
  7. That is correct, but NTFS is a native Windows file system. Try to backup a Mac drive on the Windows version.
  8. Strange. Although macOS can't write to an NTFS volume, it can read it. So Retrospect should be able to handle it perfectly well. I think you might want to open a support case. https://www.retrospect.com/en/support/edition
  9. How is "Mac Studio" formatted? And what partition map does it have? (GUID or MBR or ...)
  10. The local drives should turn up in "Sources". I have a slightly older Retrospect and a slightly older macOS, but here is what it looks like here:
  11. Without storage groups you can backup one client to one destination at a time. Which means that with multiple destinations (backup sets), you can backup multiple clients simultaneously. That could make sense if you group your clients according to where they belong in the organisation. For instance, finance department computers use the finance backup set, production department computers use the production backup set and so on. Each department can then be backed up simultaneously as the departments. With storage groups you can have a large backup set for all computers and several clients can be backed up to that backup set simultaneously. Having a single, large, backup set may or may not be an advantage. Besides, version 12 is outdated by now. For instance, recent Windows 10 versions are not supported and not Windows 11. If you run older versions of Windows you may be fine with Retrospect 12, otherwise I would not trust it to restore without problems.
  12. The question is how the old .rdb-files got there. One theory is that you had a backup set with the same name that you deleted (forgot) in Retrospect, did NOT delete the .rdb-files and then created a new backup set with the name and storing the member files in the same location. Does that sound feasible? In that case it would have been better to recycle the backup set and Retrospect would have deleted the old files for you.
  13. Say what? 14.6 is four years old by now. How old is your OS? How old is your NAS firmware?
  14. That clearly looks like a bug. You should contact support: https://www.retrospect.com/en/support/phone
×
×
  • Create New...