Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mjbarry

  • Rank
  1. Did you have any problems with the upgrade? We are planning to upgrade soon and we would like to avoid surprises.
  2. Has this been resolve? The monitor is pretty much useless on a Windows 2008 server. I have tried telling retrospect to log off and exit and the monitor still shows up hours after the backup has completed.
  3. I contacted support and they had me delete the backup set and create a new one. It appears to be working now. Thanks for the info.
  4. The tapes were in a old backup set however I erased them before I added them as members.
  5. Yes I have. The tapes are also under the Members tab. Once retrospect does a new member backup it just appends a new tap in the list.
  6. We are using Retropect 7.7.325 with an auto tape loader and have setup as scheduled backup with a backup set containing 5 blank tape members. After the first normal backup, a new member backup is performed. The new member backup does not select a tape from the member list it just selects a blank tape from the loader. Is there a trick to selecting the blank members of the same backup set? The help file states: New Member skips to a new member of the specified Backup Set. Retrospect will use an existing member with the correct name, or any new or erased media of the correct type. New Member is just like Normal, except files are copied to the next member of the Backup Set.
  7. mjbarry

    Slow matching under 7.7?

    I am running this version on a 64bit SBS 2008 Standard Server. I am not sure if that would make any difference.
  8. mjbarry

    Slow matching under 7.7?

    We have 12 GB of RAM. 1 operation was running. Total size of the NAS being backed up was 442 GB (282,311 files).
  9. mjbarry

    Slow matching under 7.7?

    We have upgraded to version 7.7.325 and are having problem similar to this. When retrospect goes to build a catalog with a large number of files it hangs and never completes. It also appears that retrospect takes all available memory. Is there a way to figure out why it hung? The logs do not show anything.