Archived - OS X Server: "Custom" service data location after migration or upgrade
After upgrading to OS X Server (Mountain Lion) from Mac OS X Server v10.6 or Lion Server, Server app may report a Service Data location of "Custom" when viewing the server Settings pane.
When trying to edit the service data location, you may receive an alert that "Existing service data is present" on the selected volume. In this case you'll need to relocate the service data to a temporary location, remove the original data, and relocate the data to the desired data location.
- Choose another volume or partition—that does not currently have any service data installed—as the "temporary" Service Data location using Server app.
- After the service data has been moved to the temporary location, you should remove any copies of the data from the desired data location volume.
- Use Server app to select the "desired" volume or partition as the service data location.
When performing the OS X Server promotion in OS X (Mountain Lion), the Server application creates a default service data directory structure in /Library/Server, while simultaneously preserving any established service data locations that were migrated from the previous installation. This creates the "Custom" service data location, because OS X Server (Mountain Lion) stores all service data on a single volume by default.
For example, you have migrated a server to OS X Server (Mountain Lion) by installing it on a new volume named "Mountain Lion". Your previous Lion Server installation stored service data on a volume called "Data." After completing migration, Server app in OS X Mountain Lion reports the Service Data location is "Custom." When editing that setting, you select the "Data" volume, and receive the "Existing service data is present" dialog. You do not want to remove the existing data, because it is in use, but you cannot move the default data from the "Mountain Lion" volume to the "Data" volume as long as the existing data is present.