Reply to thread

Message

<blockquote data-quote="MacInWin" data-source="post: 1861624" data-attributes="member: 396914">That cannot be. They both show the TM interface screen with multiple backups showing behind the one in front. So what you are really seeing is the TM contents from two different TM backups. Ordinary Finder doesn't have the &quot;stack&quot; of folders behind it like that. In any event, to your first question, yes, starting a new backup on a new drive should have triggered a full backup to that drive as the initial one. A 500 GB database will take a VERY long time to transfer, due to the compression. Yes, I know jpgs don't compress, but the system will still squeeze out all the space it can, including the unused space within a block at the end of a file. It's very aggressive in doing that. What you end up with on the target network drive is either a sparsebundle or a backupbundle file that has been stored in such a way that there is no waste space. TM does not do that for a direct-attached drive as it is not needed, but for network storage, it does that compression to get the network traffic to an absolute minimum.</blockquote>

[QUOTE="MacInWin, post: 1861624, member: 396914"] That cannot be. They both show the TM interface screen with multiple backups showing behind the one in front. So what you are really seeing is the TM contents from two different TM backups. Ordinary Finder doesn't have the "stack" of folders behind it like that. In any event, to your first question, yes, starting a new backup on a new drive should have triggered a full backup to that drive as the initial one. A 500 GB database will take a VERY long time to transfer, due to the compression. Yes, I know jpgs don't compress, but the system will still squeeze out all the space it can, including the unused space within a block at the end of a file. It's very aggressive in doing that. What you end up with on the target network drive is either a sparsebundle or a backupbundle file that has been stored in such a way that there is no waste space. TM does not do that for a direct-attached drive as it is not needed, but for network storage, it does that compression to get the network traffic to an absolute minimum. [/QUOTE]

Verification

Name this item 🌈