I'm not sure whether this is software or hardware related so I'm starting here:
From a MD Mac G4, running OS 9.2 and Retrospect 5.1
Connected to it are 2 500Gb Firewire G-Drive HDs. One contains work, the other one is completely empty. The idea is for Retrospect to mirror the main drive in order for them both to contain exactly the same data.
I set Retrospect to duplicate drive 1 (containing approx 260Gb) to dive 2 (empty). When I got in this morning, Retrospect reported that the backup was incomplete, with 7Gb yet to be copied. Strange, such as a straight duplication would see ~ 240Gb spare once finished.
Upon closer inspection, I saw that the sizes of the various folders on drive 2 were much larger than on drive 1. Looking at actual files, in one folder on drive 1, images that averaged out at about 1.5Mb each, were over 20Mb on drive 2. This has happened to pretty much every file on the disk.
Is there a reason for this? Both drives were initially formated in the same way at the same time, and both are connected to the Mac directly as opposed to being daisy-chained.
It was not a scheduled operation - I started it manually.
From a MD Mac G4, running OS 9.2 and Retrospect 5.1
Connected to it are 2 500Gb Firewire G-Drive HDs. One contains work, the other one is completely empty. The idea is for Retrospect to mirror the main drive in order for them both to contain exactly the same data.
I set Retrospect to duplicate drive 1 (containing approx 260Gb) to dive 2 (empty). When I got in this morning, Retrospect reported that the backup was incomplete, with 7Gb yet to be copied. Strange, such as a straight duplication would see ~ 240Gb spare once finished.
Upon closer inspection, I saw that the sizes of the various folders on drive 2 were much larger than on drive 1. Looking at actual files, in one folder on drive 1, images that averaged out at about 1.5Mb each, were over 20Mb on drive 2. This has happened to pretty much every file on the disk.
Is there a reason for this? Both drives were initially formated in the same way at the same time, and both are connected to the Mac directly as opposed to being daisy-chained.
It was not a scheduled operation - I started it manually.