Full, differential and accumulative backups are same in size

I am running Couchbase Community Server 4.0
Here is my backup schedule.
Sunday - full
Thursday - accu
Rest of the days - diff

And this is how the backup folders are created.

drwxr-xr-x 7 root root 4096 Feb 7 01:04 2016-02-06T193002Z-full
drwxr-xr-x 7 root root 4096 Feb 8 01:05 2016-02-07T193003Z-diff
drwxr-xr-x 7 root root 4096 Feb 9 01:05 2016-02-08T193001Z-diff
drwxr-xr-x 7 root root 4096 Feb 10 01:05 2016-02-09T193001Z-diff
drwxr-xr-x 7 root root 4096 Feb 11 01:04 2016-02-10T193001Z-accu
drwxr-xr-x 7 root root 4096 Feb 12 01:04 2016-02-11T193001Z-diff
drwxr-xr-x 7 root root 4096 Feb 13 01:04 2016-02-12T193002Z-diff

Problem is all the above folders are same in size, no size difference between full, accu and diff.

Executing cbbackup as below, replacing $Mode with full or diff or accu.
cbbackup http://x.x.x.x:8091 $BackupDir -u $User -p $Pass -m $Mode

Am I doing something wrong?

Hey @jegan4u,

In Linux, all directories are 4096 bytes in size, this is the size that you are seeing when performing an ls in the backup directory.
More details of this can be found in this StackOverflow post.

A command such as du -sh * run in this directory would be more suitable to find the total sizes of those folders, hopefully you should see that these folders are not all the same size, with the full backup being larger than the others.
For reference here is the man page for du which details how to use it to determine file and directory sizes.

Thanks for the reply. I do understand the 4096 byte directory size.
What I really meant was the size I get in du -sh. Please see the size below.
diff backup is bigger than full backup and we don’t get that much data in a single day.

du -sh 2016-03-05T193001Z-full
5.5G 2016-03-05T193001Z-full

du -sh 2016-03-06T193002Z-diff
5.6G 2016-03-06T193002Z-diff

Same has been happening with me also. When I took full/diff/accu backup, I found out that all the 3 backups were of the same size.

@jegan4u Did you find something to handle or fix this?

Any help would be appreciated.


I am using Couchbase server Community Edition 6.0.0 and this issue is still there.
Any fix will be highly appreciated.


This is a limitation in Community Edition.