[bareos-users] incremental backup same size as full

[Eric Browning]

Confused as to why my Full, Differential and Incremental backups are all the same size? I looked at job details and in each job it shows the same number of files in all three job types. I know that the 6.5M files on this server have not all changed.

Bareos server is ubuntu, clients so far are debian and macos.

I've read about ls -c or ls -lc in some ancient posts going back a few years but shouldn't this be resolved now?

[Damiano Verzulli]

Eric, to try to troubleshoot your issue, the related log messages are
required. Can you post them here?

Cheers,
DV


Il lun 30 lug 2018, 15:32 Eric Browning <

Post by Eric Browning
Confused as to why my Full, Differential and Incremental backups are all
the same size? I looked at job details and in each job it shows the same
number of files in all three job types. I know that the 6.5M files on this
server have not all changed.
Bareos server is ubuntu, clients so far are debian and macos.
I've read about ls -c or ls -lc in some ancient posts going back a few
years but shouldn't this be resolved now?
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[Eric Browning]

This is the set of messages from a differential job that backed up as a FULL even though it says differential.

2018-07-30 06:17:03 bareos-dir JobId 119: Bareos bareos-dir 17.2.4 (21Sep17):
Build OS: x86_64-pc-linux-gnu ubuntu Ubuntu 16.04 LTS
JobId: 119
Job: Staff.2018-07-30_02.05.00_58
Backup Level: Differential, since=2018-07-29 09:41:29
Client: "Staff" 17.2.4 (21Sep17) x86_64-pc-linux-gnu,debian,Debian GNU/Linux 9.3 (stretch),Debian_9.0,x86_64
FileSet: "Staff" 2018-07-27 20:00:00
Pool: "Weekly" (From Run Pool override)
Catalog: "MyCatalog" (From Client resource)
Storage: "File" (From Job resource)
Scheduled time: 30-Jul-2018 02:05:00
Start time: 30-Jul-2018 03:02:14
End time: 30-Jul-2018 06:17:03
Elapsed time: 3 hours 14 mins 49 secs
Priority: 4
FD Files Written: 6,502,309
SD Files Written: 6,502,309
FD Bytes Written: 2,184,677,025,753 (2.184 TB)
SD Bytes Written: 2,186,173,696,296 (2.186 TB)
Rate: 186900.3 KB/s
Software Compression: 9.3 % (lz4)
VSS: no
Encryption: no
Accurate: no
Volume name(s): Diff-0008
Volume Session Id: 13
Volume Session Time: 1532872330
Last Volume Bytes: 9,371,351,179,944 (9.371 TB)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK

2018-07-30 06:17:03 bareos-dir JobId 119: sql_create.c:872 Insert of attributes batch table done
2018-07-30 06:16:58 bareos-sd JobId 119: Elapsed time=03:14:44, Transfer rate=187.1 M Bytes/second
2018-07-30 06:16:09 bareos-dir JobId 119: sql_create.c:872 Insert of attributes batch table done
2018-07-30 05:54:41 bareos-dir JobId 119: sql_create.c:872 Insert of attributes batch table done
2018-07-30 05:30:57 bareos-dir JobId 119: sql_create.c:872 Insert of attributes batch table done
2018-07-30 05:09:30 bareos-dir JobId 119: sql_create.c:872 Insert of attributes batch table done
2018-07-30 04:25:59 bareos-dir JobId 119: sql_create.c:872 Insert of attributes batch table done
2018-07-30 04:00:51 bareos-dir JobId 119: sql_create.c:872 Insert of attributes batch table done
2018-07-30 03:40:23 bareos-dir JobId 119: sql_create.c:872 Insert of attributes batch table done
2018-07-30 03:24:49 bareos-dir JobId 119: sql_create.c:872 Insert of attributes batch table done
2018-07-30 03:02:31 staff-fd JobId 119: DIR and FD clocks differ by 16 seconds, FD automatically compensating.
2018-07-30 03:02:14 bareos-dir JobId 119: Using Device "FileStorage" to write.
2018-07-30 03:02:14 bareos-sd JobId 119: Ready to append to end of Volume "Diff-0008" size=7183322252918
2018-07-30 03:02:14 bareos-sd JobId 119: Volume "Diff-0008" previously written, moving to end of data.
2018-07-30 03:02:14 bareos-dir JobId 119: Start Backup JobId 119, Job=Staff.2018-07-30_02.05.00_58

[Dan]

Eric -

This sounds like the same issue reported here, https://groups.google.com/forum/#!topic/bareos-users/MlxluM-jf68.

I don't think he ever discovered the reason, but perhaps the debug will help you to troubleshoot.

Dan

[Eric Browning]

It's apparently an ongoing issue. How can I purge ALL backups made by all clients and start over? Some of the comments suggested date/time issues and I know my time is correct on both servers, same time zone and same NTP servers.

[Dan]

Eric -

I don't know if it's an ongoing issue because the previous report resolved itself, so no root cause was identified. I don't remember anything focusing on NTP or server timing. Broadly I would expect the problem falls into one of two buckets. 1) The code is not correctly identifying the last backup time or 2) The code is correctly identifying the last backup time and somehow thinks all of the files have changed. That was the point of the debug, was to try to find out which of these was occurring. I'm presuming that if it doesn't find ANY backups it will upgrade the current backup to a FULL, which is not what is happening to you.

If you really want to delete everything and start over, the simplest thing may be to delete the storage pool(s) from bconsole, then restart the director to recreate the pool.

Dan

[Eric Browning]

This was a new install so I dropped the database and recreated it and wiped out all of the stored backups in the raid. I will see what happens tonight.

[Eric Browning]

So I wiped it all out, and made rand some backup jobs that were promoted to Full but it is STILL backing up all types of jobs as FULL, even differential and incremental jobs.

Logs from an job that's run as all three types

FULL job:
2018-07-30 18:25:12 bareos-dir JobId 9: sql_create.c:872 Insert of attributes batch table done
2018-07-30 18:25:12 bareos-dir JobId 9: Bareos bareos-dir 17.2.4 (21Sep17):
Build OS: x86_64-pc-linux-gnu ubuntu Ubuntu 16.04 LTS
JobId: 9
Job: MySQL-Proxy.2018-07-30_17.51.20_33
Backup Level: Full
Client: "MySQL-Proxy" 17.2.4 (21Sep17) x86_64-pc-linux-gnu,ubuntu,Ubuntu 16.04 LTS,xUbuntu_16.04,x86_64
FileSet: "MySQL-Proxy" 2018-07-30 12:45:54
Pool: "Monthly" (From command line)
Catalog: "MyCatalog" (From Client resource)
Storage: "File" (From Job resource)
Scheduled time: 30-Jul-2018 17:51:20
Start time: 30-Jul-2018 18:21:01
End time: 30-Jul-2018 18:25:12
Elapsed time: 4 mins 11 secs
Priority: 1
FD Files Written: 59,812
SD Files Written: 59,812
FD Bytes Written: 19,380,835,123 (19.38 GB)
SD Bytes Written: 19,390,692,372 (19.39 GB)
Rate: 77214.5 KB/s
Software Compression: 32.8 % (lz4)
VSS: no
Encryption: no
Accurate: no
Volume name(s): MySQL-Proxy-Monthly-20180730-1821-9
Volume Session Id: 2
Volume Session Time: 1532994580
Last Volume Bytes: 19,408,377,338 (19.40 GB)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK

2018-07-30 18:25:11 bareos-sd JobId 9: Elapsed time=00:04:10, Transfer rate=77.56 M Bytes/second
2018-07-30 18:21:01 bareos-dir JobId 9: Start Backup JobId 9, Job=MySQL-Proxy.2018-07-30_17.51.20_33
2018-07-30 18:21:01 bareos-dir JobId 9: Created new Volume "MySQL-Proxy-Monthly-20180730-1821-9" in catalog.
2018-07-30 18:21:01 bareos-dir JobId 9: Using Device "FileStorage" to write.
2018-07-30 18:21:01 bareos-sd JobId 9: Labeled new Volume "MySQL-Proxy-Monthly-20180730-1821-9" on device "FileStorage" (/mnt/raid).
2018-07-30 18:21:01 bareos-sd JobId 9: Wrote label to prelabeled Volume "MySQL-Proxy-Monthly-20180730-1821-9" on device "FileStorage" (/mnt/raid)
2018-07-30 18:21:01 bareos-dir JobId 9: Max Volume jobs=1 exceeded. Marking Volume "MySQL-Proxy-Monthly-20180730-1821-9" as Used.

INCREMENTAL Job:
2018-07-30 21:02:44 bareos-dir JobId 12: sql_create.c:872 Insert of attributes batch table done
2018-07-30 21:02:44 bareos-dir JobId 12: Bareos bareos-dir 17.2.4 (21Sep17):
Build OS: x86_64-pc-linux-gnu ubuntu Ubuntu 16.04 LTS
JobId: 12
Job: MySQL-Proxy.2018-07-30_20.00.00_36
Backup Level: Incremental, since=2018-07-30 18:21:01
Client: "MySQL-Proxy" 17.2.4 (21Sep17) x86_64-pc-linux-gnu,ubuntu,Ubuntu 16.04 LTS,xUbuntu_16.04,x86_64
FileSet: "MySQL-Proxy" 2018-07-30 12:45:54
Pool: "Daily" (From Run Pool override)
Catalog: "MyCatalog" (From Client resource)
Storage: "File" (From Job resource)
Scheduled time: 30-Jul-2018 20:00:00
Start time: 30-Jul-2018 20:58:33
End time: 30-Jul-2018 21:02:44
Elapsed time: 4 mins 11 secs
Priority: 1
FD Files Written: 59,995
SD Files Written: 59,995
FD Bytes Written: 19,380,886,218 (19.38 GB)
SD Bytes Written: 19,390,783,595 (19.39 GB)
Rate: 77214.7 KB/s
Software Compression: 32.8 % (lz4)
VSS: no
Encryption: no
Accurate: no
Volume name(s): MySQL-Proxy-Daily-20180730-2058-12
Volume Session Id: 4
Volume Session Time: 1532994580
Last Volume Bytes: 19,408,474,986 (19.40 GB)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK

2018-07-30 21:02:42 bareos-sd JobId 12: Elapsed time=00:04:09, Transfer rate=77.87 M Bytes/second
2018-07-30 20:58:33 bareos-dir JobId 12: Start Backup JobId 12, Job=MySQL-Proxy.2018-07-30_20.00.00_36
2018-07-30 20:58:33 bareos-dir JobId 12: Created new Volume "MySQL-Proxy-Daily-20180730-2058-12" in catalog.
2018-07-30 20:58:33 bareos-dir JobId 12: Using Device "FileStorage" to write.
2018-07-30 20:58:33 bareos-sd JobId 12: Labeled new Volume "MySQL-Proxy-Daily-20180730-2058-12" on device "FileStorage" (/mnt/raid).
2018-07-30 20:58:33 bareos-sd JobId 12: Wrote label to prelabeled Volume "MySQL-Proxy-Daily-20180730-2058-12" on device "FileStorage" (/mnt/raid)
2018-07-30 20:58:33 bareos-dir JobId 12: Max Volume jobs=1 exceeded. Marking Volume "MySQL-Proxy-Daily-20180730-2058-12" as Used.

DIFFERENTIAL Job:
2018-07-31 03:27:32 bareos-dir JobId 23: sql_create.c:872 Insert of attributes batch table done
2018-07-31 03:27:32 bareos-dir JobId 23: Bareos bareos-dir 17.2.4 (21Sep17):
Build OS: x86_64-pc-linux-gnu ubuntu Ubuntu 16.04 LTS
JobId: 23
Job: MySQL-Proxy.2018-07-31_02.05.00_43
Backup Level: Differential, since=2018-07-30 18:21:01
Client: "MySQL-Proxy" 17.2.4 (21Sep17) x86_64-pc-linux-gnu,ubuntu,Ubuntu 16.04 LTS,xUbuntu_16.04,x86_64
FileSet: "MySQL-Proxy" 2018-07-30 12:45:54
Pool: "Weekly" (From Run Pool override)
Catalog: "MyCatalog" (From Client resource)
Storage: "File" (From Job resource)
Scheduled time: 31-Jul-2018 02:05:00
Start time: 31-Jul-2018 03:22:43
End time: 31-Jul-2018 03:27:32
Elapsed time: 4 mins 49 secs
Priority: 1
FD Files Written: 63,509
SD Files Written: 63,509
FD Bytes Written: 20,485,728,409 (20.48 GB)
SD Bytes Written: 20,496,169,997 (20.49 GB)
Rate: 70884.9 KB/s
Software Compression: 40.6 % (lz4)
VSS: no
Encryption: no
Accurate: no
Volume name(s): MySQL-Proxy-Weekly-20180731-0322-23
Volume Session Id: 8
Volume Session Time: 1532994580
Last Volume Bytes: 20,515,621,384 (20.51 GB)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK

2018-07-31 03:27:28 bareos-sd JobId 23: Elapsed time=00:04:45, Transfer rate=71.91 M Bytes/second
2018-07-31 03:22:43 bareos-dir JobId 23: Created new Volume "MySQL-Proxy-Weekly-20180731-0322-23" in catalog.
2018-07-31 03:22:43 bareos-dir JobId 23: Using Device "FileStorage" to write.
2018-07-31 03:22:43 bareos-sd JobId 23: Labeled new Volume "MySQL-Proxy-Weekly-20180731-0322-23" on device "FileStorage" (/mnt/raid).
2018-07-31 03:22:43 bareos-sd JobId 23: Wrote label to prelabeled Volume "MySQL-Proxy-Weekly-20180731-0322-23" on device "FileStorage" (/mnt/raid)
2018-07-31 03:22:43 bareos-dir JobId 23: Max Volume jobs=1 exceeded. Marking Volume "MySQL-Proxy-Weekly-20180731-0322-23" as Used.
2018-07-31 03:22:42 bareos-dir JobId 23: Start Backup JobId 23, Job=MySQL-Proxy.2018-07-31_02.05.00_43

[Eric Browning]

Still no resolution to this. I have three days worth of backups and they are FULL backups every single day. I'm eating up storage left right and sideways. What is the solution to this problem?

I have posted job logs and configurations. I am extremely dissatisfied with BareOS at this point to put it mildly.

[b***@jack.fr.eu.org]

Post by Eric Browning
I have posted job logs and configurations. I am extremely dissatisfied with BareOS at this point to put it mildly.

Did you ?
I cannot find your configuration in this thread, are you sure ?

Configuration looks like:
#
Client {
Name = backup1-fd
Description = "Client resource of the Director itself."
Address = backup1.fqdn
FDPort = 9102
Password = "ephohng3mitoinu3jooshoem3Theavoh"
Maximum Concurrent Jobs = 20
}

#
JobDefs {
Name = "DefaultJobConsolidate"
Type = Consolidate
Client = backup1-fd
Schedule = "Incremental"
Messages = Standard
Priority = 10
Accurate = yes

Pool = AI-Consolidated
Storage = File2
}

etc

[Eric Browning]

I will sanitize them and upload in about 15 minutes.

[Eric Browning]

Server configs and one client config attached.

I pulled out the other clients to keep it simpler. They're all configured the same with just differing priorities.

[Eric Browning]

I figured out the issue. In my client's fileset configuration I had the option "keepatime = yes" enabled. Got rid of it from fileset and changed it to "noatime = yes" and added "Accurate = yes" to the job definition. Now things backup as expected.