Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Time Machine and then Spotlight woes.

Hello All,


After many many years of use, the (local) backup volume for one of my

iMacs, which contains only my Time Machine backups only for that iMac,

is nearly full. Using Finder, I dragged Backups.backupdb to a new,

empty volume with double the capacity of the original backup volume on

a brand new disk which I had already formatted appropriately and

"Enabled Owners" on. The copy took a very very long time, but the

copy appears to have finished without incident.


I'd like to start backing up to the new backup volume as soon as

possible, and I'd like to never again do a backup to the old backup

volume. I'd like to avoid having to copy Backups.backupdb again,

because it takes so long.


First, some observations:


(1) The amount of space used on the new volume is 13.48 GB smaller

than the amount of space used on the original volume. This is

surprising, as one would imagine that a "copy" would have the same

size as the original.


(2) Spotlight went ahead and indexed the new volume during or perhaps

after the copy. Spotlight indices exist on both on the old volume and

the new volume. The Spotlight indices also differ in size, but not by

enough to explain the discrepancy in space used on the volumes. The

contents of the indices appear to be different.


(3) The Spotlight index on the new volume allows Spotlight to find

files which cannot be found on the old volume or on the iMac being

backed up. I discovered this accidently just by using Spotlight. I'd

therefore like to preserve the index as I assume that it would take a

long time to recreate. I found many many critical files which I would

like to be able to find again!


Before I feel comfortable using the new backup volume, I have

questions which need answering, mainly these:


(A) Is the space discrepancy mentioned in (1) to be expected?


(B) What is the explanation for (2) and (3)?


I would be grateful if someone could shed some light on what is going

on here!



iMac

Posted on Jan 18, 2023 12:49 PM

Reply

Similar questions

12 replies

Jan 18, 2023 3:17 PM in response to skbesler

A. Possibly TM had some things marked for removal since it was getting full.


B. I'd not index the TM drive at all, it's needless & wearing everything out sooner.


After putting the TM drive in Spotlight's Privacy Pane...


Open Terminal and run each of these one at a time


/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user


sudo /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -seed -lint -r -f -v -dump -domain local -domain system -domain user -domain network


killall Dock


sudo mdutil -E /


sudo mdutil -i on /


Rebuilding a drive index can take a long time, so be prepared to wait whether you do it through the System Preference panel or the command line.

Jan 19, 2023 11:43 AM in response to BDAqua

A. implies that I should not be concerned about the space usage

difference between the old backup volume and the new backup volume.

Thank you for that: it gets me most of the way to where I want to go.


B. and following give me some off-topic, unsolicited advice and

directions on how to destroy some of the very information that I am

trying to preserve (namely, the Spotlight index on the new backup

volume).


B. and following then tell me to run three commands that appear to be

completely unrelated to the matter at hand. If they are related,

please explain how.


B. and following then tell me to run some commands that will destroy

the Spotlight index on my boot volume (and then recreate it.) There

is no evidence that the Spotlight index on the the boot drive needs to

be recreated. The reason that the Spotlight index doesn't result in

finding the critical files on the boot drive is that those files do

NOT exist on the boot drive, they only exist in Time Machine. FYI, it

looks like this is because an (Apple-supplied!) application, at some

point, converted ALL its files from an old format to a new format

(without asking) and deleted the files in the old format (also without

asking). The old format works way better with QuickLook and Finder

and Spotlight, so I'd like to be able to access the files in the old

format.


I know that rebuilding a drive index will likely take a long time,

it's why I wrote "I'd therefore like to preserve the index as I assume

that it would take a long time to recreate".


I guess that what is going on with Spotlight on the old backup volume is:


(i) the index needs to be rebuilt: once it is rebuilt, it will find

the same results as on the new backup volume.


and/or


(ii) Spotlight and Time Machine sometimes interact in unexpected ways.

These interactions don't usually matter to the function of either of

these systems and it's possible that they were not designed to be used

together.



Jan 21, 2023 5:13 PM in response to BDAqua

We all have our own crosses to bear and our own thorns in our sides.


It is you who is the respected and highly rated member of this

community. In this community, you are the helper and I am the beggar.


Beggars usually cannot be choosers: I accept whatever help I can get.


I wrote above that the information that you provided is useful and

welcome. Thank you. I usually try to stick to the facts. I'm sorry

if my arrangement of the stated facts was insulting or out of line,

that was not my intention.


Thank you in advance for any further information that would shed light

on the topic of my post.


Thank you as well for your past answers that have helped to build

this community.


Time Machine and then Spotlight woes.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.