I have installed kaltura on two different servers which are located geographically at different places. Both servers will be used by two group of people. They would upload their own videos. Now i have a task where i have to copy the data of one server into another so that information on both servers remain common.
Please suggest me the best method available for data migration, also provide me with detailed information on tables that needs to be updated on kaltura database
I am not quite sure whether you want the two instances to just share the same data or only do a one time sync and then let them operate indep.
If the first, then what we’re actually talking about is a Kaltura cluster. Sharing the assets [entry files, players, KMC, etc] over NFS and using the same DB. For that, look at:
If it is just a one time sync, start by looking at:
Note that it is critical that both instances, the original and new, run the same Kaltura version.
Thanks for your response. As per your suggestions, i would like to try one time sync. Followed the link provided. I have doubt regarding the API file that needs to be created for downloading video from one server.
Need two clarifications :-
I would like to know the location on server to run this script file. Is it in /opt/kaltura/ or somewhere else.
Which tables in database will provide me information the input value required for running the download API script.
Souds silly, but really require your help to resolve this as my task completion date has arrived now.
that script can run from anywhere in the file system since it uses an absolute path to /opt/kaltura/web/content/clientlibs/php5/KalturaClient.php. But that only downloads the source assets.
To get the admin_secret for your partner:
mysql> select admin_secret from partner where id=$YOUR_PARTNER;
Note however that when you reingest these entries onto the new system, they will be assigned different IDs. Don’t know if that matters to you or not.
If you want a complete clone of your existing system on a new machine, you can just use /opt/kaltura/bin/kaltura-export-db.sh to export all the Kaltura DBs, then edit the resulting SQL and replace the old hostname with the new one and import it to the new system’s MySQL and copy over all the assets under /opt/kaltura/web/content/ onto the new system.
Make sure the new system has the same Kaltura version as the old one though, cause otherwise, it will not work.
Thanks for the reply. just a quick question . How much time does it take generate the output . Because i waited for half hour to get an output but it was blank , So filnally i did ctrl+C to stop the command execution.
Your service URL is wrong:
service_url = http://ip-address/start
Should not include "/start"
It should start outputting URLs rather quickly. Time it takes to conclude depends on how many entries they are…
If you’ve been waiting for half an hour and got nothing, something is wrong.
Not showing any result. I will paste the code which i am trying to use. What all things should i check on my server to make this script run successfully. It gives me the text available in echo function but does not show any URL in the output console. Please suggest.
Hi @jess , I have a similar situation, where I have kaltura 16.14 installed on one of my servers running on RHEL 7, and now I have started another server on RHEL 8 and installed kaltura 16.14.
I want to completely clone the existing data so, here’s what I have done so far:
Replaced the contents /opt/kaltura/web/content folder in RHEL 8, with the contents of RHEL 7
Updated value of host_name and url in kaltura.delivery_profile
because my database is hosted on a seperate server so i skipped the /opt/kaltura/bin/kaltura-export-db.sh (still want to know where exactly do i need to update the host in SQL)
I get the following error,
failed to unserialize server result
PHP Class map could not be loadedRunning Sphinx config..
Then on observing the kaltlog I found this
PHP Fatal error: Uncaught Zend_Config_Exception: Section 'ip-172-31-27-144.ap-southeast-1.compute.internal' cannot be found in /opt/kaltura/app/cache//batch/config.ini in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Config/Ini.php:150
#0 /opt/kaltura/app/batch/scheduler/KSchedulerConfig.class.php(129): Zend_Config_Ini->__construct()
Upon checking /opt/kaltura/app/cache//batch/config.ini, I could not find any difference in RHEL 7 and RHEL 8 servers code.