Move Portal to another server

Sometimes hardware is changed or updated for various reasons, the instructions below should help with the procedure of moving Cantemo Portal from one server to another.

On the original system

The first thing you must do is to stop Portal, Vidispine, Transcoder, Solr, Elastic and Rules Engine 3 using the appropriate commands for your operating system.

1. Rules Engine 3 is stopped through the System Overview admin page.

2. RedHat /CentOS systems stop the remaining processes using these commands:

   $ sudo systemctl stop portal.target
   $ sudo systemctl stop elasticsearch
   $ sudo systemctl stop vidispine
   $ sudo systemctl stop solr
   $ sudo systemctl stop transcoder
   

3. Export the databases with the command:

   $ sudo -u postgres /usr/pgsql-10/bin/pg_dumpall > /tmp/pg.dump
   

4. Create an archive of the solrhome, elasticsearch and thumbnail directories:

   $ sudo zip -r solrhome.zip /var/lib/vidispine/solr
   $ sudo zip -r elasticsearch.zip /opt/elasticsearch
   $ sudo zip -r thumbnail.zip /srv/thumbnail
   

Then on the new system

1. Using the same commands as on the original server stop Portal, Vidispine, Solr, Transcode, Elastic and Rules Engine 3.

2. Copy the database dump, solrhome.zip, elasticsearch.zip and thumbnail.zip.

3. Copy /etc/cantemo/portal/portal.conf from the old system

4. Copy /etc/vidispine/server.yaml from the old system

Note: If upgrading and the server.yaml is from Cantemo 4.x or older, you will need to comment out this line with a hash # because since Cantemo 5.0.0 the installer defaults to an external Active MQ:

embeddedBroker: broker:(tcp://localhost:61616)?usekahadb=true&kahadb.directory=/var/lib/vidispine/activemq/&persistent=true

=>

# embeddedBroker: broker:(tcp://localhost:61616)?usekahadb=true&kahadb.directory=/var/lib/vidispine/activemq/&persistent=true

5. Copy media (if required).

6. Back up the current database, solrhome, elasticsearch and thumbnail directories as required.

7. Remove the existing databases:

   $ sudo -u postgres psql -c "drop database portal;"
   $ sudo -u postgres psql -c "drop database vidispine;"
   $ sudo -u postgres psql -c "drop database activiti;"
   

8. Import the database dump from the old system:

   $ sudo -u postgres psql < /tmp/pg.dump
   

9. Unzip solrhome.zip, elasticsearch.zip and thumbnail.zip.

10. Replace the solrhome directory with the copy from the original system. Confirm that user and group for the directory are vidispine.:

    $ sudo mv solr /var/lib/vidispine
    

11. Replace the elasticsearch directory with the copy from the original system.:

    $ sudo mv elasticsearch /opt/
    

12. Replace the thumbnail directory with the copy from the original system.

13. Confirm that user and group for the thumbnail directory are vidispine:

    $ sudo chown -R vidispine: /srv/thumbnail
    

14. Confirm that user and group for the directory are elasticsearch

$ sudo chown -R elasticsearch: /opt/elasticsearch/

Restart redis in order to flush out any cached database entries:

$ sudo systemctl restart redis

15. Start everything up again.

RedHat / CentOS systems starts using these commands:

$ sudo systemctl start solr
$ sudo systemctl start vidispine
$ sudo systemctl start transcoder
$ sudo systemctl start elasticsearch
$ sudo systemctl start portal.target

16. Start the Rules Engine 3 app through the System Overview admin page.

Note

From Portal 2.4 the vidispine user for the database is changed from postgres to vidispine. This means that if you have an old system that you are moving as part of an upgrade you need to change the ownership or default access rights to the database.