How I migrated my caldav data (Contacts and Calendars) to Mavericks + Server

Question

Hello,
I write this post to share with you the steps I had to take for correctly migrating my caldav database (containing data for Addressbook and Calendar Server) from a Lion Server to Mavericks with Server version 3.
The problem occured like this : after downloading and installing mavericks (from the Apple Store), and downloading/installing the Server Utility (version 3), everything migrated just fine, except I had an error message during the first launch of the Server utility, but since it eventually launched, and the services were running, I didn't notice anything at first.
But I rapidly saw a big problem : my caldav data was missing. If a client connected to their calendar application, they would get (after syncing with the server) a new empty calendar named "calendar" (this is typical of a fresh empty caldav database). Same for addressbook clients (empty contacts).
So I searched and read several post that helped me greatly :
https://discussions.apple.com/thread/3890595
https://discussions.apple.com/message/23581552
BUT, what is different in mavericks, is this :
The postgres cluster that hosts the caldav data seems to have move (again!), and this is by exploring several config files that I figured which was the right socket to use to connect to the good postgres cluster.
The clues were in the file : /Applications/Server.app/Contents/ServerRoot/private/etc/caldavd/caldavd-apple.p list
Where I found the precious parameter (under the Postgres section) :
<key>SocketDirectory</key>
       <string>/var/run/caldavd/PostgresSocket</string>
What I also figured is that the user account to use for connecting to this postgres cluster is caldav, and not _postgres.
So here are basically the steps I had to take  to reinstall my old database.
Step #0 :
First, you need to locate the dump of the old postgres database, I found that the migration process seemed to make a dump inside :
This method ONLY WORKS if you have the following file :
/Library/Server/Migrated/Library/Server/PostgreSQL/Backup/dumpall.psql.gz
If you have that file, you can extract it with the command :
  gunzip /Library/Server/Migrated/Library/Server/PostgreSQL/Backup/dumpall.psql.gz
For the rest of the steps I assume this file is named  /path/to/your/dump.psql
I think (but I'm not sure of it) that THIS precise dump is different than what you would get inside a manual dump, meaning that in this dump you have all the  databases of the cluster. Again I'm not sure, but that's what I think since there are CREATE DATABASE instructions inside it).
If you don't have that file, perhaps you made a dump by hand.
If that's the case, I think that before Step #3 you will have to create an empty caldav database, BUT, I'm not sure the command "calendarserver_bootstrap_database -v" mentionned here will create the caldav in the right cluster (read above). Perhaps we could figured out together if that's your case.
Step #1 : stop the services
sudo serveradmin stop addressbook
sudo serveradmin stop calendar
Step #2 : drop the caldav database
sudo dropdb -h /var/run/caldavd/PostgresSocket -U caldav caldav
If you get this error message :
dropdb: database removal failed: ERROR:  database "caldav" is being accessed by other users
DETAIL:  There is 1 other session using the database.
then go to Step #2a, otherwise, go straight to Step #3
Step #2a : only if Step 2 didn't work, see above ! (taken from here)
# Connect to the postgres database
psql -h /var/run/caldavd/PostgresSocket -U caldav
# Terminate the current sessions
postgres=> select pg_terminate_backend(procpid) from pg_stat_activity where datname='caldav';
# Exit postgres
               postgres=> \q
Step #3 : if your database dump is not from /Library/Server/Migrated/Library/Server/PostgreSQL/Backup/dumpall.psql.gz, then PERHAPS you will have to create manually an empty caldav database (see Step #0)
Step #4 : create the new database from the dump
sudo psql -h /var/run/caldavd/PostgresSocket -U caldav -f </path/to/your/dump.psql> caldav
A lot of things should be displayed, and I eventually got an error at the end :
psql:DataDump.sql:49844: \connect: FATAL:  database "collab" does not exist
But in my case that didn't affect my migration.
Step #5 : restart services
sudo serveradmin start calendar
sudo serveradmin start addressbook
I hope that helps you.
Cheers

Answer 1

iCloud adds a new (additional) Address book to Outlook, it contains the iCloud contacts, if the iCloud contacts and the Outlook contacts are the same there will be duplicates:
Look in one Contact Folder only
Delete the Outlook Contacts (you can't delete the whole folder, only the contents
These are your choices.