Over last 3 days my Linux clients (two, one is on the urbackup server) have gone crazy.
Each has had over 30 incremental file backups run each day.
Been running a cleanup now for hours.
Max incremental backups setting is 32.
Just one shows as having 166 incremental file backups in the backup folder.
It takes about 2 minutes to delete one.
One is down to 163, the other is down to 39 incremental file backups.
Going to take a while to get town to 32 for the one.
I’ve disable all Linux backups until can get this resolved.
FYI - Backups show as successful. Server 2.2.8 Client 2.2.5
Over last 3 days my Linux clients (two, one is on the urbackup server) have gone crazy.
Each has had over 30 incremental file backups run each day.
I am unsure how you got this , the interval is in hour , so if you put 1 , you d get max 24 backup per day not 30.
Can you show a screenshot of the settings you use?
Been running a cleanup now for hours.
You can run urbackupsrv cleanup (better look at the manual for exact syntax) that allow you to specify a disk space or backup number directly (you wont have to click and wait for deletion)
Max incremental backups setting is 32.
Just one shows as having 166 incremental file backups in the backup folder.
That s possible, if you also have archiving enabled, because archive don t count against max backup.
Or is it that the backup folder shows 166 folders, but not the ui?
It takes about 2 minutes to delete one.
One is down to 163, the other is down to 39 incremental file backups.
Going to take a while to get town to 32 for the one.
As i said before , look at the cleanup command
FYI - Backups show as successful. Server 2.2.8 Client 2.2.5
The problem started when you updated to 2.2.8 , or when did changed some config?
I ran the remove-unknown command and it is deleting backups greater that 32.
One finished, the other is down to 106. The remove-unknown is showing the count each time it removes one.
Don’t know if it means anything, but they were starting about every 8 minutes.
Been running 2.2.8 for a while
I don’t do archiving. Here are settings.
Be carefull, the remove unknown is super long (takes 3 days for me).
Because it compares each files on the disk to the database.
If you dont want to spend a few day on this , maybe cancel while it still deleting backup like this.
The logs will look very different once its at th next step.
Still it s good to run it once in a while.
Hence why i suggested the cleanup , which just delete the unwanted backups.
What you may also check is for client side settings.
On the client you can also set some frequency for backups. (it s kinda confusing, i know)
So if you have a gui installed on the client just start it and look at them.
On linux you may read them via /usr/local/var/urbackup/data/settings.cfg
On windows that would be something like c:\program files\urbackup\settings.cfg
remove-unknown has never taken this long, obliviously because it never had this many backups to deal with, and nightly cleanup would take care of whatever was necessary.
I didn’t think to look at client side settings.
One thing I found that conflicts with Web tool is this:
allow_starting_full_image_backups_def=true
allow_starting_incr_image_backups_def=true
Maybe it doesn’t matter since Web tool says Image backups are not supported.
update_freq_incr_def=86400 <-- 86400 seconds in 24 hours
The deleting of files just finished.
Checked system clocks and they were OK.
Now still need to know why they run every 8 minutes or so.
The exponential backoff is 40 min. These were running every 7-8 minutes.
Since the Web tool indicated the backups were successful, I didn’t look at Server log.
Looks like I have a serious problem with the database.
These errors have been in there for a few days:
2018-03-16 00:03:54: ERROR: Backing up database failed. Copying urbackup/backup_server.db-wal to /PC_Backups/urbackup/backup_server.db-wal~ failed. No such file or directory (code: 2)
2018-03-16 00:03:56: ERROR: Backing up database failed. Copying urbackup/backup_server_settings.db-wal to /PC_Backups/urbackup/backup_server_settings.db-wal~ failed. No such file or di$
2018-03-16 00:04:03: ERROR: Backing up database failed. Copying urbackup/backup_server_files.db-wal to /PC_Backups/urbackup/backup_server_files.db-wal~ failed. No such file or director$
2018-03-16 00:04:05: ERROR: Backing up database failed. Copying urbackup/backup_server_links.db-wal to /PC_Backups/urbackup/backup_server_links.db-wal~ failed. No such file or director$
2018-03-16 00:04:07: ERROR: Backing up database failed. Copying urbackup/backup_server_link_journal.db-wal to /PC_Backups/urbackup/backup_server_link_journal.db-wal~ failed. No such fi$
I ran database-repair this morning.
No errors on screen, but these (9 of them) were in the log.
2018-03-17 09:01:28: WARNING: SQLite: statement aborts at 27: [UPDATE clients SET lastseen=datetime(?, ‘unixepoch’) WHERE id=?] attempt to write a readonly database errorcode: 1032
2018-03-17 09:01:28: ERROR: Error in CQuery::Execute - attempt to write a readonly database Stmt: [UPDATE clients SET lastseen=datetime(?, ‘unixepoch’) WHERE id=?]
