twhiting9275
Verified User
There are some pretty huge backup discrepencies here that need to be fixed, from a user (and admin's) POV.
I had to do some moving of accounts this weekend (changing providers, all that), and ran through the DA admin backup process. No options were unchecked (all were checked), the process was begun from the administrative panel, as 'admin'. Backups were made to /home/admin/backups, and backups restored on new machine as /home/admin/backups/ .. Should work as designed, and restore the whole account, right? One would logically think so,, right? Yeah, not so much
Even looking at the daily backups made via cron (again, through admin panel), there are discrepencies that need to be resolved. When you say you're going to backup an account, one would actually expect the whole account (as the user has it) to be backed up, not parts of it, not conveniently leaving out what you don't want to back up, but the whole account !
For starters:
Cron jobs ... Not backed up properly . Not a huge deal for a server admin, but again, when you say you're going to back something up, it needs to be done properly.
Now, the account (homedir) itself.... I noticed some size discrepencies from my own backups (.tar.bz2) and yours (.tar.gz) . Total about a gig and a half missing (from 10 accounts), so I did some digging.. What I found was pretty alarming... Directadmin leaves directories out of the home backup for the user. Like, just pretends they don't exist. The following directories are simply left out:
Attachments included show what I'm talking about with just one account . I did verify that this happened as standard, with every account (one of them actually has legitimate user backups, from dev work in /home/user/backup). Thankfully , I still had the old server handy to restore that data from, but that's not the point here. This should not be necessary.. At all.
I had to do some moving of accounts this weekend (changing providers, all that), and ran through the DA admin backup process. No options were unchecked (all were checked), the process was begun from the administrative panel, as 'admin'. Backups were made to /home/admin/backups, and backups restored on new machine as /home/admin/backups/ .. Should work as designed, and restore the whole account, right? One would logically think so,, right? Yeah, not so much
Even looking at the daily backups made via cron (again, through admin panel), there are discrepencies that need to be resolved. When you say you're going to backup an account, one would actually expect the whole account (as the user has it) to be backed up, not parts of it, not conveniently leaving out what you don't want to back up, but the whole account !
For starters:
Cron jobs ... Not backed up properly . Not a huge deal for a server admin, but again, when you say you're going to back something up, it needs to be done properly.
Now, the account (homedir) itself.... I noticed some size discrepencies from my own backups (.tar.bz2) and yours (.tar.gz) . Total about a gig and a half missing (from 10 accounts), so I did some digging.. What I found was pretty alarming... Directadmin leaves directories out of the home backup for the user. Like, just pretends they don't exist. The following directories are simply left out:
- /home/$user/bin
- /home/$user/backup (really?!?!?!?)
- /home/$user/public_html
- /home/$user/tmp
- more (??)
Attachments included show what I'm talking about with just one account . I did verify that this happened as standard, with every account (one of them actually has legitimate user backups, from dev work in /home/user/backup). Thankfully , I still had the old server handy to restore that data from, but that's not the point here. This should not be necessary.. At all.