Search the Community
Showing results for tags 'v16'.
Found 2 results
-
Greetings! Running Retrospect Server 16.6.0 (114) on a MacPro trashcan updated to Catalina 10.15.3. Currently there are no 'client' machines, I'm simply backing up 5 shared volumes on a Synology RS2414rp+ (also current DSM) to LTO-6. I've added the shares via Sources using 'afp://myFileServer.local/Share_Name', and set it to log in using a registered user with admin privileges. The shares all show up in Sources with the green status indicator. Backup scripts are set up to run after hours, and I've got a 5-member media set, two blanks, and a cleaning tape in my 8 slot robot. All Good, right? Nope. Shortly after a script starts, Retro begins scanning. Then it hangs and I get a macOS system alert saying the server is shutting down. After that, my Retro log fills with 'file not found' errors and nothing gets backed up. Checking the Sources pane after this, the target volume shows as disconnected. Status goes green again via either Browse button or Locate. Any ideas? Thanks in advance!
-
Storage Groups vs. standard script?
fredturner posted a topic in Retrospect 9 or higher for Macintosh
Hey Everybody— I've been very pleased w/ how much faster backups are now w/ Retrospect 16, since InstantScan is working again. And the ability to back up multiple clients at once via Storage Groups is a very welcome new feature. One problem is that there doesn't seem to be much documentation about pros/cons and caveats...just one brief KB article. Two things I've encountered are: 1. No way to limit the number of execution units a group can use (at least, not that I can tell). It appears that a Storage Group will simply use however many threads you've specified for the whole Engine in Preferences. If that's the case, I'd suggest v16.1 adds a field to the Media Set options that allows limiting based on preference and/or practical disk speed limitations (while not limiting the overall # of threads/units). 2. More importantly, I seem to have trouble w/ a standard, nightly script that I want to back up to the same Storage Group that my client stations back up to. Obviously, Storage Groups are targeted at Proactive executions, but the KB article also says, "Scheduled scripts support Storage Groups as destinations, but the backups run on a single execution and not in parallel." I keep having trouble getting these scripts to finish executing. Just now, I had one disk in the script back up 8GB, then during scanning of the next disk, the whole thing just stopped and is showing that it needs media. The media has plenty of space, and the hang appears to have occurred before the scanning even finished. Has anybody else seen this or know why it is balking after a partial backup? There may be more going on than I'm realizing, but again, I just don't see much in the way of specific documentation! Thanks for any suggestions or thoughts. Fred
