The server with the databases has crashed and there are no backups, only a bunch of .frm, .myd, .myi, but the InnoDB database refuses to be restored categorically?

Question

MySQL

In general, everything is in order.
There was a beautiful server for several years, only databases were spinning on it.
At first, a backup was set up and everything was fine, but nothing crashed and there were no problems.
Then the cloud with the backup became outdated, moved, and as a result, database backups were no longer created.
Of course, there were no problems, and no one wanted to resolve the issue promptly.
But there is nothing more permanent than temporary, and as a result, the server stood for a year without a permanent backup.
They made copies manually once a month and that's it.
But today something happened that no one expected, the server burned down, the files were restored as best they could. And sites are needed, because now there is an active advertising campaign in the store and everything needs to be returned urgently, urgently.
This is apparently according to the law of meanness.
At first, everything seemed simple and cloudless, they made copies of the files that they managed to find, put them in the same folders, with the databases as they were, everything almost turned out.
But there are two problems, InnoDB fell off the fuck and does not start, respectively, does not restore databases from ibdata1.
.myd were found only for MyISAM tables, the rest of InnoDB are not restored, it gives an error.

Table 	Op 	Msg_type 	Msg_text 	
blokus.vht63_banners 	repair 	Error 	Unknown table engine 'InnoDB'
blokus.vht63_banners 	repair 	error 	Corrupt

Same error when exporting:

--
-- Структура таблицы `vht63_banners`
--
-- используется(#1286 - Unknown table engine 'InnoDB')
-- Ошибка считывания данных: (#1286 - Unknown table engine 'InnoDB')

And actually, InnoDB itself is not visible to the server at all.

mysql> SHOW ENGINES;
+------------+---------+-----------------------------------------------------------+--------------+------+------------+
| Engine     | Support | Comment                                                   | Transactions | XA   | Savepoints |
+------------+---------+-----------------------------------------------------------+--------------+------+------------+
| MRG_MYISAM | YES     | Collection of identical MyISAM tables                     | NO           | NO   | NO         |
| CSV        | YES     | CSV storage engine                                        | NO           | NO   | NO         |
| MyISAM     | DEFAULT | Default engine as of MySQL 3.23 with great performance    | NO           | NO   | NO         |
| MEMORY     | YES     | Hash based, stored in memory, useful for temporary tables | NO           | NO   | NO         |
+------------+---------+-----------------------------------------------------------+--------------+------+------------+

Answer 1

1 Do not touch anything and call the administrator - let him fix and set up backups.
2 If there is no admin, then everything is bad - you have damaged files, including the mysql server itself, what to do:
a) copy everything that is now in the backup backup and start experiments (there should always be a copy of the files because some actions can only worsen the condition )
b) reinstall mysql-server (maria db, perkona or whatever you have there, with the same version) check that the innodb engine appeared
c) google how to use mysqlcheck and myisamchk, then use it.