Does transaction log grow in MS SQl 2012? , base in the mirror, how to reduce the log?

Question

SQL

Good afternoon, I need help.
There is a cluster of 2 nodes and 1 quorum disk. The cluster supports the clustered service (by priority). The application runs on MS SQL 2012 and has a modular structure for connecting to the database from workstations.
In MS SQL 2012, database mirroring is configured (between two nodes), naturally with the FULL model.
At the moment, the database weighs 23 GB, the transaction log is 210 GB, and it inevitably grows.
Concerned about the fact that very soon the disk space will run out, I want to know what to do.
How to truncate the transaction log?
The recovery model does not change from full to simple unless the mirror is disabled. If I turn off the mirror and compress the log through reorganization, then re-configure the mirror again?
Basically, I don't know what to do. Help

Answer 1

In order for the log not to grow, you need to save the log.
That is, in addition to mirroring, you must periodically save the database and the data log.
Saving the log will stop the log file from growing. In this case, the file cannot be reduced immediately, since the end of the file will be used by the sql server. When you save the log for the second time after some time, the sql server will let you reduce the file.
NB: You may need up to 210 GB to save the log.

Answer 2

also under the full recovery model when a transaction log is backed up

Transaction log compression .