Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling

Insixdays's Achievements


Newbie (1/14)



  1. I usually just find the client in the backup report, highlight the info that says when the last backup happened and delete that info. Be careful not to delete all clients backup information. This should put the client at or near the top of the Proactive list. Sometimes I have to go to history and delete some past history as well.
  2. I got around this problem by setting compatibility mode for setup.exe, Retrospect Client 10.0.msi to Windows 7 and instmsia.exe and instmsia.exe to Windows XP sp2. Also had setup.exe set to run as Administrator. Also, I may have started the install using the MSI instead of the setup.exe. But I am having a problem with the firewall settings.
  3. I have read many times about the algorithm used with proactive backups and how it puts the clients that have never been backed up at the top. Also it is supposed to optimize the proactive backup procedure. I have to assume this works well for other users but it does not work well for us. We have a lot of clients in our database and it takes a long time for the proactive backup to get through the entire list. I like that it seems to seen when a client connects and may start that backup right away, but I would really like the option to just let the process go through from never backed up to most recently backed up without trying over and over again to backup machines that are not in the office. This could be setup as an option, to use the algorithm or just go from top to bottom in the list. Also even when a client is set to be deferred it is not skipped over immediately. It seems to poll the client to see if it is there instead of just skipping it. This also seems to be the case when it gets to the bottom of the list. It runs through clients that were already backed up that day instead of skipping them. I would be very willing to talk with Retrospect designers about this. I like Retrospect and I think it is a good product, but I think it can become a great product. Thanks for all your work to make this product even better. Jeff
  4. Just upgraded from 7.7 to 8.0. The server does not see any of the 7.7 clients so I can update them and grooming jobs run and then I get the Assertion failure at "grx.cpp-1089" The server is Windows 2008 R2. This is also a case with Retrospect #00013353
  5. In Retrospect we have a lot of proactive backups. The problem is that instead of going through the list of possible backups rather quickly the polling will just sit at the top of the list for 10 min or more, then only poll 10 or 20 items in the list and then start over again. What can I do to get this moving through the entire list. We would like to upgrade but if this problem cannot be solved we will need to go to a different solution. I am hoping there are some settings or something I can use to change the polling speed, or even a registry hack. Thanks!
  6. Greetings, As I have been looking at Retrospect it looks like it checks to see if a file is already in a backup set before it copies it and that because of this you could backup two different computers to the same backup set and if they both had the same file there would only be one instance of that file, but the backup set or maybe the catalog would know that both computers might need that file. In which case if the entire session for one computer was deleted the backup set would still keep the file for the other computer. Is that correct? We are considering backing up all our C drives to the same backup set and yet not duplicate files that are the same, but still have the ability to restore the correct files to a particular computer as needed, and still be able to groom out obsolete computers without messing up the backup for the computers we are still using. I hope this makes sense. Is this possible to do and is there anyone out there doing it. Thanks!
  7. Thanks for the info. Who can I talk with about upgrading?
  8. Is there any good reason it should not work? I know it works in direct mode.
  9. Greetings, We are using multicast for our Windows XP computers with little problem, but we are not able to see the Windows 7 64 bit computers with multicast. The firewall has the retrospect client listed for both inbound and outbound. I also changed the core networking multicast settings scope to all networks. Even with the firewall off the Windows 7 64bit computers are not seen. We are on Retrospect 7.5.508 with hot fix Thanks!
  10. I have a followup question. Why, in my list of proactive backups does it not move to the next backup when the computer that is to be backed up is out of the office. The "Action" keeps saying Polling and then Checking Source, but it does not move on to the next item in the list. Thanks!
  11. Thank you for your response. Is there a way to merge existing backup sets into one? Thanks!
  • Create New...