Admin backup -> Wrong size!! (bug?)

[Richard G]

I'm running DA 1.50 and wanted to do a backup and transfer of an account so I used the backup/transfer option under admin.
This account was about 77 GB big, so very big.
Reason for this was there were a lot of backups in /home/user/back which were not prsent in the admin backup.

Strangely enough, after a while, DA gave a notice the backup was ready.

User foobar has been backed up. <0:05:23>
The Admin backups have been created in /home/admin/admin_backups <0:05:23>

We looked in /home/admin/admin_backups and that backup was only 1,8 GB in size. Which was not possible.

After that, we deleted all of those backups (about 50 GB in size), and some other files we did not need anymore and started another backup and this time use the option to instantely transfer it to the new server.

At this moment, the backup is already 3.6 GB and still running (and counting) on the new server.

So my question is, how can it be the backup was finished locally at 1.8GB size?
And if the reason was quota or lack of space, why did the system only said backup was ready and not a single error was given?

This is the size at this moment:

28K /home/foobar/.softaculous
8.0K /home/foobar/softaculous_backups
4.0K /home/foobar/.php
4.0K /home/foobar/backups
456K /home/foobar/.razor
18M /home/foobar/.spamassassin
5.8G /home/foobar/domains
1.3G /home/foobar/imap
7.0G /home/foobar/

Disk space:

Filesystem      Size  Used Avail Use% Mounted on
/dev/md2        1.8T  239G  1.5T  14% /
tmpfs            16G   28K   16G   1% /dev/shm
/dev/md1        496M  144M  328M  31% /boot
/var/tmpMnt     5.6G   14M  5.3G   1% /tmp

 

[Richard G]

Oke now watch this... backup declared ready again by DA message. Transfer is also done.

Now locally on the old server we see this:

rw-r----- 1 admin foobar 18G 2016-03-15 00:05 user.admin2.foobar.tar.gz

And this is on the new server:

-rw-r--r-- 1 admin admin 5.9G 2016-03-15 00:41 user.admin2.foobar.tar.gz

Difference: 12,1 GB

How is this possible?

 

[zEitEr]

Hello,

And how is the smallest backups? Is it corrupted? Did you try to unpack it and see what is missing?
Could it be so that you excluded a data from it when creating a backup task?

 

[Richard G]

I also thought like you, could there be missing something? So after restoring on the new server I did a check like this on both servers:

du -ch | grep total

which should give total size of the content of foobar's home directory, correct?
So I did:

cd /home/foobar
/home/foobar]# du -ch | grep total
7.6G total

And this was on -both- servers. So it seemed nothing is missing.

It seems the owner, had been deleting things in the meantime. He normally really -never- does anything when he knows backup has been started.
So that must have been the issue.
I made a new backup on the new server to be sure and that one is 5.9G now too, so that is ok.

Still 1 issue is left, and that is the first one.
Why did the first backup stop at 1.8G size, without any error notice, while at that moment, the total directory content was about 77 GB?
Could this be caused by the owner deleting things via the file manager? And if yes, why no error notice but only the default notice that the backup was ready?

 

[zEitEr]

We could play with our fantasy and try to guess a real reason. I'm sure it's not what you need. I've never seen such a situation, so I have no idea what could have gone wrong. What I know for sure, that directamin does backups the following way:

1. copy data into a temp location
2. gzip data in a temp location
3. remove data from temp location.

As soon as data was copied into a temp location it stopped to have any importance whether or not user removed anything from an account.
In a theory it should has dropped an error if data was removed while the first step was running. How would directadmin deal with this hardly can I say, as I did not test it.

 

[Richard G]

Well at least after checking things, everything which should be transferred has been transferred.
And I definately pointed out to the owner that next time on a backup/transfer, he should do as he always has done, keep his hands of or wait until I tell him he can add or remove things, like we always did.

Thank you Alex!