Jump to content

Search the Community

Showing results for tags 'catalog rebuilding'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. First: Background Chassis: Dell Poweredge T410 Xeon E5620 @ 2.4 GHz 8GB RAM 5TB RAID 5 on a Dell PERC 6/i RAID controller IBM ULTRIUM-HH5 Tape Drive Software Windows Server 2008 R2 Standard x64 Retrospect 7.7.620 -- It all started when I did a standard cleanup on the RAID and it wiped out the entire catalog set. So I dumped that destination, and started over. Ever since I have started having severe issues with the backup process. The screenshot attached says it all. What ends up happening is even on a full reboot, as soon as it tries to backup any client on the network, Memory usage climbs to maximum and the backup either hangs, or fails eventually with the "Not Enough Application Memory" error. On the worst case, Retrospect throws a cpp error and dumps the process. in either case it damages the catalog file belonging to the destination it was accessing, Attempting to rebuild it, fails with the same error... and endless loops ensue. I am honestly at a loss here... I have not backed up the network since the 1st and I am beginning to look at other options. Help?!
×