How to set up a correct 1C database maintenance plan in MS SQL Server for a full recovery model?

Question

1C

There is a small organization, it has a server on which Microsoft SQL Server 2012 and 1C: Enterprise are installed, there are several databases, the largest of which is ~ 60 GB, the maintenance plan is configured according to the recommendations from this source ( link), in fact, many resources indicate a similar algorithm for the "correct" 1C database maintenance sequence in the MS SQL Server bundle, namely: Full recovery model, full database backup - once a week, differential backup - every day and transaction log - every 10-30 minutes . At the same time, when backing up, there are points in the plan to Rebuild or Reorganize the Index, in fact, as I understand it, there is a problem in them, namely, at the time of these operations, the log log overflows the disk on which there is not much free space (about 60 GB), while the log grows > 60, the disk overflows and actually further you have to manually switch to a simple recovery model, cut off the transaction log.
Also, many recommend at the time of large-scale operations with the database (which include operations with the index, as I understand it) to switch the recovery mode to "Incomplete logging". I also tried this - it does not help, the log is still overflowing. The most incomprehensible thing for me is that the weight of the transaction log backup after a full backup takes more than the database itself, i.e. > 50 GB, and this is also unnecessary unnecessary information that takes up a lot of space on the backup server. Actually, I would like to ask if there is a more correct maintenance plan for MS SQL SERVER for 1C, in which the log will not grow and take up extra space on the backup server?

Answer 1

https://its.1c.ru/db/metod8dev/browse/13/-1/1989/2...
Recommendations 1C.
By time... You have 24 hours of full-time work...
Delete the log... do you need it?.... Ask yourself this question. when you used it. Know how to use.
In my practice, the use of the log was somewhere 1-3 times ..

Answer 2

Use a simple recovery model, + incremental backups more often.
Full once a day, incremental times in 30-60 90 or whatever you want.
Ful will process all indexes at night when there are not so many loads.
The problem with the logs will disappear.