Jump to content

splurzgalonk

Members
  • Content count

    10
  • Joined

  • Last visited

Community Reputation

1 Neutral

About splurzgalonk

  • Rank
    Newbie
  1. splurzgalonk

    LTO-7 under OSX

    Hmmm. 25. april and no answer? I do have the same question. LTO 7 drives compatible? I've seen Thunderbolt LTO 7 drives that said retrospect is supported... but how is it the other way round.
  2. splurzgalonk

    10.5 stops polling proactive script

    I still have that issue and I can't really pinpoint it to when or why it happens. Every now and then, the proactive scripts simply stop polling. The only way I can make it run again is to reboot the system. In the background, I see that retrospect engine is constantly running 100% (1 core) on a multi core machine. Another retrospect server of mine repeatedly looses connection to an erratic amount of machines that are on the net visible and accessible. I have to use the "Locate" button to "reactivate" that very connection and as soon as I do that, the proactive script, which runs and backs up other sources on the same net during this issue, starts to see those "Located" machines again.
  3. splurzgalonk

    10.5. looses connection to clients

    Thanks for the idea. Wouldn't RS then continue to backup the same client, if in the next backup cycle the network card isn't maxed out? In my experience, RS throws a client not found error (error -530 ( backup client not found)) and then subsequently can't access the client at all. Not even to define new favorites on the HD or something the like.
  4. splurzgalonk

    10.5 stops polling proactive script

    First of all, thanks, Lennart. I don't have any idea, where I would find the screen you've posted. Seem like the windows UI is quite different to the Mac. I derive the fact that it stopped polling by simply looking at when the last backup of ANY client on the net happened. And after a certain point there is no backup made of any client. As soon as I restart the engine, the script picks up those clients visible on the net and backs up properly. I'll have to wait until it happens again to see what the states of all the sources is at that moment. As far as I can remember, the state was "ok" for all (= green icon in Mac UI).
  5. Beside removing and adding the client again, you might want to use the "Locate" button. That does the trick for me, although I'm not pleased to have to use tricks in the first place... You might want to contact the support staff with a reference to bug reports filed in the given board. That might help putting some emphasis on those issues. Obviously it is not that obscure a bug. cheers Roland
  6. splurzgalonk

    10.5 stops polling proactive script

    It stops seeing any client that appears in the network, even if they are available for hours over gigabit ethernet and I was able to check them with ARD. If the clients are not found, I usually get a message saying so. Not in this case, the engine simply doesn't see any clients appear. Media sets are fine too. No errors, no sign of problems. The scripts simply sit there, all green, and they do NOTHING at all, as far as I can see. Restarting the engine immediately picks up the clients and starts backing up again. It really just seems to forget to listen.
  7. Same here for proactive scripts that simply stop polling for connected clients. The scripts work for a varying amount of days and suddenly they simply stop. No error no nothing... just no polling anymore. Restarting the engine solves the problem and then the backup run again fine - until the next silent drop... This is really a PITA since we don't even get errors/alerts. cheers, Roland
  8. I have 10.5.0 (145) running on a Mac (10.8.5) backing up several servers. One server is on 10.6 and has the 10.5 client installed. It works most of the time but at a certain point in time, the scheduled script simply can't find the client anymore. The work around this problem is to re-locate the source (Locate button) and suddenly, Retrospect finds the server again and starts working properly. Any idea what could trigger this "client not found" crap? I mean, using "Locate" can locate the server, can access it and once done, RS suddenly finds the "not found client" again. No changes to the server, no network hiccups, nothing. Something is fishy, methinks. Hints much appreciated. Thanks in advance Roland
  9. I have 10.5 installed on a Mac and three proactive scripts with a dozen or so sources in each. The backup runs fine until a certain point in time (seemingly erratic), when the polling simply stops. Reboot or a bit simpler, disabling and re-enabling of the retrospect engine makes the polling work again. What's happening here? Any idea on how to prevent this "sleep mode" from happening? cheers, Roland
  10. Using RS 9.0.2, I prepared a server backup containing some 500k files. I set favorite folders for dedicated folders on the server but forgot to check them in the source display. THat made Retrospect run a backup, check the 500k files and backup NONE. That's ok so far. But... on my backupdrive i found afterwards a 229 MB ( !!!) file for a empty backup ??? Hello! What is going on. Why would retrospect produce a 229 MB file on EACH run of the script, even if there was not a single file copied?
×