Problem: 30% of user tar.gz files fail to arrive at storage resoruce

[deliriant]

I'm using DA v1.40.1 on a CentOS 4 server.

Scheduled automatic system backups have been working with the exception that 17 out of the current total of 56 user directories are never transferred to the storage resource location. The storage resource account being used has unlimited space available.

Further information:
It's always the same 17 user directories that fail to show up at the storage space. And, strangely, a few of the md5 files for the aforementioned missing data files do transfer to the backup set at the storage space. The backup log in DA consistently shows no errors and always shows 'completed' for each of the user directories that never reach the storage space.

I've also noticed that upon each backup run there are 3 user directories which were deleted long ago (through the DA all users screen) that for some reason arrive at the storage space as empty 45 byte tar.gz files.

Does anyone know why this might be happening? File corruption somewhere perhaps?

 

[NoBaloney2]

Which backup are you creating? System Backup or Admin's Reseller Backup/Restore? If the former, then note that it doesn't have a restore function at all; you may want to switch.

It's always worked properly for me in the past; the only thing I can think of is that the configuration is very complex and if you've ever changed it you might have made an error somewhere.

Jeff

 

[deliriant]

Which backup are you creating? System Backup or Admin's Reseller Backup/Restore? If the former, then note that it doesn't have a restore function at all; you may want to switch.

It's always worked properly for me in the past; the only thing I can think of is that the configuration is very complex and if you've ever changed it you might have made an error somewhere.

Jeff

Thanks for the response.

Actually I'm using both of the backup options (the admin one and the system backup one). It's the 'system backup' option that's presenting the problems I've described. I have both of the backup options set to execute on cron trigger every week. The reason I'm using both of them is because the admin backup is the only one that will backup all of the users directories correctly and the system backup one at least makes a nice array of .gz zips from which i can easily retrieve specific files if/when customers lose or damage them - but only for the incomplete group of accounts that it sends to the storage space.

For info, I have never touched the configuration settings for DA's backup system, so it couldn't be that. I've only used the form to set up the backup schedules.

And by the way, what do you mean that it's not possible to restore from the system backup option? I know it backs up stuff from the /home /etc /usr and /var directories. Is it just intended to use it as I'm trying to use it (to pick out and restore certain files once in a while)? If not, what's it's purpose?

The other thing I'm not sure about is with the admin backup option. Although it does create backups of each of the users /home accounts, it has never backed up the system directories despite that I've placed check marks in all of the boxes for those system directories. So I guess I don't get why neither of the DA backup options seem to work quite right for me. I have another server running webmin. I wish DA would incorporate a backup system like webmin. That's because whatever directories I instruct webmin to backup it will compress and send to the destination I've chosen without issue.

 

[NoBaloney2]

I didn't write in this thread that it's not possible to restore from the system backup; I wrote that there's no restore function. Did I write that somewhere else? If so, let me know where and I'll fix it.

I'm not sure what you mean by the system directories; The admin reseller backup option backs up user space, not system space. Please be more specific if you can be.

Jeff

 

[deliriant]

I didn't write in this thread that it's not possible to restore from the system backup; I wrote that there's no restore function. Did I write that somewhere else? If so, let me know where and I'll fix it.

OK, now I understand what you mean. Simply that there's no restore function within system backup (which doesn't in any way suggest that you can't use the .gz files to restore the backed up elements). Please accept my apology for misinterpreting your words.

I'm not sure what you mean by the system directories; The admin reseller backup option backs up user space, not system space. Please be more specific if you can be.

And that's my second misunderstanding. Please be mindful that I just started using the admin backup/transfer option a few days ago (as an alternative) after realizing that the system backup option hasn't been backing up all of the user directories. Before that I was mainly used to webmin's backup system on my other CentOS server, where I have to individually create each backup cron task. My error in what I wrote to you is that I somehow incorrectly assumed all of the items under "step 4, what?" that are check marked by default included system folders as well. Obviously I didn't look at the labels very closely. So I apologize as well for not knowing what I was talking about in that regard.

So as things stand I'm still puzzled by the incomplete and erroneous backup transfers produced by the system backup option. And despite my bad record so far, I really don't think it's due to another misinterpretation on my part. All of the users are check marked and once the task finishes the log says that each user's backup was completed successfully. Yet the same ones are always missing and the same couple of long since removed accounts always show up as empty .gz zips. I suppose I'm still covered though because the system dirs seem to be there and the admin backup gets all of the user accounts.

 

[NoBaloney2]

OK, now I understand what you mean. Simply that there's no restore function within system backup (which doesn't in any way suggest that you can't use the .gz files to restore the backed up elements). Please accept my apology for misinterpreting your words.

No problem. The reason I always make the lack of a restore function clear is that these forums have a lot of posts from people who don't realize it until after they need a full backup restore, and don't have any idea how to go about it.

Before that I was mainly used to webmin's backup system on my other CentOS server,

While I do not recommend it, there's no reason why you couldn't set up Webadmin to backup a DirectAdmin server. There's a good reason not to use Webmin; misuse can easily break much of DirectAdmin's configuration, but if you just use it for backups and configure what you want backed up, it may work for you.

So as things stand I'm still puzzled by the incomplete and erroneous backup transfers produced by the system backup option. And despite my bad record so far, I really don't think it's due to another misinterpretation on my part. All of the users are check marked and once the task finishes the log says that each user's backup was completed successfully. Yet the same ones are always missing and the same couple of long since removed accounts always show up as empty .gz zips. I suppose I'm still covered though because the system dirs seem to be there and the admin backup gets all of the user accounts.

The only way I could figure it out would be to do forensic work on your server, and obviously, I'd have to charge for that. I no longer use it, and it's been a long time since I have, so don't have any additional insight at this time. Perhaps someone else does but I don't think too many people are using it anymore.

Jeff