Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


fredturner last won the day on August 2 2017

fredturner had the most liked content!

Community Reputation

8 Neutral

About fredturner

  • Rank
    Occasional Forum Poster
  1. Hey Everyone— I am wanting to create a rule for excluding render files and transcoded media from Final Cut Pro X. FCPX keeps these files inside event folders, which are themselves contained in Libraries, in folders called "Render Files" and Transcoded Media". So the hierarchy would look something like this: My FCPX Library.fcpbundle My Event 1 Original Media [some other files and folders] Render Files Transcoded Media My Event 2 ... I seem to be able to do 2 ALL conditions, one each to select Render or Transcode: – Folder Mac Path Contains ".fcpbundle" – Folder Name Contains "[Render Files/Transcoded Media]" and I think that will work. But it seems clumsy to me. Is there a way to only list the parent folder path w/ ".fcpbundle" once, then the other 2 below it? IOW, the parent condition is an ALL and the 2 child conditions are ANYs? I need to match the parent condition for sure, and one of the children. I don't seem to be getting the Any/All popups to do that right. In this case, it isn't critical, but if I had more subfolders under the parent that I wanted to exclude/include, having to list the parent every time gets a bit tedious. Suggestions? Am I doing it wrong? Thx! Fred
  2. That is an excellent question! ...and leads to another question/suggestion: Why is there no way (or at least no easy/obvious way that I've found) to find out how many clients you have logged in? I had to count one screen's worth and then page down and multiply. I get around 50 clients. I just don't understand why it takes SO LONG to get started on WAY OVERDUE clients. It can list all of the ones that are online in a matter of seconds when you go to Add or Locate. Why can't it do _that_ fast scan once every couple of minutes and say, "Hey, there's John's MacBook Pro...it's been 11 days since I've backed him up...nothing else is running and I have a valid backup disk...I'll start NOW!" Instead, I can have John's MacBook Pro jumping up and down and frantically waving its arms at the Retrospect server, but by the time the server has decided it might want to check John's MBP out, John's MBP has gone to sleep or left the network. I can just sit and check on it regularly for a period of a couple of hrs while I'm onsite, and it picks up hardly any clients when they are there and needing backup. I even try to help it along by clicking Browse on a client disk or doing a Refresh on the client. But it just sits there w/ its fingers in its ears. It'll eventually get to them, but I can't imagine how awful it'd be in a truly large setup. All of this "dead air" is wasteful time-wise and leads to clients getting missed. Why isn't the Engine more aggressive and active??
  3. Rebuilding the set didn't matter. I can click on the set, choose "Performance-optimized grooming" from the menu, click Save, then click on another set and click back, and it has reverted back to Storage-optimized instead. I changed back to Performance-optimized again and started a grooming operation, but the log says "optimizing for storage..."
  4. These sets were created in an earlier version. I believe I have already rebuilt 1 of the 3 sets, but I could be mistaken. I am doing a full rebuild on Set C right now and will see what I get once that's done. Thx, Fred
  5. I'm trying to enable the Performance-optimized grooming in v13, but each time I select that under Media Sets > Options, click Save, then click away and come back, it has reverted to Storage-optimized. Is there a trick to this? Does the set need to be recycled? Catalog compression turned off? Some other setting done/undone? Thx, Fred
  6. I've been wondering this for a long time now, but have never figured it out or gotten around to asking here. So, I have a site w/ numerous clients, all added to a Proactive script that has 3 sets for its destinations: Alpha, Bravo, and Charlie. When I look at Activities > Proactive > Destination column, I see 1 of these 3 sets next to each entry. However, I may have Set Bravo connected (like now), yet some of the clients show the Destination as Set Alpha. Why? So, even if the client is in need of backing up (every 24 hrs) and says Destination is Set Alpha, since I have Set Bravo connected, it won't back up. Some questions about this aspect of the Proactive scripts: 1. How is Retrospect determining the set it lists under Destination? 2. Is there any way to manually change the set (w/o some crazy cheat or workaround, I mean)? 3. Is there any way to "nudge" Retrospect to go ahead and back up a client when I know it is now connected, active, and has a suitable backup set available***? *** = I just watched it take 20+ minutes to start backing up a machine that hadn't backed up in weeks, despite clicking Schedule and setting it for the current time. In the meantime, another overdue spare MacBook that I woke up to also back up went back to sleep. Just seems like this should be quicker, or at least able to be hurried along while I'm in the Console. Thanks, Fred P.S. This is on v13 Multi Server, but also occurs on many other installations I support from v10.5 thru v13.
  7. This used to be a problem when we were using Retrospect 8 and 10 w/ clients primarily running Mac OS X 10.6.8. We have our users log out when they leave, and in the past, the logout would kill the Retrospect client. This changed when we started going to 10.9 Mavericks and Retrospect 11 (I think, I don't remember the exact combination). However, now with 10.10 Yosemite and Retro 11.5.3 (Client v11.5.2.104 currently), I've noticed this behavior becoming more and more common w/ our stations again. I have to regularly send out a launchctl unload/load combo to the client startions' daemons via Remote Desktop: launchctl unload /Library/LaunchDaemons/com.retrospect.retroclient.plist launchctl load /Library/LaunchDaemons/com.retrospect.retroclient.plist One observation about this: as soon as I send that pair of commands, most of the stations, which have been idle for possibly hours at the login window, will immediately go to sleep. Almost like the retroclient process is keeping them awake, but not facilitating a backup. I'm glad to provide whatever add'l details would be helpful, as well as test different scenarios and possible fixes. As a personal aside, I really think that you guys (Retro, Inc.) ought to focus more on testing and bug-fixing w/ networked and multiple remote-console scenarios. Another glitch that still afflicts my console (even v12) is mixing up of "content" from 2 or more different remote engines. We're essentially still paying for (incomplete) bug fixes 4 and 5 versions after the rewrite (v8). I use and have sold Retrospect to at least 10 different clients of mine, but at each purchase time I grimace a little bit because I know that the polish that ought to be there still isn't there, and I'm buying on the hopes that it'll eventually get there. If the coffers are full enough now w/ all the paid upgrades, please focus on nothing but streamlining and polishing the program— no new features— w/ some serious attention to complex, networked setups. We're not that far off anymore, but it's disheartening to continue to see such frequent releases requiring my clients to pay hundreds or thousands of dollars for in order to get some more bug fixes. Thanks, Fred
  8. I am seeing the same behavior in an environment with: Retrospect Mac 11.5 Multi-Server on Mac OS X Server 10.6.8 Windows XP Pro 32-bit clients (VMs actually); doesn't seem to matter what login state is One of the 4 Windows VMs was actually at v8.5. I was able to push the v9.0 client update from the v11.5 Mac Server. But then I was unable to go to v9.5. The error in the log was simply: !Client AVGadmin could not be updated. error -1 ( unknown) In another environment w/ the same Mac Server version (although Single, not Multi) but Windows 7 clients (probably 64-bit, but I'm not sure-- I don't handle those systems often), the v9.5 update seems to apply smoothly. Robin, a related complaint, FWIW, is that it seems to take multiple attempts to update Mac clients via Mac Console (I realize this is the Windows forum, but it may happen from a Windows Retro Server as well), and the process is quite arduous. There's no progress indicator and no way to tell if the update has succeeded. I've had to try again and again to get some clients to update. I had a little better luck by first toggling the client using Remote Desktop and the "launchctl" command, then updating. As a whole, not a very user-friendly process! Thanks, Fred
  9. Digging up an old thread, but a VERY good question, especially since we've been through a few more iterations of the Mac version. This seems so elementary and useful that I'm quite surprised it still has yet to have been addressed. I think most everybody would want to prefer Ethernet over WiFi. We have the ability in Mac OS X to "order" our interfaces so that one is preferred over another. I don't see why Retrospect Client couldn't regularly query this setting and always attempt to use the "highest" available interface.
  10. Out of about 30 machines, I have 1 Mac mini client (Retro v10.5) being backed up to a Retro 10.5 server, which each time kills the RetroEngine, which must then restart. Here's what the log shows: + Normal backup using Advent Float at 10/30/13 (Activity Thread 2) To Backup Set Advent Set Charlie... - 10/30/13 06:50:38 PM: Copying Macintosh HD on Katherine’s Mac mini Using Instant Scan 10/30/13 06:50:38 PM: No files need to be copied 10/30/13 06:57:26 PM: Snapshot stored, 108.2 MB 10/30/13 06:57:41 PM: Comparing Macintosh HD on Katherine’s Mac mini 10/30/13 06:57:44 PM: Execution completed successfully Duration: 00:07:05 (00:06:11 idle/loading/preparing) LmMark: ndex = 21579, not in range LmMark: ndex = 6917, not in range LmMark: ndex = 16339, not in range LmGet: ndex = 21579 > nsp->count = 0 Assert occurred on 10/30/13 at 07:00:47 PM + Retrospect version Launched at 10/30/13 07:00:48 PM Any ideas? Thanks, Fred
  11. Has anyone experienced less stability w/ Retrospect 10.5 vs 10.2 and earlier, particularly w/ the Engine itself? I've had to restart it to get it to proceed w/ Proactive scripts, and worse, several times it has stopped responding completely. In these cases, the Console cannot "see" the server, and using launchctl at command line or trying to toggle w/ Sys Prefs fails. I have to force quit the RetroEngine process. Anyone else seeing this or similar? Thx, Fred
  12. Updating clients

    Agreed. It is extremely tedious. At the VERY LEAST, it should return you to the same folder you last browsed to. Peter, I have, in fact, added the updaters folder to the root of my boot drive on the Retro server. Shortens by a few clicks and doesn't require as much scrolling. Still an inelegant operation. FT
  13. Got this resolved. For anyone else encountering this, it appears to have been that my Config80.dat file got corrupted during the update process. When I looked in the Application Support folder, I noticed that the Config80.dat file was about 45MB while the Config80.bak file was only about 23MB. So, I removed the corrupted Config80.dat file and restarted RetroEngine, letting it make a new one from the .bak file. HTH, Fred
  14. Hey Everyone-- I hadn't checked in a while, but was excited to see the 10.5 release available when I got the notice today. I've installed it on one server, but after drag-copying the Console and letting it run the included Engine updater, I'm seeing repeated, failed attempts to launch the engine on that machine, even after a restart. Here's what the log shows: Oct 3 15:37:39 mail2 com.retrospect.retroengine[1837]: #2> Command line is /Library/Application Support/Retrospect/RetrospectEngine.bundle/Contents/MacOS/RetroEngine Oct 3 15:37:39 mail2 com.retrospect.retroengine[1837]: #3> LmGet: ndex = 20, zero offset Oct 3 15:37:39 mail2 com.retrospect.retroengine[1837]: Assertion failure at "elem.cpp-1145", on threadID 0x10360D000 Oct 3 15:37:39 mail2 com.apple.launchd[1] (com.retrospect.retroengine[1837]): Exited with exit code: 255 Oct 3 15:37:39 mail2 com.apple.launchd[1] (com.retrospect.retroengine): Throttling respawn: Will start in 10 seconds This is on a Mac mini running Snow Leopard Server. Anyone seen this or have any idea what this might be about? Thanks, Fred
  15. RetroISA Questions

    May I tag on my related question? 4. Is there a way to set RetroISA to _not_ spew so much gunk in the system log? It makes finding anything else of value extremely difficult. I've already tried setting the logging levels to 1 and 0 in the retro_isa.ini file and relaunching the RetroISA process, but the logs are still filling up w/ these excessive notifications. Thanks, Fred