New Axigen server doesn't recognize old message storage

Old server 10.2.2 on Debian crashed. Wouldn’t Restart.
Installed new 10.3.2 on proxmox debian container and copied
old domains folder to /var/opt/axigen. New server started seemingly
ok. However did not pickup messages.2 as storage.

@pkmorrison

I don’t get exactly what are the steps you did. But seems you created the domain on the new server and copied the old folder afterwards. In which the settings will become different. Because newly created domain will give you message container (messages) as default 1, you need to create the other containers so they will be recognize. or you can do it manually by editing the axigen.cfg file under run folder. This case you can declare all your existing containers properly.

Regards,
Jay

Thanks for your reply. - The solution provided by axigen support was to
enter messages.2 in axigen.cfg

Yes correct. As I said as well

“or you can do it manually by editing the axigen.cfg file under run folder. This case you can declare all your existing containers properly.”

Regards,
Jay