Jump to content

retrospect backup problem - very slow with firewire


Recommended Posts

We have a MacOSX server with Retrospect 6. The Retrospect backupdrive is a firewire Lacie 300GB ( firewire port 1). In our previous situation the server had 2 ide drives 80 and 120GB internal. And backup was going smooth. In our new server configuration there re 2 Lacie's 300GB ( on firewire port2 ). There's about 60GB of data total on one of these drives That drive is partitioned in 2 parts and that is the only one that is backupped with retrospect. A full Backup now takes over 4 days.

( 10mb/min ) Is there an issue with retrospect and external drives?? Did some switching in the configuration between de drives but that doesnt seem to matter. There's just the server backup, there are no (network) clients that are backupped.

Link to comment
Share on other sites

> Is there an issue with retrospect and external drives?

 

No.

 

> We have a MacOSX server with Retrospect 6.

 

Please be more specific here. What model of Macintosh? How much RAM? What exact version of Retrospect? Which RDU?

 

- What Type of Backup Set are you using? (File Backup Set or Removable Backup Set)

Link to comment
Share on other sites

Quote:

The machine here is a

PowerMac 3.1 - CPU PowerPC G4 - 1 Ghz ( 2.1 )

Ram Memory about 400mb

OS: 10.4.8

 


Ok, that's your problem. You are thrashing on an underpowered machine. You need at least 1 GB of RAM to run Retrospect on that many files. OS 10.4.8 takes about 1/2 GB (you've got less than that) just for itself, and, on top of that, you are running Retrospect, which needs its buffers, catalog, etc.

 

You are paging yourself to death. Get more RAM.

 

It wouldn't hurt to have a faster computer, but that's not your most immediate problem

 

Russ

Link to comment
Share on other sites

Today i connected the second backupdisk for retrospect and this one seems to works just fine.

Backups at 500mb/min

Perhaps can it be that the backupset (rule) for the fisrt drive is broken (corrupted)?.

 

The idea of more Ram isn't bad - would increase the performance

Link to comment
Share on other sites

Quote:

Today i connected the second backupdisk for retrospect and this one seems to works just fine.

Backups at 500mb/min

 


Interesting. That's very helpful.

 

Quote:

Perhaps can it be that the backupset (rule) for the fisrt drive is broken (corrupted)?.

 


No. Can't imagine how that would cause your problem. You have a hardware issue with the drive. You might want to compare firmware versions, or perhaps there is something causing lots of disk retries, etc. It would be interesting to see your console log to see if there's anything there from the driver, or if Disk Utility reports bad SMART status (if that's available on your drive).

 

You also might try wiping the drive and putting down a new filesystem, etc.

 

It's still very hard for me to believe that you aren't thrashing (paging to death) running on that little RAM with Mac OS 10.4.8 and Retrospect. I think that it's a miracle that Retrospect is even able to run in that little memory. What does "/Applications/Utilities/Activity Monitor", "System Memory" report for pageouts and free while backup is occurring?

 

Russ

Link to comment
Share on other sites

  • 2 weeks later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...