Jump to content

Search the Community

Showing results for tags 'RetroISA'.



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 4 results

  1. Hi RetroEngine and RetroISA seem to be constantly using up LARGE amounts of CPU and RAM percentage. How can I force these to stop interfering when Retrospect is not launched ? Is it possible to set it so that they are only active when the application itself is launched ? cheers Rod
  2. I've got one client which the server isn't using Instant Scan for backup. This just started after the 7PM backup of the client last night. Backups were running in 15-20 minutes with ISA on, now take at least 30 minutes, likely more. Retrospect 10.5.0 (145) on a Mac Mini quad-core i7 running Mac OS X 10.7.5. Instant Scan is enabled in the client (Mac OS X Server 10.6.8 on a 2006 xServe). RetroISA process is happily chewing up CPU cycles there as well. "Using Instant Scan" is missing from the start of the backup log for this client. It is present on backups of other clients. Client was at 10.2 something earlier, so I upgraded to 10.5 client. I've disabled & enabled Instant Scan on the client side. I don't see anything on the forums about this problem or how to troubleshoot it. This server was restarted last Friday, early morning. Any suggestions? Short of a restart (which is difficult for this server), anything else to try? Thanks. Cheers, Jon
  3. Upgraded my server to Engine 10.2.0.201 yesterday. I have not yet upgraded any clients from 9.0.2. I noticed that my system log was getting full of messages from RetroISA: Jul 18 16:39:36 %%SERVERNAME%% com.retrospect.retroisa[7334]: | ISAVol::doIsaTreeChanged: start update on volpath "/Volumes/Server HD/", 7/18/2013 4:39:36 PM Jul 18 16:39:36 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> ISAVol::CheckPrivatePathOption: PmcGetPrivate = 0x0 Jul 18 16:39:37 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> Jul 18 16:39:37 %%SERVERNAME%% com.retrospect.retroisa[7334]: ISAVol::doIsaTreeChanged: starting pass four - rescan 4 folders for "/Volumes/Server HD/", 7/18/2013 4:39:37 PM Jul 18 16:41:30 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> Jul 18 16:41:30 %%SERVERNAME%% com.retrospect.retroisa[7334]: | ISAVol::doIsaTreeChanged: start update on volpath "/Volumes/DATA1/", 7/18/2013 4:41:30 PM Jul 18 16:41:30 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> ISAVol::CheckPrivatePathOption: PmcGetPrivate = 0x0 Jul 18 16:41:30 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> Jul 18 16:41:30 %%SERVERNAME%% com.retrospect.retroisa[7334]: ISAVol::doIsaTreeChanged: starting pass five - update 1 folders for "/Volumes/DATA1/", 7/18/2013 4:41:30 PM Jul 18 16:41:31 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> Jul 18 16:41:31 %%SERVERNAME%% com.retrospect.retroisa[7334]: ISAVol::doIsaTreeChanged: "/Volumes/DATA1/": rescanned 0, updated 1, consolidated 0, ignored 0 Jul 18 16:41:31 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> Jul 18 16:41:31 %%SERVERNAME%% com.retrospect.retroisa[7334]: ISAVol::doIsaTreeChanged: "/Volumes/DATA1/": total time was 0 seconds (rescanning 0 seconds, updating 0 seconds, fixup 0 seconds) Jul 18 16:41:31 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> Jul 18 16:41:31 %%SERVERNAME%% com.retrospect.retroisa[7334]: - ISAVol::doIsaTreeChanged: finished update on volpath "/Volumes/DATA1/", 7/18/2013 4:41:31 PM Jul 18 16:46:30 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> Jul 18 16:46:30 %%SERVERNAME%% com.retrospect.retroisa[7334]: | ISAVol::doIsaTreeChanged: start update on volpath "/Volumes/DATA1/", 7/18/2013 4:46:30 PM Jul 18 16:46:30 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> Jul 18 16:46:30 %%SERVERNAME%% com.retrospect.retroisa[7334]: ISAVol::doIsaTreeChanged: starting pass five - update 1 folders for "/Volumes/DATA1/", 7/18/2013 4:46:30 PM Jul 18 16:46:31 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> ISAVol::doIsaTreeChanged: "/Volumes/DATA1/": rescanned 0, updated 1, consolidated 0, ignored 0 Jul 18 16:46:31 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> Jul 18 16:46:31 %%SERVERNAME%% com.retrospect.retroisa[7334]: ISAVol::doIsaTreeChanged: "/Volumes/DATA1/": total time was 0 seconds (rescanning 0 seconds, updating 0 seconds, fixup 0 seconds) Jul 18 16:46:31 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> - ISAVol::doIsaTreeChanged: finished update on volpath "/Volumes/DATA1/", 7/18/2013 4:46:31 PM Jul 18 16:48:27 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> Jul 18 16:48:27 %%SERVERNAME%% com.retrospect.retroisa[7334]: ISAVol::doIsaTreeChanged: starting pass five - update 13 folders for "/Volumes/Server HD/", 7/18/2013 4:48:27 PM Jul 18 16:48:31 %%SERVERNAME%% com.retrospect.retroisa[7334]: #2> ISAVol::doIsaTreeChangedThenSave: process more changed dirs before saving scan file and so on, every five minutes. I realized that those volumes are going to be constantly changing, not only because that server is twiddling some files constantly, but also because my Retrospect Engine is on one of them, and all my Catalogs are on the other, so ISA will be constantly busy trying to keep up with file changes that are going to be skipped by my rules anyway. So I excluded those volumes in the retro_isa.ini. Here are the questions I have: (1) Does the RetroISA process have to be running on the server at all, if all the volumes are excluded? When I start upgrading my clients to Retrospect 10, and presuming that I wish RetroISA to do its thing on some of them, is there communication between RetroISA on the backup server and on the backup client, or does each client's retroclient process use the local RetroISA data, if available, for expediting the building of the snapshot? (2) If I decide that RetroISA is not a good thing for my environment, am I going to have to log into each and every one of my backup clients and disable the RetroISA launchdaemon? If so, I think we need to put in a feature request to enable a "client-by-client" configuration of features like RetroISA, as well as the ones that we currently have a Global Preference for (e.g., "Allow Clients to Turn off Retrospect Client software" "Allow Clients to Back up on demand" ... etc.) (3) Is there any way to read retroISA_log.utx? We have instructions on how to change the log size in the Instant Scan Advanced Options document ... but no way to read the log? Thanks, _rob_
  4. Suggestion: It would make Instant Scan more palatable on a laptop if there was an option to pause it when running on battery.
×