From 1055f382fc36d4c2f6876c5347aa00afec8aa0f6 Mon Sep 17 00:00:00 2001
From: Eli Ribble <eli@theribbles.org>
Date: Mon, 5 Jan 2026 14:09:27 +0000
Subject: [PATCH] Move nidus sync to its own backup buckets

When doing the restore recently it seemed likely that there were
conflicts with sharing the buckets.
---
 modules/system/nidus-sync.nix | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/modules/system/nidus-sync.nix b/modules/system/nidus-sync.nix
index 141fca9..29d0db7 100644
--- a/modules/system/nidus-sync.nix
+++ b/modules/system/nidus-sync.nix
@@ -56,7 +56,7 @@ in {
 				"--keep-monthly 2"
 				"--group-by tags"
 			];
-			repository = "s3:s3.us-west-004.backblazeb2.com/gleipnir-backup-deltamvcd/database";
+			repository = "s3:s3.us-west-004.backblazeb2.com/gleipnir-backup-nidus-sync/database";
 		};
 		services.restic.backups."${backupName}-files" = {
 			environmentFile = "/var/run/secrets/restic-env";
@@ -68,7 +68,7 @@ in {
 			paths = [
 				(builtins.toString dataDirectory)
 			];
-			repository = "s3:s3.us-west-004.backblazeb2.com/gleipnir-backup-deltamvcd/files";
+			repository = "s3:s3.us-west-004.backblazeb2.com/gleipnir-backup-nidus-sync/files";
 			
 		};
 		sops.secrets."${secretsName}" = {