Jump to content

ssevenup

Members
  • Content count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ssevenup

  • Rank
    Occasional Forum Poster
  1. 6.3.027 seems to talk to our Windows server from Leopard but Snow Leopard will only work if I turn the firewall off so far. retroclient produced a popup that added an entry in firewall:advanced but it was added blocked. Changing it to allow didn't help. 6.3.23 client DID work on my Snow Leopard laptop.
  2. I installed 6.3.027 and so far it seems our Windows server can only reach it if the firewall is off. I tried adding retroclient by hand but that didn't seem to work. I have tried Snow Leopard and Leopard but only futzed with he firewall on Snow so far.
  3. I'm assuming 6.3.027 supports Win Retro 7.x? If so, nice I'll have to get access to the clients Mac again to test the install. Thanks
  4. I ran the uninstaller first in every case but no I'm not sure that a Vise installer didn't bork something at some point. What to look for?
  5. I'm finding on 10.4.11 both the 6.2 and 6.3 client installers are setting the client owned by admin (501) and not root. Yet another reason I despise Vise installers. Get a clue and use the Apple installer which also means ARD deployment.
  6. I have never been able to get my Leopard client to successfully back up to our Windows Retrospect servers. Others in my group running Leopard on Intel Macs are backing up no problem. My Macbook has been wiped and reinstalled once with no change in behavior. It seems to be my data or sheer data volume? I was able to back up by moving blocks of data to reduce the total volume. I have about a 50GB home directory with about 15GB excluded with selectors. It dies claiming it was backing up "SSAuthorizedToolTemplate" which from what I can see does not exist, and there is no mention of it here on the forums, though it appears it might be related to Bookdog which I use. Today I installed the new client hopeful this would resolve itself. Server 7.5.508 with 7.5.14.102 update asks for the client password twice and fails to add it. Reading the Windows announcement I see we need the free 7.6 update. I can't wait to see what a nightmare that turns out to be (jaded much?). I am running 10.5.3 on an Intel Macbook. I'm about to install 10.5.4 along with any pending patches. I'm going to get the backup admin to install Bookdog to see if it kills his backup to.
  7. Quote: Does Retrospect 6.1 desktop work with Intel Based Macs? More importantly, does the client work, and when will it be a Universal binary?
  8. The more important question to me is when will the client be Intel blessed and when it will be a UB? I hope that happens MUCH sooner.
  9. Is there a way in Retro6.5.x to script an hourly "Duplicate"? The shortest interval I can find is daily and I want hourly for ReportsWatcher to my web server. --MM
  10. I had it on reasonably good authority that 6.5.336 fixed a problem where the library would fail to load the required tape for a Proactive backup to run. In my experience the problem remains. I have alternating week tape sets assigned to my Proactive backups. When I swap tapes on Monday morning, I must manually load the tapes for each Proactive script to continue running. Otherwise the status just reports waiting for media. I have one server with bar codes and one without. Both exhibit the same behavior. The library scans the media after the swap, but the required tape is never loaded after the scan completes. Win2k Adaptec 29160N SpectraLogic Treefrog AIT3 / Overland Data Loader Express DLT1
  11. ssevenup

    backup performance

    I have a trouble ticket with our network operations because of a massive glaring performance discrepency among our buildings. The network hardware is all similar and the routes in question are also, yet I get 2 to 5 times the performance if I relocate my server from it's normal location to another building. I can push packets at wire speed using a tool like iperf, but Retrospect server crawls in one subnet and flys in the other. The location of the client seems to have nothing to do with it. It has everyone totally baffled. I am seeing upwards of 500 - 600 MB/min in one subnet backing up some pretty mediocre hardware with 100base-T switched connections. It definitely looks like it's NOT a client issue. Retrospect (6.5.319) just seems to "favor" one subnet over the other. We have a mixture of Foundry and Cisco switches. I need some serious troubleshooting help from Dantz or I fear we will never figure this out. The network group has thrown up their hands because there seems to be no identifiable cause. I wonder if there is a "debug" version of the client or a "logger". Obviously we have looked for collisions, CRC errors and the like but found nothing. It's as if Retrospect throttles the connection on one subnet and not on the other. --MM
  12. ssevenup

    Poor performance

    This is a basic system load with not much user data yet. As such, it's a mixture of file types and sizes. The backup fluctuates around the 250MB/min number, where the OSX backup fluctuates around the 500-600MB/min number. I have no reason to suspect it's a file size or file type issue. I could try re-nicing, but I was more interested in what others are seeing without doing so. Then again I have a trouble ticket with our network operations because of a massive glaring performance discrepency among our buildings. The network hardware is all similar and the routes in question are also, yet I get 2 to 5 times the performance if I relocate my server from it's normal location to another building. I can push packets at wire speed using a tool like iperf, but Retrospect server crawls in one subnet and flys in the other. The location of the client seems to have nothing to do with it. It has everyone totally baffled. --MM
  13. Is anyone else noticing that the Linux client performance is Slooow? My MacOSX boxes will commonly run at 500+ MB/min. The best my Linux box can do is 250. The Macs are 100base-T connected. The Linux cluster and file server are gigabit connected and on the same gigabit switch as my Win2k Retrospect server. Is this a "nice" priority situation? --MM
×