Migrating wiki from one 10.6 server to another

Has anyone had any success and know the proper procedure for moving a wiki between two 10.6 servers? We're relocating it to different hardware. When I move the data store it does the "starting server" thing forever when you try to visit the web page. It doesn't look like python or wikid is doing much of anything after the first few seconds. When I delete the various .db sql lite databases as suggested for fixing other issues, they do get recreated but it still never fully starts.
The permissions are also correct on all the files so I know it is not that. Also, I did the migration using rsync3 and made sure it preserved proper permissions, extended attributes, etc.
I'm probably missing something but was wondering if anybody has done it. Thanks.
Message was edited by: Christopher Collins3

If you haven't figured the migration out already, you may want to check out this thread:
http://discussions.info.apple.com/thread.jspa?threadID=2205892
It looks like the path to take from everything I'm seeing, but if you've found a friendlier solution I'd be happy to give it a shot!

Similar Messages

  • Move WIKI data from one Mountain Lion Server to another

    Hi.
    I followed the instruction here:
    http://support.apple.com/kb/HT5585
    Under Copying all wikis from one OS X server to another OS X server, I am not even able to execute:
    sudo pg_dump --format=c --compress=9 --blobs --username=collab --file=/tmp/collab.pgdump collab
    It gives this error:
    pg_dump: [archiver (db)] connection to database "collab" failed: FATAL:  role "collab" does not exist
    Any idea?
    I just tested it on the productive server as well as a brand new install. Same outcome.
    which then I moved the: /Library/Server/Wiki/FileData over but even stop/start, restart, wiki server is running but not able to load content, it's like it's been wiped clean.
    matthew

    try it and RATE correct answers
    Hello Matthew
    You're looking in the wrong spot
    First things first - make yourself default sudo with sudo -s then you can forget prefixing it all the time.
    If you just use pg_dump then it'll take the command from the /var-Directory - that's the wrong version
    You have to specify the path for the Socket where the PSQL-Database for the wiki really is located by using the -h-option - it's not the default
    that's why you get the error that role collab does not exist since you're connecting to a database in place where the role collab truy isn't part of it.
    So - if you'd like to export the wiki-DB us the following and adapt the filename to what you like it to be.
    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.pgdump -U collab collab
    The first block specifies the "not default" pg_dump you'd like to use
    The second block (-h "/Library/.....) tells pg_dump where to find the DB
    The third block tells pg_dump to use port 5432
    The fourth block (-f /Volumes/......) tells pg_dump to place its output into this file
    The fifth block (-U collab) tells pg_dump to do this is role collab
    The sixth block tells pg_dump from with DB to dump from
    In your case extend my provided command with your options --format=c --compress=9 --blobs like this:
    bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/bin/pg_dump -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 -F c --compress=9 -b -f /Volumes/USBSTICK/wikidatabase.pgdump -U collab collab
    BTW- you can connect to the database, of course:
    bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 collab collab
    try it and RATE correct answers
    Here is my thread https://discussions.apple.com/thread/5751873

  • Transfer files using FTP from one r/3 server to another on windows platform

    Hi ,
    I am trying to transfer a text file from one r/3 server to another
    this should be done using ftp.
    I am working on widows OS & i have tried all the RSFTP* pgm's none satisfy my req. please tell proper method to do so or if any pgm please tell properly.
    Regards,
    Prateek Kumar

    If you haven't figured the migration out already, you may want to check out this thread:
    http://discussions.info.apple.com/thread.jspa?threadID=2205892
    It looks like the path to take from everything I'm seeing, but if you've found a friendlier solution I'd be happy to give it a shot!

  • Any way to migrate from one 10.5 server to another?

    Hi,
    I just lost a 10.5 Server installation, it just won't boot anymore. Since no one seems to be able to help with that problem, I needed to move on and install fresh. However, the old installation took considerable work. I would hate to have to do it all over again. So the question is: is there a migration assistant or something similar to migrate one OSX Leopard Server installation to another machine / hard drive?
    Cheers.
    PS: I tried carbon copy cloner, the cloned instance won't boot up either. I guess some files have been corrupted.

    Yes, you can.
    Open: System Preferences > Hardware > Keyboard & Mouse > Mouse, select menu for the side
    buttons, turn it off or select another use for the side buttons.
    It takes a little practice, but you can train yourself not to be pressing the side buttons inadvertently.
    That's the other option.
    To still use expose, you can use the keyboard. I have expose assigned to F10. Those settings can be
    adjusted using System Prefs as well.
    Kj

  • Copy reports from one business objects server to another

    How do I copy all the reports published in my production BO server to my test server. I did this once but can not remember. Is it the import wizzard?

    yes you can use the import wizard to export your reports from one server to another server
    just open the import wizard, connect to your source server, choose object types you want to export (folders, reports, users,,,,etc),,, then choose the objects itself, then connect to the destination server, and the import wizard will guide you through this process.
    good luck

  • Problem migrating account from one active directory domain to another. Using NetBIOS

    Hello,
    I'm migrating a Lion machine from one domain to another. When I try to join it to abc.example.com it joines it to 123.example.com in the list of domains. 123.example.com is the NetBIOS name of abc.example.com. This configuration does not work.
    What is even more strange, is if I go into the Open Directory Utility > Active Directory to set the create mobile account settings, once I apply the settings (or even if I don't apply the settings) when I get back to the list of domains, it show BOTH abc.example.com and 123.example.com as domains I am joined to. If I remove 123.example.com it removes abc.example.com.
    I've only seen this problem one other time and this was with a snow leopard machine that was not bound to AD. I upgraded it to Lion and tried to bind it, and had the exact same thing occur.
    I'm certain there is a "stuck" setting somewhere that is causing this. I have had successful snow leopard > lion upgrades work, and many lion machines joined to AD so this does work normally. Just not sure whats wrong or really where to look.
    The OS is fully patched and updated to the current version.
    Any thoughts?

    Case 1:
    Here you can written pre-update event handler which will check whether minor and major org code changed or not.
    If changed then first starts de-provisioning and then start provisioning.
    If not changed then do nothing.
    This approach will not transfer accounts from one domain to another but it will create fresh accounts and remove accounts from old domain.
    Case2:
    If you want to transfer accounts from one domain to another in that on pre-update you have to change OU of user on process which automatically move to another domain.
    but not sure about exchange it is possible to move to another domain.
    hopping that all domains under same forest otherwise same Connector Sever will not work.

  • Export from one oracle datasbase server to another  for version: 9.2.0.1.0

    Hi All,
    I know this is an elementory thread , however i would like to know the process of import and export of database in detail.
    I need to copy the entire database from a existing prodcution server having oracle 9.2 as its version to another server with same oracle version .
    Kindly mention the process to be carried out .
    Thanx in advance

    I need to copy the entire database from a existing prodcution server having oracle 9.2 as its version to another server with same oracle version .Its better to take a hotbackup/coldbackup or RMAN backup depending on the environment. Exp/Imp will be time consuming.
    For exp/imp;
    http://www.orafaq.com/wiki/Import_Export_FAQ
    For full export-import, you need to do is take an exp backup from source DB. Create same tablespace that of source DB and import from the dump file.
    exp system/manager full=y buffer=100000 feedback=10000 recordlength=64000
    imp system/manager full=y buffer=100000 feedback=10000 recordlength=64000

  • Can I migrate rules from one account in Mail to another?

    In mail I have 90 rules, many multi line criteria. I have just created a new  imap account linked to fastmail. My rules wont run because they seem to be linked to my first account, not imap. I tried just duplicating them and re-mapping to the new "move to" folder. Wouldn't run. Added a new criteria for the account but then all mail will go to that folder since 90 rules include that account in the rule. This would work if there was 2 levels of logic in the IF command but alas its only IF ANY/ALL.
    I really don't want to re-write all my rules as some have maybe 10 lines of criteria in them. Any suggestions?

    Transferring files from one User Account to another

  • Migrating current mobile user accounts from one OS X Server to another

    I have not been able to find ANY answers to my situlaton. 
    I have a small office that currently has a Mac Server 10.4.11 server running that has many "mobile user" accounts setup.  This was done because we have so many mobile users coming in and out of the office.  When the user comes back they sync their home directory witht th server here.  Works great.
    We recently purchased a new Mac Server running 10.7.4.  Set it up as the Open Directory Master.  I unbind from the old server and bind to the new server.  Everything seems to be working just fine except when I go and add a current mobile user to the new server it creates a new user account on the client device (MacBooks) as if the previous user settings didn't exsist.  Since they need to be mobile users and not just network users I haven't been able to find a solution to this problem any where.
    Is there a way on the client to tell it to use the old user account stored on the MacBook to use with new mobile user connected to the new server?
    Or is there an easier way of doing this that I don't know about?
    Thanks,
    TK

    If I understand what you wrote, no.  The reason is this.  If memory serves...  In 10.4.11 accounts were assigned a UID.  In 10.7.x, accounts are assigned a UID and a GUID.  Most everything relies on the GUID at this point.  So, what you have is an account named marysue on the workstation and it is assigned a UID like 1045.  Now you created marysue on the Lion server, but you likely did not recreate the UID to match the old server.  And thus, the UID value is different but more importantly you now have a GUID value like EC0F9357-8EF2-4D3B-B6F3-2E3016400114, that is associated with the account.  So, the user, despite having the same shortname, is different. 
    In addition, you are working with two different directory systems.  10.4 still used NetInfo (ah, I miss you so).  10.5 and above use DS local flat files, even when bound to an LDAP system.
    So, probably the easiest way to do this, provided I understand what you are seeing is the following.  Let's assume the following:
    You have a mobile account on a workstation for the user maryjoe with a UID of 1034 that came from the 10.4.11 system.  You have this account cached.  You have a home folder in /Users/maryjoe.  You have now bound to the new server which contains a user named maryjoe likely with a UID of something other than 1034 and with a GUID value that likely did not exist in the old directory system, also with the shortname of maryjoe and a home path of /Users/maryjoe.
    So when you log in, you are likely being pathed to /Users/maryjoe, but you are seeing a default Dock and no documents because of permissions.  My guess is that if you used Terminal to view the Users directory you would see something like this (open Terminal and issue the command ls -l /Users/:
    drwxrwxrwt   4 root       wheel  136 Apr 18 21:35 Shared
    drwxr-xr-x+ 14 locadmin  staff  476 Jan 21 7:42 locadmin
    drwxr-xr-x+ 14 1034  staff  476 Mar 21 10:42 maryjoe
    Note the folder maryjoe is not owned by maryjoe, it is owned by the UID of maryjoe from the old server.
    Ok, so long story short (sorry for the log explanation, especially if you are experiencing something else that I did not get from the post), all you need to do is update the permissions of the home folder.  Do this:
    1:  Log in as the local admin
    2:  Open Terminal
    3:  Issue this command:
         sudo chown -R maryjoe /Users/maryjoe
    Even with a lot of data in the home folder, this should not take more than a few minutes to complete.
    When the command completes, run this command again:  ls -l /Users/
    You should now see
    drwxrwxrwt   4 root       wheel  136 Apr 18 21:35 Shared
    drwxr-xr-x+ 14 locadmin  staff  476 Jan 21 7:42 locadmin
    drwxr-xr-x+ 14 maryjoe  staff  476 Mar 21 10:42 maryjoe
    Now try logging in as the user.  With a little luck I divined the issue and this will have you up and running.  Now, I normally will also purge the cached account in /var/db/dslocal/nodes/Default/users/ but that might be a bit daunting.  So let's start with the simple process first of ensuring home folder permissions are correct.

  • How to Migrate Mail from One Mac Computer (MBP) to another Mac Computer (MBA)

    I just bought a Mac Book Air (OS X Mavericks, Mac Mail) after a couple of years using a Mac Book Pro (OS X Mavericks, Mac Mail) and need to migrate my mail from MBP to MBA. Is there any steps to follow

    MVP - if you still need the advice, or if any others come across this thread hoping it will help.
    The simplest way is now that you have your mail files copied from the old Mac (as per:
    Grant Lenahan
    Simply move over your users/you/library/mail folder ( it has all the mail files).
    Now launch Mail on the new Mac and go to File > Import Mailboxes
    Select the mail boxes you want to import and Bob's your mother's brother!
    Works a treat!

  • Move Wiki from one Server to another

    I failed in moving the wiki I programmend and that worked quite well from one 10.5. server to another machine. I copied some stuff from one device to another but obviously not the correct one.
    Is there a way to do it automatically or knows somebody which files have to be moved?

    try it and RATE correct answers
    Hello Matthew
    You're looking in the wrong spot
    First things first - make yourself default sudo with sudo -s then you can forget prefixing it all the time.
    If you just use pg_dump then it'll take the command from the /var-Directory - that's the wrong version
    You have to specify the path for the Socket where the PSQL-Database for the wiki really is located by using the -h-option - it's not the default
    that's why you get the error that role collab does not exist since you're connecting to a database in place where the role collab truy isn't part of it.
    So - if you'd like to export the wiki-DB us the following and adapt the filename to what you like it to be.
    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.pgdump -U collab collab
    The first block specifies the "not default" pg_dump you'd like to use
    The second block (-h "/Library/.....) tells pg_dump where to find the DB
    The third block tells pg_dump to use port 5432
    The fourth block (-f /Volumes/......) tells pg_dump to place its output into this file
    The fifth block (-U collab) tells pg_dump to do this is role collab
    The sixth block tells pg_dump from with DB to dump from
    In your case extend my provided command with your options --format=c --compress=9 --blobs like this:
    bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/bin/pg_dump -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 -F c --compress=9 -b -f /Volumes/USBSTICK/wikidatabase.pgdump -U collab collab
    BTW- you can connect to the database, of course:
    bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 collab collab
    try it and RATE correct answers
    Here is my thread https://discussions.apple.com/thread/5751873

  • Has anyone used Migration Assistant to move services from one system running Server to a new system?

    So, I've purchased a Mac mini to replace my aging Mid 2009 mini on which I've been running Mavericks Server.  In trying to answer the question of how best to move services from the old machine to the new, I've stumbled into the fact that Migration Assistant can apparently migrate not just user data for workstations and laptops, but also service data for servers.  The problem is there isn't much detail in the docs about how good a job it does when going from one machine to another without changing OS releases.  There's a very detailed document in the KB about going from older versions of Server to new (OS X Server: Upgrade and migration from Lion Server or Snow Leopard Server) and a general doc on migrating from another Mac under Mavericks (OS X: How to migrate data from another Mac using Mavericks) but that has no details about Server.
    Has anyone used Migration Assistant to move services from one system running Server to a new system?  Are there any details that are particularly important to get right?  Are there things that require manual steps after Migration Assistant is done?
    There are other ways I could tackle the problem, of course.  I could simply swap drives between the systems, but the new system has two drives that are bigger, faster, and I intend to mirror them.  That would complicate such an approach.  I'd really like to keep the conversation constrained to a discussion of Migration Assistant as the primary method.

    yes. I migrated a server frm lion to mavericks following these notes a while back:
    OS X Server: Upgrade and migration from Mountain Lion
    i do not recall having any problems with it.

  • Migrate tracks from one server to another

    Hello, I've read a few guides how to migrate tracks from one server to another, but it doesn't help me.
    What I've done:
    1) I've exported my SC from SLD at my old server
    2) Then imported it at my new server
    3) Updated CMS from SLD
    4) Created a track at my new server and added imported SC
    Then I have to import my SC from old server with sources and there is some errors happens for me.
    First option: I have exported my SC from CMS, but the SCA file is about 5kB. I unzipped it and there was ARCHIVESOURCE folder but it hasn't anything seems to be my sources. That file is checked-in successfully through the transport studio, but no sources imported into DTR.
    Second option: I have exported the SCA file by using NWDS. It's exported OK, size ~1.3MB, ARCHIVESOURCE folder with mine sources. But when I try to check-in it, it fails with an error "import failed, because the sources are not contained in the archive
    Could anybody helps me to achieve my task? I stuck with source import.

    Hi Kirill,
    important to know that assembly ALWAYS uses the CONS/ACTIVE workspace for SCA generation.
    If you for instance create a change (an activity), and you activate and release it but you don't import this activity into CONS, then it won't be part of the CONS/active and then due to obvious reasons assembly won't produce the sources either (no possibility to do an explicit activation on cons level as here a force activation takes place at import, but of course the import into cons is a necessary step, because as mentioned assembly uses the cons/active).
    Can you please confirm/deny how this scenario looks like on your end?
    Thank you!
    Best Regards,
    Ervin

  • 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

  • Proper way to migrate schema from one DS5.2 to another

    What is the best error free way to migrate schema from one Directory Server 5.2 to another.
    Thanks,

    I have migrated schema from 5.1 to 5.2 and below are my experiences. Check if this helps you in any way.
    - After overwriting 99user.ldif from 5.1 to 5.2; experienced problems in starting the DS 5.2 instance. On looking into the logs, few object classes and attributes gave problems.
    - Modified 99user.ldif in DS 5.2 by appending schema values group by group. Able to start DS 5.2 instance without problems
    - Migrated data (ldif file) via ldif2db command to DS 5.2
    - Encountered problems in DS 5.2; Suffix got dissappeared after migrating the data and a restart of DS 5.2 instance. Upon looking logs and few troubleshooting steps, found the aci's in the data file creating problems
    - Removed aci's in data (ldif file) manually and migrated using ldapmodify command and it worked

Maybe you are looking for