Skipped non-regular file?

Support
#1

Hi,

during my last backup I noticed this:

2021-10-30 01:08:59.462 INFO SNAPSHOT_FILTER Loaded 0 include/exclude pattern(s)
2021-10-30 01:09:09.104 WARN LIST_SKIP Skipped non-regular file paperless-ng_db/postgresql/.s.PGSQL.5432
2021-10-30 01:09:10.151 INFO BACKUP_THREADS Use 10 uploading threads

Any idea why that file was a “non-regular”?

Thanks!

#2

It’s probably a pipe or socket or device or reparse point, or other thing for interprocess communication, but not a usual file with a data stream.

How to discover what exactly duplicacy means by it? search for “non-regular” in duplicacy source. You will find this self explanatory snippet:

if f.Mode()&(os.ModeNamedPipe|os.ModeSocket|os.ModeDevice) != 0 {
                        LOG_WARN("LIST_SKIP", "Skipped non-regular file %s", entry.Path)
                        skippedFiles = append(skippedFiles, entry.Path)
                        continue
                }

Btw: you should not backup Postgres database (or any other running database for that matter) as is, the result will be non-restorable, even with -vss.

Instead, in pre-backup script export (dump) the database into a file and backup that file, and add exclusion for the database itself.

Alternatively, you need to ensure the database is closed when you run backup, which is impractical for most cases.

#3

I actually stop my dbs containers before Duplicacy starts and restart the dbs after the backup ends.

#4

Backups performed after do not have that warning in the log. So this is shown only once?

#5

That file was there because your database was running at the time of backup.

This illustrates one of the reasons why this approach:

is neither reliable nor reasonable. Indeed, why would you stop important user service for an unimportant background one?

Dump database in the pre-backup script, backup that dump, and exclude the database itself from a backup.

1 Like
#6

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.