Admin Backup/Transfer BETA

pucky

Verified User
Joined
Sep 9, 2006
Messages
768
I was looking at this option and noticed that there is no place to specify and backup to a location such as another hard drive.

Currently the BETA shows the following options.

Local: ~admin/admin_backups/ - Which is ok for some and if you dont have a second hard drive but it is very dangerous to be using this option if your primary dirve takes a poop. I suppose if you only have one drive this is your only option or you can use hte FTP option which is very slow.

Remote DirectAdmin Transfer - Which is ok if you want to spend hours sending your backups elsewhere plus it opens the door for corrupt backup files during a transfer.

Please add this option;

Local: /secondrive/admin_backups/ - Since this is in beta please consider adding an otpion to create backups to an alternate hard drive. I think most people here get two drives in their boxes these days. This would give those of us who have two drives to actually make use of it and gives us better data protection.

Incremental - I would really like to see this option implamented somewhere down the road. Incremental backups using any of the options above. Incrementals are far more efficient for those who want to backup to another dirve then rsync their data to a remote offline storage device as with resync you can specify to only backup files that have changed instead of having to send every .tar.gz files over and over everytime you need to do a backup. And rsync does error checking as well and data encryption and compression which is far more efficient that FTP.

Thank you.
 
I agree; I'd like to see a changeable field for where to write backups.

However you can certainly manage this on a limited basis with a symbolic link.

Jeff
 
I will be adding some sort of field that the admin can set for different paths. It's just set that way for the time being (it's not done yet).

Incremental is a bit tricky (possibly impossible) due to the nature of our bacukp format. Of course "down the road", anything is possible.

John
 
Few bugs in the Admin backup/restore I've found:

1) Does not reset the nameservers records in the DNS...

ie:
Backup users on www2 with NS of ns2a.domain.tld/ns2b.domain.tld

Restore to to www5 and it retains the NS records from www2 instead of getting the proper ones for www5.

2) the TXT record also does not get updated with the IP from the server sites are restored to.
 
And we can expect this when? We've been shunting 5 reseller servers around and would be nice if this was available soon. :)

As it is, we have to restore then go in and do a perl search/replace to fix the *.db files for each restore. :/
 
Back
Top