Mostly it's backing up an IDE drive via USB2.

I see a lot of 500+ megs per minute on the progress dialog...then I'll see
something like 188....then I'll go away for awhile, come back, and it's down
 to
14 megs/minute.

Stop the execution without closing Retrospect, re-start the same script, and
it's back up to 500+....then, as I write this, I see it falling to 250, whoo
ps
170....Uh-oh, now it's down to 27.6 megs/minute.

Just opened TaskManager, and I see memory usage is up to 355 megs...but I ha
ve
500 physical available...

Now it's down to 12.9 megs per minute...500+ down to 12.9,  all in the space
 of
about 15 min.   Whoops, now it's back up to 236...247... climbing again.

Anybody know what gives?
--
PeteCresswell

[ Post a follow-up to this message ]

This issue gets raised often in the Dantz forums.
Obviously, Retrospect has performance issues, which the Dantz folkes deny.

Go to the forums at www.dantz.com, there are a number of such discussions.

--
http://www.standards.com/; See Howard Kaikow's web site.
"(Pete Cresswell)" <x@y.z> wrote in message
 news:f62hm0935cbu2tg1easug9fl5tk31s911j@
4ax.com...
> Mostly it's backing up an IDE drive via USB2.
>
> I see a lot of 500+ megs per minute on the progress dialog...then I'll see
> something like 188....then I'll go away for awhile, come back, and it's
down to
> 14 megs/minute.
>
> Stop the execution without closing Retrospect, re-start the same script,
and
> it's back up to 500+....then, as I write this, I see it falling to 250,
whoops
> 170....Uh-oh, now it's down to 27.6 megs/minute.
>
>   Just opened TaskManager, and I see memory usage is up to 355 megs...but
I have
> 500 physical available...
>
> Now it's down to 12.9 megs per minute...500+ down to 12.9,  all in the
space of
> about 15 min.   Whoops, now it's back up to 236...247... climbing again.
>
> Anybody know what gives?
> --
> PeteCresswell

[ Post a follow-up to this message ]

RE/
>Go to the forums at www.dantz.com, there are a number of such discussions.

Been there many moons ago, vowed not to waste any more of my time -)
--
PeteCresswell

[ Post a follow-up to this message ]

Hi, I just came across this forum when searching for info on Retrospect and 
slow performance. I am having exactly these issues. I'm running Mac OSX and 
have been wanting to update to version 6.

Well, with version 5 I've had these performance scenario where it really jum
ps around from most excellent 600/MB down to 5/MB. Usually towards the end o
f a tape on both the backup and verify passes.

Now where the real performance hit comes is in version 6.0x. Retrospect is p
ainfully slow just moving around the app to create a new storage set, add a 
volume to backup, locate a storage set to retrieve files. Sometimes 2-3 minu
tes per move. This doesn't in version 5.0.238. This version flies through al
l the options. I think I will go back to using it if no one has any ideas wh
y there is such a problem. Dantz support sure don't know.

When looking at Retrospect in the processor acttivity monitor, it's frequent
ly taking 120% to 350% of available process cycles, more than maxing out the
 system. This is retrospect, not a 3d rendering application. I'm simply back
ing up local UltraSCSI volumes. What gives? I know Pete the original poster 
here is backing up IDE volumes.

I'm ranting here. I am going to continue reading here in hopes of learning s
omething I don't know, or do know and learn more about this. If anyone knows
 of a theory and how to make things better, I'm all eyes and ears.

Thanks in advance, rob!

=====

quote:
Originally posted by (Pete Cresswell) 
Mostly it's backing up an IDE drive via USB2.

I see a lot of 500+ megs per minute on the progress dialog...then I'll see
something like 188....then I'll go away for awhile, come back, and it's down
 to
14 megs/minute.

Stop the execution without closing Retrospect, re-start the same script, and
it's back up to 500+....then, as I write this, I see it falling to 250, whoo
ps
170....Uh-oh, now it's down to 27.6 megs/minute.

Just opened TaskManager, and I see memory usage is up to 355 megs...but I ha
ve
500 physical available...

Now it's down to 12.9 megs per minute...500+ down to 12.9,  all in the space
 of
about 15 min.   Whoops, now it's back up to 236...247... climbing again.

Anybody know what gives?
--
PeteCresswell 

[ Post a follow-up to this message ]