I cannot restore a backup

[Sven_Born]

Great!

Just to summarise for myself:
Your backup file is located at /home/fazenda/backups/backup219.29112019.
The volume option of the docker command is: -v /home/fazenda/backups:/backups.

If the above is correct …

You can run the docker container and restore your backup using the command:
docker run -d -p 60001:60001 -p 8190:8190 -e ACCEPT_EULA=Y -e ADA_RESTORE_BCK=/backups/backup219.29112019 -v /home/fazenda/backups:/backups --name adabas-db softwareag/adabas-ce:7.1.1

or optionally add -e ADADBID=123 if the DBID in the backup file is 123 and not 1:
docker run -d -p 60001:60001 -p 8190:8190 -e ACCEPT_EULA=Y -e ADA_RESTORE_BCK=/backups/backup219.29112019 -e ADADBID=123 -v /home/fazenda/backups:/backups --name adabas-db softwareag/adabas-ce:7.1.1

[ls1000 (Lucimar Silva)]

keeps giving error

ou accepted the license agreement
02/27/23-20:16:20: Initialize environment
%ADAINS-I-CRFISUC, file /data/etc/ADABAS.INI created successfully.
02/27/23-20:16:20: Start Docker container for Adabas

SHOWIPC for ADABAS 7.1.1.0 (Linux 64Bit)

%ADASET-W-INVDBID, database 123 not known on node b8f3a9444ce9
02/27/23-20:16:20: Create Adabas demo database
Going to create database with ID 123.
Database with ID 123 successfully created.
02/27/23-20:16:24: Restore backup=/backups/backup219.29112019 an files *
2023-02-27 20:16:24 %ADABCK-I-STARTED, 27-FEB-2023 20:16:24, Version 7.1.1.0 (Linux 64Bit)
2023-02-27 20:16:24 %ADABCK-I-DBOFF, database 123 accessed offline
2023-02-27 20:16:24 %ADABCK-F-OPNERR, Dataset BCK001, file /backups/backup219.29112019 could not be opened
2023-02-27 20:16:24 %ADABCK-F-ILLLOG, illegal log number detected, present 1, expected 256
2023-02-27 20:16:24 %ADABCK-I-IOCNT, 2 IOs on dataset ASSO
2023-02-27 20:16:24 %ADABCK-I-IOCNT, 0 IOs on dataset BCK001
2023-02-27 20:16:24 %ADABCK-I-ABORTED, 27-FEB-2023 20:16:24, elapsed time: 00:00:00
02/27/23-20:16:24: Restore of Adabas database backup fails

[Sven_Born]

Are you sure that backup219.29112019 is a valid backup file that was created using adabck dbid=... dump=... ...?

Please provide the output of the following two commands

xxd -l 64 /home/fazenda/backup219.29112019

xxd -e -l 64 /home/fazenda/backup219.29112019

[ls1000 (Lucimar Silva)]

xd -l 64 backup219.29112019
00000000: 5de1 75d0 5de1 7561 0001 0000 1002 332e ].u.].ua…3.
00000010: 332e 342e 0000 0000 6164 6174 6573 6f75 3.4…adatesou
00000020: 0001 0001 00db 0000 0000 0000 0000 0000 …
00000030: 0000 0000 0000 0000 0000 0000 0000 0000 …

xd -e -l 64 backup219.29112019
00000000: d075e15d 6175e15d 00000100 2e330210 ].u.].ua…3.
00000010: 2e342e33 00000000 74616461 756f7365 3.4…adatesou
00000020: 01000100 0000db00 00000000 00000000 …
00000030: 00000000 00000000 00000000 00000000 …

[Sven_Born]

Okay, it is a backup file. Unfortunately it has been created with Adabas Version 3.3.4. which is out of support for years, see also ADABCK ILLLOG - Forum - Adabas & Natural - Software AG Tech Community & Forums.
Since you are trying to do a cross-platform backup/restore from a big-endian (Solaris) to a little-endian machine (Docker Linux) you need to have a backup file at least from Adabas version 6.3.

In principle you need to upgrade your backup/database on your Solaris machine until you reach at least Adabas version 6.3. using the adacvt Adabas utility.
From this point you should be able to do a cross-platform backup/restore from your big-endian Solaris machine and restore it on any other little-endian platform.

Reach out for your Software AG support team. I guess they can help you taking the steps necessary to restore your data in one of the latest Adabas versions and run it in docker, cloud or wherever.