Jump to content

Search the Community

Showing results for tags 'macos'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. Background: I have 2 Synology NAS's, one that is strictly the storage for my media (photo) files, the other is the main backup destination for the media drive as well as other local drives in my system. For reasons unknown, no software changes of any kind made in over a year, the media NAS began to experience errors and crash when Retrospect (v 15.6.1 for Mac) ran its daily backup script. Synology support suggested changing the mounting of the media NAS from AFP to SMB. I did this and it seemed to fix whatever issue was at play with the media NAS crashing. I had to add the SMB media NAS share to my Retrospect backup script, which regarded it of course as a "new" drive and began to back it up in its entirety. During this process I discovered that due to operator error on my part the grooming options on the backup NAS hadn't been enabled and it began to run out of space. Retrospect prompted me mid-backup to add a new member to the Media Set that formerly consisted of the backup NAS only. I selected a local disk drive as a stopgap measure. After the backup was complete I enabled the grooming options on the backup NAS so that it should not run out of space in the future. The issue that I now find is that I need to remove the disk drive I added as a stopgap, and can't find any way to do so. I've looked through the manual, adding a member to a storage set is covered, removing a member is not. I've marked the stopgap drive as "lost" within Retrospect, but now the Activity pane shows each daily backup with a red 'x' for an execution error because of this. I have to look at each days' backup log to determine that the only error is the lost drive and nothing more, ideally I'd like to return to each backup pass being reported with the green check so that any real errors stand out and a quick glance at the Activity pane is all that's required. Is there a way to accomplish this without losing the groomed backups already present on the backup NAS? I don't have enough local storage to temporarily cache the backup NAS (~9.6TB) nor the media NAS (3.7TB) so need an in-place solution if possible. Thank you in advance, Andre (Retrospect 15.6.1 for Mac, MacOS 10.14.6 [Mojave])
  2. Found that when I changed the name of the source drive, even if the sources are refreshed to recognize those new source names, subsequent backups seem to revert the sources to what they were and then the backups fail because that device no longer exists. My workaround was to refresh the source list and then immediately run a script using those devices. Somehow that seems to work... For now. Here's the step by step in case you want to reproduce: Change the source name ( in my case I'd reformatted the source drive in APFS and renamed it) of a device in the Retrospect Multi-Server backup plan. Go to Retrospect and refresh the source computer to register the names of the drives. Wait 24 hours. Run the backup script with the sources. The source names revert over time (and running other automated backups) to the old names ALL BY ITSELF, those new source names previously existing in the dropdown list disappear, the old names replace them and any backup scripts using the old drive source names obviously will continue to fail, lacking manual intervention. After the workaround above- reset the source list by refreshing sources (Sources>select the source machine>Refresh) and immediately perform a backup. N.B., two anomalies reading through the log. The log shows "First Access" for the device "GenieMBP", even though previous backups of the device WERE COMPLETED previously that same day. Guess it means first access of those SOURCE DRIVES? The script also changed the source drive to something that existed ALL BY ITSELF during previous backups (Macintosh HD) prior to failing on the missing drives. For some reason signatures are no longer available/presented (where I had my User equipment, versions, backup device info, etc.) So, I'll try to include on every post until that feature of the forum is restored or found again. Retro Desktop Multi-Server 15.6.1 Host (Engine) CPU:  Mac Mini, 2GHz Core2 Duo, 16GB RAM, 500GB internal SSD (APFS), OS X 10.14.3 Host Backup Media: 8x External SATA III via Thunderbolt, 2x via FW->USB, USB3.0 500GB SSD Standalone Drive Router (1000BT wired and 802.11n/b/g wireless) Retro Client: Retro 15.6.1 (all)  3 Intel Clients (iMac, MBP), CPUs running OS X 10.14.3 H Retrospect log_190219.rtf
×