https://www.stellarinfo.com/blog/how-to-use-eseutil-for-exchange-database-repair/
If you need to backup without integrity check, maybe your Exchange DB needs to be repaired ?
Points to Remember Before Using EseUtil for Exchange Database Repair
You must remember the following important points before using the EseUtil:
Prerequisites to Run EseUtil
Before you run EseUtil to verify, modify, or repair Exchange databases, you must ensure the following prerequisites,
EseUtil is located in the program files uexchange path
C:\Program Files\Microsoft\Exchange Server\V15\Bin\
To identify the database state, use the /MH switch. If the state is displayed as Clean Shutdown, there shouldn’t be any issues and the database can be easily mounted after moving all the log files to a different location.
However, if the database is in Dirty Shutdown state, the database won’t mount. This indicates an inconsistent or corrupt database. This may occur due to missing or deleted log files and when log files are not committed to the database.
The command to check database consistency or state is as follows,
c:> eseutil /mh <database file name>
If your database is in Dirty Shutdown, you will see another line under it, which mentions the log file that is required. The next step is to check if the logs are healthy or if there is a problem with the logs. To do this, use the ML prefix with EseUtil and the log path that you can copy from the Log Required section of the report.
c:> eseutil /ml "M:\mbx01\logs"
IsInteg tool for Index Repair. IsInteg is a repair only utility that understands relation between tables and records and turns them into folders and messages. The tool is located at the following location,
C:\Program Files\Exchsrvr\bin>
Then run the IsInteg test by using the following command,
c:> Isinteg –s <server_name> -fix –test alltests
You may repeat the command multiple times to get rid of errors. Once errors are fixed, you can mount the database.
Further, you can use New-MailboxRepairRequest, if you have Exchange Server 2010 with SP1 or later versions, before mounting the database on the server. One more thing, you cannot stop the process once it started. If you stop it anyway, it may cause even more damage to the database. However, if all goes well, you will be able to mount the database.