Assistance needed restoring a 7.5 TB ServiceNow-provided MariaDB SQL dump
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
We are currently trying to restore a 7.5 TB MariaDB SQL dump provided by ServiceNow into a customer-managed MariaDB environment for historical data querying and archival purposes.
The target MariaDB server is running the same MariaDB version as the source/export environment.
During the restore process, we have encountered several issues.
SQL import fails with an escape-character-related error
During the import, the MariaDB client reports an error similar to:
Unknown command involving a backslash escape character
It appears that some backslash escape sequences contained in the SQL dump are being interpreted by the MariaDB command-line client rather than being treated as SQL data.
Connection to the MariaDB server is lost during the restore
Because the dump file is approximately 7.5 TB, the import process takes a very long time. During the restore, we sometimes lose the connection to the MariaDB server.
We would appreciate guidance regarding the following questions:
Is there a recommended MariaDB configuration file for restoring large SQL dumps provided by ServiceNow?
Are there specific MariaDB parameters that should be configured for a multi-terabyte restore, such as max_allowed_packet, InnoDB buffer pool, redo log settings, timeout settings, or InnoDB page size?
Does ServiceNow recommend a particular restore/import method for SQL dump files provided as part of a data export?
Are there any MariaDB client settings or SQL modes required to correctly process escape characters contained in the dump?
Is it supported or recommended to split the large SQL dump into multiple files or tables and restore them separately?
Does the target MariaDB instance need to use the same innodb_page_size as the ServiceNow source database? If so, how can we determine the page size used by the source environment?
Are there any ServiceNow documents, KB articles, or customer examples describing how to restore a ServiceNow-provided MariaDB SQL dump into a customer-managed MariaDB environment?
Our objective is not to run a ServiceNow application instance on this database. The restored database will only be used for historical data querying and archival purposes.
Environment:
MariaDB version: 10.4.20
Dump size: approximately 7.5 TB
Operating system: Red Hat Enterprise Linux 7.8
CPU: 8 cores
Memory: 32 GB
Restore method: MariaDB command-line client
Any recommended configuration examples, documentation, or recovery procedures would be greatly appreciated.
Thanks.
