From ba6c7b9618fc6cf7bc78760adb028f0eb84e1704 Mon Sep 17 00:00:00 2001
From: shats <admin@shts.su>
Date: Wed, 11 Feb 2026 13:20:24 +0700
Subject: [PATCH] refactor(mikrotikBackupScheduler): improve logging for backup
 scheduler and remove initial backup on container restart

---
 backend/services/mikrotikBackupScheduler.js | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)

diff --git a/backend/services/mikrotikBackupScheduler.js b/backend/services/mikrotikBackupScheduler.js
index 2311551..5232cb5 100644
--- a/backend/services/mikrotikBackupScheduler.js
+++ b/backend/services/mikrotikBackupScheduler.js
@@ -160,21 +160,19 @@ function initMikrotikBackupScheduler(logger) {
     Number(process.env.MIKROTIK_BACKUP_INTERVAL_MINUTES || DEFAULT_INTERVAL_MIN) || DEFAULT_INTERVAL_MIN;
   const intervalMs = Math.max(5, intervalMin) * 60 * 1000;
 
+  const intervalMinutes = intervalMs / 60000;
   log.info(
     {
       component: 'mikrotik-backup',
-      intervalMinutes: intervalMs / 60000,
+      intervalMinutes,
+      nextRunInMinutes: intervalMinutes,
       servers: process.env.MIKROTIK_BACKUP_SERVERS || 'all jumphost',
     },
-    'Starting automatic MikroTik backup scheduler',
+    'Automatic MikroTik backup scheduler started (no backup on startup, first run in %d min)',
+    intervalMinutes,
   );
 
-  // Первый запуск с небольшой задержкой, чтобы сервер успел подняться
-  setTimeout(() => {
-    runBackupOnce(log);
-  }, 30_000);
-
-  // Периодический запуск
+  // Только по расписанию — без бэкапа при перезапуске контейнера
   setInterval(() => {
     runBackupOnce(log);
   }, intervalMs);