Jump to content

Glibbs

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Glibbs

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  1. Don't know why I spent nearly £700 for this 'upgrade'. It still doesn't 'see' clients even when they are listed in the add source page. Only after restarting the engine (that's a joke, having to wait sometimes 10 minutes or more to do so) will it deign to back up the odd client and then just stop. Rebuilding the thing is useless as it doesn't resolve anything. The Dashboard, when it displays, doesn't show accurate information ie. a client is actively being backed up doesn't show and recent backups are all zero for all days. When the engine succesfully stops the Retrospect app frequently crashes. For software which should largley be automatic is incresingly demanding more of my time managing it I have been using Retrospect ever since it first came out eons ago and if it wasn't for the fact that I have never had a problem restoring from a backup I would have used another vendor. Avoid.
  2. Good afternoon, Retrospect v11. The 'home' screen displays 'Loading Dashboard...' and that's it. Any ideas, it's been displaying this for the last fifteen minutes?
  3. Same problem here. Have done all that's been recommended:- Re-done the config file several times. Re-installed the whole App after erasing everything retrospect. Haven't re-initialised the disk.
  4. Why aren't re-scheduled proactive client backup times retained after engine restart?
  5. Glibbs

    Error -110 (invalid handle)

    My mistake but in general (so I might look in the right direction) what does the error mean please?
  6. This has happened after deleting the config80 files and re-doing the scrips (proactive) and adding clients. Retro 10.0.1 (105) Mac OSX 10.8.2 MacPro Early 2009 Running proactive script Error: Normal backup using Desktops at 06/02/2013 (Activity Thread 1) To Backup Set InHouse Backup... - 06/02/2013 09:30:59: Copying xxxxxxxx Scanning incomplete, error -1100 ( invalid handle)
  7. Glibbs

    Error -110 (invalid handle)

    I have the same thing on my Mac running Retro 10.0.1 (105) trying to backup the local disk. This has happened after deleting the config80 files and re-doing the scrips (proactive) and adding clients. (2) ?? (3) Mac OSX 10.8.2 (4) MacPro Early 2009 (5) Running proactive script (6) Normal backup using Desktops at 06/02/2013 (Activity Thread 1) To Backup Set InHouse Backup... - 06/02/2013 09:30:59: Copying barrieglibbery Scanning incomplete, error -1100 ( invalid handle)
  8. Proactive script to backup clients every two days. In the 'Activities' window, click on the client and click 'schedule'. . . .
  9. Both in V9 and now in 10 it seems that re-scheduling a backup the times are saved until you restart the machine/engine when it then defaults to the last time a backup was performed. MacPro OSX 10.8.2 - 8gb ram
  10. Hi, there's a possibility that proactive backups will revert to the schedule in the script. I quite often re-shedule client backups to the early hours of the morning but after a system re-boot the schedules are reset to the last time the client was backed up plus the scripts 'backup sources every' setting.
  11. Version 9.0.2 (107) client - 9.0.2.102 After adding a client, it is listed in the 'Sources' window and a small triang;e icon appears next to the name to access their disk but on e just one client that icon is not there. Additionally adding this particular client takes a lot longer than normal. The client's firewall is 'off' I can access the client with 'Remote Desktop' Any ideas? a later post:- Sorry, this is a -505 error but I still want to fix it please.
×