Jump to content

Search the Community

Showing results for tags 'Memory consumption'.



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. One of our clients has a Windows SBS 2011 server with Retrospect 8.5. The client has contacted us several times stating that they cannot remotely access their network through RWW (Remote Web Workplace.) Microsoft documentation shows that if the server is low on available RAM, it will shut down RWW services. The affected server has 32GB of RAM. When the client has called with the RWW access problem, we found that Retrospect was consuming over 18GB of RAM. At times, Retrospect appears to grab every bit of available RAM and not release it even though there is no active job running. Shutting down the Retrospect application resolves the problem; however, we are looking for a better long-term solution to this issue. *Retrospect has never been able to run "unattended" on the SBS 2011 server (it doesn't start up to process the backup jobs,) so we have been leaving the retrospect application open in an active session.
×