Jump to content

zz-pdb

Members
  • Content count

    11
  • Joined

  • Last visited

Posts posted by zz-pdb


  1. 5 minutes ago, JamesOakley said:

    But if it's running in the background, with no UI visible, it shouldn't pop a dialog that you have to click "OK" to before anything continues.

    I'm now on 15.6, and it just did it again - no backups ran for 3 days until I noticed that they hadn't. Killed retrospect.exe, and started the program again, and the waiting executions all began to run. The thing is, under 15.x for Windows, even Desktop edition gets multiple execution units, so one stuck job shouldn't freeze the whole setup.

    the dialog only came up as I tried to start the UI up again.

    Same here actually. updated to 15.6 and it's been fine for about a week and today, came to find 5 or so scripts just froze with no error. Had to kill retrospect.


  2. On 10/18/2018 at 2:17 PM, JamesOakley said:

    Go on, I'm intrigued: when you click "View the message", what is it?

    its just the usual messages of scripts that execute while retrospect console was not open (usually it is). those messages are usually pertaining to scripts that weren't successful because a client was not found or similar (user turned computer off type of stuff).

    Don't believe this is related, usually the console is open and so these messages don't come up.Just brought it up since we were talking about hidden messages.

    Untitled.png


  3. On 10/13/2018 at 11:33 AM, Scillonian said:

    The version of Retrospect you are running and the OS of the Backup Server and the Clients would be helpful in offering you suggestions.

    Also thoroughly check you network hardware. A momentarily failing network switch, which I have had, can wreak havoc with backups.

    whoops, added

    Windows 7 Pro x64
    Multi Server Premium
    Version 15.5.0.179

    This hasn't been a problem in the past, even with network issues it would error with "network communication error" or something along those lines. As far as invisible dialogs go, usually Interactive Services Detection from windows pops up with something (image attached)

    Untitled.jpg


  4. Many of my backups have stopped part ways. At the moment there are 5 scripts stopped on "Scanning (C:) on blah-computer", 1 script mid copy (performance and time remaining/elapsed are not moving), and 1 script in "Finding 'another-computer'"

    None of these are showing any relevant errors or warnings giving me a clue as to why it has just stopped. I'm able to pause but not stop these are all i can do is force a reboot. This happened on one other occasion and stopped all scripts from executing as well. The interface is still responsive.

    Interestingly the logs show the last entries at about 7-730 pm but all I can figure from that is they all stopped "at the same time"

    Also, not all of the scripts stopped, some scripts finished after this time period.

    Windows 7 Pro x64
    Multi Server Premium
    Version 15.5.0.179


  5. Sorry, I don't mean any of this as a flame post, they are just my observations.

    Retrospect version
    Multi Server Premium - 15.1.2.100
    Windows 7 Pro
    UAC off
    Retrospect Launcher service on
    Automatically launch retrospect on
    Always run Retrospect as the specified user (set to the user I always log in with)
    no proactive scripts, just scheduled scripts at night

    Normally I do open it and leave it running but recently I've needed to reboot for non-retrospect related things (win updates, hardware, etc).


  6. I saw the section of running as the same user as what i'm logged in with, and this is already set. To me the biggest problem is that starting the console is faster and more reliable than starting the dashboard. Is there really no way to bypass via a command line parameter or something?

    It feels like a design issue on the dashboard where retrieving the data and showing the interface are on the same thread and so if getting the data is slow, i'll never be able to click "relaunch" to start the console. The dashboard looks nice, and well organized but it's performance defeats the purpose of a "dashboard".

    On the side, the notice that says "click launch retrospect" really does not correspond with a graphics only button where it's tooltip doesn't say "launch retrospect"

×