Migration between AMS 2.4.3 and AMS 2.6.4

[KonradRatkowski]

Hi, is it possible to migrate data between two Ant Media Servers ?
I need to migrate everything between two servers. One is with Ubuntu 22.04 and second one is with Ubuntu 20.04
I tried to copying files between two servers, but unfortunately it is not working. AMS crashes few second after the launch with systemctl

Please Help :)

[yashtandon113]

Hi @KonradRatkowski
Yes, data can be transferred from one AMS to another.
Could you kindly tell us which files you copied and if you are able to share the whole server logs? Log files can be obtained from the /usr/local/antmedia/log folder.

[KonradRatkowski]

Hi @yashtandon113 thank you for response. This is log from AMS:

`2023-08-29 18:30:00,258 [main] INFO org.red5.server.Launcher - Ant Media Server Enterprise 2.4.3
2023-08-29 18:30:00,260 [main] INFO org.red5.server.Launcher -
2023-08-29 18:30:00,578 [main] INFO o.r.spring.Red5ApplicationContext - setApplicationContext: org.springframework.context.support.FileSystemXmlApplicationContext@e70f13a, started on Tue Aug 29 18:30:00 CEST 2023
2023-08-29 18:30:00,591 [main] INFO o.r.spring.Red5ApplicationContext - Red5ApplicationContext init
2023-08-29 18:30:00,688 [main] INFO org.quartz.impl.StdSchedulerFactory - Using default implementation for ThreadExecutor
2023-08-29 18:30:00,696 [main] INFO o.quartz.core.SchedulerSignalerImpl - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
2023-08-29 18:30:00,696 [main] INFO org.quartz.core.QuartzScheduler - Quartz Scheduler v.2.3.2 created.
2023-08-29 18:30:00,696 [main] INFO org.quartz.simpl.RAMJobStore - RAMJobStore initialized.
2023-08-29 18:30:00,697 [main] INFO org.quartz.core.QuartzScheduler - Scheduler meta-data: Quartz Scheduler (v2.3.2) 'Red5_Scheduler' with instanceId 'NON_CLUSTERED'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 6 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.

2023-08-29 18:30:00,697 [main] INFO org.quartz.impl.StdSchedulerFactory - Quartz scheduler 'Red5_Scheduler' initialized from the specified file : '/usr/local/antmedia/conf/quartz.properties'
2023-08-29 18:30:00,697 [main] INFO org.quartz.impl.StdSchedulerFactory - Quartz scheduler version: 2.3.2
2023-08-29 18:30:00,697 [main] INFO org.quartz.core.QuartzScheduler - Scheduler Red5_Scheduler_$NON_CLUSTERED started.
2023-08-29 18:30:01,052 [main] WARN i.antmedia.statistic.StatsCollector - Starting heartbeats for the version:2.4.3 and type:Enterprise
2023-08-29 18:30:01,063 [main] WARN o.r.spring.Red5ApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'srtAdaptor' defined in class path resource [red5-common.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [io.antmedia.enterprise.srt.SRTAdaptor]: Constructor threw exception; nested exception is java.lang.UnsatisfiedLinkError: no jnisrt in java.library.path: [/usr/local/antmedia/lib/native]
2023-08-29 18:30:01,064 [main] INFO i.antmedia.statistic.StatsCollector - Shutting down stats collector
2023-08-29 18:30:01,064 [main] INFO i.antmedia.statistic.StatsCollector - Ending analytic session
2023-08-29 18:30:01,065 [main] INFO i.antmedia.statistic.StatsCollector - Closing vertx
2023-08-29 18:30:01,066 [main] INFO org.quartz.core.QuartzScheduler - Scheduler Red5_Scheduler$NON_CLUSTERED shutting down.
2023-08-29 18:30:01,066 [main] INFO org.quartz.core.QuartzScheduler - Scheduler Red5_Scheduler$NON_CLUSTERED paused.
2023-08-29 18:30:01,067 [main] INFO org.quartz.core.QuartzScheduler - Scheduler Red5_Scheduler$_NON_CLUSTERED shutdown complete.
2023-08-29 18:30:01,071 [main] WARN o.s.c.s.FileSystemXmlApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'red5.common' defined in class path resource [red5.xml]: Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'srtAdaptor' defined in class path resource [red5-common.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [io.antmedia.enterprise.srt.SRTAdaptor]: Constructor threw exception; nested exception is java.lang.UnsatisfiedLinkError: no jnisrt in java.library.path: [/usr/local/antmedia/lib/native]
`
I will also add that when I do a clean installation (without moving data) of AMS 2.6.4 Everything works without problems on new server

[yashtandon113]

@KonradRatkowski
When I see the logs, it is from version 2.4.3. Are you trying to install v2.4.3 on Ubuntu 22.04?

In the logs, error is related to SRT beans. To solve that, you need to edit red5-common.xml file under /usr/local/antmedia/conf folder and comment out the srtAdaptor bean part as below.

<!-- <bean id="srtAdaptor" class="#{ T(io.antmedia.rest.RestServiceBase).isEnterprise() ? 'io.antmedia.enterprise.sr>        
</bean>-->

After that restart the server.

And if you want to migrate the data from old server (2.4.3) then do the fresh installation of v2.6.4 on new server and copy below files only to transfer the data.

1. Copy or move the application database files under the /usr/local/antmedia folder to the new server's same directory. Please make sure that those applications are present or have been created on the new server.
2. Copy or move recording data (VOD) files from the applications streams directory to the new server in the respective applications streams folder. The Stream folder is present under /usr/local/antmedia/webapps/App-Name.

After the process is done, restart the Ant Media Server.

I hope it helps.

[KonradRatkowski]

@yashtandon113 Both solutions you proposed solved the issue. Thanks a lot for your help !

[yashtandon113]

@KonradRatkowski
Great!
Also, if you are finding AMS useful, it would be great if you could spare a moment to share your review on G2. It would be much appreciated.