

ComputerX
Members-
Content count
102 -
Joined
-
Last visited
Community Reputation
0 NeutralAbout ComputerX
-
Rank
Frequent Poster
-
I have a storage set where Retrospect believes that there is only 8K space on one of the members, but the member properties shows 192G free. See attached screenshot. I have rebuilt the catalog, but that did not help. What now? TIA, Dan
-
The Matching phase of a backup set transfer.
-
Here is one backup in the Scanning phase, while another is in the Copy phase.
-
Here is a backup in the Preparing phase (and sucking CPU) while another backup is in the Copy phase.
-
Here is that same slow client still running, but with a second Copy as well.
-
Here is a network Copy of a very slow client. This shows how the bottleneck is sometimes at the client end.
-
And here we have three network backups in the Copy stage.
-
Here we have two network backups in the copy phase.
-
Here we have a network backup in the Copy phase.
-
Yet another time rebuilding a catalog. I really do a lot of this.
-
Rebuilding the catalog for drives on the eSATA bus. I only showed total disk queue, dagnabbit. (rebuild catalog, groom, assert error. rebuild catalog, groom, assert error. wash, rinse, repeat.)
-
Rebuilding the catalog for a disk set with SATA drives connected to the motherboard. Perfmon is showing the disk queue for the drive with the data hovering around 1 while the C: drive (also holding the catalog) spikes occasionally.
-
Opening the catalog of a disk set for the first time. This was part of moving to the new hardware. This Config75.dat had never seen the catalog. Again, nicely distributed across the cores.
-
Forgetting a backup set. Just a little CPU spike, but nicely distributed across cores.
-
Here is a local backup to a disk set. The destination is an internal SATA drive. I don't reacll how the source was connected. I know it was a PATA drive, but I don't remember if it was on the motherboard or through a USB bridge. This is one of the first sets of screenshots I took. Before I started overlapping windows and using the expanded perfmon. One screenshot of the Task Manager and one of the default perfmon showing total disk queue. Again we seem to be disk bound.