Jump to content

nulldev

Members
  • Content count

    23
  • Joined

  • Last visited

Community Reputation

0 Neutral

About nulldev

  • Rank
    Occasional Forum Poster
  1. I'm backing up an Exchange server from a dedicated backup server. The backup speeds are under 200 MB/s over gigabit ethernet. Those speeds seem really slow and I'm trying to figure out if that is typical for Retrospect with regards to Exchange backup or is there another problem? Retrospect 7.6.123 Multi-server Retrospect client on Exchange server - 7.6.107 Exchange Server 2007 running on Windows 2003 server 64-bit
  2. I tried this and it immediately closes. 10.5.3 didn't make any difference either.
  3. I have to disagree when it relates to the Retrospect Event Handler script. I've tested the following on 2 different x86 macs. One running 10.5.2 server and the other 10.5.2. - Launch a fresh copy of the Retrospect Event Handler unopened by Script Editor. It launches and stays running. - Open Retrospect Event Handler in Script Editor running native x86. Save and close the file. Launch the script and it immediately closes. - Now open the Retrospect Event Handler you just tried in Script Editor, this time in rosetta mode. Save and close the file. Launch the script and it immediately closes. - Open a fresh copy of the Retrospect Event Handler in Script Editor running through rosetta. Save and close the file. Launch the script and it stays running. I don't encounter any of these problems on a 10.5.2 PPC server.
  4. If you read the first post of this thread, you would know the problem that this solves. I have no idea why running the Script Editor in rosetta fixes the problem but it does. You can also edit the Retrospect Event Handler on a PPC mac and then copy to a Intel mac. For whatever reason, if your using Script Editor as an universal application to edit the Retrospect Event Handler. You get the symptoms discussed in the first post of this thread.
  5. To solve the problem, run the Script Editor in rosetta when you edit the Retrospect Event Handler.
  6. I've notice that Retrospect will periodically say "Please wait" while it's running a back up to a fast back up device. Does anybody know what causes this? I've attached a screenshot with the message.
  7. There is free space on the backup set.
  8. - Do the other configurations use the same hardware? The eSATA card is different and different server hardware. - Is the dialog box being presented at the same point in the process each time? Not sure, there is no data in the Retrospect logs when it happens. - What are your settings for Media Request and Media Erasure? Media Request & Media Erasure has the default options which is nothing is checked.
  9. Sorry for not being more specific. The hard drives are being handled as removable disks. There are multiple drives per backup set. I have used this same configuration in other situations without issues. It's this one server that keeps having problems.
  10. The operations log doesn't show anything. Configuration of the computer: Xserve - 2 x 2.66 GHz Dual-Core Intel Xeon with 5 GB of RAM Backing up to a Sonnet 500p enclosure using 750GB SATA drives. Retrospect version 6.1.138. Retrospect script that runs backs up itself and multiple clients nightly. When I get the blank dialog box, I have to force quit Retrospect. After that, Retrospect runs fine for a while. Haven't been able to find a pattern. Hopefully this is enough information.
  11. Does nobody have any advice to this problem?
  12. Using Retrospect 6.1.138 on an Intel Xserve running 10.4.11. Retrospect stops every few weeks with a blank dialog box with a stop sign. Does anybody know what causes this?
  13. Quote: Quote: I'm trying to figure out why it's crashing and also UserNotificationCenter crashed. Eric As an update to the issue I'm having. I've moved the hard drives to an identical Xserve to rule out if it is a hardware problem. Will keep you updated on what I find. Eric
  14. Quote: Does that concern you? Even on my OS X 10.4.8 (not-server), killing syslogd will result in the process coming instantly back alive. To have syslogd not running on OS X 10.4 IntelServer sounds like an indication of some system-wide problem. That does concern me. I'm trying to figure out why it's crashing and also UserNotificationCenter crashed. Eric
  15. The RetroRunSL crash log that I get is similar but it is dated from about a week ago. Syslogd has crashed which I'm assuming is why I don't have any current logs.
×