# Backup failing up giving indexing file error **URL:** \ **Category:** ScyllaDB\ **Tags:** error-message, backup-restore\ **Created:** [June 10, 2025, 1:29pm UTC](https://forum.scylladb.com/t/backup-failing-up-giving-indexing-file-error/4898 "2025-06-10T13:29:54Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![aditya\_choudhary](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/aditya_choudhary/32/1734_2.png) [@aditya\_choudhary](https://forum.scylladb.com/u/aditya_choudhary)\ **Post date:** [June 10, 2025, 1:29pm UTC](https://forum.scylladb.com/t/backup-failing-up-giving-indexing-file-error/4898/1 "2025-06-10T13:29:54Z")
_Installation details_ Running a 3 node scylla cluster in GKE. #ScyllaDB version: 6.2.0 #Cluster size: 3 #os (RHEL/CentOS/Ubuntu/AWS AMI): Ubuntu Hello guys, Using scylla manager for scheduled backup. After some successful backup iterations, it gets failed showing indexing file error ![Screenshot 2025-03-06 at 10.14.27 AM](https://us1.discourse-cdn.com/flex016/uploads/scylladb/original/2X/7/707b1334ccd096358538914ca316a398a1595a53.png) ---
**Author:** ![Gabriel](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/gabriel/32/60_2.png) [@Gabriel](https://forum.scylladb.com/u/Gabriel)\ **Post date:** [June 13, 2025, 2:45pm UTC](https://forum.scylladb.com/t/backup-failing-up-giving-indexing-file-error/4898/2 "2025-06-13T14:45:20Z")
Looking at your error, the backup is failing because Scylla Manager can’t find any files to index on node 10.240.5.5. Since this worked before and now suddenly fails, here’s what I’d check: **First, verify if there’s actually data to backup:** - SSH into the failing node (10.240.5.5) and check `/var/lib/scylla/data/` - Look for your keyspace directories and see if there are any .db files (SSTables) - Run `du -sh /var/lib/scylla/data/your_keyspace_name/` to see actual data size - If it shows 0 bytes or the directory is missing, that’s your problem **Check what happened to your data:** - Did someone accidentally truncate or drop tables recently? - Was there a major compaction that might have removed all data? - Check if this specific node is properly part of the cluster: `nodetool status` - Verify the node can see the keyspaces: `cqlsh -e "DESC KEYSPACES"` **Verify backup configuration:** - Double-check your backup task configuration - make sure it’s targeting the right keyspaces/tables - Run `sctool task list` to see your backup tasks - Compare the working vs failing backup configurations ---
**Author:** ![Pritam\_Nagar](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/pritam_nagar/32/1636_2.png) [@Pritam\_Nagar](https://forum.scylladb.com/u/Pritam_Nagar)\ **Post date:** [June 30, 2025, 5:52am UTC](https://forum.scylladb.com/t/backup-failing-up-giving-indexing-file-error/4898/3 "2025-06-30T05:52:17Z")
This is the logs of scylla-manger {“L”:“ERROR”, “M”:“Indexing snapshot files failed on host”, “N”:“backup.index”, “S”:“github/scylladb/go-log.Logger.log github/scylladb/go-log@v0.0.7/logger.go:101 github/scylladb/go-log.Logger.Error github/scylladb/go-log@v0.0.7/logger.go:84 github/scylladb/scylla-manager/v3/pkg/service/backup.(\*worker).Index.func2 githubcom/scylladb/scylla-manager/v3/pkg/service/backup/worker\_index.go:33 githubcom/scylladb/scylla-manager/v3/pkg/service/backup.hostsInParallel.func2 githubcom/scylladb/scylla-manager/v3/pkg/service/backup/parallel.go:89 githubcom/scylladb/scylla-manager/v3/pkg/util/parallel.Run.func1 githubcom/scylladb/scylla-manager/v3/pkg/util@v0.0.0-20241104134613-aba35605c28b/parallel/parallel.go:79”, “T”:“2025-06-22T06:00:08.273Z”, “\_trace\_id”:“UORGpSjeQWKBAeP43xVHKw”, “error”:“10.244.11.91: could not find any files”, “errorStack”:"githubcom/scylladb/scylla-manager/v3/pkg/service/backup.hostsInParallel.func1 githubcom/scylladb/scylla-manager/v3/pkg/service/backup/parallel.go:86 githubcom/scylladb/scylla-manager/v3/pkg/util/parallel.Run.func1 githubcom/scylladb/scylla-manager/v3/pkg/util@v0.0.0-20241104134613-aba35605c28b/parallel/parallel.go:72 runtime.goexit runtime/asm\_amd64.s:1700 ", “host”:“10.244.11.91”} Backup’s coming properly after reschedule until this disaster comes.