Jump to content

ferthalangur

Members
  • Content count

    63
  • Joined

  • Last visited

  • Days Won

    4

ferthalangur last won the day on June 16 2017

ferthalangur had the most liked content!

Community Reputation

7 Neutral

About ferthalangur

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  • Location
    Washington, D.C.
  • Interests
    Not spending large gobs of time babysitting backup software! :)
  1. 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_
  2. ferthalangur

    Happy with 10.2.0 (201) upgrade

    I upgraded last night from 9.0.2(107) to 10.2.0(201), although I had some trouble figuring out how to do it. I even read the User Guide, which left me scratching my head on step #2: Double-click Install Retrospect Engine -- an icon which was not provided in the installation package. The process is a little counter-intuitive, and the documentation could have been more explicit about the fact that you first upgrade the Administrative Console, either on the server or on your admin machine, and then point the new console at a running server and it will prompt you to upgrade. I felt a little dense when I finally figured it out after reading this forum post. Here is what I did: Stop the running 9.0.2 Engine on the backup server. Backed up (using tar) /Library/Application\ Support/Retrospect and all my Catalogs and all the 9.0.2 software [just in case I had to back out the upgrade]. Downloaded Retrospect-1020201.dmg to the server (I have the Admin Console installed there pointed at localhost). Double-clicked the .dmg file to mount the image. Dragged the Retrospect folder into Applications. Double-clicked Retrospect.app to open the Administrative Console. Nothing interesting happens . . . because I had stopped the Engine. Restarted the 9.0.2 Engine. The 10.2.0 Admin Console then started up and gave me the message Please update Retrospect server '$servername'. Retrospect 10.2.0.201 is available -- you have 10.0.0.201. [Cancel] [update] ... I clicked [update]. Now the Engine software gets updated, including the LaunchDaemon plists and the binaries in /Library/Application\ Support/Retrospect/*.bundle ... I am prompted for a new license code for 10, which fortunately, I had already obtained. The new Console now starts talking to my new Engine and all my stuff begins to appear. So far everything is working well. Performance seems to be better than it was in 9.x, or at least the Console tells me what it is doing as it syncs with the Engine, so I don't stare at a blank Console for ten minutes wondering whether it's going to load or hang in SPODville. My Proactives are running. My nightly backups ran. Tags display is still broken. I'm on an XServe running OS X Server 10.6.8. _rob_
  3. Thanks Maser. That is very helpful.
  4. It would be fantastic if someone at Retrospect, Inc. took a few hours to write a good Knowledge Base article on what Retrospect stores and how grooming is supposed to work, functionally. I don't think we need enough information to be able to reverse-engineer the Retrospect software. However, it would be useful to have some detail about what is supposed to happen when Retro. grooms a Media Set to X backups. What happens when I delete a Past Backup and then groom the Media Set? What happens when I delete a source and then groom the Media Set?
  5. Just my .02, but I believe that Robin should create a new forum for "Retrospect 10 for Macintosh" instead of changing the name of this forum to "or higher." As time goes on, there will be a subset of the user community who will have gone to Retro 10 and some who will stay on Retro 9, and having a separate forum for Retro 10 will reduce confusion.
  6. ferthalangur

    Retro 10 is out!

    Thanks Robin. Support responded very quickly with a new License Code and download link for Retro 10.
  7. ferthalangur

    Retro 10 is out!

    Do paid ASM customers get a free upgrade?
  8. I have an iomega storCenter px4-300r NAS volume mounted on my Retrospect Server as a Source. It is mounted correctly, using Retrospect's Admin interface. It is mounted using AFP ... not SMB. I have Retrospect 9.0.2 (107) on OS X 10.6.8 on an Xserve. I run an hourly Retrospect Script to back up this Source. It works just fine, unless there is a file in the volume that is open in Microsoft Office 2011 on another workstation. In that case, I get a 1017 "Insufficient Permissions" error for those files: - 7/17/12 1:03:15 PM: Copying CHS_IT *File "/Volumes/CHS_IT/software_licenses/general_licenses.xls": can't read, error -1017 ( insufficient permissions) 7/17/12 1:03:39 PM: Snapshot stored, 573 KB 7/17/12 1:04:13 PM: 1 execution errors Remaining: 1 files, 30 KB Completed: 0 files, 0 B, with 0% compression Performance: 0 MB/minute Duration: 00:00:58 (00:00:28 idle/loading/preparing) I do not have the "Open Files Backup for Windows Clients" option purchased because we don't need it. We have a negligible number of Windows clients in our shop. Am I getting this error because Office files, created by a Mac, open on a Mac, are being treated by Retrospect as "open files" on a Windows Client? Is this a bug, or am I misunderstanding what the "Open Files ..." option is for? Has anyone else seen this ... does it go away if the "Open Files ..." option is installed? Thanks, _rob_
  9. I've had a similar problem with a user who teleworks most of the time and only comes to the office occasionally. Retrospect seemed to miss backing up her laptop a lot, and she would get the "Retrospect hasn't backed up your machine since ..." message and she would call me and ask me to manually back it up. My solution was to create 2 backup scripts for her machine, one for each Media Set that I use for Proactive backups of user workstations. When she is here and asks for a forced backup, I just run the appropriate script. If the Proactive script is backing up another machine it will have the Media Set locked, and my script will be waiting in the queue for Proactive to finish and then it will run right away.
  10. ferthalangur

    Looking for users' opinions of Retrospect 9

    Retro. 9 does not crash with the frequency (every other week or so) that Retro 8 did. I'm happy about that. Retrospect support seems to be more responsive to fixing bugs than they were in Retro 8, based on the fact that we got 9.01 and 9.02 in relatively short order. It's not perfect by any stretch of the imagination, but it is definitely much better than 8.
  11. ferthalangur

    Multiple Members from Same NAS to Same Disk Set

    I reported this to Retrospect Support and they said that they could not reproduce the problem with their NAS. However, they did not have have either a Buffalo or an Iomega to test it with. They didn't mention what flavor of NAS their test system was. They will forward it to QA to try to reproduce. I tried to reproduce the problem using another OSX server as the source of the shares, and I found interestingly that if the shares were from the same volume on the source OSX server, Retrospect would fail to add the second Member, with the same message. If the shares were from different volumes on the source OSX server, Retrospect would be happy to use them for a multi-Member Media Set. I wanted to ask if there are other Retrospect 9.0.1 users who are backing up to NAS shares who would be willing to test this with their systems so that I can compile a list. I don't want this Support Request to go into the COD (Customer on Drugs) Queue. I can provide very specific instructions to reproduce the problem.
  12. Out of curiosity, Brian ... what version of the OSX are you running your server and admin console on? I have 10.6.8 server and 10.7.3 for the admin console and I have not seen this problem, fortunately.
  13. Are you clicking on the Share icon at the top of the sheet that opens after you click on the Add icon? The default when the sheet opens is Clients which will give you the wrong dialog for attaching a NAS. You would then get a sheet that asks for a Share address and options of how to authenticate to the remote server.
  14. Try deleting the following in Terminal: rm /Library/LaunchAgents/com.retrospect.clientapp.plist rm /Library/LaunchDaemons/com.retrospect.* rm -r /Library/PreferencePanes/Retrospect\ Client.prefPane rm /Library/Preferences/retroclient.state rm -r /Library/Receipts/retroclient.pkg If you want to be pedantic, you can also: rm /var/log/retroclient.history /var/log/retroclient.log /var/log/retropds.log But I would be shocked and awed if the install script careed about those files.
  15. ferthalangur

    Retrospect is Remounting NAS Sources -- Why?

    On a related question ... why doesn't Retrospect unmount a mount point in either SMB or AFS that it has created when I "forget" it in Sources? I would expect Retrospect to undo with "-" what Retrospect has done with "+" ... all other things being equal.
×