Jump to content

David W Lee

Employee
  • Content count

    185
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by David W Lee

  1. David W Lee

    Mac Retro 902/Client 902: Lost Client

    Sorry, please see corrections in red above.
  2. Based on user feedback through Support and Forum, we set this behavior in 10.1.0 (221). More specifics are here. We will investigate.
  3. David W Lee

    Error message in Log: nertPInstMake: wrong serial number: sought

    As Robin has replied before me, the key is whether there are actual errors connecting to or backing up clients, such as "Can't access volume XXX on YYY, error -525 ( wrong client found at that address)". If there are indeed such errors, use Console to remove and re-add the specifically named Client named in the list of Sources. (Latest corrections are in red.) Regarding the Client serial number itself: The Client serial number is auto generated and saved in Client's /Library/Preferences/retroclient.state retclient.dat the first time when a Server adds the Client to the list of Sources. From that point on: - Client side: The serial number should remain unchanged until you manually delete it. Recent versions of "Uninstall OS X Client" tool do not delete is invoked and deletes /Library/Preferences/retroclient.state. - Server side: The serial number obtained from each newly added Client is stored in the ConfigXX.dat and ConfigXX.bak files until the corresponding Client is removed in Console's list of Sources. If the ConfigXX.dat file is corrupted somehow (possibly during a Engine crash), that can cause mismatch with the Clients' serial numbers. That is fine as long as the cloned Client computers have unique names shown in Retrospect Client and get added by a Retrospect Server after cloning. Points noted. We will plan to improve the error message to include the Client name, and possibly (TBD) show each Client's serial number in Retrospect Client and Console.
  4. David W Lee

    Mac Retro 902/Client 902: Lost Client

    To fix this, use Console to remove and re-add the Client named "MB250 Lion" in the list of Sources. (Latest corrections are in red.) The Client serial number is auto generated and saved in the Client's /Library/Preferences/retroclient.state retclient.dat the first time when a Server adds the Client to the list of Sources. From that point on: - Client side: The serial number should remain unchanged until you manually delete it. Recent versions of "Uninstall OS X Client" tool do not delete is invoked and deletes /Library/Preferences/retroclient.state. - Server side: The serial number obtained from each newly added Client is stored in the ConfigXX.dat and ConfigXX.bak files until the corresponding Client is removed in Console's list of Sources. If the ConfigXX.dat file is corrupted somehow (possibly during a Engine crash), that can cause mismatch with the Clients' serial numbers.
  5. David W Lee

    VMware Agent

    For backing up a Windows VM, the newly released Retrospect VMware Host Server add-on works with VMware to enable Retrospect server to bypass the VM and read the VM’ volumes from the VMware host storage, instead of going through Retrospect Client software running inside the VM utilizing the VM's storage and network stacks. The benefit is significantly less impact to the VM's performance while achieving much higher backup throughput. The backup is still safe because during this process VMware works with Windows Volume Shadow Copy Service to prepare a crash- and application-consistent state for Retrospect to back up. And it works with Retrospect's efficient file-level deduplication across multiple physical and virtual backup sources, selectors to precisely control what to and what not to back up, disk storage management via grooming as well as the option of direct-to-tape support. There is more information here.
  6. This is bug 3692 and we are investigating. In the interim, an admittedly rough workaround is to select those 2 files' parent folder and click "Add to Favorite Folders", and then back to the "What do you want to back up" screen and check the box for that folder. If that folder contains some files to back up and other files to exclude, you can add a rule via Preferences > Rules > + > Any of the following are true > + > specify the rules for what to include.
  7. David W Lee

    Backing up on-modified files

    If the backup source is Mac OS with a Mac HFS volume, the issue may be due to file attribute modification date changing even when file creation date and file modification date haven't. In that case, if file attributes (listed by "ls -l@" or "xattr -lv") aren't important to you, you can disable your script's Options > Source > Macintosh > Use attribute modification date when matching. More info at: - Search for "Use attribute modification date when matching" at http://retrospect.com/en/documentation/user_guide/mac10/operations#creating-a-backup-script-manually - http://forums.retrospect.com/index.php?/topic/147494-copyoverwrite-entire-volume-still-copying-far-too-much-in-retrospect-9/page__st__20
  8. Please see this article and change: SetFoundationLogging=6 (from 3) SetVolumesLogging=7 (from 3) Then perform backup and see if the log shows error -1100 with additional related info. Also, does the volume with error -1100 have a hidden Time Machine folder "Backups.backupdb"?
  9. David W Lee

    Large config80.dat file? (225MB)?

    Yes if it is acceptable to no longer see in Console past Activities and associated logs. Those information do stay in Server's operations log until that gets too big. Also, Past Backups, Scripts, Sources, Media Sets, Storage Devices and Console Preferences are unaffected.
  10. Mostly yes. A scenario that can happen due to Retrospect's deduplication is: 1. Recycle, so next backup will be a full backup 2. Back up /folder1 (as one Source/Favorite) and then /folder2 (as a separate Source/Favorite) in one single run of a script. 2.1 When backing up /folder1, the freshly recycled catalog is empty and so there is no matching/deduplication. Files under /folder1 selected by the script's rule will be backed up. 2.2. When backing up /folder2 which is a separate source/favorite, the catalog now has info about files backed up from /folder1 at step 2.1. Files under /folder2 that match what have already been backed by at step 2.1 won't be backed up again, just noted by Retrospect that they exist in /folder2 to enable restore if needed. After a backup, if you see "No files need to be copied" for a particular source, you can test restore of 1 file from that source to a different location to reconfirm the backup is good.
  11. Please open a Support ticket and provide C:\ProgramData\Retrospect Client\retroclient.log as well as the Windows' event log (.evtx) files.
  12. Points noted. We will be improving online documentation shortly.
  13. We recently updated http://retrospect.com/en/documentation/user_guide/mac10/instant_scan: Starting from Retrospect 8.1.0 (266) for Windows and Retrospect 10.1.0 (221) for Mac, Instant Scan is only used for scheduled script activity, and not any activity manually started by clicking a Run button.
  14. Will check the support ticket history tomorrow. In the interim, a sanity check: Are you using a Favorite as the backup source (instead of a Rule on the entire volume or entire computer as backup source) to backup the Users Library folder? If not, that will significantly shorten the snapshot building time, which depends on how many files and folders exist on the backup source, regardless of how many files are actually backed up. I am pinging the team for update.
  15. Yes, recycle and then running back up will back up all the selected files again to the recycled media set. If that's not what you observed, it may be due to Retrospect's file deduplication feature: If /folderA/file1 matches /folderB/file1 in terms of having same properties (name, size, dates, etc.), Retrospect only backs up one of them per media set, while noting it exists in both folders to enable the correct restore behavior. This is based on media set, not script and not backup source. If scriptA backs up folderA to Media Set X and later scriptB backs up folderB also to Media Set X, the activity log for scriptB may show "No files need to be copied" because scriptA ran first and already backed up /folderA/filer1 which matches /folderB/file1. Another possible factor is the Rule selected for your script exclude all files in the folder you are concerned about.
  16. David W Lee

    Backing up on-modified files

    Is that one machine being redundantly backed up via Retrospect Client? Windows / Mac / Linux? Are the relevant volume(s) local to that machine using a file system native to that machine's OS? If remotely mounted on that machine, what is the protocol and the actual underlying file system used by the file server?
  17. See http://retrospect.com/en/documentation/user_guide/mac10/whats_new#tips about "Restoring from Retrospect 6.x backups".
  18. David W Lee

    Large config80.dat file? (225MB)?

    Retrospect's Config*.* files have a proprietary format. One of the situations where .bak is created is when Retrospect Engine exits, to preserve the small amount information most important to users, such as sources, scripts and configurations. It is created from the .dat but without execution history and events, therefore much smaller. When Retrospect can't find the .dat, it automatically copy the .bak to .dat.
  19. Please see newly added information (including launchctl -w and related installation issue) at: http://retrospect.com/en/documentation/user_guide/mac10/instant_scan
  20. David W Lee

    Retrospect 9 not adding a new member

    We have added to the to-do list. Thanks for raising this.
  21. We have reproduced this in some environments and are investigating now.
  22. Morrie and Swish, when such issue occurs, do you see anything unusual in Retrospect's operations log after restarting the Engine?
  23. David W Lee

    Is grooming working in 10.1?

    Is it possible that since prior groom no additional files in the media sets have fallen out of the grooming policy: Retrospect’s default policy retains two backups for each source, saving the last backup of the day for each source from the two most recent days on which each source was backed up. Given enough space in the Media Set, Retrospect keeps a backup of each source for every day in the last week, a backup for each week in the last month, and a backup for each previous month.
  24. David W Lee

    Copy Media Set selection rules

    Thanks for sharing the update. We have been and are continuing to address several key areas, particularly grooming and catalog rebuild.
  25. Both Mac and Windows Client help links have been fixed on retrospect.com. Thanks for raising this.
×