Question: I bought an Apple Time Machine. I have a home studio with several hard drives. I'm trying to find the best way to setup Time Machine to keep all my storage backed up all the time.

Studio Computer (12 Core Mac Pro)

* 250 GB - Internal SSD System Drive
* 2 TB - Internal Media Drive (Audio Samples, Sample Instrument Files)
* 2 TB - Internal Storage 1 (Recording Sessions)
* 2 TB - Internal Storage 2 (Recording Sessions)
* (Note: Internal Storage 1 & 2 are used until full and then they are stored away and new drives are purchased to replace them)

MacBook Pro (13″ i7)

* 250 GB - Internal SSD (OS X files and software only)
* 1 TB - Internal Media (Audio Samples, Instruments, User Folder, Etc.)

Questions:

* What kind of setup do I need to back all of this up?
* Do I need a big USB hub with a hard drive connected that mirrors every drive in my system?
* Do those drives need to be larger than each of the primary drives?
* Should I get a Drobo or some kind of RAID drive?

Answer: 
I found my extensions in:

```
/System/Library/PrivateFrameworks/ShareKit.framework/Versions/A/PlugIns

```

Delete FinderSyncTest.appex, restart Finder, and it should be gone.
I found my location via the `"Open Files and Ports"` location in Activity Monitor mentioned in the other answer.

This lead to the location:

`/Users/USER/Library/Developer/Xcode/Archives/2018-10-09/MyApp 10-9-18, 9.35 PM.xcarchive/Products/Applications/MyApp.app/Contents/PlugIns/MyAppFinderSync.appex/Contents/MacOS/MyAppFinderSync`

This archive was 10 days old and I'm not sure why it would have been running. I've been deleting my app since that date, and I believe the extension was being removed from System Preferences.

I deleted the archives in that location, and the app extension no longer runs (which it was doing before). However, it's still listed in System Preferences. Still looking for a way to fully delete.

Edit: I started running a new version of the container app, from `/Applications/`. About 10 minutes later, I went back to System Preferences and toggled the Extension on/off and back to on. This launched the new version of the Extension and everything appears to now be working normally.