Community Forum

Resolved
0 votes
Hi,

I have been running my 6.x COS server for years without ANY hiccups whatsoever and the only downside I can see in that is that I had to tend to is so absolutely darn little that my Linux skills and ~knowledge have faded away badly. - Therefore it took me a bit to overcome my embarassment and to even ask this question, but here goes... ;)

COS 7.3 has just been released and it is high time to move my server to a higher spec'd hardware base. However, during or after the install the new server would have to assume its role as the new PDC and the old server would ultimately have to be removed from its role, probably/hopefully with a synchronization step in between.

My question now is how to best go about this, i.e. what steps to take in what sequence? Is there perhaps some precanned information you can point me to or did I perhaps miss some relevant forum posts?

TIA,
Ingmar
Friday, May 12 2017, 09:44 AM
Share this post:
Responses (5)
  • Accepted Answer

    Thursday, May 18 2017, 12:55 PM - #Permalink
    Resolved
    0 votes
    I have a feeling something has changed between versions and I don't know if Zarafa is the same version in 6.x and 7.x. An alternative is imapsync (which is great as it can work incrementally) but you will need everyone's passwords.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, May 18 2017, 08:58 AM - #Permalink
    Resolved
    0 votes
    What I did once for testing was backup and restore Zarafa's directories with tar and mysql database and it did work (i also backup Zarafa that way - db+attachment folders.)
    As usual, testing on non-production system is neccesary to avoid downtime and mistakes, but I thin, everything is doable if prepared.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, May 12 2017, 12:47 PM - #Permalink
    Resolved
    0 votes
    When I did it I cheated. I hooked up the new server's WAN port to my LAN and opened up the WAN firewall to ssh and Webconfig. I then ssh'd into the new server and ran the imapsync and rsync from there. This way nothing on the LAN could really see the new server until I swapped it into the LAN.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, May 12 2017, 11:38 AM - #Permalink
    Resolved
    0 votes
    Hi Nick,

    this is very helpful, thank you. - Would you by any chance have some advice for me on how to make sure the old and new server do not get in each other's way PDC/Domain wise during the setup/installation of the new server?

    Regards,
    Ingmar
    The reply is currently minimized Show
  • Accepted Answer

    Friday, May 12 2017, 11:26 AM - #Permalink
    Resolved
    0 votes
    There is no direct upgrade path. You can do a config backup from 6.x and restore it to 7.x. This will bring all your users across with their passwords. You can then use rsync to get user files across. If you use ClearOS for e-mail, you can use imapsync to move e-mails across but you need each user's passwords. Both imapsync and rsync can work incrementally. If you use cyrus-imap for your e-mails rsync will work, but you can *probably* just copy across everything under /var/spool/imap and /var/lib/imap. I did it from 5.x to 6.x but from 6.x - 7.x I used imapsync. I've no idea what you can do with Zarafa apart from imapsync.

    If you do a config backup and restore, check your own firewall rules that they do not specify any interfaces. if they do, you will need to correct the interfaces in the rules manually.

    If you use cyrus-imap, your cyrus certificate is not copied across with the backup and restore and it will generate a new one. This could cause you problems with your clients if you use IMAPS or POPS. I copied mine across manually (from somewhere under /etc/PKI) when I discovered the issue.
    The reply is currently minimized Show
Your Reply