LaunchBar starts reindexing a directory (folder) as soon as it sees a change there, e.g. a new folder/subfolder, a modified document, a deleted or newly installed application etc.
So if it constantly starts indexing when you are cloning your hard drive it is most likely, that it sees changes on the target volume (the volume you are cloning towards. Bring up LaunchBar's index and check the section 'Files and Folder' > 'Mounted Volumes'. If the target volume is checked, uncheck it and see, if the problem is solved.
Btw, I see no use in indexing a clone or a back up volume with LaunchBar as the original items are already located on the volume you are working with.
Also my advice is to not index whole volumes as it not only creates a big index, which makes not only the indexing process longer, it also evokes the indexing process more often. I'd never index a complete volume as I also would not index a complete home folder of a user. I rather index only selected folders and depending on the items you want to launch, you can also look in the options-tab for each item in LaunchBar's index, where you can define, if and how many subfolders LaunchBar should go and what kind of items it should scan in that folder.
For example, if you want to launch scripts that you have filed in ~/Documents/Scripts I would not index ~/Documents, I would index only scripts-folder.
Another example: I want to launch my desktop, but I don't want to have it index every single time that a new document is saved to it. So in LaunchBar's index > Files and Folders > 'Home ~' I have set the options to search only 1 level of subfolders and to search only for folders.
If it not helps, when you uncheck the target volume as described above, you check if LaunchBar indexes ~/Library/Caches on your boot volume, which could happen, when you have LaunchBar indexing your whole home folder. Caches change constantly and this would also make LaunchBar indexing almost constantly.
Hope this helps. I can definitely tell you, that LaunchBar doesn't start indexing when I'm cloning a volume here. It's no mystery, it's only the index and it's rules.
So if it constantly starts indexing when you are cloning your hard drive it is most likely, that it sees changes on the target volume (the volume you are cloning towards. Bring up LaunchBar's index and check the section 'Files and Folder' > 'Mounted Volumes'. If the target volume is checked, uncheck it and see, if the problem is solved.
Btw, I see no use in indexing a clone or a back up volume with LaunchBar as the original items are already located on the volume you are working with.
Also my advice is to not index whole volumes as it not only creates a big index, which makes not only the indexing process longer, it also evokes the indexing process more often. I'd never index a complete volume as I also would not index a complete home folder of a user. I rather index only selected folders and depending on the items you want to launch, you can also look in the options-tab for each item in LaunchBar's index, where you can define, if and how many subfolders LaunchBar should go and what kind of items it should scan in that folder.
For example, if you want to launch scripts that you have filed in ~/Documents/Scripts I would not index ~/Documents, I would index only scripts-folder.
Another example: I want to launch my desktop, but I don't want to have it index every single time that a new document is saved to it. So in LaunchBar's index > Files and Folders > 'Home ~' I have set the options to search only 1 level of subfolders and to search only for folders.
If it not helps, when you uncheck the target volume as described above, you check if LaunchBar indexes ~/Library/Caches on your boot volume, which could happen, when you have LaunchBar indexing your whole home folder. Caches change constantly and this would also make LaunchBar indexing almost constantly.
Hope this helps. I can definitely tell you, that LaunchBar doesn't start indexing when I'm cloning a volume here. It's no mystery, it's only the index and it's rules.