Migrating Wiki Calendars from Lion from Lion

This was an information article, since I spent a few hours on this one and there was no documentation and may help someone one day!
Description: This article was a guide on how to move a Wiki Calendar form a Lion server to another Lion Server.
Problem: Wiki Calendar Service wasn't running properly, and the service was stopped / restarted and never came back on. There was a few errors on our XServ regurading this, but since there was no phone support, I created a work around by migrating the data to another mini, to get calendars back up and running. This may come in handy for someone to migrate servers.
Another problem that came into factor here was also we upgraded from Snow Leapord, so instead of all of your files being in 1 place like they would be on a lion machine they were in multiple directories, which made the process more difficult.
Process: A few steps will have to be done in order for this to work. As our configuration was binded to AD, in a multi domain forest. Also remember the wiki calendars are inbended into the wiki, so not only moving the calendar files are enough to get it working on a different machine.
1) Bind to AD and get your 2nd machine up and running
2) Migrate the Wiki Calendars over using the KB article on apples forumn. http://support.apple.com/kb/HT5082
3) Copy the config files for the Calendar - I included the default folders for this below.
/Library/Server/Calendar and Contacts/Data ---> /Library/Server/Calendar and Contacts/Data on the new server
**note**
If you came from a snow leapord machine you will have a folder called migrated-data / .calendarserver_version files stored in a different place, once found it will have to be copied to /Library/Server/Calendar and Contacts/Documents
Both of these files need to be in this folder on the new server if your using the apple defaults ---> /Library/Server/Calendar and Contacts/Documents
I also had renamed my calendars-migrated to calendars-migrated-old after they were moved to the proper location.
The folder calendars-migrated will also have to be copied over via a USB drive since hidden attributes are embedded and any sort of network sync drops these files. (rsync / sftp) If you navigate into the calendars-migrated data, you will see filse like this with permissions drwxr-x---@ and you need to retain the @ if you have multiple calendars in 1 wiki.
Once the folder calendars-migrated is moved to the new location in /Library/Server/Calendar and Contacts/Documents/ you will have to use a chown to change the ownership of the permissions for the calendars-migrated folder
# sudo chown -R root:_calendar calendars-migrated
4) Next we will have to export the database for caldav
Stop the calendar / address book services
# sudo serveradmin stop calendar
# sudo serveradmin stop addressbook
Export the Database to the /tmp folder (file will be called caldav.pgdump)
# sudo pg_dump --format=c --compress=9 --blobs --username=caldav --file=/tmp/caldav.pgdump caldav
Move the file /tmp/caldav.pgdump from the old server to the new server on /tmp/caldav.pgdump.
One the new machine wipe the database so you can import it with the correct version (form moving the .calendarversion file over)
# sudo dropdb -U _postgres -i caldav
Create a new database on the new machine
# sudo createdb -U caldav caldav
Import that database to Collab so it can be used in the wiki
# sudo -u _postgres pg_restore -d caldav -U collab --single-transaction /tmp/caldav.pgdump

Hi,
I'll just say my try of wiki migration from SLS(MacPro) to LS(MacMini with Internal Disk1&2).
1)Fisrt I made a bootable backup of SLS to Disk2 of MacMini.
2)Second I booted from Desk2.  MacMini was  running as SLS.  After that, I installed Lion and LS from App Store.
    Wiki migration was successful. So Disk1 is an original LS and Disk2 is LS with wiki migration.
Good luck!
Tac

Similar Messages

  • Problems Migrating Wiki Calendars

    We upgraded a 10.6.8 server with several wikis to OS X Server 10.8.2. The wikis appear to have imported ok, except for the calendar information. When accessing the calendar page, an error is returned saying File Not Found.
    There are no obvious errors in the migration log. If I make a new wiki, the calendar works ok on that wiki so I'm pretty sure CalDAV Server is working ok. 
    I found the migrated data in a migration folder on the 10.8 server. I even found the wiki's .ics files tucked away in a subfolder. I could probably find a way to re-import those files if I could blow away whatever problem the migrated wikis have.
    I've deleted the wikis, re-imported them (http://support.apple.com/kb/HT5082) from the old Collaboration folder and they come back with the same problem. Documentation on this product is pretty light. Does anyone have any beta on the relationship between the wikis and their calendars? If the migration won't work, I'd be glad to just reset the calendars and work on a way to import the .ics files.

    Some further input. I have created a clone HDD to play with.
    On Snow Leopard, I have done unbind from Active directory, set up Open Directory as a local master, change permissions on all wikis to have everyone read and write permissions without login.
    then Reboot, checked that wiki is accessible without any password, then upgrade to Lion on that partition.
    Everything went fine, but I still get same result.
    There are no wikis in wikiserver.
    When I check the info in /Library/Collaboration/Groups/ all info is there, also it is in /Library/Server/Wiki/FileData
    But I still can't see anything when I launch wiki

  • Can I add more than one Wiki calendar to my web cal?

    Hi,
    I would like to add more than one Wiki-Cal to my Webcal (or CalDAV). Well I have two Wikis with calendars both are shown in my webcal (see photo)
    I have added the wiki calendar "Oberstufe" and from another wiki "Praktikum".
    In one Wiki I want to add a second calerndar "stundenplan". This works very fine (see photo)
    The problem is that I can't add this second calendar "Stundenplan" to my iCal calendars. The Link is added. When the mouse is over this link there is a hand. But pressing this link doesn`t work.
    Where is my mistake?
    I'm using OS Lion Server with an SSL-Connection and a selfsigned certificate.

    Hi,
    See my post here:
    https://discussions.apple.com/message/15253863#15253863
    Best wishes
    John M

  • Migrating wiki from Leopard Server (10.5) to Lion Server

    Is there any way to migrate Wiki Server data from Leopard Server (i.e. 10.5 not 10.6) to Lion Server without upgrading to Snow Leopard first. I'm happy to set up everything else afresh but I've migrated wiki data before and it was a nightmare.
    The situation we'll soon be in is needing to migrate wiki data on a PowerPC mac running Leopard Server to a new Power Mac pre-installed with Lion Server.

    From: http://images.apple.com/macosx/server/docs/Upgrading_and_Migrating_v10.7.pdf
    Need to set up Lion Server first, then:
    Copy the wiki data located in /Library/Collaboration/ by default or in the location specified in Server Admin on the v10.5.8 or later server to a local volume Lion Server can access.
    Use the following steps to manually migrate your Mac OS X v10.5.8 or later server’s Wiki data to Lion Server.
    If you are migrating a v10.5.8 wiki server’s data, make sure Lion Server is bound to the same Open Directory master as the v10.5.8 server, so the ACLs for wikis can convert. If not, wikis are only readable or writeable by admins, and ACLs must be reset.
    To migrate wiki data:
    1 Start Wiki service in the Server app.
    2 Enter the following command.
    sudo wikiadmin migrate -r /path/to/collaboration/folder

  • How do I access iCloud Calendar & Contact data from a pre-Lion iMac?

    How do I access iCloud Calendar data from my pre-Lion iMac?
    Hardware Overview:
      Model Name:          iMac
      Model Identifier:          iMac4,1
      Processor Name:          Intel Core Duo
    System 10.7 is not available for this iMac. 
    Since MobileMe has died, and my other iMac is running 10.7 Lion, iCloud is now the fact in Apple internet data sharing. 
    I'd like to keep my Address Book (now Contacts in 10.7) and Calendar in sync with my pre-10.7 iMac.  How is this done?
    Many Thanks,
    PBH

    A nice idea, but ≈$100 for far more than I need. It feels like overkill. 
    I was thinking something more like a simple CalDAV connection. 

  • HT4889 Migration Assistant unable to transfer from OS 10.4.11 to Mountain Lion

    I am following the instructions here
    How to use Migration Assistant to transfer files from another Mac
    http://support.apple.com/kb/HT4889?viewlocale=en_US&locale=en_USto migrate from OS 10.4.11 to Mountain Lion, but Migration Assistant gets stuck looking for my old computer. This occurs after I select "From a Time Machine backup or other disk". 
    My old computer is in Target Disk mode and visible in the new Macbook's Finder, so the Firewire cable is OK.
    I also tried migrating from a 120 GB hard-drive backup through the USB port. Still no luck.
    I am running Tiger on my old Powerbook G4, and Mountain Lion on a MacBook Pro.
    Any ideas?
    Any good guides to transferring the files manually?
    Thanks
    Seth

    It is not a good idea to wholesale restore your entire home directory from Tiger to Mountain Lion. If Migration Assistant had worked, you would have a nightmare on your hands with incompatibilities in the home library folder.
    Here is what I would do:
    Use Target Disk Mode to mount the old Tiger Mac on the new Mountain Lion Machine installation.
    Ensure that the original files have the same user id and group ownership between both machines.
    Get the Tiger home directory files to the ML home directory
    Do not drag and drop folders from Tiger, that already exist on ML. Drag the contents between folders. The reason is that folders created by ML, may have different permissions and lower level access control list settings than their Tiger counterparts.
    Do not move the contents of the home Library folder on Tiger at all. You are asking for mayhem if you splatter this over its counterpart on ML.
    You can drag and drop any folders that you created on the Tiger home directory to your new home directory on ML.
    Do not drag any Tiger applications to the new Mountain Lion installation. They are incompatible, and you need current revisions with confirmed ML support.
    Unmount Firewire Target disk mode.
    Start using ML.

  • Calendar from Time Machine Lion backup to Mountain Lion

    Hello,
    I copied the Time Machine backup from my crashed Lion iMac to my Mountain Lion Mac Mini, folder ~/Library/Calendars.
    The calendar data is not correct converted from Lion to Mountain Lion: ex. appointment from 31-jan-2013 18:30 upto 19:30 is changed to 31-jan-2013 18:30 upto 01-feb-2013 19:30.
    How can I correctly convert the calendar database from my Lion backup to Mountain Lion ?
    Thanks,
    Hubert

    Here are the steps I would use.. do not connect by ethernet at all whilst you do them.
    Factory reset the TC.
    The Factory Reset universal
    Unplug your TC/AE. Hold in reset. and power the TC/AE back on..  all without releasing reset and keep holding in for about 10sec. The time is not important.. it is the front LED rapid flashing that indicates you are in factory mode.
    Release reset.
    If it doesn’t flash rapidly you have released reset at some point and try again.
    Be Gentle! Feel the switch click on. It has a positive feel..  add no more pressure after that.
    TC/AE will reboot after a couple of minutes with default factory settings and will wipe out previous configurations.
    No files are deleted on the hard disk.. No reset of the TC deletes files.. to do that you use erase from the airport utility.
    Redo the setup with different names. Short, no spaces and pure alphanumeric. eg TCgen5 as base station name. TCwifi for wireless name.
    Make sure the password for disk and wireless etc.. are 8-20 characters pure alphanumeric mix of case and numbers.
    Reset TM then to the new drive location.
    See A4 pondini for a full reset.
    http://pondini.org/TM/Troubleshooting.html
    Strongly recommend you also verify the backup and install the Widget.. A5 and A1. The log you get from the widget is a big help to see what is going wrong.
    Ensure the ipv6 is set to link-local only in wireless.
    I would do the whole lot but you can test at each step if you want.. I just had it happen to me.. first time in 12months and regular posting in this area. Doing the above got me going again.. although it takes a bit of patience to work through the lot.

  • How long should it take a well-qualified server admin to migrate from Tiger to Lion...

    How long should it take a well-qualified server admin to migrate from Tiger to Lion...
    For a small company, if the Tiger server is running on a G4 Tower:
    -Roughly 500GB in user files
    -Data resides on old-school ATA drives
    -OD Master - Kerberized
    -AFP
    -Mobile Homes
    -DHCP
    -DNS (for 2 domains)
    -FTP
    -iChat
    -Mail (non SSL)
    -NetBoot
    -Print Server
    -SWUPD
    -VPN
    -Hosting website using MySQL
    -User & Computer Management
    Considerations/Hurdles/Challenges:
    -Tossing old G4 into garbage, upgrading Mini client to Snow Leopard, adding Lion iMac client to the LAN
    -Fresh OS installs on the Mini and iMac
    -Upgrading from CAT5 to CATE on the LAN (not it the walls - just loose cables)
    -All new hardware must be sourced out (take some time to price compare)
    -Must find a way to transfer data from ATA drives to SATA drives or Lion Server
    -Company must not have any email downtime (MX Records to be modified on DNS Providers site)
    -Servers hostname goes from "companyserver.company.com" to "server.company.com"
    -ISP blocks some SMTP ports
    -DNS Provider doesn't support TSL/SSL SMTP
    -Implementing a switch into the network
    -Implementing a new router (for firewall and NAT) from ISP
    Upgrading to Lion Mini Server
    -All the same services
    -Using SSL
    -Implementing Mobile Device Enrolment and Deployment
    That should just about cover it. I'll add any other details/hurdles as they come to mind.
    Can you guys give me your best guesstimate as to how many hours you think this job should take? I'd appreciate any feedback as to how long you guys think it'd take you to make this transition. I'm trying to plan, and we're going to be down-and-out, the boss NEEDS to know for how long.!
    Thanks in advance guys!

    It's about a gigabyte, so if you have a slow connection, it might take some time.
    But - you shouldn't be getting the beach ball - that's a different thing.
    Can you do open Activity Monitor, or is it stuck completely?

  • HT4413 I am trying to use migration assistant to move everything from snow leopard (10.6.8) to mountain lion (10.8.3) using a direct machine to machine ethernet cable connection but it stalls out at about 17 minutes remaining.  Thoughts on how to proceed?

    I am trying to use migration assistant to move everything from snow leopard (10.6.8) to mountain lion (10.8.3) using a direct machine to machine ethernet cable connection but it stalls out at about 17 minutes remaining.  Thoughts on how to proceed?

    Have you set both to never sleep?
    Is the source (old) Mac's software up to date (including the Migration Assistant for Mac OS X Snow Leopard update)?
    Is the old Mac healthy?  Have you run Verify Disk on it lately?
    The estimates are wildly inaccurate under the best of circumstances.  How long has it been stuck? 

  • If I upgrade to Lion from Snow Leopard on my Mac will MobileMe calendar and mail integrate with iCloud?

    If I upgrade to Lion from Snow Leopard on my Mac will MobileMe calendar and mail integrate with iCloud?

    There is no Mobile Me anymore. It has been gone for several years, now. However, your existing calendar and mail will integrate with iCloud if you enable it on your system.

  • How to use Migration Assistant to transfer files from osx lion to osx snow leopard

    I have MacBook with osx Lion and I need transfer my user acount to another mac computer (Mac mini) because my MacBook was broke and I send it to service. On Mac mini I have osx Snow Leopard. Is possible to use Migration Assistant to transfer files from osx Lion to osx Snow Leopard?

    Sorry, but there's no way to "go back" with Migration Assistant.
    Can you upgrade the Mini?

  • Is there a step by step guide on upgrading from leopard to lion inlcuding data backup and migration?

    is there a step by step guide on upgrading from leopard to lion inlcuding data backup and migration?

    Let me just give you the breakdown:
    Snow Leopard (10.6) needs to be purchased. You need Snow Leopard because it has the Mac App StoreAlternatively, you could get the Lion USB drive, but much more expensive
    Once you have installed Snow Leopard, open the Mac App Store and find OS X Lion. This downloads OS X Lion Installer. After the download finishes, click on it, follow the steps and the installation begins!
    No data will be lost during any of the upgrades
    Let me know if you have any further questions.

  • Moving wiki from SL to Lion - how to move one wiki

    As I was migrating the wikis to Lion (10.7.2) I sent out notification that I will delete un-used wikis (using the list of wikis that command line showed migrated) and to let me know which ones they need. I got about a dozen responses that their wiki was not on the list. When I asked for a link it would point to wiki.servername.org/groups/missingwiki  On the SL (10.6.8) server I see under groups the missingwiki, in fact all the missing ones are there. How do I move these missing wikis over to Lion server????

    Not really. For starters, the database will be migrated to postgres, and probably be modified to suit the newer wiki server framework. In principle, it should be possible to continue using the SL wiki under Lion, or restore a SL Wiki implementation to run on Lion Server. It might be necessary to run on its own apache instance (using different ports), in order to avoid having the admin tool destroy legacy settings.

  • Can I convert Wiki's from SL to Lion

    Is it possible to convert Wiki's made in SLS to Lion Server?

    Not really. For starters, the database will be migrated to postgres, and probably be modified to suit the newer wiki server framework. In principle, it should be possible to continue using the SL wiki under Lion, or restore a SL Wiki implementation to run on Lion Server. It might be necessary to run on its own apache instance (using different ports), in order to avoid having the admin tool destroy legacy settings.

  • Migrate wiki from MLS to MAVS

    Dear Folks,
    I want to provide a solution on how to migrate the Wiki from a Mountain Lion Server to a Mavericks Server. Both Servers are running but in different locations and they can't communicate directly with each other. Upgrading the MLS was no option - after what I had read in hundreds of threads. The MLS is a 10.8.5 (with the latest version of server.app up until the 15th of October 2013) and Mavericks a 10.9.1 (with the latest version of server.app up until New Years Eve).
    I hadn't done it without the help of Andreas from Metalab in Vienna (lovely Hackspace) - so the grace goes to him!!
    First things first - he isolated 2 issues on MLS - revolving postgresql Version AND Socket! Thank you Apple-developers you did a great job here - since this product is called „The Server for everyone“ I believe either the title is incorrect or some guys haven’t understood what the a server for everyone implies - since everyone isn’t a geek, nerd, developer etc. - think about it!
    Trying to connect to psql on MLS:
    bash-3.2# psql
    psql: could not connect to server: No such file or directory
              Is the server running locally and accepting
              connections on Unix domain socket "/var/pgsql_socket/.s.PGSQL.5432"?
    What?!
    bash-3.2# serveradmin status postgres
    postgres:state = "RUNNING"
    What?!
    So he started digging on MLS:
    bash-3.2# netstat -na|grep LISTEN
    nothing tangible here - nothing ist listening to 5432
    Dig deeper on MLS:
    bash-3.2# lsof | grep postgre
              #output omitted for clarity
    postgres_ 2546      _postgres   10u     unix 0xa319efaa0af41357       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
    postgres_ 2547      _postgres   10u     unix 0xa319efaa0af3fbe7       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
              #output omitted for clarity
    postgres_ 2548      _postgres   10u     unix 0xa319efaa0af3fa57       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
              #output omitted for clarity
    postgres_ 2549      _postgres   10u     unix 0xa319efaa0af3f8c7       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
              #output omitted for clarity
    postgres_ 3102      _postgres   10u     unix 0xa319efaa0b220357       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
              #output omitted for clarity
    Hold the horses still - that got him thinking! How does that fit to the output of the psql-command just seconds earlier (and I literally mean seconds!) Can you see it?
    The truth is, the Socket is at:
    /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
    but is expected by psql to be in /var/psql_socket/.s.PGSQL.5432!
    Expected What?!
    Verified it again on MLS:
    bash-3.2# psql
    psql: could not connect to server: No such file or directory
              Is the server running locally and accepting
              connections on Unix domain socket "/var/pgsql_socket/.s.PGSQL.5432"?
    bash-3.2# psql --help
    Yep - when postgresql was compiled obviously somebody was sitting on his fingers - during implementation nobody had told psql the path for the socket at the "new" location?! Ergo - psql is looking for the socket in the default location - where it is not.
    Then, with the help, he managed it to get in.
    Trying to get in on MLS:
    bash-3.2# psql -p "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432"
    psql: invalid port number: "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432"
    Trying again on MLS:
    bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432"
    psql: could not connect to server: Not a directory
              Is the server running locally and accepting
              connections on Unix domain socket "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432/.s.PGSQL.5432"?
    And again - almost there on MLS:
    bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432
    psql: FATAL:  role "root" does not exist
    Typo:
    bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 -u colab
    psql: invalid option -- u
    Try "psql --help" for more information.
    And - tata - he was in on MLS:
    bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 template1 collab
    psql (9.1.9, server 9.2.4)
    WARNING: psql version 9.1, server version 9.2.
             Some psql features might not work.
    Type "help" for help.
    template1=#
    Lets find the databases and roles on MLS:
    template1=# \l
                                       List of databases
           Name        |   Owner    | Encoding | Collate | Ctype |    Access privileges   
    -------------------+------------+----------+---------+-------+------------------ -------
    caldav            | caldav     | UTF8     | C       | C     |
    collab            | collab     | UTF8     | C       | C     |
    device_management | _devicemgr | UTF8     | C       | C     |
    postgres          | _postgres  | UTF8     | C       | C     |
    template0         | _postgres  | UTF8     | C       | C     | =c/_postgres           +
                       |            |          |         |       | _postgres=CTc/_postgres
    template1         | _postgres  | UTF8     | C       | C     | _postgres=CTc/_postgres+
                       |            |          |         |       | =c/_postgres
    webauth           | webauth    | UTF8     | C       | C     |
    (7 rows)
    And there are the roles on MLS:
    template1=# \du
                                  List of roles
    Role name  |                   Attributes                   | Member of
    ------------+------------------------------------------------+-----------
    _devicemgr | Create DB                                      | {}
    _postgres  | Superuser, Create role, Create DB, Replication | {}
    caldav     | Create DB                                      | {}
    collab     | Superuser, Create role, Create DB              | {}
    webauth    | Superuser, Create role, Create DB              | {}
    Aaaaah - so there is a role collab and a database collab! Lets connect to the "right" database and dive into it on MLS.
    template1=# \q
    bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 collab collab
    psql (9.1.9, server 9.2.4)
    WARNING: psql version 9.1, server version 9.2.
             Some psql features might not work.
    Type "help" for help.
    collab=# \d
                       List of relations
    Schema |            Name             | Type  | Owner 
    --------+-----------------------------+-------+--------
    public | blog_entity                 | table | collab
    public | document_entity             | table | collab
    public | entity                      | table | collab
    public | entity_acls                 | table | collab
    public | entity_acls_defaults        | table | collab
    public | entity_attrs                | table | collab
    public | entity_changesets           | table | collab
    public | entity_comment              | table | collab
    public | entity_lock                 | table | collab
    public | entity_preview              | table | collab
    public | entity_private_attrs        | table | collab
    public | entity_tag                  | table | collab
    public | entity_type                 | table | collab
    public | file_entity                 | table | collab
    public | filedata_entity             | table | collab
    public | filename_reservation        | table | collab
    public | global_settings             | table | collab
    public | groups                      | table | collab
    public | migration_entity            | table | collab
    public | migration_status            | table | collab
    public | migrationplaceholder_entity | table | collab
    public | notification                | table | collab
    public | page_entity                 | table | collab
    public | podcast_entity              | table | collab
    public | podcast_episode_entity      | table | collab
    public | preview_queue               | table | collab
    public | project_entity              | table | collab
    public | relationship                | table | collab
    public | savedquery_entity           | table | collab
    public | search_index                | table | collab
    public | search_stat                 | table | collab
    public | session                     | table | collab
    public | subscription                | table | collab
    public | user_activity               | table | collab
    public | user_entity                 | table | collab
    public | user_entity_favorites       | table | collab
    public | user_entity_read_status     | table | collab
    public | user_entity_unread_status   | table | collab
    public | user_entity_updates         | table | collab
    public | user_entity_watched         | table | collab
    public | user_readall_time           | table | collab
    (41 rows)
    That looks fantastic! Lets start dumping with some help through pg_dump --help and then issuing the following on MLS:
    bash-3.2# pg_dump -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 -f /Volumes/USBSTICK/wikidatabase -U collab collab
    pg_dump: server version: 9.2.4; pg_dump version: 9.1.9
    pg_dump: aborting because of server version mismatch
    What?! How could that be?! The commands refer to an older version?!
    Start digging again on MLS!
    bash-3.2# which psql
    /usr/bin/psql
    bash-3.2# which pg_dump
    /usr/bin/pg_dump
    That's where I stepped in and told Andreas "Hey - ahm - I know of a path completely different…. /Applications/Server.app/.….". Thanks mate!
    Dig again on MLS!
    bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/bin/pg_dump --version
    pg_dump (PostgreSQL) 9.2.4
    Lovely - that one looks good - lets use it. All of that got us finally to the right command on MLS.
    bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/bin/pg_dump -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 -f /Volumes/USBSTICK/wikidatabase -U collab collab
    There it is - the whole Database on the stick - finally - it took Andreas only 5 Minutes - approximately? I am just baffled.
    Then I copied the Folders from the /Library/Server/Wiki/FileData of the MLS to the exact same location on the MAVS and sat permission - navigating to /Library/Server/Wiki first:
    bash-3.2# chown -R _teamsserver:_teamsserver FileData/
    bash-3.2# chmod -R +a "_www allow read" FileData/
    I compared the the collab DB on the MLS with the MAVS collab DB to see the differences - BTW - the Socket has moved again on the MLS! Move up in this documentary and you’ll see on how to find it on MAVS.
    bash-3.2# lsof | grep 5432 
              #output omitted for clarity
    postgres_   382    _teamsserver    3u     unix 0x399cdd6eeea1efe1       0t0         /Library/Server/Wiki/PostgresSocket/.s.PGSQL.5432
              #output omitted for clarity
    bash-3.2# psql -h "/Library/Server/Wiki/PostgresSocket/" -p 5432 collab collab
    psql (9.2.4)
    Type "help" for help.
    collab=# \d
                       List of relations
    Schema |            Name             | Type  | Owner 
    --------+-----------------------------+-------+--------
    public | adc_device_entity           | table | collab
    public | adc_team_entity             | table | collab
    public | blog_entity                 | table | collab
    public | bot_entity                  | table | collab
    public | botgroup_entity             | table | collab
    public | botrun_entity               | table | collab
    public | build_agent_registry        | table | collab
    public | document_entity             | table | collab
    public | email_notification          | table | collab
    public | entity                      | table | collab
    public | entity_acls                 | table | collab
    public | entity_acls_defaults        | table | collab
    public | entity_attrs                | table | collab
    public | entity_auditlog             | table | collab
    public | entity_changesets           | table | collab
    public | entity_comment              | table | collab
    public | entity_lock                 | table | collab
    public | entity_preview              | table | collab
    public | entity_private_attrs        | table | collab
    public | entity_tag                  | table | collab
    public | entity_type                 | table | collab
    public | file_entity                 | table | collab
    public | filedata_entity             | table | collab
    public | filename_reservation        | table | collab
    public | global_settings             | table | collab
    public | groups                      | table | collab
    public | migration_entity            | table | collab
    public | migration_status            | table | collab
    public | migrationplaceholder_entity | table | collab
    public | page_entity                 | table | collab
    public | podcast_entity              | table | collab
    public | podcast_episode_entity      | table | collab
    public | preview_queue               | table | collab
    public | relationship                | table | collab
    public | savedquery_entity           | table | collab
    public | scm_commit_entity           | table | collab
    public | scm_server                  | table | collab
    public | scmrepogroup_entity         | table | collab
    public | search_index                | table | collab
    public | search_stat                 | table | collab
    public | session                     | table | collab
    public | subscription                | table | collab
    public | timeseries                  | table | collab
    public | timeseries_toc              | table | collab
    public | user_activity               | table | collab
    public | user_entity                 | table | collab
    public | user_entity_favorites       | table | collab
    public | user_entity_read_status     | table | collab
    public | user_entity_unread_status   | table | collab
    public | user_entity_updates         | table | collab
    public | user_entity_watched         | table | collab
    public | user_readall_time           | table | collab
    public | visible_entity_tag          | view  | collab
    public | wiki_entity                 | table | collab
    public | work_queue                  | table | collab
    public | work_schedule               | table | collab
    public | work_schedule_recurrence    | table | collab
    public | work_schedule_status        | table | collab
    (58 rows)
    Hmmm - 41 tables in the old, and 58 in the new. What am I going to do? To be able to roll back I dumped the MAVS DB before I would do anything else.
    I had to decide between trying to take the old MLS DB and just pg_restore it into the MAVS DB, or - trying to upgrade the MLS instance to MAVS. I was afraid doing the upgrade since the MLS was a mess. At the end I would decide to go for the latter - since I had dumps. It took a while but - hey - it worked. Everything in place! Wiki running - everything else, too! The database has now 58 tables - ok - lets dump it. Notice again - no need to specify the proper version of pg_dump, but the Socket has changed from MLS to MAVS - again - you could see this when I connected with psql as well!
    Please use (-F c) compression when dumping - otherwise you’ll receive a nasty error when importing it at the MAVS.
    bash-3.2# pg_dump -h "/Library/Server/Wiki/PostgresSocket/" -p 5432 -F c -f /Volumes/USBSTICK/MLSafterupgrade2MAVS_collab_db_compressed.pgdump -U collab collab
    I then copied the dump to the server - the Desktop of the administrativ account - I did it through screensharing which is accessible after establishing a VPN to the location the server resides in.
    Unfortunately the command for pg_restore has a different syntax then the pg_dump. Use pg_dump --help to see the details. I’ll explain it quickly:
    -c is to clean entries in the target tables (you must not use capital c)
    -d specifies the database into which you would like to restore
    -h specifies (again) where the DB is - the socket
    -p the port to use
    -U is the role that likes to work on the DB
    you must not use -f since it’s not needed
    bash-3.2# pg_restore -c -d collab -h "/Library/Server/Wiki/PostgresSocket/" -p 5432 /Volumes/OSXDATA/Users/macminiadmin/Desktop/MLScollabdb_compressed.pgdump -U collab
    pg_restore: [archiver (db)] Error while PROCESSING TOC:
    pg_restore: [archiver (db)] Error from TOC entry 2466; 2605 16639 CAST CAST (text[] AS public.hstore)
    pg_restore: [archiver (db)] could not execute query: ERROR:  cannot drop cast from text[] to public.hstore because extension hstore requires it
    HINT:  You can drop extension hstore instead.
        Command was: DROP CAST (text[] AS public.hstore);
    pg_restore: [archiver (db)] Error from TOC entry 1816; 2616 16636 OPERATOR CLASS hash_hstore_ops collab
    pg_restore: [archiver (db)] could not execute query: ERROR:  cannot drop operator class hash_hstore_ops for access method hash because extension hstore requires it
    HINT:  You can drop extension hstore instead.
        Command was: DROP OPERATOR CLASS public.hash_hstore_ops USING hash;
              #output omitted for clarity
    I saw quite a lot errors (some revolving functions etc.) - however, it worked. Wikis are present again on the MAVS. Not without the initial help of Andreas - thank you once again!
    I would like to recommend to everyone joining hackerspaces in their location. I do not know them in other areas - I can only speak for the metalab in Vienna. Fantastic place with fantastic, very knowledgable people. I would also recommend reading a book like PostgreSQL 9 Admin Cookbook - this helped me quit a lot as well. It’s available through various stores - virtual or real - choose what you prefer.

    Frustrated, not angry...
    Well folks. I think this is goodbye to OS X Server - the server that I thought was much easier to use.  I've followed instructions on this forum and several others over the past 7 months.  It's cost me so much time and headache.
    Migrating wikis from Mountain Lion Server to Mavericks server has yet to work
    Upgrading our Mountain Lion Server to Mavericks leaves us without wiki, calendar, and other services
    Apple support docs don't do the trick
    Phone calls with Apple support techs haven't provided any solutions.
    Our current Mountain Lion Server suddenly lost all filesharing authentication capability and Apple enterprise solutions haven't been able to figure this one out.
    I'm stuck with a server with broken mountain lion server I have never been able to upgrade and/or migrate and ultimately would be left to copy/paste wikis to a fresh Mavericks server, export/import calendars from each client station, and contacts - I don't even know how that's going to work.
    I believe in keeping IT folks employed, but...
    The support from Apple seems so marginal (just for the server) and the plethora of problems with upgrading to Mavericks server and/or the manual fight to only potentially get it done seems very un-Apple like and just downright counter to what Apple represents.
    So I'll think different...
    Our server will be relegated to a client machine with simple file sharing.  Perhaps We'll buy Daylite to assume some of the responsibilites.  Truth is, even when things were working, it was always flaky in some way.
    I really wanted to employ OS X Server in an efficient way, but it's been more trouble than I can accomodate.
    Fortunately I am not an average client user nor a novice, so working in terminal is comfortable.
    Perhaps in a few years or so, I'll reconsider, but my experience with OS X server on Mountain Lion and Mavericks has affected my trust.
    Thanks for all of the help to those who provided instructions, workarounds, directions toward solutions, etc.
    For those of you who had a successful migration - consider yourself lucky.
    ...by the way...after finishing the incredible instructions on this page (and i sincerely mean that despite them not working for me) the result was a wiki page that looked like this
    Caught exception "[<CSEntityPlaceholder 0x7fb2d15d5910> valueForUndefinedKey:]: this class is not key value coding-compliant for the key externalID." [NSUnknownKeyException] executing route /app-context/wiki/:
    0   CoreFoundation                      0x00007fff8a0fe25c __exceptionPreprocess + 172
    1   libobjc.A.dylib                     0x00007fff8da20e75 objc_exception_throw + 43
    2   CSService                           0x0000000104bc7957 -[CSLocalServiceProxy forwardInvocation:] + 1229
    3   CoreFoundation                      0x00007fff8a05c1c4 ___forwarding___ + 452
    4   CoreFoundation                      0x00007fff8a05bf78 _CF_forwarding_prep_0 + 120
    5   CSService                           0x0000000104bf9573 __27-[CSAppContextService init]_block_invoke240 + 180
    6   CSService                           0x0000000104bdf81a __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
    7   CSService                           0x0000000104be2d6c -[CSHTTPBackgroundResponse bounce:] + 286
    8   Foundation                          0x00007fff9073976b __NSThread__main__ + 1318
    9   libsystem_pthread.dylib             0x00007fff8bc58899 _pthread_body + 138
    10  libsystem_pthread.dylib             0x00007fff8bc5872a _pthread_struct_init + 0
    11  libsystem_pthread.dylib             0x00007fff8bc5cfc9 thread_start + 13

Maybe you are looking for

  • How to convert Excel to vCard?

    I have 5000 contacts stored in Excel sheet and I am using Office 2010. It's such a cumbersome task to copy each contact in Gmail for bulk emailing. Is there any online tool available through which I can convert all these contacts into single VCF file

  • IPad 2 no sound while playing without Headphone .

    Hi Folks, Hope you all master mind over there are in good spirits. It's been while now that all of sudden sound stop coming from my iPad 2  .When I use the side volume up/down,nothing happens and only the icon is displayed that shows just a volume bu

  • I'm having problems downloading: the file cascades a bizzillion times on the screen and it appears to be a .part file.

    I'm on a Mac - my hard drive crashed last week (got a new one) so I downloaded the Firefox again. When I download, I can view my downloads under the "Tools" menu, but in my download file in my dock, the files say pdf.part - and when I download, the f

  • SQL Loader in 10g

    friends! I have a flat file which have 15.millions rows i want to load into one column. Flat_File data: (column is seprated with whitespace) ============ 002785 034730 060844 092119 122773 156571 187202 215782 247631 284387 318394 003954 035668 06125

  • How to write read dataset statement in unicode

    Hi All, I am writing the program using open dataset concept . i am using follwing code.     PERFORM FILE_OPEN_INPUT USING P_P_IFIL.     READ DATASET P_P_IFIL INTO V_WA.     IF SY-SUBRC <> 0.       V_ABORT = C_X.       WRITE: / TEXT-108.       PERFORM