How to restore a MySQL database with InnoDB tables with a sector-by-sector copy?

Question

MySQL

You have a MySQL 5.6.10 database from a disk partition backup taken with Symantec System Recovery 2013 R2. I understand that using a sector-by-sector backup program is not entirely appropriate for MySQL, but still I would like to understand how realistic it is to start (reanimate) this database. When setting all paths and starting the MySQL service, the following information is displayed in the log file:

2016-01-02 11:07:34 7144 [Note] Plugin 'FEDERATED' is disabled.
2016-01-02 11:07:34 7144 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
2016-01-02 11:07:34 155c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2016-01-02 11:07:34 7144 [Note] InnoDB: The InnoDB memory heap is disabled
2016-01-02 11:07:34 7144 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-01-02 11:07:34 7144 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-01-02 11:07:34 7144 [Note] InnoDB: Not using CPU crc32 instructions
2016-01-02 11:07:34 7144 [Note] InnoDB: Initializing buffer pool, size = 1.0G
2016-01-02 11:07:34 7144 [Note] InnoDB: Completed initialization of buffer pool
2016-01-02 11:07:34 7144 [Note] InnoDB: Highest supported file format is Barracuda.
2016-01-02 11:07:34 7144 [Note] InnoDB: Log scan progressed past the checkpoint lsn 392051760322
2016-01-02 11:07:34 7144 [Note] InnoDB: Database was not shutdown normally!
2016-01-02 11:07:34 7144 [Note] InnoDB: Starting crash recovery.
2016-01-02 11:07:34 7144 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-01-02 11:07:37 7144 [Note] InnoDB: Restoring possible half-written data pages 
2016-01-02 11:07:37 7144 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 392052903240
2016-01-02 11:07:39 7144 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2016-01-02 11:07:41 7144 [Note] InnoDB: 128 rollback segment(s) are active.
2016-01-02 11:07:41 7144 [Note] InnoDB: Waiting for purge to start
2016-01-02 11:07:41 7144 [Note] InnoDB: 5.6.10 started; log sequence number 392052903240
2016-01-02 11:07:41 7144 [ERROR] Aborting

2016-01-02 11:07:41 7144 [Note] Binlog end
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'partition'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_METRICS'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_CMPMEM'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_CMP'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_LOCKS'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'INNODB_TRX'
2016-01-02 11:07:41 7144 [Note] Shutting down plugin 'InnoDB'
2016-01-02 11:07:41 7144 [Note] InnoDB: FTS optimize thread exiting.
2016-01-02 11:07:41 7144 [Note] InnoDB: Starting shutdown...
2016-01-02 11:07:46 7144 [Note] InnoDB: Shutdown completed; log sequence number 392052905321
2016-01-02 11:07:46 7144 [Note] Shutting down plugin 'BLACKHOLE'
2016-01-02 11:07:46 7144 [Note] Shutting down plugin 'ARCHIVE'
2016-01-02 11:07:46 7144 [Note] Shutting down plugin 'MRG_MYISAM'
2016-01-02 11:07:46 7144 [Note] Shutting down plugin 'MyISAM'
2016-01-02 11:07:46 7144 [Note] Shutting down plugin 'MEMORY'
2016-01-02 11:07:46 7144 [Note] Shutting down plugin 'CSV'
2016-01-02 11:07:46 7144 [Note] Shutting down plugin 'sha256_password'
2016-01-02 11:07:46 7144 [Note] Shutting down plugin 'mysql_old_password'
2016-01-02 11:07:46 7144 [Note] Shutting down plugin 'mysql_native_password'
2016-01-02 11:07:46 7144 [Note] Shutting down plugin 'binlog'
2016-01-02 11:07:46 7144 [Note]

I don't understand the reason why the process of starting the MySQL service is interrupted:
2016-01-02 11:07:41 7144 [ERROR] Aborting
An attempt to start MySQL with the innodb_force_recovery key specified in the configuration with a value increasing in order from 1 does not give the proper result.
What can be done in this situation?

Answer 1

You have tried these methods, there is no other way, just have backups. I do table-by-table dumps with a lock of the entire database for all backups