Failed to restore axon server backup file from another machine

I copied the data directory from my production machine (single node) on my local machine. I added a recovery.json file and then tried to start the axon server in recovery mode but I got this error:

     _                     ____
    / \   __  _____  _ __ / ___|  ___ _ ____   _____ _ __
   / _ \  \ \/ / _ \| '_ \\___ \ / _ \ '__\ \ / / _ \ '__|
  / ___ \  >  < (_) | | | |___) |  __/ |   \ V /  __/ |
 /_/   \_\/_/\_\___/|_| |_|____/ \___|_|    \_/ \___|_|
 2024.0.2                      Powered by AxonIQ

2024-10-02 19:15:36.241  INFO 30431 --- [           main] io.axoniq.axonserver.AxonServer          : Starting AxonServer using Java 17.0.5 on Dominiques-Mac-Studio-2.local with PID 30431 (/Users/dschoen/LesToises/dev/AxonProd/restore/axonserver.jar started by dschoen in /Users/dschoen/LesToises/dev/AxonProd/restore)
2024-10-02 19:15:36.243  INFO 30431 --- [           main] io.axoniq.axonserver.AxonServer          : No active profile set, falling back to 1 default profile: "default"
2024-10-02 19:15:37.961  INFO 30431 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8024 (http)
2024-10-02 19:15:38.048  INFO 30431 --- [           main] A.i.a.a.c.MessagingPlatformConfiguration : Configuration initialized with SSL DISABLED and access control DISABLED.
2024-10-02 19:15:39.627  INFO 30431 --- [           main] io.axoniq.axonserver.AxonServer          : Axon Server version 2024.0.2
2024-10-02 19:15:41.934  WARN 30431 --- [           main] i.a.axonserver.enterprise.init.Recover   : Starting in recover mode with file /Users/dschoen/LesToises/dev/AxonProd/restore/recovery.json
2024-10-02 19:15:42.257  INFO 30431 --- [           main] i.a.a.e.c.i.MessagingClusterServer       : Axon Server Cluster Server started on port: 8224 - no SSL
2024-10-02 19:15:42.262  WARN 30431 --- [           main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Failed to start bean 'ClusterController'; nested exception is io.axoniq.axonserver.exception.FailedToStartException: [AXONIQ-0001] Current node's internal hostname/port (localhost.internal:8224) has changed,  new values localhost.local:8224. Start AxonServer with recovery file.
2024-10-02 19:15:42.327 ERROR 30431 --- [           main] o.s.boot.SpringApplication               : Application run failed

org.springframework.context.ApplicationContextException: Failed to start bean 'ClusterController'; nested exception is io.axoniq.axonserver.exception.FailedToStartException: [AXONIQ-0001] Current node's internal hostname/port (localhost.internal:8224) has changed,  new values localhost.local:8224. Start AxonServer with recovery file.
	at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182) ~[spring-context-5.3.31.jar!/:5.3.31]
	at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:54) ~[spring-context-5.3.31.jar!/:5.3.31]
	at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:357) ~[spring-context-5.3.31.jar!/:5.3.31]
	at java.base/java.lang.Iterable.forEach(Iterable.java:75) ~[na:na]
	at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:156) ~[spring-context-5.3.31.jar!/:5.3.31]
	at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:124) ~[spring-context-5.3.31.jar!/:5.3.31]
	at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:946) ~[spring-context-5.3.31.jar!/:5.3.31]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:594) ~[spring-context-5.3.31.jar!/:5.3.31]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:147) ~[spring-boot-2.7.18.jar!/:2.7.18]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:732) ~[spring-boot-2.7.18.jar!/:2.7.18]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:409) ~[spring-boot-2.7.18.jar!/:2.7.18]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:308) ~[spring-boot-2.7.18.jar!/:2.7.18]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1300) ~[spring-boot-2.7.18.jar!/:2.7.18]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1289) ~[spring-boot-2.7.18.jar!/:2.7.18]
	at io.axoniq.axonserver.AxonServer.main(s:5) ~[classes!/:na]
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[na:na]
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
	at java.base/java.lang.reflect.Method.invoke(Method.java:568) ~[na:na]
	at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49) ~[axonserver.jar:na]
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:108) ~[axonserver.jar:na]
	at org.springframework.boot.loader.Launcher.launch(Launcher.java:58) ~[axonserver.jar:na]
	at org.springframework.boot.loader.PropertiesLauncher.main(PropertiesLauncher.java:467) ~[axonserver.jar:na]
Caused by: io.axoniq.axonserver.exception.FailedToStartException: [AXONIQ-0001] Current node's internal hostname/port (localhost.internal:8224) has changed,  new values localhost.local:8224. Start AxonServer with recovery file.
	at io.axoniq.axonserver.enterprise.cluster.ClusterController.g(caa:58) ~[classes!/:na]
	at io.axoniq.axonserver.enterprise.cluster.ClusterController.start(caa:179) ~[classes!/:na]
	at io.axoniq.axonserver.enterprise.cluster.ClusterController$$FastClassBySpringCGLIB$$f0043f62.invoke(<generated>) ~[classes!/:na]
	at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) ~[spring-core-5.3.31.jar!/:5.3.31]
	at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:792) ~[spring-aop-5.3.31.jar!/:5.3.31]
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) ~[spring-aop-5.3.31.jar!/:5.3.31]
	at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:762) ~[spring-aop-5.3.31.jar!/:5.3.31]
	at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:123) ~[spring-tx-5.3.31.jar!/:5.3.31]
	at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:388) ~[spring-tx-5.3.31.jar!/:5.3.31]
	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:119) ~[spring-tx-5.3.31.jar!/:5.3.31]
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) ~[spring-aop-5.3.31.jar!/:5.3.31]
	at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:762) ~[spring-aop-5.3.31.jar!/:5.3.31]
	at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:707) ~[spring-aop-5.3.31.jar!/:5.3.31]
	at io.axoniq.axonserver.enterprise.cluster.ClusterController$$EnhancerBySpringCGLIB$$d07f2fbd.start(<generated>) ~[classes!/:na]
	at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:179) ~[spring-context-5.3.31.jar!/:5.3.31]
	... 22 common frames omitted

Hi Dominique,
In the logs you can see that there is a difference between the two hostnames:
localhost.internal:8224... localhost.local:8224
Fixing this will probably bring the cluster back up.
Also, make sure to be able to resolve the hostnames with that domain suffix.
Kind regards,
Marco

I’ve just realised that the recovery mode feature is only available with the enterprise edition. So may be that the reason of the error