Jump to content

offthewall

Members
  • Content count

    64
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by offthewall


  1. If you are on an active support contract it is free.

     

    Customers who purchase on or after February 1, 2015 receive a FREE upgrade.

     

    http://www.retrospect.com/products/upgrade

    Thanks, it was that Upgrade Wizard I was unable to find. Looks like my upgrade is $499 Retrospect Upg Single Server Unltd Wkstn Clts v. 12 for Mac. I couldn't convince the purse string keepers to go for a support contract last time. :(


  2. Let us know if relaunching the console fixes the issue. If it doesn't, could you enable debug logging for the console using the option in Secret Preferences and send us the output (from /Applications/Utilities/Console) in a support ticket? Just reference this thread. It should indicate what the issue is.

    Restarting the engine or console (on both remote and server) does not cause the members to  return. I enabled logging and will attach log to my existing ticket.


  3. I have 8 Media disk sets setup. Four at a time are online. Two of them are missing all members (there is actually one for each) in the console.

     

    I tried the Repair function and pointed to the existing disk set file but nothing seems to happen and the set is still listed as having no members and backups request media.

     

    The console listing shows real usage of the sets but no members in the summary or "Members" tab.

     

    See screen shot.

     

     

     

     

    post-11680-0-74635500-1414012017_thumb.png


  4. 10.6.8 seems a little 'old' for v11, doesn't it?  What Mac are you on?  I'm running 11 on a Mac MINI and it works great, but it is a 2.6GHz i7 with 8GB RAM.  Even before the newer MINI I was running v9 on OS 10.5.8 on a 2006 MINI without issues.  A little more info on your Mac could help...

     

    _________________

     

    Just read the specs for v11 and I apologize... it does say compatible with 10.6.8.  Still, which Mac?  I'm running a backup right now and Retrospect is using 28% CPU according to Activity Monitor.

     

    I run the retro engine on 10.6.8 as well. Since that was the last real server OS from Apple, I believe there are probably a lot of Retrospect Server installs running on that OS.


  5. The two clients I have updated the client software on does vary for the block level backup but not in any way that makes sense to me. Another client which is still running the Windows 8.5 client has not changed. So far I have only seen the negative value for files remaining once.

     

    Here are the results for one client since installing Retrospect Desktop 9.0.0:

     

    - 2014-03-11 19:51:03: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
    Using Instant Scan
    Backing up -64 files using block level incremental backup.
     
    - 2014-03-12 20:21:24: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
    Using Instant Scan
    Backing up -64 files using block level incremental backup.
     
    - 2014-03-13 19:34:25: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
    Backing up -63 files using block level incremental backup.
     
    - 2014-03-13 20:34:44: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
    Backing up -65 files using block level incremental backup.
     
    - 2014-03-14 18:15:55: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
    Backing up -56 files using block level incremental backup.

     

    Running the Block Level Filter selector against this client reveals there are currently 96 files eligible for block level backup.

     

    Is the backup set you are using an existing one from a previous Retrospect version or a new one? The backup set I am using was created by an Windows 8.x version of Retrospect Professional.

    The backup set is an existing Disk set on a 12TB RAID created with Retrospect Macintosh v 10.5


  6. Seeing the same result for at least two of my Windows clients being backed-up by Retrospect Desktop 9 on Windows:

     

    - 2014-03-13 19:34:25: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT

    Backing up -63 files using block level incremental backup.

     

    - 2014-03-13 19:11:59: Copying Pushka Windows 7 Professional (C:)... on Pushka-LT

    Using Instant Scan

    Backing up -11 files using block level incremental backup.

     

    It would be nice to know what this means.

     

    I have also seen negative values for files remaining after backup completion in the new version.

    Is it always the same negative numbers for you or does it vary?


  7. I enabled block level incremental backup on my main proactive user folder backup script. Looking through the logs to ensure backups are actually being completed, there are a couple of puzzling items.

     

    I've noticed that every source states "Backing up -27 files using block level incremental backup."

    "-27 files"?? What exactly does that mean? Is that an error message? A number of files? A dash?

     

    Also the "Completed", "Remaining", and "completed successfully" entries don't make a lot of sense to me when taken collectively. Why are there still 2145 files remaining, 318 files completed yet the script was completed successfully?

     

    Using Instant Scan
    Backing up -27 files using block level incremental backup.
    3/12/14 3:45:54 PM: Snapshot stored, 323.3 MB
    3/12/14 3:46:30 PM: Execution completed successfully
    Remaining: 2145 files, 381 MB
    Completed: 318 files, 419.5 MB, with 0% compression
    Performance: 449.5 MB/minute
    Duration: 00:30:29 (00:29:32 idle/loading/preparing)

    3/12/14 3:46:35 PM: Script "User Home Folders - RAID 10.5" completed successfully


  8. v11 bugs are far more likely to be fixed than v10. If it's no worse than v10, you've "moved the ball".

     

    Block level backups have a lot of potential. I have not yet had much chance to use them, but they have the potential to change my backup strategies, because some large files that ate up enormous backup space, will now be reasonable to back up on a frequent schedule.

    The frequent console quitting of 10.0 was finally solved after working with Retrospect tech support and a couple of new builds, so I've gone backwards a bit there. I'm as excited about block level backups as I am fearful of enabling them until I hear from others that it's reliable.


  9. Well, against my better judgement, I put v11 in. :)

     

    I seem to be having a repeat of many of the v10.0 issues I had;

     

    1) The console is unexpectedly quitting often.

     

    2) I'm attempting to upgrade the clients to v11 via the console and, like 10.x, the process seems hit or miss. Some clients will update, most will not. The ones than do update will not show the correct version until either the client is renamed (a trick I discovered with v 10.x) or the console restarted. 2/3 of the clients will not accept an upgrade via the console. I haven't visited each in person yet, but with 10.x, a manual update always worked.


  10. I would definitely like to see a test build addressing this issue.

     

     

    Very sorry for not replying sooner.

     

    Dennis, thank you for uploading the Activity Monitor sample of the SPOD'ing Mac console. We think it pinpoints your issue. It's a known problem (#3798) with 10.1.0.221 that comes up in certain environments, and it will be fixed in the next update.

     

    For everyone else seeing seeings SPODs or sporadic hanging, it would be a great help if you could also sample the hung Retrospect process with Activity Monitor and upload the resulting file to a support ticket. That way, we can make sure we fix all instances of these hangs in the next update. As iCompute suggested, the root cause is the chatty console/engine protocol that ensures the console information is up-to-date.

     

    Please contact our support team if you are interested in seeing if an upcoming test build will fix your issue.

    Is there a test build or update available yet? I would LOVE to test it for you. The constant SPOD'ing is ever present with both of my installations. thx.


  11. Very sorry for not replying sooner.

     

    Dennis, thank you for uploading the Activity Monitor sample of the SPOD'ing Mac console. We think it pinpoints your issue. It's a known problem (#3798) with 10.1.0.221 that comes up in certain environments, and it will be fixed in the next update.

     

    For everyone else seeing seeings SPODs or sporadic hanging, it would be a great help if you could also sample the hung Retrospect process with Activity Monitor and upload the resulting file to a support ticket. That way, we can make sure we fix all instances of these hangs in the next update. As iCompute suggested, the root cause is the chatty console/engine protocol that ensures the console information is up-to-date.

     

    Please contact our support team if you are interested in seeing if an upcoming test build will fix your issue.

     

    I would definitely like to see a test build addressing this issue.


  12. Do you really mean freezing, or do you mean frequent SPODs/beachballs in the console app?

     

    We've been experiencing a lot of SPODs with the Retro 10.1(221) console. Most are of just a few seconds' duration, but if the Retrospect engine is busy for any reason, they can last for 10 seconds or more. I've been attributing this to the way the console now updates the data from the engine more frequently. I've found them to be annoying but not paralyzing, though the delays can be rather frustrating when all you want to do is make a quick change or view some information. Given how the earlier versions of the console used to be rather haphazard in the way they updated themselves from the engine, I had been thinking that the tradeoff between responsiveness and timely data was worth it, but now I'm wondering why we can't have both.

     

    I'm curious what kinds of configurations those of us have who are experiencing reduced console responsiveness. It would seem logical that a more complex configuration would require more frequent polling of the engine by the console to see if changes have been made.

     

    Our setup consists of 42 local and client sources, most of which have between two and seven favorite folders; 6 media sets, two of which have 14 members each; 21 scripts; and 12 rules, a couple of which have around 30 elements. 1,800 past backups are listed. This doesn't seem particularly complex to me. Your thoughts?

     

    Yes, your description of SPODs is what I mean by freezing. The problem is that the 10 second or more SPOD is followed by only a 1 or 2 sec period of responsiveness then the beach ball returns. It took me almost an hour to change the media set on 10 scripts this afternoon. You get that second or two to try to click what's needed and then you wind up clicking something that your were trying to click 15 minutes ago.

     

    Underneath, the backups are continuing at a decently fast pace.


  13. If you see the performance problem with a local console, that eliminates the network performance. (as long as you are connecting to 127.0.0.1 - you might want to check) That means that whatever is dragging is local to the machine, unless the catalogs or config files are "remote" for some reason, like mounted NFS or AFS.

     

    I wish I were in NYC. It might be interesting to do some analysis to see what's so slow. All I can tell you is that it's not a problem for me. There must be something peculiar in your installation, and something that changed from 8.0 to 10.1.

     

    One question: Do you have any heavy-duty debugging settings turned on in Retrospect? I think those could cause performance problems if set aggressively enough.

     

    I'm not sure, not intentionally. Where would I check for those debugging settings?

     

    I get spurts of responsiveness. For about 10-15 seconds, I can zip about the UI, then spinning ball again.

×