Backing up

D

Dougy

Verified User
Joined
Sep 1, 2010
Messages
127
Let's say I wanted to rdiff-backup the key directadmin files to an offsite server.

What are the directories I need? Only ones that come to mind are /usr/local/directadmin/conf, /home, /var/lib/mysql, /var/named.. and /directadmin/data

What am I missing?
 
Last edited:
I believe Admin Backup/Transfer was meant to replace the System Backup at least to some degree. After an Admin Backup there is not a whole lot left to backup.
 
I'm not using the system backup feature at all. All user data has been covered by admin backups, config files and certificates I backup myself when I change something.
 
sysbq seems most efficient. Admin backup etc doesn't back up server configs the way sysbq does, or does it?
 
Admin Backup backs up all the user related configuration files such as their apache related and mail related files.

I believe there are very few files other than those that you might want to backup but only if you have made custom changes to them.

Perhaps backup passwd, shadow, group, gshadow since they have system users in them.

Admin Backup has a restore function and System Backup has to be manually restored.
 
The sysbk script was first offered because DirectAdmin, at the time, didn't offer a backup function. It's been well covered in these forums that it doesn't offer a restore function; it's meant for administrators who know what/how to restore.

It's more suited to administrators who want to get as close as they can to a bare-metal restore.

I've restored from sysbk backups many times, but it's never easy, and now we make admin backup/restore backups.

If you don't want to use the Admin Backup/Restore, then you're on the right track.

Jeff
 
jlasman said:
The sysbk script was first offered because DirectAdmin, at the time, didn't offer a backup function. It's been well covered in these forums that it doesn't offer a restore function; it's meant for administrators who know what/how to restore.

It's more suited to administrators who want to get as close as they can to a bare-metal restore.

I've restored from sysbk backups many times, but it's never easy, and now we make admin backup/restore backups.

If you don't want to use the Admin Backup/Restore, then you're on the right track.

Jeff
Click to expand...

I have a 20GB backup account with my friends over at www.bqbackup.com (who are FANTASTIC by the way..) and have ~4GB of usage right now.. so daily or even once a week backups will use all the space. I'd rather incremental :)
 
So there is no 'good way' to do an incremental backup? Gotta script it?
 
You have to script it.

Many of us prefer to not use incremental backups because it makes it hard to find a file to restore, and because restoring an entire website means restoring multiple backups.

That said, I can see why you'd want to do it under some circumstances, especially if you need to keep multiple backups over time and have limited backup space.

Jeff
 
jlasman said:
You have to script it.

Many of us prefer to not use incremental backups because it makes it hard to find a file to restore, and because restoring an entire website means restoring multiple backups.

That said, I can see why you'd want to do it under some circumstances, especially if you need to keep multiple backups over time and have limited backup space.

Jeff
Click to expand...

I am limited on space but it's not just that. Making backups every day or even a few times a week to off site a) uses a lot of cpu resources and b) uses a lot of bandwidth.

I'm just taking backups in case of hdd failure(s), not in case a client is a moron :D
 
You must log in or register to reply here.
Back
Top